Created attachment 22171 [details] xorg.conf Host: q45 Arch: x86_64 OSD: Fedora release 9 (Sulphur) Kernel: 2.6.29-rc2 Libdrm: (master) 27fae006853647ad0087067adc4eaa8d4ed4594a Mesa: (master) 65118a51b609cbcfdd6698a8e22c18e98152f362 Xorg: 7.2 Xserver: (master) 0d3c3dad21857ef502fe0d0235620a1228248e13 Xf86_video_intel: (master) b6f3ce32e295929f461a7bc37e61f126fb51e4aa Kernel: (drm-intel-next) f2515ef1ce257b842b19e5b5f5c077dcdbf0f22c Bug Description: --------------------- I built kenel in drm-intel-next branch, and added kernel mode setting in it. Then after it passes grub, it will soon be black screen. But I can still log in it from remote side. When start X, the screen will have output there as normal, then I start Gnome, it can enter into the desktop environment, but with the fonts and icons blurred. You can see it in attachment. I have tried to disable kernel mode setting in grub but it takes no effect. And on gm45 and g43 I also made such kernel but has no such issue. Reproduce Steps: --------------------- 1. add a line of CONFIG_DRM_I915_KMS=y, and build kernel 2. just boot the OS. (afer the grub it will become black screen soon)
Created attachment 22172 [details] xorg.0.log
Created attachment 22173 [details] blurred screen
When reporting kernel issues, dmesg is required. (It's a good idea regardless)
Created attachment 22201 [details] dmsg of booting system with KMS
The blank screen could be due to a missing fbcon driver. Did you load it or build it in before loading the i915 driver with 'modeset=1'? The screen corruption looks like a separate issue.
Jian, let's focus on "black screen before X" in this bug tracker. And leave "corruption screen after X" as a separate issue (and note UXA is required).
just a "me too" : black screen if i enable modesetting. No console, no X, nothing in the display. I had similar dmesg warnings as the reporter with -rc2, with -rc3 the "drm_mode_object_get called w/o mode_config lock" warnings went all away but still no output at all in the display. I thought there maybe was a kernel/userspace mismatch ( or any other related problem) and i tried pulling everything from current master with the same result. Hardware is eeepc901 - gem/uxa are enabled and working according to logs. What bugs me is that inteldrmfb device / panic notifier are created at startup and if i ssh to the laptop everything is working apparently fine ... Comment5 suggests a missing fbcon driver, all i have (FB related) in my kernel config is CONFIG_FB=y and CONFIG_FRAMEBUFFER_CONSOLE=y IIRC, am i missing sth. here ? I have limited access to this laptop right now, sorry, but i can provide more info later. thanks for your time !
(In reply to comment #5) > The blank screen could be due to a missing fbcon driver. Did you load it or > build it in before loading the i915 driver with 'modeset=1'? Yes, it's working now (probably caused by missing fbcon), so I'm closing this. Andy, you might file a separate bug for your issue. Thanks.
Hi Jesse, I built with 2.6.29-rc2 again and boot without i915.modeset=1, it now can boot up. But it has no resolution change compared with former ones. But the only difference is in xorg.0.log all the output has been added a number in suffix, is it to say kernel mode setting is OK? (as following shows) (II) intel(0): Output VGA1 connected (II) intel(0): Output DVI1 disconnected (II) intel(0): Output DVI2 connected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output VGA1 using initial mode 1024x768 (II) intel(0): Output DVI2 using initial mode 1024x768
Created attachment 22893 [details] xorg.0.log
Closing old verified.
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.