[ubuntu karmic] intel-video finds correct screen size but sets it incorrectly

[ullix]

A fresh karmic-alpha4 install on a computer with motherboard Intel D945GCLF2 (w. atom330) and an IBM 14" flat screen with native resolution of 1024x768.

As can be seen in the attached screenshot (taken by camera) the Display Preferences show that the monitor is correctly recognized as being 1024x768, but the desktop is extending beyond the edges of the screen; the maximized Synaptic window does not fit on the screen. The reason is that, as visible from the OSD of the monitor, the resoltíon provided by the vga outlet is actually 1152x900.

xrandr also states a max res of 1024x768 at 60Hz being available, but this is not what the monitor receives.

I can, via Dispplay Preferences set resolutions on 800x600, 0r 640x480, and both desktop image and OSD agree. But then setting it back to 1024x768 results in the above described inconsistency.

The monitor does behave correctly in other setups.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
     Subsystem: Intel Corporation Device [8086:464c]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02)
     Subsystem: Intel Corporation Device [8086:464c]

[Bryce Harrington (bryce)]

Hi ullix,

Thanks for including an image to demonstrate the issue. Could you also please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log or Xorg.0.log.old file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[ullix (ullix)]

Bryce,
filles are following:

[ullix (ullix)]

no /etc/X11/xorg.conf existing on my system

[Geir Ove Myhr (gomyhr)]

Hi ullix,

Could you please also provide the output of `xrandr --verbose` from when the monitor is in the 1024x768/1152x900 resolution, which should be useful for us in this case. It would also be nice if you could take a screenshot using the screenshot tool and see what size the resulting image is.

Could you also remove the file ~/.config/monitors.xml which contains your user specific monitor configuration and see if this changes anything?

This is not an automated message ;-)

Geir Ove

[ullix (ullix)]

Geir,
after my yesterday's post of various files I updated the system (>100MB changes). The error persists. The monitor OSD is exactly the same as shown in my original camera shot - it sees 1152x900 while the system believes it is 1024x768.

But since both kernel and intel video driver have changed, I am adding those files again, just in case.
The system now is:
uname -a:
Linux atom330 2.6.31-8-generic #28-Ubuntu SMP Thu Aug 27 14:43:30 UTC 2009 i686 GNU/Linux
xserver-xorg-video-intel: 2:2.8.1-1ubuntu1

There is still no Xorg.conf; there is also no ~/.config/monitors.xml. I am adding a screenshot of that folder, in case some of the files is relevant.

[ullix (ullix)]

one more thing: I cold booted with both the VGA monitor (as before) plus now also a US TV-set are attached.

The TV shows a clone of the vga in color (but in a horrible quality) and does seem to show the full desktop.

During booting the vga monitor receives a 1024x768 signal, which is switching to 1152x900 probably with the start of the xserver.

When switching to a terminal with CTRL-ALT-F1 the signal also changes to the correct 1024x768, and goes back to the wrong 1152x900 when switching back to the desktop.

xrandr --verbose and Xorg.0.log attached.

[Geir Ove Myhr (gomyhr)]

ullix, all your logs show a connection on the TV-port. It is a common problem that something is detected on the TV-connection when in fact nothing is connected there, but since you have a TV there sometimes, could you just verify that there is indeed no TV connected? For troubleshooting we would like to remove any complicating factors that doesn't influence the result, so for reporting here it would be nice if you do so without the TV connected. If the logs (Xorg.0.log and xrandr output) still show TV as connected, you may explicitly disable it with an xorg.conf (see https://wiki.ubuntu.com/X/Quirks#Ignore%20TV%20Output%20Quirk).

There may be some mode changes going on that we can't see in Xorg.0.log. It may show up in the output of `dmesg`. Could you: 1. Cold boot your computer, 2. Wait a few minutes after Xorg starts (so that it is easier to distinguish boot messages from other messages in the log), 3. Switch between VT1 (Ctrl-Alt-F1) and the desktop (Ctrl-Alt-F7) a 4-5 times. 4. Log in and attach the output of `dmesg` here.

It's nice that your OSD shows the exact mode H- and V-frequency and sync polarity. Could you tell us what exact mode is used when at VT1? (by attaching another picture if you want) Is this the same mode that works fine in "other setups"?

