[g45] GMA 4500MHD on UL30Vt doesn't support HDMI output

[Barosl LEE]

Binary package hint: xserver-xorg-video-intel

UL30Vt has two video cards, Intel GMA 4500MHD and NVIDIA G210M. Although G210M supports HDMI video output, 4500MHD doesn't recognize the external monitor connected by HDMI at all. But both support VGA connector.

Meanwhile, G210M cannot be an option; G210M isn't supported properly on UL30Vt yet. To enable the card, we must change SATA operation mode to Compatible. It will decrease performance of the hard disks. So we should stay on 4500MHD until the issue is fixed.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768
 edid-base64: AP///////wAGrywQAAAAAAESAQOAHRB4Crplm1lUniYaTVIAAAABAQEBAQEBAQEBAQEBAQEBIBxWgFAAIzAwIDYAJaQQAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTMzWFcwMSBWMCAKALw=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Feb 21 17:41:12 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: ASUSTeK Computer Inc. UL30VT
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=e5df11c4-a023-44d4-afcd-f88cfc79dfa4 ro i915.modeset=1
ProcEnviron:
 PATH=(custom, user)
 LANG=ko_KR.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 07/14/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL30VT
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL30VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
nvidia-settings:

system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-25-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:1af2]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218 [GeForce G210M] [10de:0a74] (rev a2) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:1af2]

[bugbot (bugbot)]

Hey Barosl,

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.

[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.

[Rob (rob-mobhi)]

The issue still exists in Natty. Works under windows 7 so not a h/w problem. Seems same as described above.