On Sunday 06 January 2002 02:37, S.Toms wrote: [...]
I suspect the drivers are causing some problem, but I also suspect the the KDE logout has a problem. I have been debating about going back to the SuSE brand of the drivers until I tried doing a quick logout from KDE by pressing Ctrl+Alt+Shift+Del which seems to exit safetly back to the KDM logon screen.
Well, for me Ctrl+Alt+Shift+Del gives the same crash. However Ctrl+Alt+Backspace brings me back to the KDM logon screen. Great, at least a workaround for now!
The reason I suspect KDE as being part of the problem is that when hitting the logout button or pressing Ctrl+Alt+Del it asks to save the current configuration which I'm skipping with the above key sequence.
Did you try what happens if you logout under Gnome? For me it is exactly the same problem - the same crash just before the KDM logon screen should appear. So at least in my installation it is not a kde specific logout problem, however it could of course be a kdm logon problem. I did not switch off the nvidia logo, so I see it coming up nicely just before the crash. Does anyone know what happens differently at a logout compared to the first login, or the one forced with Ctrl+Alt+Backspace ? Thanks, Matt On Sunday 06 January 2002 02:37, S.Toms wrote:
On Sat, 5 Jan 2002, Matt wrote:
m> Hi all, m> m> I run Suse 7.2 prof with kde2.2.2 and qt2.3.1 on a MSI K7T Turbo RAID m> motherboard with an NVIDIA 2 MX 200 32 MB AGP Graphics Card. RAM is 512 MB. m> X as installed with 7.2 prof. not modified. m> I'm also running SuSE 7.2 professional, with KDE-2.2.1, QT-2.3.1 on an iWill motherboard and a Viper 16 MB graphics card. Ram is at 768MB and nothing has changed with X accept what YOU and yast update would do.
m> Originally I used the nv driver, but, to gain some speed, especially because m> changing the desktops was quite slow, I installed the new nvidia drivers m> NVIDIA_kernel-1.0-2313.suse72.i386.rpm and m> NVIDIA_GLX-1.0-2313.suse72.i386.rpm, using sax2.
The drivers I'm using are the same, installed via YOU
m> m> Then, after switching from nv to the nvidia driver, first no change. desktop m> updates had been as slow as before. X did eat the memory away as before. But m> now, when I log out from kde, the screen freezes with a nice black-white m> stripe pattern. Nothing works, no reaction on any keyboard input. I have to m> hard-reboot. m>
I have noticed this ame thing, accept mine is colored as green and blue stripes. Exiting X via CTRL+Alt+1-6 does nothing. Only options I have are to do a hard reset or to logon through one o the other computers with SSH and do a 'shutdown -r' there. I also tried doing an 'init 3' but nothing happens, it shows X isn't running when I check with top or ps -ax but it appears and acts locks up from the actual workstation.
m> m> My guess is that the nvidia drivers had been installed, but for a special m> reason not used properly at the beginning. The crash did delete something, m> which then allowed the nvidia drivers to really work. But what? m>
I suspect the drivers are causing some problem, but I also suspect the the KDE logout has a problem. I have been debating about going back to the SuSE brand of the drivers until I tried doing a quick logout from KDE by pressing Ctrl+Alt+Shift+Del which seems to exit safetly back to the KDM logon screen. The reason I suspect KDE as being part of the problem is that when hitting the logout button or pressing Ctrl+Alt+Del it asks to save the current configuration which I'm skipping with the above key sequence.
m> It would be fine now, but the crashes after logging out from kde are NOT m> gone, and they surely will cause some damage soon. m> m> So I'm stuck between the crashes at every log out and going back to nv, and m> possibly re-introducing the memory hunger of X, which makes the system m> quickly slow and also forces reboot regularly. m> m> Well, you understand, I would appreciate any ideas and hints to address this m> problem, if possible staying with the nvidia drivers and stopping the m> crashes, and, if that is not possible, to go back to nv but without getting a m> overly memory hungry X again. m> m>