Re: [SLE] More Nvidia Fun
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start... -ronc On Monday 04 June 2001 10:34, you wrote:
On Monday 04 June 2001 10:23 am, you wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
Change: Driver "nv" to be Drive "nvidia" and that should work.
Good luck! -Steven
--snip--
On Monday 04 June 2001 16:52, Ron Cordell wrote:
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start...
I'm not following this thread really but just wanted to say I have weird behaviour with KDE (maybe with any desktop actually) when I set nvidia instead of nv. When I go to console mode, for example, I got a strange screen.. I can come back to KDE but switching again to console is the same. When I shutdown/restart the computer I keep seeing the X cursor and cannot view the console shutting down sequence. It is not really a problem has I know the system works well, but I'm using consoles quite often and I have to reboot to be able to go to console mode (sometimes the switching problem doesn't occur). That's my story :)) Ju.
-ronc
On Monday 04 June 2001 10:34, you wrote:
On Monday 04 June 2001 10:23 am, you wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
Change: Driver "nv" to be Drive "nvidia" and that should work.
Good luck! -Steven
--snip--
Ya alot of people have complained about this and it's happens to me as well. I've noticed a message when you logout of the gui and get the gui login again, in the console a message states the there's still a "que" for the nvidia driver. I don't the that X is fully released, hence the "still que" message. Nvidia really needs to do something about this. I think I send an e-mail about the bug to them. Cheers. Curtis Rey On Monday 04 June 2001 09:59 am, Julien Biezemans wrote:
On Monday 04 June 2001 16:52, Ron Cordell wrote:
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start...
I'm not following this thread really but just wanted to say I have weird behaviour with KDE (maybe with any desktop actually) when I set nvidia instead of nv. When I go to console mode, for example, I got a strange screen.. I can come back to KDE but switching again to console is the same. When I shutdown/restart the computer I keep seeing the X cursor and cannot view the console shutting down sequence.
It is not really a problem has I know the system works well, but I'm using consoles quite often and I have to reboot to be able to go to console mode (sometimes the switching problem doesn't occur).
That's my story :))
Ju.
-ronc
On Monday 04 June 2001 10:34, you wrote:
On Monday 04 June 2001 10:23 am, you wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
Change: Driver "nv" to be Drive "nvidia" and that should work.
Good luck! -Steven
--snip--
Curtis Rey wrote:
Ya alot of people have complained about this and it's happens to me as well. I've noticed a message when you logout of the gui and get the gui login again, in the console a message states the there's still a "que" for the nvidia driver. I don't the that X is fully released, hence the "still que" message. Nvidia really needs to do something about this. I think I send an e-mail about the bug to them.
According to one message (don't remember who sent it), NVidia has tried, so far unsuccessfully, to reproduce the bug. I'm wondering if it has anything to do with the SuSE distribution. It would be interesting to know if it also happens on a non-SuSE system. Paul
I wouldn't be surprised if it is related to XSuSE server. I don't know anyone who's using another distro, but I can post a message on the Lug in my neck of the woods and see if I get anyfeed back. Cheers, and I'll let everyone know if I find out. Curtis On Monday 04 June 2001 10:46 am, Paul Abrahams wrote:
Curtis Rey wrote:
Ya alot of people have complained about this and it's happens to me as well. I've noticed a message when you logout of the gui and get the gui login again, in the console a message states the there's still a "que" for the nvidia driver. I don't the that X is fully released, hence the "still que" message. Nvidia really needs to do something about this. I think I send an e-mail about the bug to them.
According to one message (don't remember who sent it), NVidia has tried, so far unsuccessfully, to reproduce the bug. I'm wondering if it has anything to do with the SuSE distribution. It would be interesting to know if it also happens on a non-SuSE system.
Paul
Julien Biezemans wrote:
I'm not following this thread really but just wanted to say I have weird behaviour with KDE (maybe with any desktop actually) when I set nvidia instead of nv. When I go to console mode, for example, I got a strange screen.. I can come back to KDE but switching again to console is the same. When I shutdown/restart the computer I keep seeing the X cursor and cannot view the console shutting down sequence.
It is not really a problem has I know the system works well, but I'm using consoles quite often and I have to reboot to be able to go to console mode (sometimes the switching problem doesn't occur).
Join the club! I and several other people have encountered very similar behavior and reported it here. One hint: If you're running the kdm login manager, the behavior is different on first login versus second login. On the very first login, the text consoles are accessible. On subsequent logins, they aren't and you get the odd behavior (which you can escape from with Ctl-Alt-F7). Alas, we'll have to wait for NVidia to fix it. Paul
On Monday 04 June 2001 17:18, Paul Abrahams wrote:
Julien Biezemans wrote:
I'm not following this thread really but just wanted to say I have weird behaviour with KDE (maybe with any desktop actually) when I set nvidia instead of nv. When I go to console mode, for example, I got a strange screen.. I can come back to KDE but switching again to console is the same. When I shutdown/restart the computer I keep seeing the X cursor and cannot view the console shutting down sequence.
It is not really a problem has I know the system works well, but I'm using consoles quite often and I have to reboot to be able to go to console mode (sometimes the switching problem doesn't occur).
Join the club! I and several other people have encountered very similar behavior and reported it here. One hint: If you're running the kdm login manager, the behavior is different on first login versus second login. On the very first login, the text consoles are accessible. On subsequent logins, they aren't and you get the odd behavior (which you can escape from with Ctl-Alt-F7).
Ah yes, I think you're right :) the consoles are accessible right now and it is my first login of this "computer session". What to do? Do we have toall send bug reports to NVidia or are they smart enough to understand with only a few messages? :)) Ju.
Alas, we'll have to wait for NVidia to fix it.
Paul
On Monday 04 June 2001 11:36 am, Julien Biezemans wrote:
On Monday 04 June 2001 17:18, Paul Abrahams wrote:
Julien Biezemans wrote:
I'm not following this thread really but just wanted to say I have weird behaviour with KDE (maybe with any desktop actually) when I set nvidia instead of nv. When I go to console mode, for example, I got a strange screen.. I can come back to KDE but switching again to console is the same. When I shutdown/restart the computer I keep seeing the X cursor and cannot view the console shutting down sequence.
It is not really a problem has I know the system works well, but I'm using consoles quite often and I have to reboot to be able to go to console mode (sometimes the switching problem doesn't occur).
Join the club! I and several other people have encountered very similar behavior and reported it here. One hint: If you're running the kdm login manager, the behavior is different on first login versus second login. On the very first login, the text consoles are accessible. On subsequent logins, they aren't and you get the odd behavior (which you can escape from with Ctl-Alt-F7).
Ah yes, I think you're right :) the consoles are accessible right now and it is my first login of this "computer session". What to do? Do we have toall send bug reports to NVidia or are they smart enough to understand with only a few messages? :))
Ju.
Alas, we'll have to wait for NVidia to fix it.
Paul
I have submitted a bug report to an nVidia engineer on behalf of all of us, and requested to be kept "in the loop". Hopefully we'll see something soon :) -Steven
Julien Biezemans wrote:
On Monday 04 June 2001 17:18, Paul Abrahams wrote:
Join the club! I and several other people have encountered very similar behavior and reported it here. One hint: If you're running the kdm login manager, the behavior is different on first login versus second login. On the very first login, the text consoles are accessible. On subsequent logins, they aren't and you get the odd behavior (which you can escape from with Ctl-Alt-F7).
Ah yes, I think you're right :) the consoles are accessible right now and it is my first login of this "computer session". What to do? Do we have toall send bug reports to NVidia or are they smart enough to understand with only a few messages? :))
The more bug reports they get, the better. At least they'll be convinced that the bug is real and not just in the imagination of one crazed Linuxer. linux-bugs@nvidia.com Paul
I'm guessing the kernel module didn't load properly. If you just installed the rpm for the driver you've more than likely got a version that isn't compiled for your kernel. Either do insmod -f in boot.local, or get the source and compile it for your kernel version Regards Anders On Monday 04 June 2001 16:52, Ron Cordell wrote:
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start...
-ronc
On Monday 04 June 2001 10:34, you wrote:
On Monday 04 June 2001 10:23 am, you wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
Change: Driver "nv" to be Drive "nvidia" and that should work.
Good luck! -Steven
--snip--
On Monday 04 June 2001 10:52 am, Ron Cordell wrote:
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start...
That means that the nvidia driver isn't working properly. My suggestion is to download the tar.gz files from nVidia, and compile/install them. You should be able to use the GLX RPM, and you don't need to run the "switch" script. Good luck! -Steven --snip--
Ron Cordell wrote:
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start...
I wonder -- are you running KDM or some other login manager? I'd suggest booting up with "linux 3" as lilo input to get you into text mode initially. Then you can experiment with startx and see all the interesting messages, even if it doesn't work. You can always call kdm from text mode (as root, of course). Paul
Ya, I am running KDM. I have read in this email list that the nvidia drivers had problems with KDM, and that remains an outstanding issue (among others). I'll experiment as you suggest and see what happens, and await nvidia fixes. As to which RPM's I have downloaded and installed, I downloaded via YAST2, so I assume that SuSE directed me to the SuSE packaged RPMs on the nvidia site. Thanks all, -ronc On Monday 04 June 2001 11:15, you wrote:
Ron Cordell wrote:
I forgot to mention that I *did* change "nv" to "nvidia". When I do that and restart X, I get a garbled screen and the keyboard stops functioning. I have to telnet into the box and reboot it. If I leave the setting and reboot, it appears as if the X Server attempts to start 3 times and fails, because I can see the screen flash between the text and a blank screen before it goes back to the text screen. Changing back to "nv" allows X to start...
I wonder -- are you running KDM or some other login manager? I'd suggest booting up with "linux 3" as lilo input to get you into text mode initially. Then you can experiment with startx and see all the interesting messages, even if it doesn't work. You can always call kdm from text mode (as root, of course).
Paul
Ron Cordell wrote:
Ya, I am running KDM. I have read in this email list that the nvidia drivers had problems with KDM, and that remains an outstanding issue (among others). I'll experiment as you suggest and see what happens, and await nvidia fixes.
As to which RPM's I have downloaded and installed, I downloaded via YAST2, so I assume that SuSE directed me to the SuSE packaged RPMs on the nvidia site.
I don't think that assumption is correct. I'd go to the Nvidia site. You want version 1251 of the drivers, although I remember having a hard time locating it on the site. The correct URL was posted here a while ago but I can't find it. If you have no better luck than I do, you might want to post a query as to the correct path to the 1251 drivers. They don't solve the problem, but they probably do provide about as stable a system as you're going to get with the problem left unsolved. Paul
http://www.nvidia.com/drivers * Paul Abrahams (abrahams@acm.org) [010604 10:47]: ->Ron Cordell wrote: -> ->> Ya, I am running KDM. I have read in this email list that the nvidia drivers ->> had problems with KDM, and that remains an outstanding issue (among others). ->> I'll experiment as you suggest and see what happens, and await nvidia fixes. ->> ->> As to which RPM's I have downloaded and installed, I downloaded via YAST2, so ->> I assume that SuSE directed me to the SuSE packaged RPMs on the nvidia site. -> ->I don't think that assumption is correct. I'd go to the Nvidia site. You ->want version 1251 of the drivers, although I remember having a hard time ->locating it on the site. The correct URL was posted here a while ago but I ->can't find it. If you have no better luck than I do, you might want to post a ->query as to the correct path to the 1251 drivers. -> ->They don't solve the problem, but they probably do provide about as stable a ->system as you're going to get with the problem left unsolved. -> ->Paul -> -> -- Ben Rosenberg mailto:ben@whack.org ----- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Ben Franklin
Cool... they already have the 1251 drivers packaged and ready for SuSE 7.2 weeks before release :-) -tosi Þann mánudagur 04 júní 2001 18:52 skrifaðir þú:
* Paul Abrahams (abrahams@acm.org) [010604 10:47]: ->Ron Cordell wrote: -> ->> Ya, I am running KDM. I have read in this email list that the nvidia drivers ->> had problems with KDM, and that remains an outstanding issue (among others). ->> I'll experiment as you suggest and see what happens, and await nvidia fixes. ->> ->> As to which RPM's I have downloaded and installed, I downloaded via YAST2, so ->> I assume that SuSE directed me to the SuSE packaged RPMs on the nvidia site. -> ->I don't think that assumption is correct. I'd go to the Nvidia site. You ->want version 1251 of the drivers, although I remember having a hard time ->locating it on the site. The correct URL was posted here a while ago but I ->can't find it. If you have no better luck than I do, you might want to post a ->query as to the correct path to the 1251 drivers. -> ->They don't solve the problem, but they probably do provide about as stable a ->system as you're going to get with the problem left unsolved. -> ->Paul -> ->
participants (8)
-
Anders Johansson -
Ben Rosenberg -
Curtis Rey -
Julien Biezemans -
Paul Abrahams -
Ron Cordell -
Steven Hatfield -
Tor Sigurdsson