http://bugzilla.novell.com/show_bug.cgi?id=595655 http://bugzilla.novell.com/show_bug.cgi?id=595655#c0 Summary: Radeon X600 Mobility does not work with KMS Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: robin.knapp@ts.fujitsu.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 I've tested Live CD/USB Build 553 (M5) on a notebook with a Radeon X600 Mobility. The radeon module does not get loaded automatically during boot (see Bug 595653), but if I boot into runlevel 3 and modprobe radeon manually, KMS gets activated (switches automatically to native LCD resolution). If I start X after loading the module, the screen first gets corrupted (looks like some random memory content), and a few seconds later I see the KDE splash screen. So in general this works, but it is painfully slow and the GPU fan turns up. After a while, GPU reset messages are shown on the console: [ 124.160085] [drm:radeon_fence_wait] *ERROR* fence(f6a14e60:0x00000005) 508ms timeout going to reset GPU [ 124.161490] [drm] CP reset succeed (RBBM_STATUS=0x00000140) [ 124.161496] [drm] radeon: cp idle (0x10000000) [ 124.161532] [drm] radeon: ring at 0x00000000B0000000 [ 124.161557] [drm] ring test succeeded in 0 usecs [ 124.161563] [drm] GPU reset succeed (RBBM_STATUS=0x00000140) [ 124.161571] [drm:radeon_fence_wait] *ERROR* fence(f6a14e60:0x00000005) 516ms timeout [ 124.161577] [drm:radeon_fence_wait] *ERROR* last signaled fence(0x00000005) See attachment 353616 of bug 574749 for full dmesg output Reproducible: Always Steps to Reproduce: 1. boot live cd/usb into runlevel 3 on notebook with X600 Mobility 2. modprobe radeon 3. init 5 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.