should't I be able to switch between ALT+Ctrl+F1 and ALT+F7

[michaa7]

After switching to ALT+Ctrl+F1 it is *not* possible to switch back to X using Alt+F7.

I don't know what else to explain, I assume it should be possible, but it isn't anymore.

I don't know whether or not todays d-u is the culprit or if it isn't working since some time as I didn't try to switch between console and X for a long time.

What am I missing?

(It's nvidia 304.88, 32 bit)

[dibl]

In my world, it is necessary to use Ctrl+Alt for all ttys including the one at F7.  I didn't know you could do Alt-F7 and get back to X.

[ReinerS]

Well, as I remember it you do need to press CTL+Alt+Fx to switch to Consoles from X. Within consoles Alt+FX whitches and it also brings you back to X when selecting the X-conxole (usually F7, sometimes F8).
LatelyI had some trouble tog et back to X at all. The box did freeze immediately instead. This happened on an laptop with ATI graphics card running the radeon driver.

regards

Reiner

[hschn]

Hello,
did you try Alt+F8?

[ReinerS]

Yes, I did. I mentioned it already but I didn't realize that it was turned into a smily. Should have previewed the post.

regards

Reiner

[farinet]

Did you by chance install the fglrx (catalyst) driver? I had this problem with an old G4 based powerbook and on a very modern Samsung 535UC. In both cases in relation to the fglrx drivers ... Turning back to the standard radeon driver solved it (but brought other problems )

[ReinerS]

No,it was a fresh install no catalyst driver was installed since then on this box.

regards

Reiner

[michaa7]

In my world, it is necessary to use Ctrl+Alt for all ttys including the one at F7.  I didn't know you could do Alt-F7 and get back to X.

I confused myself by runing an update in one tty and a ssh session in an other tty. When I was in the ssh session I tried to switch to X using "ALT+F7" (yes this *is* possible without "Ctrl") not caring about the fact that I did d-u in the other tty by first runing "init 3" and thus killing X. Within the ssh session I wasn't aware of X being killed and therefor did not understand why I ended up in front of a black screen where X was supposed to appear.

So all is well, it just was stupid me.