Re: nVidia driver problem on Linux
These are the drivers that we are running - the latest available from your web site. You aren't talking to your average everyday normal users here.. we know our stuff :-) This is repeatable, and is happening on any computer that runs KDM + nVidia drivers with a GeForce2 based machine. You can imagine how many of them there are. It has something to do with KDM and the nVidia drivers. If you run in init level 3 / console mode, they seem to work fine, because the respawning of the X session doesn't happen like in KDM. But by using KDM, and logging in/out a few times, and then trying to switch to virtual terminal mode with ctrl-alt-F1, F2, F3, etc, will pretty much freeze your computer entirely, unless you have the ability to telnet/ssh in from some other computer and reboot it remotely. You know how often Linux people like to reboot ;^) Let me know if I can be of any help. Thanks, Steven On Monday 04 June 2001 05:46 pm, Andrew Ritger wrote:
Greetings, Steven.
Can you try just booting to console (usually init level 3) and seeing if the problems go away? Also, I've attached updated drivers that seem to fix the problem for us. Can you let us know if your problems go away with them? Please don't distribute these drivers... I just want to confirm that the bug is fixed. Another public release will come out in the next couple weeks.
Thanks, - Andy Ritger
On Mon, 4 Jun 2001, Steven Hatfield wrote:
On Friday 01 June 2001 02:01 pm, Andrew Ritger wrote:
Greetings, Steven.
Could you send us the details of your system (motherboard, video card type, etc...)? We haven't been able to reproduce this in house. Also, if you could find out the system specs of any other users you're aware of that are having this problem, it would be useful to know what's similar or different about the systems that exhibit this.
Thanks, - Andy Ritger
Oh, and could you check to see if this same behavior occurs if you're not using KDM? (ie set your run level to 3 and just do startx)
On Fri, 1 Jun 2001, Steven Hatfield wrote:
Hi, I am having a problem with the nVidia drivers on linux. It appears that when I hit ctrl-alt-F1-F6 while in an X Session, my system locks up, and my screen goes blank. If I use the 'nv' driver that comes with my distribution (SuSE 7.1 Pro), the lock up doesn't happen. Running the "nvidia" driver + GLX results in a very fast system, with great 3D Acceleration. It's just this bug that is getting in the way of a perfect experience.
Also, when I exit out of KDE2 to KDM, and choose "reboot" or "halt", the screen goes all weird, and I see "movement", and then my system finally reboots. If I choose "Exit to Console", I get the same lockup as I get when I press ctrl-alt-Fx.
I am using the latest nVidia driver from your website, v1.0-1251. This problem was also apparent in the last v0.9-769.
On the SuSE-Linux-E users mailing list, there are several other people who have the same problem, so this isn't just my system.
Good luck, and I hope this helps. Let me know if you need any further information.
Thanks, Steven
Ok, I've recieved about 10 emails about this, from different list members. It appears to be a KDM<->nVidia driver problem. Ben Rosenberg reports that he runs in console mode, starting X with "startx", and doesn't have any problems. Anyone else running KDM has problems. The setup seems to be any number of CPU choices, and a GeForce2 based card, running SuSE 7.0/7.1 with the latest KDE2.1.2.
I can generate this error pretty much on demand, so if you need a guinnea pig for testing, just let me know.
Let me know if you need any further information... and please keep me informed.
Thanks, Steven
---------------------------------------- Content-Type: APPLICATION/octet-stream; charset="us-ascii"; name="NVIDIA_kernel-1.0-1251.tar.gz" Content-Transfer-Encoding: BASE64 Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: APPLICATION/octet-stream; charset="us-ascii"; name="NVIDIA_GLX-1.0-1251.tar.gz" Content-Transfer-Encoding: BASE64 Content-Description: ----------------------------------------
Just an FYI. I have the TNT2 based Viper 770 and it happens as well. Even thought I never use KDM..it is a pronouced bug in the driver. I am also using the latest and greatest from the website. * Steven Hatfield (ashari@knightswood.net) [010604 15:19]: ->These are the drivers that we are running - the latest available from your ->web site. You aren't talking to your average everyday normal users here.. we ->know our stuff :-) -> ->This is repeatable, and is happening on any computer that runs KDM + nVidia ->drivers with a GeForce2 based machine. You can imagine how many of them there ->are. It has something to do with KDM and the nVidia drivers. If you run in ->init level 3 / console mode, they seem to work fine, because the respawning ->of the X session doesn't happen like in KDM. But by using KDM, and logging ->in/out a few times, and then trying to switch to virtual terminal mode with ->ctrl-alt-F1, F2, F3, etc, will pretty much freeze your computer entirely, ->unless you have the ability to telnet/ssh in from some other computer and ->reboot it remotely. You know how often Linux people like to reboot ;^) -> ->Let me know if I can be of any help. -> ->Thanks, ->Steven -> ->On Monday 04 June 2001 05:46 pm, Andrew Ritger wrote: ->> Greetings, Steven. ->> ->> Can you try just booting to console (usually init level 3) and seeing if ->> the problems go away? Also, I've attached updated drivers that seem to ->> fix the problem for us. Can you let us know if your problems go away with ->> them? Please don't distribute these drivers... I just want to confirm ->> that the bug is fixed. Another public release will come out in the next ->> couple weeks. ->> ->> Thanks, ->> - Andy Ritger ->> ->> On Mon, 4 Jun 2001, Steven Hatfield wrote: ->> > On Friday 01 June 2001 02:01 pm, Andrew Ritger wrote: ->> > > Greetings, Steven. ->> > > ->> > > Could you send us the details of your system (motherboard, video card ->> > > type, etc...)? We haven't been able to reproduce this in house. Also, ->> > > if you could find out the system specs of any other users you're aware ->> > > of that are having this problem, it would be useful to know what's ->> > > similar or different about the systems that exhibit this. ->> > > ->> > > Thanks, ->> > > - Andy Ritger ->> > > ->> > > Oh, and could you check to see if this same behavior occurs if you're ->> > > not using KDM? (ie set your run level to 3 and just do startx) ->> > > ->> > > On Fri, 1 Jun 2001, Steven Hatfield wrote: ->> > > > Hi, ->> > > > I am having a problem with the nVidia drivers on linux. It appears ->> > > > that when I hit ctrl-alt-F1-F6 while in an X Session, my system locks ->> > > > up, and my screen goes blank. If I use the 'nv' driver that comes ->> > > > with my distribution (SuSE 7.1 Pro), the lock up doesn't happen. ->> > > > Running the "nvidia" driver + GLX results in a very fast system, with ->> > > > great 3D Acceleration. It's just this bug that is getting in the way ->> > > > of a perfect experience. ->> > > > ->> > > > Also, when I exit out of KDE2 to KDM, and choose "reboot" or "halt", ->> > > > the screen goes all weird, and I see "movement", and then my system ->> > > > finally reboots. If I choose "Exit to Console", I get the same lockup ->> > > > as I get when I press ctrl-alt-Fx. ->> > > > ->> > > > I am using the latest nVidia driver from your website, v1.0-1251. ->> > > > This problem was also apparent in the last v0.9-769. ->> > > > ->> > > > On the SuSE-Linux-E users mailing list, there are several other ->> > > > people who have the same problem, so this isn't just my system. ->> > > > ->> > > > Good luck, and I hope this helps. Let me know if you need any further ->> > > > information. ->> > > > ->> > > > Thanks, ->> > > > Steven ->> > ->> > Ok, I've recieved about 10 emails about this, from different list ->> > members. It appears to be a KDM<->nVidia driver problem. Ben Rosenberg ->> > reports that he runs in console mode, starting X with "startx", and ->> > doesn't have any problems. Anyone else running KDM has problems. The ->> > setup seems to be any number of CPU choices, and a GeForce2 based card, ->> > running SuSE 7.0/7.1 with the latest KDE2.1.2. ->> > ->> > I can generate this error pretty much on demand, so if you need a guinnea ->> > pig for testing, just let me know. ->> > ->> > Let me know if you need any further information... and please keep me ->> > informed. ->> > ->> > Thanks, ->> > Steven -> ->---------------------------------------- ->Content-Type: APPLICATION/octet-stream; charset="us-ascii"; ->name="NVIDIA_kernel-1.0-1251.tar.gz" ->Content-Transfer-Encoding: BASE64 ->Content-Description: ->---------------------------------------- -> ->---------------------------------------- ->Content-Type: APPLICATION/octet-stream; charset="us-ascii"; ->name="NVIDIA_GLX-1.0-1251.tar.gz" ->Content-Transfer-Encoding: BASE64 ->Content-Description: ->---------------------------------------- -- Ben Rosenberg mailto:ben@whack.org ----- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin
* Ben Rosenberg <ben@whack.org> (Mon, Jun 04, 2001 at 03:24:29PM -0700)
Just an FYI. I have the TNT2 based Viper 770 and it happens as well. Even thought I never use KDM..it is a pronouced bug in the driver. I am also using the latest and greatest from the website.
More FYI if you check the readme for the latest drivers, and check what they say about the geforce2go (restarting X freezes the machine) then it looks like it's the same problem in a different flavour. Oddly enough, using the 0-967 drivers on a Geforce2Go (which apparently is unsupported) 1) works fine 2) does not have the problem that KDM logout/login freezes your machine 3) doing a CTrl-Alt-FX does require a power cycle though. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical Support Fax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) gdenhollander@jasongeo.com POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON.......#1 in Reservoir Characterization The Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Gerhard den Hollander wrote:
* Ben Rosenberg <ben@whack.org> (Mon, Jun 04, 2001 at 03:24:29PM -0700)
Just an FYI. I have the TNT2 based Viper 770 and it happens as well. Even thought I never use KDM..it is a pronouced bug in the driver. I am also using the latest and greatest from the website.
More FYI if you check the readme for the latest drivers, and check what they say about the geforce2go (restarting X freezes the machine) then it looks like it's the same problem in a different flavour.
Oddly enough, using the 0-967 drivers on a Geforce2Go (which apparently is unsupported) 1) works fine 2) does not have the problem that KDM logout/login freezes your machine 3) doing a CTrl-Alt-FX does require a power cycle though.
Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical Support Fax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1)
gdenhollander@jasongeo.com POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON.......#1 in Reservoir Characterization The Netherlands
This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Not sure if this will help, it might seem slightly offtopic...But.. With SuSE 7.1 the problems that were encountered with the game Heavy Gear 2 returned, despite being listed as fixed. I know this seems offtopic, but its strange that there are issues with KDM (I get them too) and then a bug with HG2 again (identical to the past issues). Hope that helps. Please let us know what exactly we need to give over in terms of helping fix this issue. Matt
participants (4)
-
Ben Rosenberg -
Gerhard den Hollander -
Matthew -
Steven Hatfield