Created attachment 31384 [details] Xorg.0.log using driver 2.9.1 with ModeDebug turned on Bug description: I'm using an ASUS P5Q-EM motherboard with a VGA, DVI-D and HDMI connector on the back. Using the VGA and DVI, monitors are detected. Currently the DVI-D and HDMI are both connected to the same Philips HDTV (DVI to HDMI cable and plain HDMI cable respectively). The DVI connection is detected and configured with 1080p, however the HDMI connection is sort of detected but appears to not be able to read EDID data and is set as unconnected (see Xorg.0.log file). The Xorg.0.log shows this for HDMI-2 (HDMI connector): (II) intel(0): DVI monitor detected on HDMI-2 (II) intel(0): EDID for output HDMI-2 (II) intel(0): Output HDMI-2 disconnected While HDMI-1 (DVI-D connector) shows this: (II) intel(0): HDMI monitor detected on HDMI-1 (II) intel(0): EDID for output HDMI-1 ... (full EDID data listing) ... (II) intel(0): Output HDMI-1 connected HDMI-2 output (the HDMI connector) can be forced on using xrandr by adding the 1920x1080 modeline and setting it to HDMI-2. Display when forced appears to be larger than the screen however (parts of it outside screen) and the mouse cursor disappears. When forced xrandr still reports HDMI-2 to be disconnected. System environment: -- chipset: G45 -- system architecture: i686 32-bit -- xf86-video-intel: 2.9.1 -- xserver: 1.6.3.901 (1.6.4 RC 1) -- mesa: 7.5.1 -- libdrm: 2.4.13 -- kernel: 2.6.28-hardened-r9 -- Linux distribution: Gentoo Hardened 10.0 -- Machine or mobo model: ASUS P5Q-EM -- Display connector: HDMI Reproducing steps: Start X Additional info: I occassionally get these odds errors from the drm module: [drm:i915_setparam] *ERROR* unknown parameter 4 [drm:i915_getparam] *ERROR* Unknown parameter 6
Created attachment 31385 [details] xorg.conf
Created attachment 31386 [details] xrandr --verbose
Created attachment 31387 [details] lspci -vvnn
dmesg with debug=0x06 Became quite large, linking to it instead: http://artamir.org/dmesg
Hi, Henric Will you please try the latest kernel(2.6.33-rc7) with KMS enabled and add the boot option of "drm.debug=0x04"? After the system is booted, please run "xrandr -q --verbose" and then attach the output of dmesg. It will be great if you can attach the output of vbios.dump on your box, which can be obtained by using the following command: 1. echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom 2. cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump 3. echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom Thanks. Yakui
Hello Yakui, I've tried the latest kernel 2.6.33-rc7 as you asked and booted with the following boot options: i915.modeset=1 drm.debug=0x04 I'll attach VBIOS, xrandr output and dmesg for that try. As far as I can see, the actual HDMI connector is still seen as "disconnected" while the DVI connector is working properly. /Henric
Created attachment 33316 [details] dmesg with debug=0x04
Created attachment 33317 [details] Video BIOS
Created attachment 33318 [details] xrandr -q --verbose
Hi, Henric Sorry for the late response. It is strange that the HDMI monitor is not detected on your box. Can you only use the HDMI to connector your HDTV monitor and see whether it is detected?(that means that the DVI is not used). I have a Asus P5Q-EM mainboard in my hand. In my test the HDMI monitor can be detected correctly. I don't know why the HDMI monitor can't be detected on your box. thanks. Yakui
Hello Yakui, I tried with only the HDMI display plugged in and as expected I get this in Xorg.0.log: (II) intel(0): DVI monitor detected on HDMI-2 (II) intel(0): EDID for output HDMI-2 (II) intel(0): Output VGA disconnected (II) intel(0): Output HDMI-1 disconnected (II) intel(0): Output HDMI-2 disconnected (WW) intel(0): No outputs definitely connected, trying again... (II) intel(0): Output VGA disconnected (II) intel(0): Output HDMI-1 disconnected (II) intel(0): Output HDMI-2 disconnected (WW) intel(0): Unable to find initial modes (EE) intel(0): No valid modes. Followed by a "no screens found". Could this be a result of a defect board? I have been getting other strange issues with it as well such as newer versions of GRUB failing to start because it is unable to detect any upper memory at all. /Henric
> > Could this be a result of a defect board? I have been getting other strange > issues with it as well such as newer versions of GRUB failing to start because > it is unable to detect any upper memory at all. Hi, Henric It is very interesting that the HDMI output can't be detected. From the log it seems that the EDID can't be obtained. Maybe this issue is related with the mainboard. Do you have an opportunity to try windows on this machine and see whether the HDMI output can be detected as expected? thanks Yakui > > /Henric >
Hello Yakui, I'm afraid Windows is out of the question on this machine. It is in part my home server (hence the Gentoo Hardened distro). /Henric
(In reply to comment #13) > Hello Yakui, > > I'm afraid Windows is out of the question on this machine. It is in part my > home server (hence the Gentoo Hardened distro). Thanks for the updating. As the windows can't be tested, we have no way to compare the difference between windows and Linux about this issue. Maybe the issue is related with the mainboard. Can you contact with the other vendor about this issue? Thanks. > > /Henric >
Hello Yakui, Sorry for the long time since last reply. I just today figured the whole thing out and it was not a software issue at all but rather a faulty HDMI cable (doh!). I guess I should've tried that earlier but only today I put a graphics card with HDMI out in another computer and tried that same cable and couldn't get any video out. New cable solved that problem and so I tried the same in my linux-box and everything worked! Thanks for your time anyway. I'm closing this "bug". /Henric
Hi, Henric Thanks for updating the bug status. It is good news that the HDMI can be detected correctly after changing the HDMI cable. Thanks Yakui
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.