[dundee] Hardy Heron unstable with NVIDIA proprietary drivers

[Lee Hughes]

This why device drives that run in kernel mode are a really bad idea....

Both NT(VaxVms) and The Unix way of doing things is fatally flawed....

A Device driver crash should not take the whole system with it...

I'm not sure what debug options are available to the nvidia drivers, 
might be a good idea to enable them and see if anything shows up.

What happens when you but the system under high X server stress,
like games or benchmarking? same thing?




Andrew Clayton <andrew at digital-domain.net> wrote: On Sun, 8 Jun 2008 17:57:16 +0100, Simon Wells wrote:

> Hi Dave,
> 
> Should have mentioned that there weren't any problems withNVIDIA  
> proprietary and Gutsy on the same machine which made me wonder
> whether it might be a Hardy specific problem. Not really eager to get
> to the bottom of this was just curious whether anybody else had
> experienced similar. It is the first time I have experienced hard
> lockups of this type with a Linux box, I thought Linux was not
> supposed to do that.

Your right, it's not, but when you load MB's of binary gunk into your
kernel... all bets are off. I have used the nvidia binary drivers long
ago in the past and got constant lockups.

Today my graphics card of choice is a Radeon 9200/9250, solid open
source driver support. If I was looking at a new machine, I'd seriously
consider on board Intel graphics as that's where all the cool stuff is
happening with kernel mode setting etc.

> Simon

Andrew

_______________________________________________
dundee GNU/Linux Users Group mailing list
dundee at lists.lug.org.uk  http://dundee.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/dundee
Chat on IRC, #tlug on dundee.lug.org.uk


       
---------------------------------
Sent from Yahoo! Mail.
A Smarter Email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.lug.org.uk/pipermail/dundee/attachments/20080610/9fedc547/attachment.html