[Q965] "No screens found"

[Dag-Erling Smørgrav]

Binary package hint: xserver-xorg-video-intel

Lenovo ThinkCentre M55 (8811-92G) with integrated Intel 965Q graphics chipset. Sony 1600x1200 flat panel connected to TMDS-1 with single-link DVI-D cable.

00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02)
 Subsystem: Lenovo Device 1011
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at d0000000 (32-bit, non-prefetchable) [size=1M]
 Memory at c0000000 (64-bit, prefetchable) [size=256M]
 I/O ports at 3400 [size=8]
 Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
 Capabilities: [d0] Power Management version 2

This worked correctly with Hardy (see attached configuration file)

Upgraded from latest Hardy to Intrepid on 2008-10-09, using xserver-xorg-video-intel 2:2.4.1-1ubuntu6.

When run with old xorg.conf (from Hardy), X loads the correct driver, but terminates with "no screens found".
X -configure produces a minimal xorg.conf that works - but only at 1152x864:

% xrandr
Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360
VGA disconnected (normal left inverted right x axis y axis)
TMDS-1 connected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768 59.8
   1152x864 60.0*
   1024x768 60.0
   800x600 60.3
   640x480 59.9

Using the vesa driver, I get full resolution (1600x1200) but obviously no acceleration.

[Dag-Erling Smørgrav (dag-erling)]

The failsafe configuration looks like this:

Section "Device"
        Identifier "Configured Video Device"
        Driver "vesa"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
EndSection

The auto-generated configuration file is the same minus the 'Driver "vesa"' line.

[Geir Ove Myhr (gomyhr)]

From your Hardy xorg.conf I see that you have used the i810 driver. This has been discontinued in Intrepid, so you're now using the intel driver (https://wiki.ubuntu.com/X/Drivers#-intel%20video%20driver). This driver seems to have some problems with some chipsets that worked well with the i810 driver (I have the same resolution problem with intrepid on 915G, see # 273306).

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Have you tried starting X without a configuration file at all? A bare minimum one, not using the vesa driver, should be created for you and I'd be interested to hear how that works. Thanks in advance.

[Dag-Erling Smørgrav (dag-erling)]

Brian, yes - read the bug report.

[Dag-Erling Smørgrav (dag-erling)]

Still marked "incomplete"?

[Bryce Harrington (bryce)]

[This is an automatic notice.]

We'd like to forward your bug upstream, however upstream requires
that you first test it against their newer driver code.

To save you the effort of building the driver from source, we've built
packages for the driver and its new dependencies.

So you have a couple options:

 1. Download and test .debs for intrepid, from:
     https://edge.launchpad.net/~intel-gfx-testing/+archive

 -or-

 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
     (which includes a beta of the new xserver 1.6 as well).
     See http://cdimage.ubuntu.com/releases/9.04/ for ISOs

Thanks ahead of time! You can simply reply to this email to report your
findings.

P.S., if you wish to forward your bug upstream yourself, please follow
these directions to do so:
  http://intellinuxgraphics.org/how_to_report_bug.html

[Dag-Erling Smørgrav (dag-erling)]

No visible improvement.

xrandr reports the same as before:

Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360
VGA disconnected (normal left inverted right x axis y axis)
TMDS-1 connected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768 59.8
   1152x864 60.0*
   1024x768 60.0
   800x600 60.3
   640x480 59.9

Unfortunately, today is the last day I have access to this machine.

[Bryce Harrington (bryce)]

Thanks for testing; this should go upstream. Setting to Triaged for now.

[Geir Ove Myhr (gomyhr)]

Seeing the "0mm x 0mm" part in the xrandr output makes me think that this may be a problem with obtaining the EDID information from the monitor. To check this, one would need Xorg.0.log with
Option "ModeDebug" "true"
in the "Device" section, and the output of `xrandr -verbose`.

Since the computer is no longer available for testing, I guess there is not much we can do unless someone else with a Lenovo ThinkCentre M55 comes around (?)

[Jordi Puigsegur (jordi-puigsegur)]

Hi all,

I just have a similar problem (though with different hardware). I have an ASUS barebone with an Intel video card connected to a Samsung LCD TV. Hardy worked perfectly but when upgrading to Intrepid Xserver crashed and the "no screens found" error appeared in the log.

Since intrepid didn't work I upgraded to Jaunty with the same result.

Currently I am forced to use vesa driver, but with unsatisfactory results (slow refresh, bad resolution, etc.).

I'll gather all information and submit here (or maybe it is better to create a new bug?)

[Geir Ove Myhr (gomyhr)]

Jordi, unless you have the exact same hardware with the exact same symptoms, it is better to file a new bug. You may mention similar bugs in the new bug report.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

It seems likely to me this bug is gone; the -intel driver has improved immensely in Karmic and a lot of bugs are being reported as no longer present. So hopefully that's the case here too.