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
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 SD
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
--
[i945] shuttle X50/intel 945 "No outputs definitely connected" (needs intel
2.7.1)
https://bugs.launchpad.net/bugs
** Description changed:
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 wit
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
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Triaged
--
[i945] shuttle X50/intel 945 "No outputs definitely
** Summary changed:
- [i945] shuttle X50/intel 945 "No outputs definitely connected"
+ [i945] shuttle X50/intel 945 "No outputs definitely connected" (needs intel
2.7.1)
--
[i945] shuttle X50/intel 945 "No outputs definitely connected" (needs intel
2.7.1)
https://bugs.launchpad.net/bugs/375545
6 matches
Mail list logo
