MJ,
That did it! 'vesa' worked in place of 'nv'.
Incidentally, 'sax2' still wanted to use 'nv' as its default (so it would crash), but I found a sneaky binary called 'sax2-vesa'. Basically, Sax2 in vesa mode. That allowed me to turn on NVidia's 3D acceleration via Sax2.
Strange. SuSE 8.2/X86Config used 'nv' w/o problems. What exactly is the difference between 'nv' & 'vesa'? How about I throw 'aa' in there and see what happens! ;)
Anyway, much thanks to you, MJ!
Eric Pierce --- MJ Ray mjr@dsl.pipex.com wrote:
On 2003-12-14 00:18:55 +0000 Julie A juliebread@yahoo.com wrote:
SuSE 8.2 (w/my NVidia TNT2 32mB) starts out with
the
'nv' driver, and once I d/l NVidia's driver it
goes
with 'nvidia'. I installed the NVidia driver under 9.0, but
nothing
change for the better.
In my experience, it never does, which is why I asked. I wonder if you can try the "vesa" driver to see if that avoids the locking up. After that, try "vga" as an act of desperation. Given that your network connection seems to work otherwise, I doubt that is the problem. If it still locks up with the vga driver, I'm stumped. Maybe someone who knows SuSE will have some better ideas to try.
-- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
__________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/