Re: [SLE] KDM shutdown: messages are invisible
Yannis Zikos wrote:
Bet you have an NVidia Card, using nvidia drivers Same thing happened to me, I switch to gdm, shutdowns now fine, though I prefer kdm.
When I first installed 7.1, I noticed that when I did a shutdown from the graphical login manager KDM (which 7.1 installs by default), the X window terminated and I saw the normal sequence of shutdown messages in a text window (virtual terminal 1, I presume). But at some point as I was updating my system (alas, I don't know when), the behavior changed: now I get an immovable cursor on the screen until the computer actually shuts down, and no visible messages. Presumably the X server is still alive and controlling the screen but not doing anything.
Yannis, you're either wise, psychic, or both. Yes, I do have an NVidia card. I wonder if the behavior depends on which version of the drivers I'm using. Paul Abrahams
Paul W. Abrahams wrote: I tested the version of NVdriver that came with Suse 7.1, Nvidia's drivers 0-9-6, 0-9.767 and 0-9.769, but didn't manage to solve the problem, since there ain't no such a behaviour on both xdm and gdm, probably is some strange behaviour of KDM + Nvidia's drivers (cause opensource nv driver works fine).
Yannis Zikos wrote:
Bet you have an NVidia Card, using nvidia drivers Same thing happened to me, I switch to gdm, shutdowns now fine, though I prefer kdm.
When I first installed 7.1, I noticed that when I did a shutdown from the graphical login manager KDM (which 7.1 installs by default), the X window terminated and I saw the normal sequence of shutdown messages in a text window (virtual terminal 1, I presume). But at some point as I was updating my system (alas, I don't know when), the behavior changed: now I get an immovable cursor on the screen until the computer actually shuts down, and no visible messages. Presumably the X server is still alive and controlling the screen but not doing anything.
Yannis, you're either wise, psychic, or both. Yes, I do have an NVidia card. I wonder if the behavior depends on which version of the drivers I'm using.
Paul Abrahams
-- ________________________________________________________________ Yanzae Zaeko Madman out of this World ________________________________________________________________
Yannis Zikos wrote:
I tested the version of NVdriver that came with Suse 7.1, Nvidia's drivers 0-9-6, 0-9.767 and 0-9.769, but didn't manage to solve the problem, since there ain't no such a behaviour [no shutdown messages]on both xdm and gdm, probably is some strange behaviour of KDM + Nvidia's drivers (cause opensource nv driver works fine).
Where can one find the opensource drivers? Paul Abrahams
lördag 31 mars 2001 00:55 skrev du:
I tested the version of NVdriver that came with Suse 7.1, Nvidia's drivers 0-9-6, 0-9.767 and 0-9.769, but didn't manage to solve the problem, since there ain't no such a behaviour [no shutdown messages]on both xdm and gdm, probably is some strange behaviour of KDM + Nvidia's drivers (cause opensource nv driver works fine).
I have the same problem after installing Nvidia's own driver. I can live with that, what's worse is that I can't use ctrl-shift-F2 or any other combination to get to a loginscreen. Everything is just black. Olle Viksten
More on the subject On my previous machine (Riva TNT) kdm had this behaviour, once I logged in to KDE I could switch to console, once I logged out I couldn't On my current machine (Geforce 2 MX) the same things happen, so I quess the workarounds mentioned on NVdrivers documentations aren't worthy on the current subject, I 'd tried every possible combination on them. Q3A works fine for me with the latest Nvidia Drivers, though any of you having problems will might consider to use switch2nvglx (a script found on SuSE 7.1). Another strange fact is that I couldn't get NVagp to work with my VIA chipset, so I used kernel's agpgart module for this task. ________________________________________________________________ Yanzae Zaeko Madman out of this World ________________________________________________________________
Yannis Zikos wrote:
More on the subject On my previous machine (Riva TNT) kdm had this behaviour, once I logged in to KDE I could switch to console, once I logged out I couldn't On my current machine (Geforce 2 MX) the same things happen, so I quess the workarounds mentioned on NVdrivers documentations aren't worthy on the current subject, I 'd tried every possible combination on them. Q3A works fine for me with the latest Nvidia Drivers, though any of you having problems will might consider to use switch2nvglx (a script found on SuSE 7.1). Another strange fact is that I couldn't get NVagp to work with my VIA chipset, so I used kernel's agpgart module for this task.
A couple of questions: 1. Which variant is Q3A? 2. What exactly was the effect of switch2nvglx? Another interesting observation: because of some unrelated glitches I had to reinstall the driver from the 7.1 CD, along with some other stuff that seemed to come with it. Now the screen hangup has gone away and I have my shutdown messages back, but I haven't tried enabling the 3D option in Sax2. Paul Abrahams
participants (3)
-
Olle Viksten -
Paul W. Abrahams -
Yannis Zikos