To help isolate the problem it would be nice if you could tell us whether this works in some other configurations:
- In any of the other 1024x768 modes listed? I think the way to change this would be `xrandr --mode 0x3d` and `xrandr --mode 0x3e`. You should get the starting mode with `xrandr --mode 0x3f`. I'm not 100 % sure the syntax is right and I don't have a linux machine to test on right now.
- With UMS (Userland Mode Setting) instead of KMS (Kernel Mode Setting). To use UMS, press Esc at boot and 'e' at the boot menu to edit the boot parameters and add the parameter i915.modeset=0.
- With any previous versions of ubuntu or other linux distribution if you have tried that before.

[ullix (ullix)]

Geir,
with your comment I realized that indeed there was a connection on TV1 to a TV, which was not only switched off but also unplugged from power for at least a month. I kind of dismissed the connection statement of xrandr as just another bug ...

However, playing with the connect led to the discovery that VGA settings depend on TV connect status and sequence of steps, which I don't think is the intended behaviour. Also, there is a severe, reproducible crash of the xserver.

I did various cold boots with two scenarios: either only VGA connected, or also the TV (via the s-video outlet of the motherboard), and attach camera-screenshots and dmesg and Xorg.0.log files. I did not do most of the things you had asked for, as I believe the sitation has changed, but if you need more/other please tell me.

When booting, only the vga - even if the tv is connected - gets a signal, which seemingly at random fluctuates between 800x600, 720x400, 640x480, 640x400 settings, too fast to follow. At the point where the ubuntu logo with the progress bar appears, the signal switches to 1024x768. Up to here all is independent of whether only vga or also tv is connected. If tv is connected the same picture is visible also on the tv (see pic imgp2060.jpg).

When the xserver starts the signals depend on what is connected. With both connected the resolution becomes 1152x900 (imgp2065.jpg), when only vga connected it remains 1024x768 (imgp2069.jg). This is kept into the desktop, whereby in the dual connect case xrandr pretends it is connected with 1024x768, while the monitor osd says otherwise (imgp2066.jpg). In the single connect case the two agree (imgp2071.jpg). Only the vertical refresh rates are correctly stated in both cases as 60Hz, or 75Hz, resp.

When, in the dual case, I unplug the tv cable from the mb, nothing happens. But after a xrandr command the signals change and the vga now receives a 1024x768 signal (imgp2067.jpg). Note, however, that both the signal frequency and the polarities are different from the other 1024x768 signals!

When I then re-insert the tv cable into the mb (nothing happens) and issue xrandr, then the xserver crashes. keyboard (PS/2 connected) and mouse (USB connected) are dead. I can ssh into the computer from another machines, and see xrandr and Xorg running. From remote I can kill xrandr, but Xorg resists all kill attempts. (Frame buffer allocation issue? see last line in Xorg.0.log-commented).

The attached Xorg.0.log_commented is for the dual-screen scenario. I inserted comments (search for ullix) between the steps described above. The dmesg_commented is the matching dmesg file (no changes though due to the steps). Dmesg_vga-only and Xorg.0.log_vga-only are from the other scenario.

Booting with only vga attached is unfortunately no solution. Beyond the xserver crashing, the desktop is shifted downwards by about half the height of the lower panel and makes it illegible, and a black space is inserted at the top (compare picture imgp2071 with 2066 or 2067). I can press the monitor OSD button, and it jumps up, only to jump down again after 5-50 sec. This IBM monitor worked perfectly well with older versions of Ubuntu.

I noticed...

[Bryce Harrington (bryce)]

Forwarding this bug from Ubuntu reporter ullix:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/413788

[Problem]
xrandr and the Display Preferences both show that the monitor is correctly recognized as being 1024x768, but the desktop is extending beyond the edges of the screen. The OSD of the monitor indicates that the vga output is actually setting 1152x900. xrandr shows TV1 active even with no device connected.

[Original Description]
A fresh karmic-alpha4 install on a computer with motherboard Intel D945GCLF2 (w. atom330) and an IBM 14" flat screen with native resolution of 1024x768.

As can be seen in the attached screenshot (taken by camera) the Display Preferences show that the monitor is correctly recognized as being 1024x768, but the desktop is extending beyond the edges of the screen; the maximized Synaptic window does not fit on the screen. The reason is that, as visible from the OSD of the monitor, the resoltíon provided by the vga outlet is actually 1152x900.

xrandr also states a max res of 1024x768 at 60Hz being available, but this is not what the monitor receives.

I can, via Display Preferences set resolutions on 800x600, 0r 640x480, and both desktop image and OSD agree. But then setting it back to 1024x768 results in the above described inconsistency.

The monitor does behave correctly in other setups.

