VT's don't work when switched to from X

ptero · Apprentice Joined: 02 Mar 2007 Posts: 164

I've got a strange bug on a newly set up box. When i try to switch to a VT from X, I get a black screen with a blinking cursor. No matter, what VT and if switched with Ctrl+Alt+Fx or with chvt x. Before starting X or after killing it, i cann access all my VTs without a problem
My setup: kernel-2.6.27-r6, xorg-server-1.5.3., xorg-x11-7.4, nvidia-drivers-177.82.
xorg.conf: http://pastebin.ch/740
Xorg.0.log: http://pastebin.ch/741

ptero · Apprentice Joined: 02 Mar 2007 Posts: 164

hmmmmh, very interesting... i dist-upgraded my fluxbuntu to intrepid out of interest and get the same problem. those are the same xorg and nvidia-driver versions... so, it kinda seems to be the new xorg's bug.

ptero · Apprentice Joined: 02 Mar 2007 Posts: 164

all right, by screwing around with different kernels, nvidia-drivers and xorg-versions i found out, that it seems to be a problem of new xorg. with the old one all nvidia-driver-versions work without blocking VT's, with the new one all driver versions "block" them.
and if it wasn't strange enough, here's something what make me shout "FTW???" in my head

:
in ubuntu VTs get completely messed up after killing x - the screen gets grey, at the positions where cursor "went" i get black vertical lines. sometimes strange "psychedelic" (

) symbols appear on the gray area. anyway, i accidentally deleted my backup xorg.conf, so i had to copy one over from gentoo. however, what i forgot, was that my mouse-id differs in ubuntu and gentoo by one character, so the mouse didn't work first. as i killed x, however, the VT was perfectly normal! after couple of tries i found out that even though VTs still don't work while mouse doesn't, VTs only get messed up after killing x while mouse works.
so it made me kinda think, that the whole problem may be caused by the new hal/fdi hardware handling thing. i guess, i'll contact nvidia and ask them about that whole matter, because everything works perfectly well with nv, so it seems, nvidia still uses some X-function(s), which was(were) recently changed and don't work completely correctly anymore...