No DVI output on Intel 82G33/G31 in Maverick

[ockels]

Binary package hint: xorg

On an ACER ASPIRE L3600 after a clean install and after latest updates of Kubuntu / Ubuntu 10.10 (32/64bit, doesn' t matter) DVI output fails, VGA works fine though. On the same machine with 10.04 (lucid) DVI & dual screen setup worked flawlessely.

%lspci
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 10)
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)
00:02.1 Display controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GH (ICH7DH) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
04:06.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

xrandr:

ockels@ockels-Aspire-L3600:~$ xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 410mm x 257mm
   1440x900 59.9*+ 75.0
   1280x1024 75.0 60.0
   1280x960 60.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1
DVI1 disconnected (normal left inverted right x axis y axis)

DVI1 remains status disconnected while connected (works on the same machine on Lucid)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1440x900 1280x1024 1280x1024 1440x900 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
 edid-base64: AP///////wBMLYUCOTFBSB0RAQMOKRqHKtelollKliQUUFS/74CVAJUPgYCBQHFPAQEBAQEBmimg0FGEIjBQmDYAmgERAAAcAAAA/QA4Sx5RDgAKICAgICAgAAAA/ABTeW5jTWFzdGVyCiAgAAAA/wBITURQNzMxODIzCiAgAL0=
Date: Sun Dec 12 11:35:55 2010
GdmLog:
 Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /home/ockels/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Acer Aspire L3600
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=da85f4ef-e7ae-430c-907e-1d0b0fccaa81 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 01/18/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A3
dmi.board.name: G31
dmi.board.vendor: Acer
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd01/18/2008:svnAcer:pnAspireL3600:pvrR01-A3:rvnAcer:rnG31:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Aspire L3600
dmi.product.version: R01-A3
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
peripherals: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-23-generic

[ockels (ockels)]

It has been three months now, i still cannot upgrade or do a fresh install of 10.10 because of this bug.
I would also like to add when running al clean setup of 10.10 directly from USB with DVI attached only my screen isn't detected at all. There's no output whatsoever an the screen just turns off. On Lucid on the same machine i do not have this problem and it's working flawlessely.

Anyone please? i'm really stuck here .....

[Tom Keim (tomkeim94)]

I have exact the same problem on my Acer Aspire L3600. Very annoying.

I use a DVI->HDMI converter. but also a normal DVI screen won't work. The chipset is the Intel GMA 3100

[blobbybigwig (wepmaschda)]

Same for me.

Using maverick or natty on an Acer Travelmate 8472TG with Acer EasyPort IV connected. DVI output is recognized as "HDMI1" showing correct resolutions but display always turns to powersave (=no data received).

[bugbot (bugbot)]

Hey ockels,

Thanks for your interest in Ubuntu.

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[blobbybigwig (wepmaschda)]

Created a new bug since it was recommended by apport:
https://bugs.launchpad.net/ubuntu/+bug/772283

Is this as duplicate?

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Jue202 (juergen202)]

I have the same issue. DVI is not working with Acer Easyport IV and Acer TM8372T. Additionally Ethernet cable and USB do not work. I use Ubuntu 10.10. I also tried 11.04. It didn't work either.

[ockels (ockels)]

I bought a new computer with an nvidia card, so i do not have the hardware anymore to test it. But i'm quite sure that this serious bug still exists. signed https://bugs.launchpad.net/ubuntu/+bug/772283 too.

[Hans-Joachim Kliemeck (bj7u6139zdyf-info-jjcftv6wldnz)]

any success on this issue? i HOPE that the issue is resolved in Oneiric!

[Naoyuki Tai (ntai)]

I have the same issue.
My machine is not a laptop but uses mobile CPU.
With Precise, VGA works but DVI and HDMI do not work.

I know the machine worked just fine with Lucid.
So, I downgraded xorg to Lucid. It does not fix the problem.
I brought back xorg to Precise.
I also tried the tip of xorg from PPA and did not fix the issue.

Then, I downgraded kernel to Lucid.
That fixed the DVI output.
Kernel that works is 2.6.32-33-generic. 3.2.0-xx-generic deos not work.

When DVI is working, in "Display" control panel, the DVI is recognized as "Digital display" while VGA display's maker is recognized correctly.

When DVI is not working, in "Display" control panel, the DVI and VGA's makers are both correctly recognized.
According to /var/log/Xorg.0.log, DVI1 is correctly recognizing the monitor EDID, sets up the resultion, etc, but the signal is not coming out.

[Chris Wilson (ickle)]

A starting point for debug information here is a boot dmesg with drm.debug=6 appended to the kernel commandline; then we can start to figure out why we are failing to communicate with the monitor across the DVI connector.

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.