Bug 19548 - [i946GZ] - VGA output works, but SDVO DVI is not detected
Summary: [i946GZ] - VGA output works, but SDVO DVI is not detected
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: MaLing
QA Contact: Xorg Project Team
URL: https://bugs.edge.launchpad.net/ubunt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-13 20:49 UTC by Bryce Harrington
Modified: 2009-02-03 17:55 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.vga.works.log (60.57 KB, text/plain)
2009-01-13 20:51 UTC, Bryce Harrington
no flags Details
Xorg.0.hdmi.fail.log (9.35 KB, text/plain)
2009-01-13 20:51 UTC, Bryce Harrington
no flags Details
Xorg.0.DVI.fail.log (9.35 KB, text/plain)
2009-01-13 20:51 UTC, Bryce Harrington
no flags Details
Xorg.0.log with debugmode set to true. (17.40 KB, text/x-log)
2009-01-25 09:04 UTC, Jeremy Lucier
no flags Details
lshw dump (14.71 KB, text/plain)
2009-01-25 09:14 UTC, Jeremy Lucier
no flags Details
please try the patch, thanks. (1.50 KB, application/octet-stream)
2009-01-31 22:34 UTC, MaLing
no flags Details
Xorg - post svdo patch. (6.34 KB, text/x-log)
2009-02-01 12:30 UTC, Jeremy Lucier
no flags Details
Xorg.0.log - latest pull - working (120.95 KB, text/x-log)
2009-02-03 16:28 UTC, Jeremy Lucier
no flags Details

Description Bryce Harrington 2009-01-13 20:49:52 UTC
Forwarding this bug from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/289883

[Problem]
This hardware boots display on VGA port ok, but neither the HDMI nor DVI port seem to be detected according to Xorg.0.log, and so X fails to boot, with the error "no screens found".

[System Environment]
-- chipset:  i946gz
-- system architecture: i686
-- xf86-video-intel:  both 2.5.1 and 2.4.1 tested and affected
-- xserver:  1.5.2 (2:1.5.2-2ubuntu3)
-- kernel:  2.6.27-7-generic
-- Linux distribution:  Ubuntu Jaunty
-- Display connector:
-- Monitor:  Asus VK222H monitor (22" widescreen)

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82946GZ/PL/GL Memory Controller Hub [8086:2970] (rev 02)
	Subsystem: ASUSTeK Computer Inc. Device [1043:81ea]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02)
	Subsystem: ASUSTeK Computer Inc. Device [1043:81ea]

[Reproducing steps]
1.  Boot up
2.  After usplash, when gdm attempts to show the login screen, X generates these errors:
- (EE) intel(0): No valid modes.
- (EE) Screen(s) found, but none have a usable configuration.

