Red Hat Bugzilla – Bug 810662
software rendering by default on HD 5770 despite Xorg.0.log claiming otherwise
Last modified: 2012-04-09 15:36:40 EDT
Created attachment 575969 [details]
Description of problem:
After a yum upgrade (!) of F16 to F17 from today (2012-04-07) gnome-shell started using excessive CPU time (150% of my quadcore AMD while moving a window).
I suspected software rendering was enabled so I tried to verify using Xorg.0.log and glxinfo. However I get conflicting information: glxinfo says that I'm running "Gallium 0.4 on llvmpipe", with "vmware" as the vendor. However this is most assuredly a physical box. Xorg.0.log claims that DRI is provided by r600. Please find both glxinfo as well as Xorg.0.log attached.
I tried to force r600 DRI by moving both /usr/lib64/dri/swrast_dri.so and /usr/lib64/dri/vmwgfx_dri.so out of the way but without those libraries GDM could not show a login window. Interestingly X did appear to start and I could move the mouse, but that was it.
[stijn@tangaloor] <~> rpm -q mesa-dri-drivers xorg-x11-drv-ati
Created attachment 575970 [details]
Please attach the output from:
$ LIBGL_DEBUG=verbose glxinfo
Created attachment 576284 [details]
env LIBGL_DEBUG=verbose glxinfo |& tee glxinfo-debug.out
Not sure whether this is what you mean but the error output is interesting. Where is my drm device and how can I check the permissions?
OK, some Googling cleared that up:
$ ls -l /dev/dri
crw-rw----. 1 root video 226, 0 Apr 9 20:55 card0
crw-------. 1 root video 226, 64 Apr 9 20:55 controlD64
$ sudo usermod -a -G video stijn
$ glxinfo | grep -i renderer
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER
Not entirely sure why I needed to add myself though, but it's not mesa at fault. I'll go poke at stuff like ConsoleKit I guess?
Booting a Live USB results in the correct behaviour from the start. Closing this as it seems most likely that my yum upgrade botched something and I doubt it's worth the time to track this down. I'll simply reinstall from Beta RC3.