[Bug 313525]

The reporter answered these questions in comment 2. The logs in the downstream bug indicates it broke between xserver 1.4.0.90 and 1.5.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/313525 Title:

[Bug 148117]

Yes, this is still the same on Ubuntu 10.10 which has xserver 1.9.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/148117 Title: [r128] Rage 128: Unsuitable videomode autoselected To manage

[Bug 1083032]

Can you please try savage driver version 2.3.7? It looks like it is already in Arch Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083032 Title: Video driver not working for Savage chipset

[Bug 1225320]

Thanks for your report and fix. This has been committed to git now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1225320 Title: Unresolved symbol in savage_drv.so To manage notifications about

[Bug 1083032]

Have you tried without any xorg.conf? You have two device sections in your configuration, I don't understand why. The last working configuration from comment 11 simply switches to EXA, which is the default now. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1083032]

Musikolo, please attach (no pastebin) your new Xorg.0.log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083032 Title: Video driver not working for Savage chipset To manage notifications about

[Bug 1083032]

I have committed a couple of fixes to the savage driver repository. One problem was that the driver, even when built for an xserver without XAA support, would internally default to XAA instead of EXA nonetheless. Secondly there was an EXA function that needed an update for recent xservers. This

[Bug 1083032]

Simply using EXA (and a 1.14 fix backported to 1.13) worked for me. Maybe more is broken in 1.14. What exactly happens in your case? Please be more specific than does not work. There is no schedule for such bug fixes, most developers do not care about hardware which is more than a few years old.