Thanks, this means that the Karmic savage driver is OK, so you do not need to file a bug for it. The need to set frequency ranges manually is because EDID transfer fail (getting monitor information through the monitor cable), which I do not think is the driver's fault. It is the server's "fault" that the fallback resolution is only 800x600.
The Xorg.0.log.vesa above is actually using savage. You said it tried vesa first, is there an Xorg.0.log.old using vesa? I am not sure the "xforcevesa" thing for "safe mode" works any longer. -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-vesa in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
