hardware acceleration on jessie/sid #704
Comments
|
Can you try the branch in #646 and see if it fixes things? |
|
No, still running on software acceleration with this branch. |
|
@feeddageek what does the following give you? For now it only works for vendor However I doubt this patch will do you any good. As you pointed out |
(that's from my usual chroot, not the divix118 one) On sid (and jessie/saucy/trusty) it uses the software renderer. But adding the following file in |
|
I'm not sure when Parrot will move to 3.8 (if ever), so we're probably going to need to support pinning mesa to older versions that don't require it when we detect the 3.4 kernel. |
|
@feeddageek what did you do to rollback the mesa drivers specifically? |
|
@peter-gulka : Do not update your chroot after running this (some packages may get upgraded again: some pinning is necessary, I'll work on it if this works). Please report if 3D apps actually work (as a start, try |
|
We've got some errors here and also I'm an idiot and don;t know how to add markup to format this stuff (trusty)peter@localhost: (Reading database ... 83137 files and directories currently installed.) dpkg: error processing package libgles2-mesa:amd64 (--install): dpkg: error processing package libegl1-mesa-drivers:amd64 (--install): |
|
and yet, when I rebooted, the problem went away. Minecraft works now :) very curious... |
@drinkcat ⭐ - You're the MAN! 👏That fixed my blank/black gnome DE with a white X cursor AND it fixed my xbmc DE that was complaining that it needed 'hardware accelerated OpenGL rendering'. My 'trusty' chroot and all of my targets (gnome,kde,xfce,xbmc) are working at 100% now -Yay! Thanx very much - again, |
|
more info - we've got some conflicts. My taskbar disappeared - the top-right controls. If I try to reinstall the indicator app, I get these errors: (trusty)peter@localhost: |
Well, we should also update the 32-bit mesa packages, I'll think about how to fix that in a nice way.
See https://help.github.com/articles/github-flavored-markdown#fenced-code-blocks
I guess I should have told you to backup your chroot before running these commands, sorry... You should be able to recover your chroot with a combination of
That's awesome, thanks. |
|
@peter-gulka : Once you have recovered your install, can you try the following improved instructions? That should pull in 32-bit libraries as well and fix your issue. Also, do you happen to know what package requires 32-bit OpenGL libraries? Maybe Steam? Create Create Then run: |
|
OK - more feedback:
I created a fresh chroot with trusty/lxde instead of unity and tried the original instructions again and it appears to have worked fine. No error messages during the install of the I'll back up this fresh LXDE install, and restore the Unity install w/ Steam later today and try the revised instructions. |
|
Create This isn't working - it claims |
|
@peter-gulka - You'll probably need to run |
I believe it shoud be |
|
yessir - Both scripts ran fine with no errors. Upon reboot everything is running lickity-split. I was successfully able to install So what is the process from this point? Should I still avoid updating this chroot? |
My configuration is probably too complex with gnome,kde,xfce, & xbmc installed together. I'm not sure if there is a solution to my problem or not so I'll just avoid upgrading via crouton or apt-get for the time being. Thanx for all your help and insight, |
|
UPDATE: My kde DE was broken but I discovered that the @drinkcat 'pinning' fix files (
[ Note to self: heed warnings about updates... ] |
|
Thank you both for testing. There is indeed a problem with kde ( |
|
You're very welcome; I'm hoping Google will soon move on from 3.4.0... |
|
Older devices on 3.4.0 will, unfortunately, remain there. |
|
@dnschneid , Thanx for the info., I hadn't seen that before.
My Acer C710 is barely a year old so it's a little disconcerting that it's already an 'older device'... On a brighter note, I'll bet your'e excited about Google I/O :-) |
|
As far as Chromium OS is concerned, you'll be getting updates and improvements for a long time...just not a fresh kernel for crouton to use. |
|
That's good to know too. On Tue, Jun 24, 2014 at 1:16 PM, David Schneider [email protected]
DennyL@GMail |
|
Please find an updated version here: https://gist.github.com/drinkcat/4376b28383c324fd42ab . Its a custom target file now, you can install it by running: It should be safe to upgrade crouton after that (even without the custom target file), please test that too. This solution is a bit of a monster though... Solving the kde problem was not easy. I create a fake @DennisLfromGA: Can you test if kde is still working? (and using hardware acceleration? Not sure how to test that actually). Thanks! UPDATE: I just updated the gist. Found a solution that does not require a local repo, I need to use |
|
Slick! |
|
@drinkcat ( or @dnschneid if available ) I just tested all of my targets in my 'trusty' chroot, namely gnome, kde, xfce, & xbmc and they all worked so I backed it up in preparation for this test. Sorry but I have just a couple of questions before I get started -
As soon as I get this clarified I'll start but I didn't want to test it with a chroot in a state that wouldn't provide a good test. Sorry to ask so many questions and thanx for the work on this, |
Yep that's it, exactly. Also, after the last step, do a normal update Thanks! |
On saucy onwards, if kernel version is 3.4, manually pin down old mesa libraries from precise, as new ones require version >=3.6. Fixes dnschneid#704.
|
@DennisLfromGA : If you haven't started testing yet, please hold for a while. I'm going to integrate the fix to couton and put together a Pull Request tomorrow, so it would be better to test that. |
|
@drinkcat - I was going to get to it today but I'll hold for awhile until it's merged or another avenue is defined. Thanx for letting me know, |
On saucy onwards, if kernel version is 3.4, manually pin down old mesa libraries from precise (mesa 8), as new ones (mesa >=9) require kernel >=3.6. Fixes dnschneid#704.
On saucy onwards, if kernel version is 3.4, manually pin down old mesa libraries from precise (mesa 8), as new ones (mesa >=9) require kernel >=3.6. Fixes dnschneid#704.
On saucy onwards, if kernel version is 3.4, manually pin down old mesa libraries from precise (mesa 8), as new ones (mesa >=9) require kernel >=3.6. Fixes dnschneid#704.
On saucy onwards, if kernel version is 3.4, manually pin down old mesa libraries from precise (mesa 8), as new ones (mesa >=9) require kernel >=3.6. Fixes dnschneid#704.
|
FYI, started writing this page: And this issue is not really closed yet (we probably want to include the fix for |
|
Quick update - the pull in #913 worked for me on my Acer C710. On Wed, Jul 9, 2014 at 2:32 AM, David Schneider [email protected]
|
dnschneid
changed the title
I had no hardware acceleration on my Acer C7 when using the following release
saucy,trusty,jessieandsid.There are two lines in the logs that attract my attention
setversion 1.4 failed: Permission deniedWhich I have no idea of what it mean (if someone can, please enlighten me)
and
Gen6+ requires Kernel 3.6 or later.I still don't know exactly what Gen6+ is, but it seems to be some kind of name for the intel dri
Since my chrome os kernel is 3.4, I downgrader libgl1-mesa-dri to the wheezy version and it seems to work for now (I only tested this fix on sid, but it must work the same on other releases).
I don't know if downgrading mesa is a clean enough fix to be included, but that did it for me.
The text was updated successfully, but these errors were encountered: