It can be seen in the log that X started with the "vesa" driver - the one used by "failsafe mode", instead of the debug savage driver. I don't know why, it worked fine with my own savage laptop. Well, I now included the debug stuff in the new xserver-xorg-video-savage 2.2.1+git20081230 .aea0496f-0ubuntu0tormod2 in my PPA (for Jaunty), please try that one instead of the one I attached.
The vesa driver falls back to reasonable default sync ranges, that's why it comes up in 848x600. Yes, the user switcher will be confused when using startx, nothing to worry about. What did you use for "trying to switch screen modes"? The "Screen Resolution" preferences? Can you please attach the output from "xrandr --verbose"? Maybe we need to file a vesa bug about that "0 Hz" you saw here. Or the vesa information in the card bios is broken... -- No signal with Samsung SyncMaster 750s and ProSavage8 https://bugs.launchpad.net/bugs/294899 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
