Created attachment 38984 [details] xorg server log I've tried to use the xorg state tracker as a replacement for the xf86-video-ati driver. The server fails to start with the following error message: "LoadModule: Module radeon does not have a radeonModuleData data object."
I am getting the same when building mesa with r600 gallium, with the autogen command - --enable-debug --disable-egl --enable-gallium-r600 --enable-gallium-swrast --with-dri-drivers=r600,swrast My radeon_drv.so gets overwritten so that the next startx fails with the error as reported.
Either the binary needs to be renamed to radeong_drv.so, or the references to 'radeong' in src/gallium/targets/xorg-radeon/radeon_xorg.c need to be changed to 'radeon'.
Created attachment 38991 [details] [review] replaces 'radeong' in src/gallium/targets/xorg-radeon/radeon_xorg.c with 'radeon' Thank you! I changed the references in radeon_xorg.c like you said.
Forgot to mention: After replacing 'radeong' with 'radeon' xorg server was starting and I was able to log into KDE. Looks fine so far.
So it's fixed ?
(In reply to comment #5) > So it's fixed ? It's been a while since I was playing with the Xorg state tracker. It did work when I booted into the graphical mode using the xf86-video-ati driver, then quit the xserver and restarting the xserver with the Xorg state tracker. It didn't work after a reboot of the system. There is a little bit more information in this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=30406
(In reply to comment #6) > (In reply to comment #5) > > So it's fixed ? > > It's been a while since I was playing with the Xorg state tracker. It did work > when I booted into the graphical mode using the xf86-video-ati driver, then > quit the xserver and restarting the xserver with the Xorg state tracker. It > didn't work after a reboot of the system. > > There is a little bit more information in this bug report: > https://bugs.freedesktop.org/show_bug.cgi?id=30406 If it is still broken: Could you please attach a full log of a failed Xorg start with the state tracker enabled. cu, Knut
Hello Knut, thanks for looking into the problem. I did try to make a package with the xorg driver but xorg doesn't start. I don't know what the exact problem is though. Could you have a look at my build file which I use to build my packages if I have some configuration problem? Greetings Martin
Created attachment 51779 [details] log file for xorg server
Created attachment 51780 [details] Build script used to create mesa package
Created attachment 51815 [details] Screenshot of Firefox when 2d acceleration is disabled
Created attachment 51816 [details] Screenshot of Firefox when 2d acceleration is enabled
Created attachment 51817 [details] Configuration for r600 card
Created attachment 51818 [details] Xorg configuration for r300 card
Created attachment 51819 [details] Xorg log file for r300 card when 2d acceleration is disabled
Created attachment 51820 [details] Xorg log file for r300 card when 2d acceleration is enabled
Created attachment 51821 [details] Xorg log file for r600 card when 2d acceleration is disabled
Hello, I've found the problem why it didn't work. I didn't know that the entry funtion (or whatever it is called) has to have the same name as the driver. After creating a xorg.conf file I was able to successfully start the Xorg server. It's working great on my two systems (no problems after rebooting the system). One system has a r500 type card installed and the other system has a r600 type card installed. When I enable 2d acceleration in xorg.conf I get screen corruptions though (see attached screenshots of Firefox). There is an error/info message in the Xorg log file: "[ 2724.965] (II) r300(0): xorg_composite_accelerated fallback Component alpha not supported with source alpha and source value blending. (op=3)" This message is the same for both cards. Best regards Martin
The bug reported here is fixed. Current Mesa Git produces lib/gallium/r300_drv.so which can be loaded with Driver "r300". (In reply to comment #18) > When I enable 2d acceleration in xorg.conf I get screen corruptions though (see > attached screenshots of Firefox). That's not related to the original problem and needs to be tracked separately. > There is an error/info message in the Xorg log file: > "[ 2724.965] (II) r300(0): xorg_composite_accelerated fallback Component alpha > not supported with source alpha and source value blending. (op=3)" That's not related. If you don't want to get these debugging messages, use Option "DebugFallback" "off".
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.