Created attachment 36138 [details]
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.
Try booting with radeon.dynpm=0 and attach new dmesg.
Was boot parameter closing.
It was "vga=791" that crashed KMS, and after I replaced it with video=1024x768, everything went fine.
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?
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.
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.
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...
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.
So there was no bug - just a problem with missing firmware?
If yes, please close the bug.
This is not a bug although the missing firmware is another bug.
This bug is closed.