Bug 13598 - No valid modes on Chipset: G33 with HDMI output
Summary: No valid modes on Chipset: G33 with HDMI output
Status: RESOLVED DUPLICATE of bug 13252
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Eric Anholt
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-10 13:13 UTC by Dick Marinus
Modified: 2007-12-11 16:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (31.51 KB, text/plain)
2007-12-10 13:15 UTC, Dick Marinus
no flags Details
xorg.conf (2.24 KB, text/plain)
2007-12-10 13:16 UTC, Dick Marinus
no flags Details

Description Dick Marinus 2007-12-10 13:13:23 UTC
I'm using X.Org X Server 1.4.0 with a cloned git from today.

lspci:
# lspci -s 00:02 -n
00:02.0 Class 0300: 8086:29c2 (rev 02)
00:02.1 Class 0380: 8086:29c3 (rev 02)

The hardware is "Shuttle Barebone SG33G5M iG33"

X fails to start with the following error:

X.Org X Server 1.4.0
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: rPath Linux 
Current Operating System: Linux routi.mrns.nl 2.6.22.13-0.1.smp.pae.gcc3.4.x86.i686 #1 SMP Mon Nov 19 18:19:50 EST 2007 i686
Build Date: 07 December 2007  05:59:05PM
 
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 10 22:12:14 2007
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "mouse" (module does not exist, 0)
(EE) Failed to load module "kbd" (module does not exist, 0)
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(II) Module "ddc" already built-in
(II) Module "i2c" already built-in
(EE) intel(0): No valid modes.
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
Comment 1 Dick Marinus 2007-12-10 13:15:16 UTC
Created attachment 13022 [details]
Xorg.0.log
Comment 2 Dick Marinus 2007-12-10 13:16:02 UTC
Created attachment 13023 [details]
xorg.conf
Comment 3 Dick Marinus 2007-12-10 13:19:24 UTC
And I'd like to use the HDMI output port.
Comment 4 Gordon Jin 2007-12-11 00:07:45 UTC
This looks very similar to bug#13252, which was just fixed by:

commit e720ae4476c3f986f623ce0f0ab9775b8b9b7e05
Author: Jesse Barnes <jbarnes@jbarnes-mobile.amr.corp.intel.com>
Date:   Mon Dec 10 13:00:14 2007 -0800

    CRT hotplug detection improvements
    
    Patch from Hong Liu.
    
    Fixup CRT detection by making sure the pipe is enabled before CRT
    detection actually occurs.  Fixes bugs Hong was seeing on G35 and other
    machines.

Could you check if you've already included that commit? (It was committed almost the same time you reported this bug) If not, please repull.

btw, is this issue specific to HDMI? Did you have chance to try VGA or DVI?
Comment 5 Dick Marinus 2007-12-11 05:29:41 UTC
I've repulled xf86-video-intel and now my VGA output works!

(II) intel(0): Output configuration:
(II) intel(0):   Pipe A is on
(II) intel(0):   Display plane A is now enabled and connected to pipe A.
(II) intel(0):   Pipe B is off
(II) intel(0):   Display plane B is now disabled and connected to pipe B.
(II) intel(0):   Output VGA is connected to pipe A

and:

chosen: dotclock 31500 vco 2520000 ((m 105, m1 17, m2 8), n 2, (p 80, p1 8, p2 10))

But the HDMI output (I suppose Pipe B) is still off and I can't enable it by using xrandr.
Comment 6 Gordon Jin 2007-12-11 16:57:46 UTC
Good to know VGA works. So I'm marking the original issue duped with #13252.

Please file a new bug for the HDMI issue, though I'm not sure if it's implemented yet. keithp is working on that.

*** This bug has been marked as a duplicate of bug 13252 ***


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.