Bug 17764 - [G35 HDMI->DVI] TMDS-1 not detected
Summary: [G35 HDMI->DVI] TMDS-1 not detected
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: MaLing
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2008-09-25 00:55 UTC by Andreas Horter
Modified: 2008-11-26 06:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log with VGA only and ModeDebug (60.53 KB, text/plain)
2008-09-30 14:15 UTC, Andreas Horter
no flags Details
Xorg.0.log with HDMI only and ModeDebug (20.75 KB, text/plain)
2008-09-30 14:21 UTC, Andreas Horter
no flags Details
Xorg.0.log with HDMI only and ModeDebug with SyncMaster (50.90 KB, text/plain)
2008-10-20 12:38 UTC, Andreas Horter
no flags Details

Description Andreas Horter 2008-09-25 00:55:00 UTC
I have an ASUS P5E-V HDMI motherboard and can't get X working with a HDMI to DVI cable on a Iiyama ProLite E481.

When I connect the monitor with VGA everything works fine. When I connect it with the packaged HDMI to DVI adapter and a DVI-DVI cable (or a HDMI-DVI cable, just to rule out hardware problems of the adapter) I can see the BIOS post and all text-mode output. But when I start X the monitor goes black. Exactly I have both, VGA and DVI connected at the same time. The monitor starts with the digital signal and stays there until I start X, when it switches to the analog input. 

xrandr --prop tells me:

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1600 x 1600
VGA connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
        EDID_DATA:
                00ffffffffffff0026cd0a4828240000
                110e01030e261e782ac830a3584c9a25
                125054bfef008180714f010101010101
                010101010101302a009851002a403070
                1300782d1100001e000000ff00303532
                33374734343039323536000000fd0037
                4c18530e000a202020202020000000fc
                00504c453438310a202020202020003f
   1280x1024      60.0*+   75.0     60.0     60.0* 
   1600x1024      60.2  
   1400x1050      60.0  
   1440x900       59.9  
   1280x960       60.0  
   1360x768       59.8  
   1152x864       75.0     75.0     75.0     70.0     60.0  
   1024x768       75.1     75.0     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   640x480        75.0     72.8     72.8     75.0     66.7     60.0     59.9
   720x400        70.1  
TMDS-1 disconnected (normal left inverted right x axis y axis)

It seems the driver is unable to see the connected monitor... but when I switch to the VESA driver I can get X working via HDMI-DVI. At first I thought this can be related to bug #13968, but I can't even get the monitor recognized. 

OS: Debian unstable / experimental
xorg: 1:7.4~3
xserver-xorg-video-intel: 2:2.4.2-1
Hardware: ASUS P5E-V HDMI with HDMI to DVI cable and VGA cable
          Iijama ProLite E481
Comment 1 Wang Zhenyu 2008-09-30 05:10:20 UTC
So just to be sure with HDMI->DVI issue, could you try without VGA connected?
Please turn on ModeDebug option, and upload the X log. 
Comment 2 Andreas Horter 2008-09-30 14:15:50 UTC
Created attachment 19319 [details]
Xorg.0.log with VGA only and ModeDebug

This is with VGA only connected and the following xorg.conf

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
        Option          "XkbRules"      "xorg"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "de"
        Option          "XkbVariant"    "nodeadkeys"
EndSection

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
EndSection

Section "Device"
        Identifier      "Configured Video Device"
        Option          "ModeDebug"     "true"
EndSection

Section "Monitor"
        Identifier      "Configured Monitor"
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Monitor         "Configured Monitor"
EndSection
Comment 3 Andreas Horter 2008-09-30 14:21:37 UTC
Created attachment 19320 [details]
Xorg.0.log with HDMI only and ModeDebug 

This is with HDMI only connected and the same xorg.conf as with VGA. I got it by starting X, and now when I can't get displayed anything on the monitor switch via Ctrl-Alt-F1 to a (also black) console and reboot via Ctrl-Alt-Del.
Comment 4 Wang Zhenyu 2008-10-13 20:17:45 UTC
So I think this might be relate to SDVO port probe change in recent 2.4 release. Does 2.3.2 work for you?
Or  you might try 2.5 branch or master and with "ForceSDVODetect" option on.
Comment 5 Andreas Horter 2008-10-16 07:05:17 UTC
With xserver-xorg-video-intel 2:2.3.2-2+lenny4 from debian testing I am getting exactly the same behaviour. 
I have to try out 2.5 branch or master though.
Comment 6 Andreas Horter 2008-10-20 12:38:05 UTC
Created attachment 19767 [details]
 Xorg.0.log with HDMI only and ModeDebug with SyncMaster

I had a chance to connect an other monitor (a Samsung SyncMaster 226BW) to my computer and with this one everything works as expected. 
Now I don't know if this is some hardware incompatibility or not... exactly the same monitor did work over DVI with a Radeon 9200 and a Radeon X300 before.
Comment 7 MaLing 2008-11-18 02:55:41 UTC
hi,
Coudl you set up your initial mode as
 Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz), and instead of initial mode 1680x1050.

Thanks
Ma Ling
Comment 8 Andreas Horter 2008-11-21 00:46:01 UTC
I'm sorry, I don't have this monitor any more. And with the new one everything works as expected. 
Thanks
Comment 9 Michael Fu 2008-11-25 20:32:09 UTC
Andreas, it's good to know this issue is gone now anyway.

just a couple of questions to confirm with you:
- you said that monitor works with a Radeon card. In that case , do you use the same HDMI->DVI cable? Or just a DVI->DVI cable?
- with the new monitor , this issue is gone. again, are you using the same HW environment, except the monitor? Asus Mobo, HDMI->DVI cable, etc...
Comment 10 Andreas Horter 2008-11-26 06:31:35 UTC
> - you said that monitor works with a Radeon card. In that case , do you use the
> same HDMI->DVI cable? Or just a DVI->DVI cable?

As the Radeon cards both only had a DVI output and the old monitor only had a DVI input I used a DVI->DVI cable, which did work. 

> - with the new monitor , this issue is gone. again, are you using the same HW
> environment, except the monitor? Asus Mobo, HDMI->DVI cable, etc...

Yes, it is exactly the same HW as before, Asus Mobo with onboard graphics. Right now I have connected it with exactly the same HDMI-> DVI cable which didn't work with the old monitor before. If it may be of any use I can try to connect the Mobo (VGA, HDMI) with any of the monitor inputs (VGA, DVI, HDMI). 



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.