<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Radeon 9600 r300] Xorg fails with radeonfb and KMS" href="https://bugs.freedesktop.org/show_bug.cgi?id=89808#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Radeon 9600 r300] Xorg fails with radeonfb and KMS" href="https://bugs.freedesktop.org/show_bug.cgi?id=89808">bug 89808</a> from <a class="email" href="mailto:chris.bainbridge@gmail.com" title="Chris Bainbridge <chris.bainbridge@gmail.com>"> Chris Bainbridge</a> <pre>I retested and it isn't an actual hang. It is this issue: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762047">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762047</a> (not sure why I saw some kind of pink corrupt image before, but now it is just black). When both radeonfb and KMS are in the kernel, lightdm will boot to a black screen. As you said in the Debian bug, this can be worked around by forcing X to another colour depth (/etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -depth 24) - If KMS is now preferred, would it be more useful to default to using it rather than have to manually specify 'video=radeonfb:off' ? - With radeonfb and KMS, dmesg shows: [ 4.292750] [drm] Initialized drm 1.1.0 20060810 [ 4.292866] [drm] radeon kernel modesetting enabled. This is confusing given that KMS isn't enabled. It would be more informative to print a warning like "KMS disabled because you have radeonfb enabled". - Is there any point in having CONFIG_FB_RADEON on a modern kernel? If not, it would be informative if the kernel config for CONFIG_FB_RADEON stated that it was deprecated, and enabling it will cause KMS to be disabled. It isn't obvious that it isn't desirable to enable that config option, or that enabling it will cause KMS to be disabled by default.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>