Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Stefan Smietanowski]

Hi.

> when I upgraded to 2.4.14, I found that console-switching doesn't work
> anymore with the latest NVIDIA driver installed. When I try to return
> to the console from X11 the system simply hangs (this includes
> shutdown, which makes it a real problem). Reverting to 2.4.13 fixed
> things. Sorry I can't report more hints.

Report the error to NVidia, it's their module and they don't distribute 
the source. It's difficult to help since the bug might be in their code.

// Stefan

kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Michael N. Lipp]

Hello,

when I upgraded to 2.4.14, I found that console-switching doesn't work
anymore with the latest NVIDIA driver installed. When I try to return
to the console from X11 the system simply hangs (this includes
shutdown, which makes it a real problem). Reverting to 2.4.13 fixed
things. Sorry I can't report more hints.

Regards,

    Michael

Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[François Cami]

Michael N. Lipp wrote:

> Hello,
> 
> when I upgraded to 2.4.14, I found that console-switching doesn't work
> anymore with the latest NVIDIA driver installed. When I try to return
> to the console from X11 the system simply hangs (this includes
> shutdown, which makes it a real problem). Reverting to 2.4.13 fixed
> things. Sorry I can't report more hints.

Are you using framebuffer ? A friend of mine had exactly the same
problem, and it went away when he disabled the framebuffer...

François

Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Alvaro Lopes]

On Sáb, 2001-11-17 at 17:45, Michael N. Lipp wrote:
> Hello,
> 
> when I upgraded to 2.4.14, I found that console-switching doesn't work
> anymore with the latest NVIDIA driver installed. When I try to return
> to the console from X11 the system simply hangs (this includes
> shutdown, which makes it a real problem). Reverting to 2.4.13 fixed

Well I have the same kind of problem. But you don't have to shutdown!
Just switch again to your X vt, and X should work again.

> things. Sorry I can't report more hints.
> 
> Regards,
> 
>     Michael
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re[2]: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Matt Cahill]

  I actually just upgraded to 2.4.13 and have been experiencing this
  problem also. I get 'Waiting for X server to shutdown', forcing me
  to reboot. I reloaded the Nvidia kernel again (no problems with
  that), but the GLX driver is coughing and spitting when I try to
  reinstall it. It can't seem to find or read
  /usr/X11R6/lib/module/nvdriver.o (filename may be a little
  different...sorry, I'm in Windows right now), but it's there. This
  is also nvidia version 1541 (latest stable).

AL> Well I have the same kind of problem. But you don't have to shutdown!
AL> Just switch again to your X vt, and X should work again.

  I'm not sure I follow this... how do I switch to an X vt, and how do
  you mean 'X should work again'? Just curious if you meant this as a fix or
  a work-around.

  Thanks for any info,

  Matt Cahill
m-cahill@home.com

Re: Re[2]: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Alvaro Lopes]

On Dom, 2001-11-18 at 16:42, Matt Cahill wrote:
> 
>   I actually just upgraded to 2.4.13 and have been experiencing this
>   problem also. I get 'Waiting for X server to shutdown', forcing me
>   to reboot. I reloaded the Nvidia kernel again (no problems with
>   that), but the GLX driver is coughing and spitting when I try to
>   reinstall it. It can't seem to find or read
>   /usr/X11R6/lib/module/nvdriver.o (filename may be a little
>   different...sorry, I'm in Windows right now), but it's there. This
>   is also nvidia version 1541 (latest stable).
> 
> AL> Well I have the same kind of problem. But you don't have to shutdown!
> AL> Just switch again to your X vt, and X should work again.
> 
>   I'm not sure I follow this... how do I switch to an X vt, and how do
>   you mean 'X should work again'? Just curious if you meant this as a fix or
>   a work-around.

First of all this problems seem to be fixed in 2.4.15-pre5 with Nicholas
Aspert i8xx AGP patch. (one or another or both are responsable - didn't
test :) )

This is a work-around of course. Try CTRL+ALT+F7 (vt07 is the default XT
vt). 
BTW. what do you mean by "Waiting for X server to shutdown" ? Does this
appear when you reboot or when you switch consoles ?

Alvie

> 
>   Thanks for any info,
> 
>   Matt Cahill
> m-cahill@home.com
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Aric Cyr]

I have been running 2.4.14 since it came out and it works fine.  Try
running with/without the linux kernel agpgart.  That is, try it with the
nVidia agp driver and with the kernel agpgart to see if that may be
the problem.  If you need help you can ask people on IRC at
irc.openprojects.net, channel #nvidia.

RE: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[PVotruba]

Hi,
Please try to be more specific. Do you use VGA textmode console or NVidia
console framebuffer? I had also some freezes due to console framebuffer,
after returning closing X - the command line never appeared again. Try to
use only textmode console, NVidia framebuffer is currently in EXPERI-MENTAL
state :)

Regards,
Petr


> -----Původní zpráva-----
> Od:	Michael N. Lipp [SMTP:MNL@MNL.de]
> Odesláno:	17. listopadu 2001 18:46
> Komu:	linux-kernel@vger.kernel.org
> Předmět:	kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching
> 
> Hello,
> 
> when I upgraded to 2.4.14, I found that console-switching doesn't work
> anymore with the latest NVIDIA driver installed. When I try to return
> to the console from X11 the system simply hangs (this includes
> shutdown, which makes it a real problem). Reverting to 2.4.13 fixed
> things. Sorry I can't report more hints.
> 
> Regards,
> 
>     Michael
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Lionel Bouton]

PVotruba@Chemoprojekt.cz wrote:

>Hi,
>Please try to be more specific. Do you use VGA textmode console or NVidia
>console framebuffer? I had also some freezes due to console framebuffer,
>after returning closing X - the command line never appeared again. Try to
>use only textmode console, NVidia framebuffer is currently in EXPERI-MENTAL
>state :)
>
Very experimental on my box, it broked hard the last time I tried (SMP 
2.4.13-ac7) on my config :
lockup on first X -> fb console switch , SysRq worked for 
sync/umount/reboot, didn't tried blind "killall X" in initlevel 5 though 
(so X restart not tested).
If the maintainer wants some testing on a SMP with a Geforce2 MX, with 
every single partition reiserfs or ext3 mounted I can afford reboots now 
(130 GB on 4 IDE drives weren't especially fast to fsck)...

Re: kernel 2.4.14 breaks NVIDIA-1.0-1541 console switching

[Emiliano Garcia]

On Tue, 20 Nov 2001, Lionel Bouton wrote:

> 
> 
> PVotruba@Chemoprojekt.cz wrote:
> 
> >Hi,
> >Please try to be more specific. Do you use VGA textmode console or NVidia
> >console framebuffer? I had also some freezes due to console framebuffer,
> >after returning closing X - the command line never appeared again. Try to
> >use only textmode console, NVidia framebuffer is currently in EXPERI-MENTAL
> >state :)
> >
> Very experimental on my box, it broked hard the last time I tried (SMP 
> 2.4.13-ac7) on my config :
> lockup on first X -> fb console switch , SysRq worked for 
> sync/umount/reboot, didn't tried blind "killall X" in initlevel 5 though 
> (so X restart not tested).
> If the maintainer wants some testing on a SMP with a Geforce2 MX, with 
> every single partition reiserfs or ext3 mounted I can afford reboots now 
> (130 GB on 4 IDE drives weren't especially fast to fsck)...
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


This is interesting, I've been having the same problem. However, in my 
struggle to fix this blatant hang I've disabled my nvidia driver, 
disabled glx, dri, and framebuffer, only to find that with the stock XFree 
4.0.3 and 4.1.0 nv driver I can't logout halt, control-alt-backspace or 
switch to a console without hanging the machine. No signs of what is 
amiss, it hangs at a hardware level. Since I've removed the NVidia driver 
I can safely say it's not the cause of the hang (at least in my case). I'm 
going to try going back to a 2.4.3 or so kernel to see if that helps, that 
is if my volume survives another few fscks without completely messing 
everything up.

I'm running an Athlon XP 1800+ with a geforce 2 pro ddr, AMD 761 
northbridge chipset with VIA southbridge. Linux-2.4.15-pre6. Any knowledge 
about this is greatly appreciated. 

A week ago I was running a P3 1GHz with an 815 chipset, the same setup, 
and it was ticking along perfectly. I have a feeling it's something to do 
with this chipset, but like I said I'm not even loading agpgart now and it 
still freezes.

Symptom: halt, logout, or console switch hangs linux with a hard lock.