Created attachment 30117 [details] X-log when starting up with DRI enabled When enabling DRI in xorg.conf login screen fails to show up buttons and some texts. Logging in is still possible and gnome logs in correctly except that the gdm login screen does not get replaced by desktop, but stays unchanged. Because the mouse works all the time, I can see the cursor changing and I can manipulate the invisible windows and even type some text inside the gnome-terminal which starts up automatically. Mouse cursor reacts correctly to everything, but I cannot get the screen to update. With DRI off and EXA on my desktop works as it should. My graphics card is HD 2600Pro AGP with dual DVI and tv-out. I'm running stable gentoo with: kernel: 2.6.32_rc3 xorg-server: 1.6.4 radeonhd: 1.2.5 mesa and libdrm from git.
Created attachment 30118 [details] X-log when starting up with DRI disabled This works, but is slow.
Created attachment 30119 [details] xorg.conf in use. I just comment/uncomment the DRI-section.
Created attachment 30120 [details] emerge --info This describes the state of my current system from development point of view.
I'm continuously updating the git packages for better use. I might be able to take the screenshots from the unchanging gdm-login screen after logging in if requested.
Added info about hardware.
Created attachment 30121 [details] glxinfo when running without DRI
The root problem was and still is the AGP-bus. By forcing BusType to PCIE I get working DRI2 and KMS.
(In reply to comment #7) > The root problem was and still is the AGP-bus. By forcing BusType to PCIE I get > working DRI2 and KMS. > radeonhd does not support KMS; you need to use radeon (xf86-video-ati). Also, the xorg.conf BusType option is not relevant for KMS (or radeonhd). For KMS, you need to load the radeon drm with agpmode=-1.
This was caused by problems with AGP and the situation was solved by adding radeon.agpmode=-1 as kernel boot option. This can be closed now.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.