Re: [SLE] KDM shutdown: messages are invisible
![](https://seccdn.libravatar.org/avatar/dde14ae637ae8f7452e3a6cf286272fc.jpg?s=120&d=mm&r=g)
Yannis Zikos wrote:
Works fine only in 2D, you won't have 3D acceleration (only software GL), nv is included in Suse, the only thing you have to do is to change an entry in /etc/X11/XF86Config from "nvidia" to "nv" (under the section Driver - I think). For me GL acceleration is much more important, so I just used yast to switch from Kdm to gdm login
I discovered another disadvantage of the combination of KDM and the accelerated nvidia drivers: once you've logged in, you can no longer switch to any other virtual console (e.g., Alt-Ctl-F2). It does seem surprising that the problem would show up with one login manager but not a different one. I wonder if the flaw lies in the NVidia drivers or in KDM. Paul Abrahams
![](https://seccdn.libravatar.org/avatar/d3bb859347f167d19af78e6fe4782c78.jpg?s=120&d=mm&r=g)
* Paul W. Abrahams
It does seem surprising that the problem would show up with one login manager but not a different one. I wonder if the flaw lies in the NVidia drivers or in KDM.
It's the NVidia drivers. I cannot shift to the console after using that driver, even though I startx from runlevel 3 on a system without KDE. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
![](https://seccdn.libravatar.org/avatar/7ce72c46b6ab41ad3bb822a75c7ea410.jpg?s=120&d=mm&r=g)
How come I can? I can with my Diamond Viper 770..it works fine. The only
thing I have run into with nVidia or XFree86 4.X.X is that after I
upgraded to 4.0.3 .. Quake3 stopped working and kills X everytime. I was
told to get the latest drivers from nVidia, but this didn't help. Every
other 3D game I have works ..but not Q3A. Weird huh?
* Mads Martin Jørgensen (mmj@suse.com) [010330 16:07]:
=>* Paul W. Abrahams
![](https://seccdn.libravatar.org/avatar/a60e63cedec3ebb432651aeacbd7acf9.jpg?s=120&d=mm&r=g)
I had the same problems: invisible logout messages. Plus quirky behavior. I switched to the nv driver with no 3D and it works fine. During the install there is a message warning about the use of the nVIDIA driver for 3D. Basically nVIDIA is no hurry to produce a good driver. Here is an excerpt from file:/usr/share/doc/packages/nv_glx/NVIDIA_Linux.html (on your computer): 6.5 Known Bugs TNT Cards We have gotten some reports that the X Server locks up when starting with some TNT cards. This appears to be due to a wrong bios loaded on the card by the manufacturer. We are working on a more transparent fix for the problem, but in the meantime have provided a user workaround. Please read the file TNT_USERS_README for more information, included in the NVIDIA_GLX package (the NVIDIA_GLX RPM will install the file in /usr/doc/NVIDIA_GLX/). So some of our cards may have the wrong BIOS loaded on them. That may be why they work so bad. -- Cheers, Jonathan
![](https://seccdn.libravatar.org/avatar/7ce72c46b6ab41ad3bb822a75c7ea410.jpg?s=120&d=mm&r=g)
=> => So some of our cards may have the wrong BIOS loaded on them. That may be why =>they work so bad. => Or why in my case the card works fine. It might be good to check out the site of the company that made the cards and see if they have a different bios revision the cards could be flashed with. I know Diamond has flashable video card bios. -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
![](https://seccdn.libravatar.org/avatar/a60e63cedec3ebb432651aeacbd7acf9.jpg?s=120&d=mm&r=g)
More Happy News:
From file:/usr/share/doc/packages/nv_glx/TNT_USERS_README (on your cpmputer)
TNT USERS NVIDIA Release 0.9-3 This driver should correct the problem we've had relating to SGRAM/SDRAM TNT cards. There is the rare chance, however, that your video card has the wrong bios installed, and that this driver will continue to fail for you. Another solution according to the README's is this: - disable TURBO AGP MODE in the BIOS. (That is your computers BIOS not the graphics card BIOS). Personally I have tried these things and I think the card or it's software drivers are poorly designed. -- Cheers, Jonathan
![](https://seccdn.libravatar.org/avatar/acf92fa3f6414dfe1f86279d9979b5ec.jpg?s=120&d=mm&r=g)
Hi, Since upgrading to 4.0.3 shifting to console works for me. As for Q3, I have no problems so far. Only some random pieces of the screen flashing with the geforce DDR when playing in mode depth 32 bit, texture 32 bit trilinear, highest texture details. I don't have these with the geforce Ultra. I installed the latest .gz drivers. Cheers, Filip. Le Samedi 31 Mars 2001 02:14, vous avez écrit :
How come I can? I can with my Diamond Viper 770..it works fine. The only thing I have run into with nVidia or XFree86 4.X.X is that after I upgraded to 4.0.3 .. Quake3 stopped working and kills X everytime. I was told to get the latest drivers from nVidia, but this didn't help. Every other 3D game I have works ..but not Q3A. Weird huh?
* Mads Martin Jørgensen (mmj@suse.com) [010330 16:07]: =>* Paul W. Abrahams
[Mar 30. 2001 16:03]: =>> It does seem surprising that the problem would show up with one login =>> manager but not a different one. I wonder if the flaw lies in the =>> NVidia drivers or in KDM. => =>It's the NVidia drivers. I cannot shift to the console after using that =>driver, even though I startx from runlevel 3 on a system without KDE. => =>-- =>Mads Martin Joergensen, http://mmj.dk =>"Why make things difficult, when it is possible to make them cryptic and =>totally illogic, with just a little bit more effort." => -- A. P. J. => =>-- =>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 FAQ at http://www.suse.com/support/faq =>
![](https://seccdn.libravatar.org/avatar/a60e63cedec3ebb432651aeacbd7acf9.jpg?s=120&d=mm&r=g)
Hi Paul:
I discovered another disadvantage of the combination of KDM and the accelerated nvidia drivers: once you've logged in, you can no longer switch to any other virtual console (e.g., Alt-Ctl-F2).
It does seem surprising that the problem would show up with one login manager but not a different one. I wonder if the flaw lies in the NVidia drivers or in KDM.
The flaw is probably in the nVIDIA driver; supposedly it was fixed. Look: 2000-08-30 version 0.95 * Improve XFree86 4.0.1 support * re-fixed console switch lockup <snip> This is from file:/usr/share/doc/packages/nv_glx/NVIDIA_Changelog (on your computer) -- Cheers, Jonathan
participants (5)
-
Ben Rosenberg
-
filip
-
Jonathan Drews
-
Mads Martin Jørgensen
-
Paul W. Abrahams