Bug 21486 - [965GM KMS LVDS] bad resolution/timings of LMDS with KMS active
Summary: [965GM KMS LVDS] bad resolution/timings of LMDS with KMS active
Status: RESOLVED DUPLICATE of bug 21246
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Gordon Jin
QA Contact: Xorg Project Team
URL: http://quarto.pl/~gotar/intel/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-30 00:25 UTC by Tomasz Pala
Modified: 2009-05-03 22:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
LMDS display with inteldrmfb running (769.03 KB, image/jpeg)
2009-04-30 00:25 UTC, Tomasz Pala
no flags Details
xrandr verbose without KMS (5.29 KB, text/plain)
2009-04-30 01:11 UTC, Tomasz Pala
no flags Details
xrandr verbose with KMS (wrong display) (1.70 KB, text/plain)
2009-04-30 01:12 UTC, Tomasz Pala
no flags Details
X server log with KMS active (22.62 KB, text/plain)
2009-04-30 01:36 UTC, Tomasz Pala
no flags Details

Description Tomasz Pala 2009-04-30 00:25:39 UTC
Created attachment 25287 [details]
LMDS display with inteldrmfb running

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
        Subsystem: Fujitsu Siemens Computers Device [1734:110e]

X server 1.6.1, libdrm 2.4.9 (from PLD Linux i686) running on Fujitsu Siemens Esprimo Mobile V5505.

After activating KMS (and only then) I've encountered problem with screen resolution/timing:

- 2.6.3 Intel driver: initial (first-run) screen is smaller (like http://launchpadlibrarian.net/12354400/screen.png), restarting X fixes the problem, as well as setting https://wiki.ubuntu.com/X/Quirks#Ignore%20TV%20Output%20Quirk

- 2.7.0 Intel driver: screen photo attached, none of the xorg.conf settings help to work this out.
Comment 1 Tomasz Pala 2009-04-30 01:09:41 UTC
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)
Comment 2 Tomasz Pala 2009-04-30 01:11:21 UTC
Created attachment 25293 [details]
xrandr verbose without KMS
Comment 3 Tomasz Pala 2009-04-30 01:12:38 UTC
Created attachment 25294 [details]
xrandr verbose with KMS (wrong display)
Comment 4 Tomasz Pala 2009-04-30 01:36:52 UTC
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.
Comment 5 Tomasz Pala 2009-04-30 01:49:04 UTC
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.
Comment 6 Gordon Jin 2009-05-03 22:09:27 UTC
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 ***
Comment 7 Gordon Jin 2009-05-03 22:09:53 UTC
(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.


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.