On Fri, Aug 02, 2002 at 03:37:08PM +0200, Russell Coker wrote: > On Fri, 2 Aug 2002 14:31, Ditch, Derek P., MO-ARNG wrote: > > Using X version 3.x for that card is gonna be a pain. I'd suggest > > using 4.1 and get the custom Savage chip from here > > (http://www.probo.com/timr/savagemx.html). They have a version for 3.x and > > 4.x If you use the 4.x version from xfree86 then you'll get problems with > > system locking up when running some programs like staroffice and other > > large java-based programs (java programs are the only ones I've noticed > > that do this). 4.x is the version that has a common x server with > > different "modules" for different drivers. Hope this helps > > Brian May pointed out to me that one of the X screen savers will also trigger > this, Brian, which one is it?
blaster It locks up X with 4.0.x and 4.1.x. Everytime. Guaranteed. This has been reproduced on other thinkpads (one being a T20 IIRC), but mine is a T21. According to <URL:http://www.probo.com/timr/savage40.html>: "People still report that the "blaster" and "critical" modes for xscreensaver hang. I absolutely cannot reproduce this on my Savage/IX with this driver; both ran happily for hours. " However, with X 4.1.x, switching from X to text mode consoles no longer works properly, so X 4.0.x is better for me. > I solved the problem on my laptop by using the frame-buffer X server and the > VESA frame buffer driver. Brian unfortunately doesn't have this option > because the vesafb driver doesn't support 1400x1050 (I only have a 1024x768 > display which is well supported by vesafb). Actually, I suspect isn't the resolution. Not only did I try other resolutions (which also work find under X), and same setups other people said worked fine, nothing worked (IIRC I get a black screen everytime). (PS. Please CC to me as per the Mail-Followups-To header). -- Brian May <[EMAIL PROTECTED]>
