[Bug 89808] [Radeon 9600 r300] Xorg fails with radeonfb and KMS

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Mar 30 07:31:19 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=89808

--- Comment #3 from Chris Bainbridge <chris.bainbridge at gmail.com> ---
I retested and it isn't an actual hang. It is this issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762047 (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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150330/9f38f09f/attachment.html>


More information about the dri-devel mailing list