one more thing: I cold booted with both the VGA monitor (as before) plus now also a US TV-set are attached.

The TV shows a clone of the vga in color (but in a horrible quality) and does seem to show the full desktop.

During booting the vga monitor receives a 1024x768 signal, which is switching to 1152x900 probably with the start of the xserver.

When switching to a terminal with CTRL-ALT-F1 the signal also changes to the correct 1024x768, and goes back to the wrong 1152x900 when switching back to the desktop.

I realized that indeed there was a connection on TV1 to a TV, which was not only switched off but also unplugged from power for at least a month. I kind of dismissed the connection statement of xrandr as just another bug ...

However, playing with the connect led to the discovery that VGA settings depend on TV connect status and sequence of steps, which I don't think is the intended behaviour. Also, there is a severe, reproducible crash of the xserver.

I did various cold boots with two scenarios: either only VGA connected, or also the TV (via the s-video outlet of the motherboard), and attach camera-screenshots and dmesg and Xorg.0.log files. I did not do most of the things you had asked for, as I believe the sitation has changed, but if you need more/other please tell me.

When booting, only the vga - even if the tv is connected - gets a signal, which seemingly at random fluctuates between 800x600, 720x400, 640x480, 640x400 settings, too fast to follow. At the point where the ubuntu logo with the progress bar appears, the signal switches to 1024x768. Up to here all is independent of whether only vga or also tv is connected. If tv is connected the same picture is visible also on the tv (see pic imgp2060.jpg).

When the xserver starts the signals depend on what is connected. With both connect...

[Bryce Harrington (bryce)]

User posted a bunch of images and files, but many are larger than bugzilla will allow to be uploaded, so here's links:

screenshot by camera to show OSD
http://launchpadlibrarian.net/30337566/imgp2016.jpg

http://launchpadlibrarian.net/30944276/lspci-vvnn.txt

http://launchpadlibrarian.net/30944336/Xorg.0.log

screenshot by screenshot tool, showing 1024x768 resolution (428.2 KiB, image/png)
http://launchpadlibrarian.net/30964159/Screenshot-1.png

http://launchpadlibrarian.net/30964211/xrandr--verbose.txt

http://launchpadlibrarian.net/30964228/Xorg.0.log

xrandr--verbose_w_ntsctv.txt
http://launchpadlibrarian.net/30965869/xrandr--verbose_w_ntsctv.txt

http://launchpadlibrarian.net/30965886/Xorg.0.log

booting. Same signal to vga irrespective of vga+tv or only vga connected
http://launchpadlibrarian.net/31018019/imgp2060.jpg

xserver starts with vga+tv connected, resolution change to 1152x900
http://launchpadlibrarian.net/31018122/imgp2065.jpg

2069-xserver starts with only vga connected, resolution remains at 1024x768
http://launchpadlibrarian.net/31018189/imgp2069.jpg

2066-vga + tv connected, discrepancy xrandr and osd
http://launchpadlibrarian.net/31018800/imgp2066.jpg

2071-vga only connected, same for xrandr and osd, note frequencies
http://launchpadlibrarian.net/31018925/imgp2071.jpg

2067-resetting by xrandr after tv removal from dual screen boot
http://launchpadlibrarian.net/31018995/imgp2067.jpg

dmesg_commented for dual-screen scenario
http://launchpadlibrarian.net/31019089/dmesg_commented

Xorg.0.log-commented for dual-screen scenario
http://launchpadlibrarian.net/31019119/Xorg.0.log_commented

dmesg for vga-only scenario
http://launchpadlibrarian.net/31019134/dmesg_vga-only

Xorg.0.log for vga only scenario
http://launchpadlibrarian.net/31019173/Xorg.0.log_vga-only

[Bryce Harrington (bryce)]

ullix - I've forwarded this bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=23721 - please subscribe yourself to this bug, in case they need further information or wish you to test something. Thanks ahead of time!

[Bryce Harrington (bryce)]

Oh btw, this sounds like a "phantom output" bug - see https://wiki.ubuntu.com/X/Quirks#Ignore%20TV%20Output%20Quirk for more info on this particular problem. If I'm right, that page has some tips for working around the problem, and the info we need to solve it if that does it.

[yakuizhao (yakui-zhao)]

Will you please try the latest linus git tree and see whether the issue still exists?
Thanks.

[yakuizhao (yakui-zhao)]

As there is no response, this bug will be rejected.

[Bryce Harrington (bryce)]

[Closing as expired due to no response from reporter either here or on the upstream bug report.]