Re: Consoles inaccessible w/ Ctl-Alt-FN
Jumping in here with a longshot (especially considering I only got 3 hrs
sleep last night - treat this advice accordingly)
With the fact that it "locks" when doing C-M-F1 (and, I'm assuming, for any
other F-key), I wonder if it's a problem with X switching to the framebuffer
(if you're using a fb console...) I know mine takes about a 1/2 second to a
second to "resync" to the console (Both running @ 1024x768, FB is vesa, X is
4.0.2 ati)
While you're in the "locked" condition, is the terminal active (even though
you can't see anything)? Try logging in blind and touching a file...
<C-M-F1>
<username><enter>
<password><enter>
touch XYZZY<enter>
...then switching back to X (C-M-F7) and seeing if the file is there...
If it is, it's obviously a conflict between X and whatever console you're
using -- if it's a framebuffer, try using the "normal" one (vga=normal in
lilo.conf) and see if that helps. If you're using the normal one...I dunno.
If you DON'T start X (IE: you don't go through x/k/gdm) can you switch
terminals? If not, I don't think it's GNOME...might start looking into the
console-* packages to see if there's anything amiss.
-b3
On Mon, Apr 23, 2001 at 09:01:34AM +0100, Etienne Grossmann wrote:
> According to 'xev', my 'alt' is 'Alt_L', which I would say is
> ok. The left 'Windows' is 'Select' and the right one is
> 'Mode_switch'. Neither C-Left_Windows-F1 nor C-Right_Windows-F1
> changes to console.
>
> I forgot to say that when I do C-M-F1, the terminal "freezes" : the
> mouse and keyboard have no apparent effect, except that C-M-F7
> restores control over the terminal.
>
> I guess I'll try to install the usual gnome. The problem is that apt
> only sees the helix packages. I'll see if removing the 'extra' cd from
> the sources.list does the trick.
Reply to: