Intel HD graphics: Starts always with 1024x768 resolution on a 1920x1080 monitor (HDMI and DisplayPort)

Bug #1029865 reported by Till Kamppeter
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xf86-video-intel
Won't Fix
Medium
linux (Ubuntu)
Invalid
High
Maarten Lankhorst

Bug Description

I have a new Intel DZ77BH-55K motherboard with an i5-2400 processor with on-chip HD graphics. The motherboard has one HDMI and one DisplayPort output. For testing reasons and on the search to solve the problem I have connected both outputs to my EIZO EV2333W 23-inch 1920x1080 (16:9) monitor (HDMI to DVI via adapter, DisplayPort to DisplayPort), but I have the same problem when the DisplayPort cable is not connected.

The problem is that if the computer boots up and shows the login screen the login screen appears with 1024x768 resolution and not with the monitor's native 1920x1080. The driver is actually the intel driver (no fallback to VESA). After login I can correct thedisplay to 1920x1080 with the "Displays" section of the System Settings and this persists when I log out an log in again, only the login screen and the desktop of every new user stays 1024x768.

The problem seems that there are more than the two (HDMI and DisplayPort) displays reported by the driver, according to the xrandr output. Especially there is a "VGA1" display always considered as connected and with max resolution of 1024x768. This seems to somehow determine the default resolution, probably because the standard multi-monitor mode is mirroring and due to the VGA1 ghost display also a system with one monitor and one monitor cable is already in multi-monitor mode.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.4-0ubuntu5
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Fri Jul 27 12:12:56 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes,
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2040]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-6-generic root=UUID=270acb41-78a4-4df9-84b3-2e3943b4d4dd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.37-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~really6.14.4-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Raising importance as Intel HD graphics is common in modern PCs.

Changed in xorg (Ubuntu):
importance: Undecided → High
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Workaround (NOT FIX!) for everyone else affected:

Edit /etc/default/grub, adding "video=VGA1:d" between the quotes in the GRUB_CMDLINE_LINUX line, then run the command

sudo update-grub

in a terminal window. Reboot and the problem should be gone.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Added "drm.debug=0xe" to the kernel cmmand line (as in comment #3), after reboot attaching syslog.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Notetha the workaround of comment #3 does not work on every boot. For me it worked only once.

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

temporary bug early in 3.5 cycle, to accommodate kvm switches we tried to probe the crt and missed that the fallback from that would accidentally decide the display was connected

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Also important to say that this problem occurs under both Precise and Quantal.

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

It's purely a kernel problem, i915 is detecting that vga is connected erroneously.

Changed in linux (Ubuntu):
importance: Undecided → High
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
tags: added: precise
Changed in linux (Ubuntu):
assignee: nobody → Maarten Lankhorst (mlankhorst)
no longer affects: xorg (Ubuntu)
Revision history for this message
In , Maarten Lankhorst (mlankhorst) wrote :

The problem is that if the computer boots up and shows the login screen the login screen appears with 1024x768 resolution and not with the monitor's native 1920x1080. The driver is actually the intel driver (no fallback to VESA). After login I can correct thedisplay to 1920x1080 with the "Displays" section of the System Settings and this persists when I log out an log in again, only the login screen and the desktop of every new user stays 1024x768.

The problem seems that there are more than the two (HDMI and DisplayPort) displays reported by the driver, according to the xrandr output. Especially there is a "VGA1" display always considered as connected and with max resolution of 1024x768. This seems to somehow determine the default resolution, probably because the standard multi-monitor mode is mirroring and due to the VGA1 ghost display also a system with one monitor and one monitor cable is already in multi-monitor mode.

syslog with drm.debug=0xe: https://launchpadlibrarian.net/111274170/syslog

affects: linux → xserver-xorg-video-intel
Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Chris Wilson (ickle) wrote :

The hw is convinced something is attached. Is the physical connector dirty? Does plugging in and removing a real monitor clear the erroneous state? Does Windows work?

About the only brute force you have available is to do a forced hw probe instead of checking the state changed, or to always use the EDID detection (which then breaks those monitors without EDID).

Revision history for this message
In , Till Kamppeter (till-kamppeter) wrote :

Chris, note that for the vga1 there is no connector on the PC. The only connectors are HDMI and DisplayPort, no VGA connector.

Revision history for this message
HeWhoE (hewhoe) wrote :

I'm experiencing the same issue with an Intel 845G.

I'm using a "Natty"-based system with Linux 3.5.1.

I was previously using Linux 3.4.7 without issues. To get HD videos to play smoothly, all I had to do was add Option "AccelMethod" "uxa" to the Device section of my xorg.conf file.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

What does Windows do here (if you can test this ...)? Since the vga hotplug logic is all in hw in snb, there's not much we can do to prevent this, I fear ...

Revision history for this message
In , Till Kamppeter (till-kamppeter) wrote :

I do not have Windows here. So I cannot do Windows tests.

Changed in xserver-xorg-video-intel:
status: Confirmed → Incomplete
Revision history for this message
In , Till Kamppeter (till-kamppeter) wrote :

I do not have Windows here. So I cannot do Windows tests.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

Ok, till we have evidence to the contrary I'll shrug this off as a hw bogosity ... crt detection is a funky business and we get way too much hate-mail from people because every time we touch it we break something. So I prefer not to touch it. Since you can easily work around the issue with xrandr, shouldn't be to horrid.

Changed in xserver-xorg-video-intel:
status: Incomplete → Won't Fix
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Maarten, upstream has rejected the bug report. Is there still some way to fix, as your comment #6 makes the impression that it is easy to fix?

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

When I was looking around at Amazon I have found this user comment:

http://www.amazon.com/Diablotek-Dual-Core-1-8GHz-Keyboard-Wireless-N/product-reviews/B007W66BRG/ref=cm_cr_dp_see_all_btm?ie=UTF8&showViewpoints=1&sortBy=bySubmissionDateDescending

It is about the

Diablotek U310 All-in-One Atom Dual-Core D525 1.8GHz 2GB 500GB Ubuntu Linux Keyboard PC

This is a PC completely integrated in the keyboard (like the good old Commodore 64) qith Intel Atom and on-chip Intel 3150 (X3000 series) GPU.

The user reports the same problem with Ubuntu Precise as I am reporting here:

----------
There is an odd thing about the computer's hardware. It reports a built in display of 1024x768. That display, of course, isn't there, but the chips supporting it remain on the motherboard. This means you will deal with a perpetual, dual, phantom display. It's easy enough to turn off the internal, non-existent display, but it's still odd.
----------

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

Ok closing this as a hardware issue then. :)

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Bug 1156310 shows the same symptoms and a solution is posted, which works on other machines but not on this one.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.