Created attachment 22540 [details]
dmesg after loading drm modules
Using kernel 2.6.29-rc3 from git (airlied/drm-next branch of today) I see the following:
Loading the drm modules with kernel modesetting enabled, the screen turns black, no framebuffer console (support is in kernel). Even the backlight turns off.
Starting X (git master as of today, as well as all drivers) brings back the backlight, but apart from that still the black screen. The machine is not frozen, as I can handle it blind or via ssh.
Do you need any logs apart from those attached?
Created attachment 22541 [details]
dmesg before loading drm modules
Created attachment 22542 [details]
Created attachment 22543 [details]
Created attachment 22544 [details]
Output of fbset -v
Created attachment 22545 [details]
Output of lspci -vv
Can you try the patch at
it prevents corruption of the LVDS mode, which may explain what you're seeing.
Unfortunately that does not help in my case.
Here some more detailed info:
Loading the drm modules with the patch you mentioned puts out the following to kernel log:
[ 326.489925] [drm] Initialized drm 1.1.0 20060810
[ 326.507709] pci 0000:00:02.0: setting latency timer to 64
[ 326.730160] integrated sync not supported
[ 327.300154] integrated sync not supported
[ 327.356566] [drm] TV-15: set mode NTSC 480i 0
[ 327.704745] allocated 1680x1050 fb: 0x007df000, bo f69c6f60
[ 327.705075] fb0: inteldrmfb frame buffer device
[ 327.705078] registered panic notifier
[ 327.705084] [drm] Initialized i915 1.6.0 20080730 on minor 0
fbset -v says
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven
Opening frame buffer device `/dev/fb0'
Using current video mode from `/dev/fb0'
# D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
geometry 1680 1050 1680 1050 32
timings -1 0 0 0 0 0 0
What puzzles me is the timing, looks like the/a correct mode cannot be detected for some reason. Can I somehow get better debug information about the reasons? Do I need Ben Gamari's patches for debugfs integration?
some of the debugfs stuff might help, but it looks like KMS is failing to detect your outputs correctly, which might cause it to draw in the wrong place and/or fail to enable the LVDS output. You could try commenting out the call to intel_tv_init in intel_display.c:intel_setup_outputs() to see if that's the cause...
That helps. Thanks! Do we need an additional quirk?
This is fixed by commit 36c3f7d79c475ed0b11fc1506c29ec439e9193ee.