Bug 21486

xrandr with KMS:

Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800       60.0*+
TV1 disconnected (normal left inverted right x axis y axis)

xrandr without KMS:
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096
VGA disconnected (normal left inverted right x axis y axis)
LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800       60.0*+
   1024x768       85.0     75.0     70.1     60.0
   832x624        74.6
   800x600        85.1     72.2     75.0     60.3     56.2
   640x480        85.0     72.8     75.0     59.9
   720x400        85.0
   640x400        85.1
   640x350        85.1
TV disconnected (normal left inverted right x axis y axis)

Created attachment 25293 [details]
xrandr verbose without KMS

Created attachment 25294 [details]
xrandr verbose with KMS (wrong display)

Created attachment 25295 [details]
X server log with KMS active

Note:

1.

(II) intel(0): Output TV1 connected

when it's NOT (I've got nothing but laptop LCD attached). It happens sometimes, otherwise I get:

(II) intel(0): Using exact sizes for initial modes

instead of "sloppy heuristic".

2.

(II) intel(0): Output VGA1 using monitor section LVDS
(II) intel(0): Output LVDS1 using monitor section LVDS

VGA is not connected either and default (empty) xorg.conf produces:

(II) intel(0): Output VGA1 using monitor section Monitor0
(II) intel(0): Output LVDS1 has no monitor section

but it's the same like without KMS (when it works fine).

3.

(==) intel(0): VideoRam: 4194303 KB

without KMS it's more real:

(==) intel(0): VideoRam: 262144 KB

4. without KMS there's more entries in Xorg.*.log, like

(II) intel(0): found backlight control method /sys/class/backlight/acpi_video0
(II) intel(0): detected 512 kB GTT.
(II) intel(0): detected 7676 kB stolen memory.

dmesg difference after activating modeset:

i2c-adapter i2c-0: adapter [intel drm CRTDDC_A] registered
i2c-adapter i2c-1: adapter [intel drm LVDSDDC_C] registered
i2c-adapter i2c-1: master_xfer[0] W, addr=0x50, len=1
i2c-adapter i2c-1: master_xfer[1] R, addr=0x50, len=128
i2c-adapter i2c-1: master_xfer[0] W, addr=0x50, len=1
i2c-adapter i2c-1: master_xfer[1] R, addr=0x50, len=128
[drm] TV-13: set mode NTSC 480i 0
allocated 1280x800 fb: 0x007df000, bo f78ae7e0
fb0: inteldrmfb frame buffer device
registered panic notifier

egrep -i '(drm|fb)'

[drm] Initialized drm 1.1.0 20060810
i2c-adapter i2c-0: adapter [intel drm CRTDDC_A] registered
i2c-adapter i2c-1: adapter [intel drm LVDSDDC_C] registered
[drm] TV-13: set mode NTSC 480i 0
allocated 1280x800 fb: 0x007df000, bo f78ae7e0
fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 on minor 0

That's all I got for now. I'm not using KMS anyway (fbcon under inteldrmfb it's almost 2 times slower than uvesafb, there's also slideshow when using xterm+mc viewer), but if more info is required I can switch.

I don't see any resolution symptom. My understanding is your main pain is "broken screen with tiling" with 2.7.0 driver. That's a known issue and you need an additional kernel patch.

*** This bug has been marked as a duplicate of bug 21246 ***

(In reply to comment #4)
> Created an attachment (id=25295) [details]
> X server log with KMS active
> 
> Note:
> 
> 1.
> 
> (II) intel(0): Output TV1 connected
> 
> when it's NOT (I've got nothing but laptop LCD attached). It happens sometimes,
> otherwise I get:
> 
> (II) intel(0): Using exact sizes for initial modes
> 
> instead of "sloppy heuristic".

This looks similar to bug#21204.