switch from X to any tty freezes the macine

[CraigG4C]

The latest Nv driver -- as of 5 Oct 07 -- shows the same problem on my machine -- gentoo 2007. Downgrading to an older driver isn't an option with the 2.6.23-rcX kernels, since the older drivers won't compile with the latest kernels.

I strongly doubt that this is a hardware-specific problem, since my machine is an ancient dual-P3 with an only-slightly-less-ancient FX5300 card.

The problem occurs not only with the latest -rcX kernels but also with any earlier versions; everything on my machine is compiled with vesafb-tng.

(Sorry I can't be more specific about versions; I'm posting this from the [gasp!] Win2k side of the machine.]

[weak-ling]

Still not fixed in 100.14.23.

[Ghodmode]

I can confirm that the bug still exists with driver version 100.14.23 in Kubuntu Gutsy (Linux v2.6.22).

All graphical applications seem to work fine. I am using the special effects provided by Compiz. When I try to switch to any virtual terminal (CTRL-ALT-F1 - CTRL-ALT-F6), the screen goes blank and the monitor's power light blinks to indicate that there is no signal.

However, after reading through some of the older messages in this thread, it seems that installing svgatextmode has fixed the problem. I didn't even configure it, I just installed it with apt-get.

It occurs to me that there might still be a problem. I haven't tried any higher-resolution settings. This very basic VGA mode serves my needs well enough because I usually only use the virtual terminals for troubleshooting or messing with X.

-- Ghodmode

[gabriele75]

bug still there but fading effect changes every version

[r_posix]

For what it's worth, I have this problem too.

I've been able to narrow it down to a problem with digital connections. I don't run into the black terminal problem when I use the analog connector.

[oakld]

Same problem.
http://www.nvnews.net/vbulletin/showthread.php?t=100564
Picture:
http://www.sub-club.org/images//screen.jpg

[moment]

I have this problem too. Disabling frame buffer or using vesafb-tng or not using quiet kernel and vga=normal options did not help. I have this problem with the latest drivers 100.14.23 and 100.14.19 but not with 1.0.9639.

[CraigG4C]

A further note -- the problem occurs with the new (100 series) drivers with either vesafb or vesafb-tng and any kernel. It's not actually a machine freeze, in my case at least; it's just that the console screen isn't restored properly. If, though, I exit X normally, get the dead black screen, and type (blind) "reboot", linux behaves properly but with no display.

This does not occur with the 9755 driver; everything is tickety-boo with either framebuffer and any kernel. But the driver doesn't compile under the 2.6.24-rcX kernels -- I did manage to charm 9755 into compiling under .23 by changing the number of args to kmem_cache_create in nv-linux.h, but things get much hairier in .24.

[huiii]

confriming from here, black-screen when hiting ctrl+alt+F1 or any other attempts to switch over to VT...
i am running ubuntu gutsy and nvidia go6600 with driver vers 9639.
ANY SOLUTIONS?
thanks in advance

[huiii]

I FOUND A SOLUTION! this might help others too:
it seems in most cases not nvidia-related, specially if you installed ubuntu gutsy. it looks like somebody forgot to add the fbcon in startup scripts.
have a look here:
https://bugs.launchpad.net/ubuntu/+s...ls/+bug/129910

here, this works for me!!!:::

ubuntu gutsy framebufer fix for switching to VT:

1. sudo gedit /etc/initramfs-tools/modules

add following lines:

fbcon
vesafb

2. sudo update-initramfs -u

3. sudo gedit /etc/modprobe.d/blacklist-framebuffer

change the line "blacklist vesafb" to "# blacklist vesafb"

4. sudo sh -c "echo 'fbcon' >>/etc/initramfs-tools/modules"

5. sudo gedit /boot/grub/menu.lst

this line should look like this (for 1280x800 resolution screen)

# defoptions=quiet vga=773 splash



it works perfect.
hope for u too.

[moment]

I'm glad you managed to get around it but I have CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FB_VESA with vesa-tng support built into my kernel and I'm experiencing this issue.

[ctheo]

Originally Posted by huiii

I FOUND A SOLUTION! this might help others too:
it seems in most cases not nvidia-related, specially if you installed ubuntu gutsy. it looks like somebody forgot to add the fbcon in startup scripts.
have a look here:
https://bugs.launchpad.net/ubuntu/+s...ls/+bug/129910

here, this works for me!!!:::

ubuntu gutsy framebufer fix for switching to VT:

1. sudo gedit /etc/initramfs-tools/modules

add following lines:

fbcon
vesafb

2. sudo update-initramfs -u

3. sudo gedit /etc/modprobe.d/blacklist-framebuffer

change the line "blacklist vesafb" to "# blacklist vesafb"

4. sudo sh -c "echo 'fbcon' >>/etc/initramfs-tools/modules"

5. sudo gedit /boot/grub/menu.lst

this line should look like this (for 1280x800 resolution screen)

# defoptions=quiet vga=773 splash



it works perfect.
hope for u too.

the proposed workaround does not fix the corrupted framebuffer bug after start x with my graphics card