[i945] doesn't detect CRT monitor

Bug #337648 reported by bsh
4
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Hello
i'm using ubuntu 8.04.2 on an asus eee box 202 with intel gma945. the box is running completely headless as a home server. the only time i was using a monitor and a keyboard with it was when i installed ubuntu on it, since then it is running with vnc and ssh.
yesterday there were some updates, i noticed there were new restricted drivers too.
after the update the system rebooted, and i could not connect to it anymore.
so i took a spare crt monitor and a keyboard, connected to the box, and i saw, that when it tries to start the xserver, it fails. switches the monitor on/off every 5 seconds. i assume it tries to use a display mode or refresh that is out of range.
digging out the xorg logs, i saw the reason: "SDVO reports failed to sync" (or something) so it apparently doesn't thetect the monitor or just ignores the ddc/edid info and tries to use a bad display mode.
i was using a dvi->vga adapter, since the monitor has a vga (dsub) connector and the box only has a dvi conector.
the driver reports the card is dual monitor capable, which is probably true for this chipset, but not for this computer: it only has one dvi connector.
i remember when i was installing ubuntu, i used a lcd flat display, it didn't work either: the driver didn't detect the proper resolution and refresh. furthermore, it was thinking, it is a dual monitor setup and was detecting the connected dispaly as secondary...

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
 Subsystem: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Unknown device [1043:1252]

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi bsh,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in xserver-xorg-video-intel:
status: New → Incomplete
Revision history for this message
bsh (bsh) wrote :
Revision history for this message
bsh (bsh) wrote :

unfortunatelly, i have deleted the old xorg logs, and the current log is clean, sinc i'm now using vesa driver to make the computer work at all, and therefore xorg.conf is basically a copy of the corg.conf.failsafe, uninteresting i think.
i'll revert the xorg.conf to the default and do a reboot when i can, and post the log.

Geir Ove Myhr (gomyhr)
description: updated
Revision history for this message
Carey Underwood (cwillu) wrote :

bsh, can you apply the recent updates and retest the intel driver?

tags: added: gma950
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → New
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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