Some short time after loading the radeon and drm modules I receive a hard lock of my system. Commenting out 'Load "dri"' in the module section of my xorg.conf resolves the issue. I am aware of some issues with certain r300 chips (I have a 9500pro), but am uncertain as to whether this is related. Output of my lspci, xorg.conf, and Xorg.0.log to follow.
Created attachment 5694 [details] Xorg.0.log
Created attachment 5695 [details] xorg.conf
Created attachment 5696 [details] lspci output
One thing of possible interest is the repeated "(**) RADEON(0): RADEONSaveScreen(2)" in my Xorg.0.log. With the modules loaded these messages fill my log.
First of all, you should get xf86-video-ati 6.5.8 or 6.6.0. Then, which version of the radeon DRM is that? (Check the kernel output after loading the radeon module). There are known issues with versions prior to 1.24 with pretty much anything but pre-9500 cards on 32 bit systems.
I am using gentoo's xf86-video-ati of version 6.6.0 (I've reemerged them just to be sure) and cvs drm with dmesg output: [drm] Initialized radeon 1.24.0 20060225 on minor 0:
I use Radeon 9800 Pro and to have stable DRI I must start X once with fglrx driver, then start it with DRI driver. Without first step system crashes with DRI. (I think this is known issue)
(In reply to comment #6) > I am using gentoo's xf86-video-ati of version 6.6.0 The attached log file clearly shows 6.5.7. Anyway, as Jacek pointed out, this might be the known initialization issue with some cards.
(In reply to comment #8) > (In reply to comment #6) > > I am using gentoo's xf86-video-ati of version 6.6.0 > > The attached log file clearly shows 6.5.7. $ rpm -q xorg-x11-drv-ati xorg-x11-drv-ati-6.6.0-1 $ rpm -Vv xorg-x11-drv-ati ......... /usr/lib64/xorg/modules ......... /usr/lib64/xorg/modules/drivers ......... /usr/lib64/xorg/modules/drivers/ati_drv.so ......... /usr/lib64/xorg/modules/drivers/atimisc_drv.so ......... /usr/lib64/xorg/modules/drivers/r128_drv.so ......... /usr/lib64/xorg/modules/drivers/radeon_drv.so ......... /usr/lib64/xorg/modules/multimedia ......... /usr/lib64/xorg/modules/multimedia/theatre200_drv.so ......... /usr/lib64/xorg/modules/multimedia/theatre_detect_drv.so ......... /usr/lib64/xorg/modules/multimedia/theatre_drv.so ......... /usr/share/hwdata/videoaliases/ati.xinf ......... /usr/share/hwdata/videoaliases/r128.xinf ......... /usr/share/hwdata/videoaliases/radeon.xinf ......... d /usr/share/man/man4/ati.4.gz ......... d /usr/share/man/man4/r128.4.gz ......... d /usr/share/man/man4/radeon.4.gz So, the RPM database finds the same files on the fs it knows installed. But: $ grep "6\.5" /var/log/Xorg.1.log compiled for 7.0.0, module version = 6.5.7 (II) ATI: ATI driver (version 6.5.7) for chipsets: ati, ativga So, the 6.6.0 ATI driver announces itself as 6.5.7.
I stand corrected. Stupid ati wrapper.
(In reply to comment #10) > I stand corrected. Stupid ati wrapper. Is it? $ pwd /home/zozo/cvs/xorg/xf86-video-ati-6.6.0/src $ grep ATI_VERSION ativersion.h ... #define ATI_VERSION_MAJOR 6 #define ATI_VERSION_MINOR 5 #define ATI_VERSION_PATCH 7 configure.ac says 6.6.0. The diff between 6.5.7.3 (this version comes with FC5) and 6.5.8 isn't the same as the diff between 6.5.7.3 and 6.6.0 so I don't think 6.5.7.x was released accidentally as 6.6.0. The ativersion.h version numbers should have been bumped, too.
Is this still an issue?
Unfortunately I cannot test this bug right now. The hard drive died as a result of this issue. I suppose I could reopen the bug, or create a new one when I am able to test. Which ever is the correct procedure?
Test with newer ati driver, we figured out on missing initialization things on r300 card like your one.
Closing due to inactivity. Assumed fixed. Reopen if it's not fixed.
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.