Kernel Bug Tracker – Bug 14274
radeon KMS unusable on RadeonHD 3650
Last modified: 2012-06-14 16:40:26 UTC
Having KMS enabled just gives me a blank screen, be it X or console. My hardware is a T500 ThinkPad running Debian Sid (radeonhd 1.2.5, X.org core 1.6.4). It's running fine without KMS.
Created attachment 23293 [details]
relevant dmesg from -rc3
Created attachment 23294 [details]
relevant Xorg.log fragments
What kernel version are you running? You need to load fbcon to get a framebuffer console with kms. Radeonhd does not have support for kms. You need to use radeon (xf86-video-ati) to use X with kms.
It's 2.6.32-rc3. I've tried radeon and it doesn't work either (I get a blank screen instead of the GDM login). Please see the Xorg and kernel logs that I've attached.
Created attachment 23321 [details]
dmesg from -rc3 with radeon
Created attachment 23322 [details]
Xorg log (using radeon)
The radeon driver you are using is too old or not compiled with KMS support see :
I've compiled both the radeon driver and libdrm from the master branches. It still won't work. With -rc3, I get strage dotted lines (thin & vertical) instead of the GDM login window. The fb console works properly.
Created attachment 23351 [details]
-rc3 dmesg, radeon as module
Created attachment 23352 [details]
-rc3 xorg log, radeon as module
Again your ddx (xf86-video-radeon) is not compiled with kernel modesetting enabled. Make sure you build libdrm with --enable-radeon-experimental-api and that the ddx compilation use these libdrm and not one installed somewhere on the system, then check that Xorg use the proper ddx. Yet the easier way to test KMS is to use a distribution which handle that for you, so far only fedora does (to the best of my knowledge).
It "works" now (I can log on into GDM), but it's still unusable: the image freezes or the screen gets black after more ore less one minute. Yes, libdrm is configured with the experimental API and --prefix=/usr, so it's the only one the ddx can use. Same way, the ddx is configured with --prefix=/usr. I'm using .32-rc4 and xserver-xorg-core 1.6.5.
please attach your dmesg and xorg log.
Created attachment 23423 [details]
-rc4 dmesg, radeon built-in
Created attachment 23424 [details]
-rc4 xorg log, radeon built-in
Again your ddx is not built with KMS support. Rebuild drm with :
./autogen.sh --prefix=/usr --libdir=/usr/lib64
Then rebuild ddx with :
./autogen.sh --prefix=/usr (attach output of this command to the bug)
Created attachment 23428 [details]
-rc5 dmesg, radeon built-in
Created attachment 23429 [details]
-rc5 xorg log, radeon built-in
Created attachment 23430 [details]
autogen output for ddx
I did exactly as instructed but it still has the same behaviour. I added --enable-radeon-experimental-api to the autogen command.
Ok so now ddx is kms enabled, can you confirm that booting in init 3 doesn't give you a console ? Please also attach an Xorg log of radeon with kms disabled.
Created attachment 23431 [details]
-rc5 xorg log, radeon built-in, KMS disabled
On Debian, init 3 is identical to 2,4 and 5: graphical login. Booting
the normal way and stopping X ASAP gives me a stable console with the
I wonder if it's an Xserver issue can you try with fedora 12 live cd:
Created attachment 23473 [details]
fedora 12 dmesg
Created attachment 23474 [details]
fedora 12 xorg log
I can confirm the same behavour on my Lenovo W500
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650
upon logging in with kdm, get a lockup. Using 2.6.32-rc4 + drm-next even, nightly mesa snapshot and DDX.
Is this still seen with modern kernels ?
None, been using Composite Window managers for awhile now and no issues related to this. Please close.