maverick: S3 savage (but also with vesa driver): X crash/restart after first switch to console and back, garbaged and unusable screen after second console switch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Hello,
after running Ubuntu on two HP omnibook XE3-GC laptop machines successfully since version 9.04 (with only minor impacts), version 10.10 maverick has a severe problem with X since upgrading from 10.04 lucid. This type of machine has a S3 Savage/MX chip attached via AGP 2x.
Since upgrading, X does no more tolerate any switching to text mode, no matter if caused, for example, by changing to a text console or by energy saving like DPMS or setting the laptop to standby/suspend.
The first switch to text mode after the system has booted still works, but getting back to X afterwards results in an immediate shutdown and restart of X, so at least the session is gone and I am back at the gdm login screen.
If I try to switch to text mode for a second time, the screen gets garbaged, usually filled with little squares in rainbow-like colours, mainly in the colour range from red to orange. In this case there is no way out anymore - I only can try to login blindly n a text console as root and type "reboot", which still works, so the system does not hang.
Please remember that there was NO such problem in 10.04 lucid!
This behaviour can be reproduced with or without an xorg.conf, and it does not matter if I try to switch off DRI, GLX or disable even these modules. Or disable AGP and use PCI initialisation - it makes graphics slow but does not resolve the problem.
As I have two identical machines which show exactly the same behaviour, random hardware failure is NOT an issue.
Please don't hesitate to ask for any further information that is necessary. To me the problem is quite urgent as it makes normal system usage quite impossible.
Best regards,
Hans-Juergen Mauser
summary: |
- S3 savage (but also with vesa driver): X crash/restart after first - switch to console and back, garbaged and unusable screen after second - console switch + maverick: S3 savage (but also with vesa driver): X crash/restart after + first switch to console and back, garbaged and unusable screen after + second console switch |
Changed in xorg (Ubuntu): | |
status: | Incomplete → New |
visibility: | public → private |
visibility: | private → public |
tags: | added: maverick |
affects: | xorg (Ubuntu) → xorg-server (Ubuntu) |
In my case:
Upgrading from Lucid Lynx. After grub and loading screen, the display (an old CRT - AOC Spectrum 4v) lights starts to blinking (a possible warning about Vsync or Hsync out of range.). Testing with an LCD Display (Samsung Syncmaster 510n) shows X working, but with Flickering. Trying to change resolution (from 1024x768 to 800x600), shows the same problem as Hans. X crash, no virtual consoles. Black screen.
Testing with "vesa" X works with the old CRT...on this moment i'm writing from it!
"vesa" it's activated from /etc/X11/xorg.conf - by the way, the CRT it's incorrectly detected. Fixed. Trying with "savage" after the correction, problem still appears. The crash problem with the virtual consoles still continues, even with vesa or savage.
Possibly an xserver-xorg issue?