Bug 14274

Summary: radeon KMS unusable on RadeonHD 3650
Product: Drivers Reporter: Mircea Gherzan (mgherzan)
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: CLOSED CODE_FIX    
Severity: normal CC: alan, alexdeucher, glisse, shawn.starr
Priority: P1    
Hardware: x86-64   
OS: Linux   
Kernel Version: 2.6.32-rc1 Subsystem:
Regression: No Bisected commit-id:
Attachments: relevant dmesg from -rc3
relevant Xorg.log fragments
dmesg from -rc3 with radeon
Xorg log (using radeon)
-rc3 dmesg, radeon as module
-rc3 xorg log, radeon as module
-rc4 dmesg, radeon built-in
-rc4 xorg log, radeon built-in
-rc5 dmesg, radeon built-in
-rc5 xorg log, radeon built-in
autogen output for ddx
-rc5 xorg log, radeon built-in, KMS disabled
fedora 12 dmesg
fedora 12 xorg log

Description Mircea Gherzan 2009-09-30 07:49:55 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.
Comment 1 Mircea Gherzan 2009-10-06 23:59:58 UTC
Created attachment 23293 [details]
relevant dmesg from -rc3
Comment 2 Mircea Gherzan 2009-10-07 00:00:49 UTC
Created attachment 23294 [details]
relevant Xorg.log fragments
Comment 3 Alex Deucher 2009-10-07 01:32:11 UTC
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.
Comment 4 Mircea Gherzan 2009-10-09 23:03:50 UTC
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.
Comment 5 Mircea Gherzan 2009-10-09 23:05:47 UTC
Created attachment 23321 [details]
dmesg from -rc3 with radeon
Comment 6 Mircea Gherzan 2009-10-09 23:06:29 UTC
Created attachment 23322 [details]
Xorg log (using radeon)
Comment 7 Jérôme Glisse 2009-10-10 09:35:46 UTC
The radeon driver you are using is too old or not compiled with KMS support see :

http://wiki.x.org/wiki/radeonBuildHowTo
Comment 8 Mircea Gherzan 2009-10-12 01:45:11 UTC
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.
Comment 9 Mircea Gherzan 2009-10-12 01:45:56 UTC
Created attachment 23351 [details]
-rc3 dmesg, radeon as module
Comment 10 Mircea Gherzan 2009-10-12 01:47:05 UTC
Created attachment 23352 [details]
-rc3 xorg log, radeon as module
Comment 11 Jérôme Glisse 2009-10-12 08:39:03 UTC
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).
Comment 12 Mircea Gherzan 2009-10-15 10:33:13 UTC
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.
Comment 13 Alex Deucher 2009-10-15 14:30:52 UTC
please attach your dmesg and xorg log.
Comment 14 Mircea Gherzan 2009-10-16 02:39:30 UTC
Created attachment 23423 [details]
-rc4 dmesg, radeon built-in
Comment 15 Mircea Gherzan 2009-10-16 02:41:22 UTC
Created attachment 23424 [details]
-rc4 xorg log, radeon built-in
Comment 16 Jérôme Glisse 2009-10-16 09:22:34 UTC
Again your ddx is not built with KMS support. Rebuild drm with :
./autogen.sh --prefix=/usr --libdir=/usr/lib64
make
make install

Then rebuild ddx with :
./autogen.sh --prefix=/usr  (attach output of this command to the bug)
make
make install
Comment 17 Mircea Gherzan 2009-10-16 12:39:16 UTC
Created attachment 23428 [details]
-rc5 dmesg, radeon built-in
Comment 18 Mircea Gherzan 2009-10-16 12:39:54 UTC
Created attachment 23429 [details]
-rc5 xorg log, radeon built-in
Comment 19 Mircea Gherzan 2009-10-16 12:43:59 UTC
Created attachment 23430 [details]
autogen output for ddx
Comment 20 Mircea Gherzan 2009-10-16 12:45:24 UTC
I did exactly as instructed but it still has the same behaviour. I added --enable-radeon-experimental-api to the autogen command.
Comment 21 Jérôme Glisse 2009-10-16 12:57:20 UTC
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.
Comment 22 Mircea Gherzan 2009-10-16 13:02:32 UTC
Created attachment 23431 [details]
-rc5 xorg log, radeon built-in, KMS disabled
Comment 23 Mircea Gherzan 2009-10-16 17:02:56 UTC
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
right resolution.
Comment 24 Jérôme Glisse 2009-10-19 20:15:50 UTC
I wonder if it's an Xserver issue can you try with fedora 12 live cd:

http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/
Comment 25 Mircea Gherzan 2009-10-20 01:54:23 UTC
Created attachment 23473 [details]
fedora 12 dmesg
Comment 26 Mircea Gherzan 2009-10-20 01:54:50 UTC
Created attachment 23474 [details]
fedora 12 xorg log
Comment 27 Shawn Starr 2009-10-25 03:20:04 UTC
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.
Comment 28 Alan 2012-06-13 18:53:04 UTC
Is this still seen with modern kernels ?
Comment 29 Shawn Starr 2012-06-13 21:49:02 UTC
None, been using Composite Window managers for awhile now and no issues related to this. Please close.