Description of problem: When KMS is enabled with radeon.modeset=1 bootup hangs when plymouth starts up. Non-KMS startup works OK. Version-Release number of selected component (if applicable): kernel-2.6.29.1-35.rc1.fc11.i586 xorg-x11-drv-ati-6.12.1-2.fc11.i586 libdrm-2.4.5-3.fc11.i586 mesa-libGL-7.5-0.6.fc11.i586 How reproducible: always Additional info: Smolt profile attached as URL.
I reproduced this on my system as well. http://www.smolts.org/show?uuid=pub_dd3d0c48-9a13-4ecd-a8a7-70b3de694bf2
Sorry, forgot to mention: connected to Samsung DLP TV with HDMI. It's a VDR, so there is no other monitor :-)
Mine is on a Philips 170S LCD, connected via VGA.
Created attachment 337535 [details] X Log file from default boot (modesetting disabled)
It also hangs on RV730 and RV770 when doing the modesetting, but did Dave post anywhere KMS was functional on R600+ ? Personally, I don't think so.
According to the basic test case instructions: If you have an r600 or r700 chipset card (Radeon HD 2xxx, HD 3xxx or HD 4xxx), add radeon.modeset=1 as a kernel parameter: in the live CD, hit any key when the 'automatic boot in X seconds' prompt appears, then hit tab to edit boot options I tried this with the live CD and the kernel complained that it didn't understand the radeon.modeset option. The screen then went blank and I eventually rebooted the system. If I don't provide the radeon.modeset option, then it will boot up in text mode and then start X successfully. I will test it with a rawhide install next. My smolt profile: http://www.smolts.org/client/show/pub_d0215872-38fe-4625-8f82-ced21a8e012f
Created attachment 337672 [details] Requested dmesg from loading radeon with modeset=1
Created attachment 337673 [details] Requested lspci -nn output
ATI 3650 shows a blankscreen when radeon.modeset=1 is used, without this everything is fine.
*** Bug 493388 has been marked as a duplicate of this bug. ***
Created attachment 337884 [details] Xorg.0.log without modesetting
Also have a blank screen when radeon.modeset=1 is used. lspci -nn: 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics] [1002:9612]
Thanks for the logs and information, switching severity to high because of crash, keeping priority low because we have a workaround. Switching to ASSIGNED. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 338096 [details] dmesg.log from radeon crash on HD3200 You probably have this information already, but I thought I add the log from my system too: boot with nomodeset 3 modprobe -r radeon drm modprobe drm debug=1 modprobe radeon modeset=1
kevin dekorte, can you file a separate bug? KMS failures on different chipsets don't necessarily have the same cause, so we need separate reports for each failing chipset. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 Radeon Test Day: KMS works now on this HW. I doubt this will ever be fixed for F11, because it still uses the old radeon code base.