[Additional info]
* VESA driver works okay
* Worked in Hardy (-intel 2.2.x)
* Checked for LVDS disablement quirks in -intel - none found for this HW
Comment 1 Bryce Harrington 2009-01-13 20:51:11 UTC
Created attachment 21964 [details]
Xorg.0.vga.works.log
Comment 2 Bryce Harrington 2009-01-13 20:51:27 UTC
Created attachment 21965 [details]
Xorg.0.hdmi.fail.log
Comment 3 Bryce Harrington 2009-01-13 20:51:42 UTC
Created attachment 21966 [details]
Xorg.0.DVI.fail.log
Comment 4 Wang Zhenyu 2009-01-13 23:28:44 UTC
Logs are for intel 2.4.1, which doesn't have support for integrated HDMI/DVI. 
Please attach log for at least 2.5.1 with ModeDebug. Could you try 2.5.99.2 too?
Comment 5 Bryce Harrington 2009-01-14 09:57:20 UTC
The user reported that the issue still exists for 2.5.1.  He did not provide Xorg.0.log however.
Comment 6 Michael Fu 2009-01-18 23:19:48 UTC
(In reply to comment #5)
> The user reported that the issue still exists for 2.5.1.  He did not provide
> Xorg.0.log however.
> 

Bryce, please help introduce the bug reporter here. The latest update he posted to Ubuntu uses VESA driver... I don't see any log using 2.5.1 from him..
Comment 7 Bryce Harrington 2009-01-21 22:17:35 UTC
http://launchpadlibrarian.net/21300876/Xorg.0.log
Comment 8 Michael Fu 2009-01-21 22:46:05 UTC
(In reply to comment #7)
> http://launchpadlibrarian.net/21300876/Xorg.0.log
> 

yeah, I know, that's what I mean he is using vesa driver. will the bug reporter be able to show up here?
Comment 9 Bryce Harrington 2009-01-21 22:57:48 UTC
Hi Wang Zhenyu,

Ah.  You can see my encouragements for the reporter to join here, but beyond that I have little control so can't say.

Do you know of the LP/BZ plugin?  I think it could help avoid the problem we're in at the moment:

https://help.launchpad.net/Bugs/BugzillaPlugin
Comment 10 Wang Zhenyu 2009-01-21 23:32:53 UTC
sorry, no idea about LP bug plugin, maybe Gordon will know better with bugzilla.

We still need X log with ModeDebug for intel driver to know why those outputs not working.
Comment 11 Jeremy Lucier 2009-01-22 04:43:38 UTC
Hey guys, let me know which Xorg.0.log you need.  The following one is what just occurred on boot up while using the latest test packages referenced back in our launchpad thread (before reverting back to vesa to login).

http://launchpadlibrarian.net/21534330/Xorg.0.log
Comment 12 Michael Fu 2009-01-23 19:18:59 UTC
Jeremy Lucier, pls add Option "ModeDebug" "True" to the device section of your xorg.conf, then paste the xorg log. thanks.
Comment 13 Michael Fu 2009-01-23 19:22:08 UTC
and, please tell us what's the model your motherboard or machine you are using. 946GZ is too general. thanks.
Comment 14 Jeremy Lucier 2009-01-25 09:04:38 UTC
Created attachment 22227 [details]
Xorg.0.log with debugmode set to true.
Comment 15 Jeremy Lucier 2009-01-25 09:14:27 UTC
Created attachment 22228 [details]
lshw dump

I'm running the base Asus Nova P22 media PC (specs seem hard to find for it).  

So, graphics: 82946GZ/GL Integrated Graphics Controller
Motherboard: Asus P2P5B1-DHS
Comment 16 Jeremy Lucier 2009-01-28 15:30:45 UTC
Please let me know if you need further information.
Comment 17 MaLing 2009-01-31 22:34:14 UTC
Created attachment 22429 [details]
please try the patch, thanks.

hi Jeremy Lucier
From Xorg log, we can see sdvo device is not found.
Could you try the patch, which is forced to find sdvo device. after runing it, please paste xorg log file.

Thanks
Ma Ling
Comment 18 Jeremy Lucier 2009-02-01 12:30:23 UTC
Created attachment 22439 [details]
Xorg - post svdo patch.

I ran the patch against the latest git clone of the xf86-video-intel driver.  Throws up an error on-load stating that there's a driver error.  It compiled fine during the make process, so nothing wrong there.
Comment 19 MaLing 2009-02-01 17:44:11 UTC
(In reply to comment #18)
> Created an attachment (id=22439) [details]
> Xorg - post svdo patch.
> I ran the patch against the latest git clone of the xf86-video-intel driver. 
> Throws up an error on-load stating that there's a driver error.  It compiled
> fine during the make process, so nothing wrong there.
hi Jeremy,
I found the log is not true, it shows Xorg don't run normally.
log file in comment #14 says driver detect SDVO device, but log from comment #18 didn't run the same position, nor give us corresponding message.

Thanks
Ma Ling  
Comment 20 Michael Fu 2009-02-01 18:38:58 UTC
Jeremy Lucier, I googled the machine and found there is no HDMI port on the machine. What do you mean of using HDMI also fail? Do you use a DVI-to-HDMI adapter?
Comment 21 Jeremy Lucier 2009-02-01 18:56:33 UTC
It's a DVI->HDMI adapter, but it doesn't work DVI to monitor either.  I'll recompile the driver tomorrow and hopefully that will give us a valid log output.
Comment 22 Michael Fu 2009-02-01 19:00:18 UTC
ok. in this case, HDMI == DVI for us. The HDMI in the title is a bit misleading. I just remove it.
Comment 23 Jeremy Lucier 2009-02-01 19:03:31 UTC
Correct. I'll get the fixed up log asap.
Comment 24 Michael Fu 2009-02-03 05:47:20 UTC
(In reply to comment #23)
> Correct. I'll get the fixed up log asap.
> 

also please double check ling's comment in comment# 19... double check every step you used to apply the debug patch and build the driver. It shouldn't break the xserver and your updated log doesn't prove it's hit that point, either...
Comment 25 Jeremy Lucier 2009-02-03 05:52:05 UTC
(In reply to comment #24)
> (In reply to comment #23)
> > Correct. I'll get the fixed up log asap.
> > 
> 
> also please double check ling's comment in comment# 19... double check every
> step you used to apply the debug patch and build the driver. It shouldn't break
> the xserver and your updated log doesn't prove it's hit that point, either...
> 

Yeah, it was odd seeing it dump out like that considering the build went successfully.  I'll do a full pull from git tonight (about 8 hours from now), patch it, and build the driver again.  
Comment 26 Michael Fu 2009-02-03 06:15:54 UTC
Please also help to test if you get rid of this line in i830_i2c.c

    OUTREG(GMBUS0, 0);

(test without ling's patch)

thanks.
Comment 27 Jeremy Lucier 2009-02-03 16:28:42 UTC
Created attachment 22554 [details]
Xorg.0.log - latest pull - working

Well, I did a full git pull, and did another compile.  Loaded up, and like magic the newest driver started working like a champ!  Looks like the latest upstream driver fixes the issue.  I've attached the Xorg.0.log and rebooted.  It works both under DVI, as well as DVI->HDMI.

So, would you guys like me to run the patch as well as that last requested change?  (I'm guessing not, but perhaps it's of value to you?)
Comment 28 Michael Fu 2009-02-03 17:52:24 UTC
though it's a bit strange to see your sdvo device is detected as HDMI, I'm close it for now as it works for you. may need your help to do some testing later.. thanks.
Comment 29 Jeremy Lucier 2009-02-03 17:55:07 UTC
Sounds good, let me know if you ever need some testing done.  Thanks for the hard work everyone :)


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.