[i945] shuttle X50/intel 945 "No outputs definitely connected" (needs intel 2.7.1)

Bug #375545 reported by Arsinio
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Using a Shuttle X50 with built-in monitor.

When starting X, it falls back to failsafe mode using VESA. From the best I can tell, X can't tell there is a monitor attached. I thought it might be an EDID problem with the monitor, but `get-edid` seems to reporting the monitor just fine.

Ubuntu 9.04

`apt-cache policy xserver-xorg-video-intel:`
xserver-xorg-video-intel:
  Installed: 2:2.6.3-0ubuntu9
  Candidate: 2:2.6.3-0ubuntu9
  Version table:
 *** 2:2.6.3-0ubuntu9 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Xorg.conf:
Section "Device"
        Identifier "Intel Integrated Video"
        Driver "intel"
        VendorName "Intel Corporation"
        BoardName "82945G/GZ Integrated Graphics Controller"
        BusID "PCI:0:2:0"
EndSection

Section "Monitor"
        Identifier "AUO:ec10"
        VendorName "AUO"
        ModelName "AUO:ec10"
        Mode "1366x768"
            DotClock 72.000000
            HTimings 1366 1414 1446 1486
            VTimings 768 771 775 806
            Flags "-HSync" "-VSync"
        EndMode
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "AUO:ec10"
        Device "Intel Integrated Video"
        DefaultDepth 24
        SubSection "Display"
            Depth 1
            Modes "1366x768"
        EndSubSection
EndSection

Section "ServerFlags"
        Option "DontZap" "false"
EndSection

Xorg.log:
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux rna-ocu 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686
Build Date: 09 April 2009 02:10:02AM
xorg-server 2:1.6.0-0ubuntu14 (<email address hidden>)
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
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: Tue May 12 12:03:17 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "AUO:ec10"
(**) | |-->Device "Intel Integrated Video"
(**) Option "DontZap" "false"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
        Entry deleted from font path.
