Re: xorg.conf (WAS: sudden power loss)

[Tommy Trussell <tommy.trussell@gmail.com>]

On 12/2/05, Cedric Pradalier <cedric.pradalier@inrialpes.fr> wrote:

>> > On 12/1/05, Tommy Trussell <tommy.trussell@gmail.com> wrote:
>> > >  and Xorg won't let me switch to virtual consoles using keyboard
>> > commands.
>> >
>> > have you set your keyboard type to 'macintosh' in xorg.conf? changing it
>> > to
>> > 'pc105' or 'pc104' might solve this. keyboard setup on the pbooks has
>> > quite
>> > some atrocities to offer to the unsuspecting. ;-)

...

>I tried both and they have the same effect as before -- no change....


I've added the following line in my .xmodmap:

keycode 67 = F1 F1 XF86_Switch_VT_1 XF86_Switch_VT_1

It basically means that alt+fN+F1 makes a VT_Switch (67 is
the keycode for F1 key according to xev on my ibook), with
shift or not.
This is also relying on the fact that alt makes a mode
switch which hopefully is the default behavior.

please forgive my ignorance, but your wording said "added" to .xmodmap... I gather that file does not exist on a standard installation. And if I want to be able to chvt from the gdm login screen I suspect I'll need to try putting that in the root directory.

But anyway... I tried creating the file ~/.xmodmap with
that one line in it and got no response. I killed off X with
ctrl-alt-backspace and when it restarted I still had no effect.

so I opened xev (which I didn't know about until this thread -- thanks
Cedric! --and here's what I see when I press ctrl-alt-F1 (and then
release):

> KeyPress event, serial 27, synthetic NO, window 0x2200001,
>     root 0x40, subw 0x0, time 154341, (-125,284), root:(712,327),
>     state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>   
> KeyPress event, serial 30, synthetic NO, window 0x2200001,
>     root 0x40, subw 0x0, time 156860, (-125,284), root:(712,327),
>     state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>   
> KeyPress event, serial 30, synthetic NO, window 0x2200001,
>     root 0x40, subw 0x0, time 159462, (-125,284), root:(712,327),
>     state 0xc, keycode 67 (keysym 0xffbe, F1), same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>   
> KeyRelease event, serial 30, synthetic NO, window 0x2200001,
>     root 0x40, subw 0x0, time 159591, (-125,284), root:(712,327),
>     state 0xc, keycode 67 (keysym 0xffbe, F1), same_screen YES,
>     XLookupString gives 0 bytes:
>   
> KeyRelease event, serial 30, synthetic NO, window 0x2200001,
>     root 0x40, subw 0x0, time 175598, (-125,284), root:(712,327),
>     state 0xc, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
>     XLookupString gives 0 bytes:
>   
> KeyRelease event, serial 30, synthetic NO, window 0x2200001,
>     root 0x40, subw 0x0, time 175611, (-125,284), root:(712,327),
>     state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
>     XLookupString gives 0 bytes:

I don't know what I'm seeing here, but it looks like there's no cumulative response from the system -- it's seeing each keystroke but not responding to them together. Whatever that means.