I can sort of confirm this bug. I have got an S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02), which according to Xorg.0.log is a "Twister PN133", Chip: id 8d01.
On a Dapper install, the savage driver was not used, but the vesa driver was used instead. Now, with the upgrade to xorg 7.1.1 in edgy, the slowness of vesa became unbearable, so I started using the savage driver -which, BTWis also not loaded for my laptop when using Knot3, still vesa is used. Now when I started using the savage driver, the maximum resolution I could use was 800x600, which on a 1024x768 laptop screen is not the best, I have to say. All 1024x768 modes in Xorg.o.log were dropped because of them being out of range I got the driver to work at a 1024x768 resolution by explicitly specifying hsync and vrefresh in xorg.conf: VertRefresh 55-61 HorizSync 31.5-80 What are your hsync and vrefresh ranges? What do the "Monitor" and "Device" sections of your xorg.conf look like? ** Attachment added: "My modified xorg.conf" http://librarian.launchpad.net/4439457/xorg.conf -- can't use 1024x768 with savage driver in edgy (vrefresh out of range) https://launchpad.net/bugs/60762 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