(==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
        built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
        If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x3bc0
(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 5.0
        X.Org XInput driver : 4.0
        X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7

(--) PCI:*(0@0:2:0) Intel Corporation 82945G/GZ Integrated Graphics Controller rev 2, Mem @ 0xfdf00000/524288, 0xd0000000/268435456, 0xfdf80000/262144, I/O @ 0x0000ff00/8
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
        [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 1.13.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 2.6.3
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 5.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ,
        965GM, 965GME/GLE, G33, Q35, Q33,
        Mobile Intel® GM45 Express Chipset,
        Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
        [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) resource ranges after probing:
        [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
        [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
        [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
        [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
        [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.6.0, module version = 0.1.0
        ABI class: X.Org Video Driver, version 5.0
(II) intel(0): Creating default Display subsection in Screen section
        "Default Screen" for depth/fbbpp 24/32
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945G
(--) intel(0): Chipset: "945G"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xFDF00000
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(==) intel(0): Using EXA for acceleration
(II) intel(0): 2 display pipes available.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA using monitor section AUO:ec10
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): No SDVO device found on SDVOB
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
(II) intel(0): Resizable framebuffer: not available (1 3)
(II) intel(0): Output VGA disconnected
(WW) intel(0): No outputs definitely connected, trying again...
(II) intel(0): Output VGA disconnected
(WW) intel(0): Unable to find initial modes
(EE) intel(0): No valid modes.
(II) UnloadModule: "intel"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/xorg/modules//libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

`get-edid | parse-edid`:
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
        Function supported
        Call successful

        VBE version 300
        VBE string at 0x11110 "Intel(r) 82945G Chipset Family Graphics Chip Accelerated VGA BIOS"

VBE/DDC service about to be called
        Report DDC capabilities

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
        Function supported
        Call successful

        Monitor and video card combination does not support DDC1 transfers
        Monitor and video card combination supports DDC2 transfers
        0 seconds per 128 byte EDID block transfer
        Screen is not blanked during DDC transfer

Reading next EDID block
VBE/DDC service about to be called
        Read EDID

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
        Function supported
        Call successful

parse-edid: EDID checksum passed.

        # EDID version 1 revision 3
Section "Monitor"
        # Block type: 2:0 3:f
        # Block type: 2:0 3:fe
        # Block type: 2:0 3:fe
        Identifier "AUO:ec10"
        VendorName "AUO"
        ModelName "AUO:ec10"
        # Block type: 2:0 3:f
        # Block type: 2:0 3:fe
        # Block type: 2:0 3:fe
        # DPMS capabilities: Active off:no Suspend:no Standby:no

        Mode "1366x768" # vfreq 60.114Hz, hfreq 48.452kHz
                DotClock 72.000000
                HTimings 1366 1414 1446 1486
                VTimings 768 771 775 806
                Flags "-HSync" "-VSync"
        EndMode
        # Block type: 2:0 3:f
        # Block type: 2:0 3:fe
        # Block type: 2:0 3:fe
EndSection

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:3151]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02)
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:3151]

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

This problem seems to be because of your xorg.conf. I'm not sure if it is a misconfiguration or if the driver is misenterpreting it. Anyway, what happens if you remove/rename your xorg.conf?

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Also, please upload the output of the command `lspci -vvnn` as an attachment (not in the comment itselft).

Revision history for this message
Arsinio (arsinio) wrote :

Geir,
Thank you for your response! I'd venture to say there is an underlying problem somewhere, the ubuntu installation CD couldn't start X properly either, and fell back into safe mode. I wound up installing in text mode thinking there was just some configuration file tweaking needed...

Here is the output of trying to start without an xorg.conf

Revision history for this message
Arsinio (arsinio) wrote :

Here is the output of lspci -vvnn:

Geir Ove Myhr (gomyhr)
tags: added: 945g intel jaunty no-screens xorg
summary: - shuttle X50/intel 945 "No outputs definitely connected"
+ [i945] shuttle X50/intel 945 "No outputs definitely connected"
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Geir Ove Myhr (gomyhr) wrote : Re: [i945] shuttle X50/intel 945 "No outputs definitely connected"

You're right, this is not about the xorg.conf. For some reason, the driver only checks the VGA connection, and does not find anything there. Normally, built in monitors are connected via an LVDS connection. In this case, the chipset is a 945G (not 945GM - which is the mobile version normally used in laptops). I haven't seen a computer with a non-mobile intel chipset and and a built in monitor before[*].

I wonder if the monitor is connected using LVDS, but since the driver sees that it is a non-mobile chipset, it simply assumes there is nothing there (I'm not even sure if the non-mobile chipsets have LVDS possibility, but let's assume it has for now). In this case, the telling the driver explicitly to use LVDS may help. If this is the case, we may quirk the driver to do this for this particular computer.

First, I would like you to add a minimal xorg.conf by running `dpkg-reconfigure -phigh xserver-xorg` and then add the line
Option "ModeDebug" "true"
to the "Device" section (or you can get a ready-made file from http://launchpadlibrarian.net/26665729/xorg.conf).
This will add a lot of extra information to Xorg.0.log the next time you start. Please upload this Xorg.0.log.

Next, I would like to know if the log from the failsafe session tells us anything interesting. By adding the line
  Driver "vesa"
to the "Device" section of xorg.log, that should use the generic vesa driver which is the same as what the failsafe option does. Please also upload the log for this case.

Finally, try to enable the LVDS explicitly in your xorg.conf. I'm not very familiar with the details for how to do this, but I guess following the "Ignore LVDS Quirk" at
https://wiki.ubuntu.com/X/Quirks#Ignore%20LVDS%20Output%20Quirk
should give the basic syntax, except that instead of
Option "Ignore" "True"
you should use
Option "Ignore" "False"
As I said, I'm not sure this is the right way to do it but hey, it just might work. If it does, it should be possible to add a quirk to the driver.

[*] Usually the problem is the other way around: A mobile chipset is used in a PC without a built-in monitor on the LVDS, and the driver implicitly assumes that all mobile chipsets have something attached to their LVDS.

Revision history for this message
Arsinio (arsinio) wrote :

Here is the log from the minimal xorg.conf with the 'Option "ModeDebug" "true"':

Revision history for this message
Arsinio (arsinio) wrote :

Here is the log from the minimal xorg.conf with debug and the driver set to VESA. An interesting thing to note is that the VESA driver does detect the monitor correctly and displays the EDID information in the log file...

Revision history for this message
Arsinio (arsinio) wrote :

Here is the log from explicitly enabling LVDS...no luck there either, in fact, I don't really see anything in the log file to indicate that it did anything different at all. Could this option possibly only be enabled for the mobile chipsets?

On a side note, I really appreciate your effort and fast responses!

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

I can't find anything in those logs that tells me what is going on. I think we should report this upstream. To make sure it is not something they have fixed already, you should test a newer driver. If it is still there, we report it upstream with the logs from the newer drivers. You have two options:
1. You can test the 2.7.1 driver from the x-updates PPA (Personal Package Archive) at https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/ . This PPA contains updated stable drivers that were released too late to get into jaunty. These packages solve a number of problems, but has a small chance of introducing new ones.
2. You can test the latest driver from the GIT master respository. This is the development version of the driver, and you can get it from the xorg-edgers PPA at https://launchpad.net/~xorg-edgers/+archive/ppa (see also info on https://launchpad.net/~xorg-edgers). This has a much higher chance of breaking something, is maybe a bit more complicated, but will probably make the intel developers a little more happy.

If you can test one of these and upload the Xorg.0.log if it does not fix things, then I can file the bug report upstream. I will then ask you to subscribe to it too in case the intel devs have questions or possible workarounds. You may also file the bug upstream yourself if you want to give it a try. There are instructions at http://intellinuxgraphics.org/how_to_report_bug.html. If you file it yourself, I will subscribe to the upstream bug and be able to help you with any questions.

Revision history for this message
Arsinio (arsinio) wrote :

Looks like your first recommendation fixed it! I added the package archived, downloaded the 2.7.1 driver, and everything seems to be working. Here is the xorg.0.log:

Thanks for your help!

Geir Ove Myhr (gomyhr)
summary: - [i945] shuttle X50/intel 945 "No outputs definitely connected"
+ [i945] shuttle X50/intel 945 "No outputs definitely connected" (needs
+ intel 2.7.1)
Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

I'm glad 2.7.1 solved the problem. Let's not send it upstream then ;-)

Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

We've got newer than 2.7.1 in karmic now, so we can consider this solved in development.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
chrisisbd (chris-isbd) wrote :

I have this problem and, for me, it *isn't* fixed by the 2.7.1 drivers.

Here is the relevant section from my Xorg.0.log file:-

(II) intel(0): Output VGA using monitor section Configured Monitor
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): No SDVO device found on SDVOB
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
(II) intel(0): Output HDMI-1 has no monitor section
(II) intel(0): I2C bus "HDMIDDC_B" initialized.
(II) intel(0): HDMI output 1 detected
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72.
(II) intel(0): No SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): Output HDMI-2 has no monitor section
(II) intel(0): I2C bus "HDMIDDC_C" initialized.
(II) intel(0): HDMI output 2 detected
(II) intel(0): Resizable framebuffer: not available (1 3)
(II) intel(0): I2C device "HDMIDDC_C:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "HDMIDDC_C:ddc2" registered at address 0xA0.
(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.

... and I do have version 2.7.1:-

chris$ apt-cache showpkg xserver-xorg-video-intel
Package: xserver-xorg-video-intel
Versions:
2:2.7.1-0ubuntu1~xup~1 (/var/lib/apt/lists/ppa.launchpad.net_ubuntu-x-swat_x-updates_ubuntu_dists_jaunty_main_binary-amd64_Packages) (/var/lib/dpkg/status)

My system works because (as described in the first report) the first gdm/X using Intel fails completely on console 7 and I get a second one using the vesa drivers on console 9 which works OK (but no Intel acceleration etc.).

Is there anything I can do to help debug this problem and/or any workarounds?

My motherboard is an Asus P5Q-VM with on-board Intel G45/G43 chipset.

Revision history for this message
Ned Taylor (entaylor) wrote :

I had the same problem, and again it wasn't fixed by the 2.7.1 driver.

I had my monitor connected to a KVM switch which was connected to the video output on my machine. I discovered (by accident) that when the monitor was connected directly to the machine the problem went away. The problem turned out to be the cable from the KVM to the machine. When I replaced it everything worked fine. What's weird is that the old cable worked fine for everything else, and once I had started up, I could replace the new cable with the old and everything continued to work fine.

Anyway, I'm now back in business.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.