Bug 810662

Summary: software rendering by default on HD 5770 despite Xorg.0.log claiming otherwise
Product: [Fedora] Fedora Reporter: Stijn Hoop <stijn>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: ajax
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-09 19:36:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg.0.log
none
glxinfo
none
env LIBGL_DEBUG=verbose glxinfo |& tee glxinfo-debug.out none

Description Stijn Hoop 2012-04-07 21:18:30 UTC
Created attachment 575969 [details]
Xorg.0.log

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
mesa-dri-drivers-8.0.2-2.fc17.x86_64
xorg-x11-drv-ati-6.14.4-2.20120329gitde2419e55.fc17.x86_64

Comment 1 Stijn Hoop 2012-04-07 21:18:58 UTC
Created attachment 575970 [details]
glxinfo

Comment 2 Adam Jackson 2012-04-09 17:31:14 UTC
Please attach the output from:

$ LIBGL_DEBUG=verbose glxinfo

Comment 3 Stijn Hoop 2012-04-09 18:59:32 UTC
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?

Comment 4 Stijn Hoop 2012-04-09 19:08:53 UTC
OK, some Googling cleared that up:

$ ls -l /dev/dri 
total 0K
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

<logout/login>

$ 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?

Comment 5 Stijn Hoop 2012-04-09 19:36:40 UTC
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.