udippel
April 29th, 2009, 06:40 AM
Firstly: Thanks to a really great 9.04! It runs on my desktop at office and home; as well as on my Acer Aspire One; beautifully!
I had a harrowing experience with my office desktop, though, when I plugged my high-end CRT IBM P260 instead of the cheap monitor used for install.
It would start - and do nothing. No keyboard, no mouse, low resolution. After a forced reboot ('Reset'-button), all I would get was a black, dead screen. Also, all recovery options would not make any difference, neither 'fix x', nor even going to root and nvidia-xconfig. All would result in a black screen and a number of pressing the hard Reset. No Xorg, no Xorg -configure.
The last and only resort: plug back that cheapo install monitor, for which another nvidia-xconfig was needed. Then I saved the xorg.conf there, plugged my IBM P260 after a restart, and finally I could work up my way by editing that xorg.conf, with Horiz (30-121) Vert (50-160), finally metamode to 1600x1200, with intermediate reboots for testing, and now I am at the usual 1600x1200 85 Hz. And the keyboard layout is still wrong.
Long story, short end: I guess Ubuntu/Xorg needs to better cater for situations when the monitor cannot be probed. There seems to be no proper fallback in case of something like
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
(II) NVIDIA(0): NVIDIA GPU GeForce 6200 TurboCache(TM) (NV44) at PCI:2:0:0
(II) NVIDIA(0): (GPU-0)
(actually, the 6200 is there only, because the NVIDIA-driver is broken for IGP 8300, but that's not a story for ubuntu forums).
That's a complete show stopper for anyone with less experience when plugging the 'wrong' monitor! Somehow I wonder if this is worth a bug report?
Uwe
I had a harrowing experience with my office desktop, though, when I plugged my high-end CRT IBM P260 instead of the cheap monitor used for install.
It would start - and do nothing. No keyboard, no mouse, low resolution. After a forced reboot ('Reset'-button), all I would get was a black, dead screen. Also, all recovery options would not make any difference, neither 'fix x', nor even going to root and nvidia-xconfig. All would result in a black screen and a number of pressing the hard Reset. No Xorg, no Xorg -configure.
The last and only resort: plug back that cheapo install monitor, for which another nvidia-xconfig was needed. Then I saved the xorg.conf there, plugged my IBM P260 after a restart, and finally I could work up my way by editing that xorg.conf, with Horiz (30-121) Vert (50-160), finally metamode to 1600x1200, with intermediate reboots for testing, and now I am at the usual 1600x1200 85 Hz. And the keyboard layout is still wrong.
Long story, short end: I guess Ubuntu/Xorg needs to better cater for situations when the monitor cannot be probed. There seems to be no proper fallback in case of something like
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
(II) NVIDIA(0): NVIDIA GPU GeForce 6200 TurboCache(TM) (NV44) at PCI:2:0:0
(II) NVIDIA(0): (GPU-0)
(actually, the 6200 is there only, because the NVIDIA-driver is broken for IGP 8300, but that's not a story for ubuntu forums).
That's a complete show stopper for anyone with less experience when plugging the 'wrong' monitor! Somehow I wonder if this is worth a bug report?
Uwe