Created attachment 30430 [details] Xorg.0.log when booting. When booting, after KMS takes over, there is no text console available. The screen is blank until X starts. When trying to switch to a console, the color goes "inverse" until switched back. This is with the 2.6.32-rc4 kernel and the 2.9.0 version of the Intel driver. Xorg.0.log is attached.
Do you enable CONFIG_FRAMEBUFFER_CONSOLE? If not, that's bug#24208.
Yes, I have, I've attached my kernel .config now as well.
Created attachment 30434 [details] My kernel .config file
Info now provided.
I also just read Greg mentioned fbcon is enabled in mailing list. So it's a different issue. Let Jesse to handle. I guess dmesg output (with drm.debug=0x06) will be needed.
Yeah your dmesg with debug=0x06 could help here. It's strange that X comes up fine but fbcon doesn't...
Ping, Greg can you attach your dmesg from a fresh booth with the drm debug param set to 6? Ideally with Eric's drm-intel-next branch from his drm-intel.git tree on kernel.org.
Created attachment 31785 [details] dmesg with drm_debug=9 Here's the boot log for 2.6.31.10-rc1. Note the long timeout delay of the i2c reading, could that be the problem (look at the end of the file) If you need me to boot any other kernel version, please let me know.
(In reply to comment #8) > Created an attachment (id=31785) [details] > dmesg with drm_debug=9 Oops, I did it with =9, should I reboot with it at 6? Can't hurt I guess...
Created attachment 31786 [details] drm_debug=6 Here's with drm_debug=6. And the kernel version is 2.6.31.7-rc1, too many different kernel versions floating around here, sorry.
Hi, Greg Can you try the 2.6.33 kernel and attach the output of dmesg with the boot option of "drm.debug=0x4"? Thanks.
This hardware is now dead, so don't really worry about this bug. I don't use the machine anymore, so don't waste any time on it.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.