[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-e
Subject:    Re: [SLE] Suse 8 - nvidia beware!
From:       Rick Green <rtg () mich ! com>
Date:       2002-05-04 4:00:54
[Download RAW message or body]

On Fri, 3 May 2002, dids wrote:

> Bad
> Got a spare drive out for my 2xPIII, sblive, orinoco silver, nvidia gforce2mx,
> usb intellimouse
> install v speedy.
>
> Reboot, to no mouse ! eh

 Sounds similar to my experience.  AMD K62-500 w/nVidia Geforce2 MX.  SAX
detected and set up the card OK.  I selected my monitor, and
1280x960x24bpp.  At reboot, KDM starts up, but the mouse cursor is
transparent.  However, 'fishing blindly' around the screen, I realize it's
there somewhere, and the buttons work appropriately.

I posted this several days ago, and from one response, and some searching
on the SDB, I added 'option "sw_cursor" ' to the Device section of
XF86Config.

That made my cursor appear, so now I thought I could proceed.  I set up
kinternet, logged in, and immediately ran YOU.
  Amazing, isn't it, how many patches and replacement packages there are
just a week after the distribution is published?  This is not a complaint
- The folks at SuSE are never satisfied, and keep on working long after
the CD images are frozen for production.  Other companies would sit back
once it's 'out the door', and let the customers find the remaining bugs
for them.

  Well, just as with SuSE 7.2, the nvidia drivers aren't current, and YOU
redirects me to an nvidia site for nvidia_GLX and nvidia_kernel. (1 meg
each! slow at 28,8k.)
  I wait for all the packages to install, reboot, and startx, thinking I'd
bring it up once before re-editing XF86Config to try removing the
sw_cursor.
  OOPS, here's one case where the cure is worse than the cold.  X started,
the bottom two parts of the KDE splash screen appeared, and the mouse,
keyboard, and display froze up solid.
 (By 'bottom two parts' I mean:  The dark bar with the status message
appears, with ...interprocess communication' in a garbled font, and the
row of icons just above it appears.  The large image of the gears does not
appear at all.)
  I was able to ssh into the machine from my laptop, but killing all the X
and KDE related tasks did not free up the main display.  I ended up
killing one too many things, and locked up the whole machine.
  ...a reboot and try it again.  Yup, it's repeatable.  This time when I
ssh in from the laptop, I simply `shutdown -h now`.

I'm trying to blame this on the nvidia drivers, but I noticed that YOU
also updated kde_base, so this lockup might be a kde problem instead...

One other thing noted:  the original nvidia driver off the CD didn't
present a splash screen at startup, while the updated one did.

I'll keep posting what I learn from the process.  I'd love to hear what
others are experiencing, too!

Rick Green


-- 
To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com
For additional commands send e-mail to suse-linux-e-help@suse.com             
Also check the archives at http://lists.suse.com     


[prev in list] [next in list] [prev in thread] [next in thread]