Today i noticed that Ctrl+Alt+Fn does not work in X any more (i can't switch into vt outside X), is that a new "feature" in udev or some new bug in nvidia drivers, or something else that i'm not aware of?

_________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

Last edited by Kollin on Thu Mar 14, 2013 9:04 pm; edited 2 times in total

It was x11-drivers/nvidia-drivers-304.84, i masked it and now everything is fine _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

It was x11-drivers/nvidia-drivers-304.84, i masked it and now everything is fine

Kollin I too am experiencing this on my ~amd64 laptop. Once the new Nvidia driver loads it refuses to allow any framebuffer graphics. If I Ctrl+Alt+Fn I can no longer get a vt console, nor when I log out of X can I get one either (just a blank screen). Furthermore, Tuxonice no longer works, as the computer hibernates properly, but without any graphic displays indicating progress (also just a blank screen) and at shutdown all of my framebuffer splash screens vanish in the same way.

I'm going to file a bug report on this on gentoo bugzilla, but my guess is this is an upstream issue. I'll post back with that information for others to join in that thread.

However, I think that you shouldn't mark this thread as being solved, because you didn't really solve the problem just masked and temporarily postponed it. This is because these newer Nvidia drivers (304.84) are the first (and only) to support the new Xorg-1.14 API for those of us with "legacy" cards. It may not be an issue now because of using an older xorg-server, but it will be a serious issue when xorg-server-1.14 eventually hits the stable arches.

However, I think that you shouldn't mark this thread as being solved, because you didn't really solve the problem just masked and temporarily postponed it. This is because these newer Nvidia drivers (304.84) are the first (and only) to support the new Xorg-1.14 API for those of us with "legacy" cards. It may not be an issue now because of using an older xorg-server, but it will be a serious issue when xorg-server-1.14 eventually hits the stable arches.

I encourage you or anyone else with this issue to chime in here and on that thread.

Hmm, i think you are correct. I will change the title again
I'm going to follow the bug report also. _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

For the last month or so I've been having similar "blank screen when switching to terminal" issues, except I'm using ati-drivers. Looking at my package.mask file, the problem occurs on 13.2_beta7, 13.3_beta2, and 13.3_beta3, and I've kept going back to 13.1, since that seems to be the last release that doesn't have the problem. I have no idea if the problem is solvable on my end or if I just have to hope somebody at AMD realizes there's a problem, and hope that it gets solved soon. Given my experience with how Portage is maintained, I'm sort of surprised 13.1 is still in the repo.

_________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I don't remember exactly when it was the last time I accessed the virtual terminal, but I am sure it wasn't long ago.

Unfortunately I just reinstalled Gentoo on my system recently (and I have accessed the virtual terminals since then even with nvidia-drivers) so I cannot simply check and reverse any recent modification I made since there is a lot I did in the last two weeks (it took so much because I had an out-of-home vacation in between the process); therefore I have to ask if anyone is aware of something else in specific that may interfere with the virtual terminals.

Thanks in advance.

Update 2
Solved. In my case it was the g15daemon that was interfering; killed it and now I can easily access the virtual terminals.