[Bug 28440] New: Linux kernel 2.6.34's KMS crashes and disables GPU acceleration with X1250.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
Summary: Linux kernel 2.6.34's KMS crashes and disables GPU acceleration with X1250. Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: coomasiehead@yahoo.com
Created an attachment (id=36138) --> (https://bugs.freedesktop.org/attachment.cgi?id=36138) 2.6.34 kernel's KMS doesn't support X1250 well.
OS: Slackware64 13.1 Kernel : 2.6.34-smp(It's not included in slackware. I compiled myself) I told kernel to enable KMS automatically and compiled the kernel. While I boot 2.6.34-smp, I see a fuzzy brown rectangle in the right side of my screen for about half a second.
dmesg tells me GPU acceleration is disabled, and I can't use compiz. I included dmesg.txt.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
--- Comment #1 from Jerome Glisse glisse@freedesktop.org 2010-06-08 04:14:28 PDT --- Try booting with radeon.dynpm=0 and attach new dmesg.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
Jerome Glisse glisse@freedesktop.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NOTOURBUG
--- Comment #2 from Jerome Glisse glisse@freedesktop.org 2010-06-08 04:45:48 PDT --- Was boot parameter closing.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
coomasiehead@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |FIXED
--- Comment #3 from coomasiehead@yahoo.com 2010-06-08 05:11:53 PDT --- It was "vga=791" that crashed KMS, and after I replaced it with video=1024x768, everything went fine.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
--- Comment #4 from Marcin Slusarz marcin.slusarz@gmail.com 2010-06-08 09:10:50 PDT --- If disabling vesafb fixes your problem, it means vesafb->radeon handoff does not work properly. I fixed similar issue in nouveau code and I can prepare a patch for radeon. Are you willing to test it?
https://bugs.freedesktop.org/show_bug.cgi?id=28440
coomasiehead@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |
--- Comment #5 from coomasiehead@yahoo.com 2010-06-08 22:23:53 PDT --- If you prepare it, sure. I am willing to test it although it takes about 15~20 minutes to recompile a kernel.
Why don't you use KMS from the beginning? I included radeon in initrd, but radeon in initrd complains like the below. [ 4.227541] platform radeon_cp.0: firmware: requesting radeon/RS600_cp.bin [ 64.227150] [drm:r100_cp_init] *ERROR* Failed to load firmware! [ 64.227295] radeon 0000:01:05.0: Disabling GPU acceleration You saw it right. Initrd tried for a while to load the firmware and had it display a black screen until it failed to load the firmware. I thought the kernel was in a panic.
Unless I know how to have initrd recognize or include the firmware, compiling radeon into kernel is the only solution for making KMS appear so early. However, recompiling kernel each time I compile radeon would be a waste of time, which emphasizes the importance of including radeon with the right firmware in initrd.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
--- Comment #6 from coomasiehead@yahoo.com 2010-06-08 22:26:15 PDT --- No.... vesafb was not likely a problem. I specified vga=791 as a global option in /etc/lilo.conf, and it caused the problem. After I replaced vga=791 with video=800x600, KMS started working again.
Whether vesafb handles the control over to KMS well should be tested since I didn't test it.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
--- Comment #7 from Marcin Slusarz marcin.slusarz@gmail.com 2010-06-09 08:07:20 PDT --- I'm confused. You seem to respond to some questions I didn't ask... vga=791 enables vesafb, but you claim you didn't test it...
https://bugs.freedesktop.org/show_bug.cgi?id=28440
--- Comment #8 from coomasiehead@yahoo.com 2010-06-09 18:08:09 PDT --- Sorry for my bad language plus sleep deprivation. The original configuration was vesafb & DRM & radeon & KMS compiled into the kernel with vga=791 in /etc/lilo.conf. When it generated error, I removed vesafb from the kernel, recompiled the kernel, replaced vga=791 with video=800x600 in /etc/lilo.conf, and rebooted. Thus, I only tested if vga=791 crashes KMS, but I couldn't test if vesafb handles the control over to KMS smoothly with or without video=800x600 in /etc/lilo.conf. But I guess vesafb(or uvesafb) and KMS can live together if vesafb has no problem with video=800x600.
I pasted dmesg. http://pastebin.org/322359 Beware this paste will be expired after a month from now.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
--- Comment #9 from Marcin Slusarz marcin.slusarz@gmail.com 2010-06-10 12:51:28 PDT --- So there was no bug - just a problem with missing firmware? If yes, please close the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=28440
coomasiehead@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |NOTABUG
--- Comment #10 from coomasiehead@yahoo.com 2010-06-10 16:58:21 PDT --- This is not a bug although the missing firmware is another bug. This bug is closed.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org