Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 23 Aug 2019, 05:05
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
Keyboard Suddenly Unmapped (Solved)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [6 Posts]  
Author Message
theinfamousj

Joined: 03 Sep 2006
Posts: 88

PostPosted: Sat 25 Feb 2012, 00:13    Post subject:  Keyboard Suddenly Unmapped (Solved)  

Hi all! I have a bit of a puzzle. I have puppy installed to an Asus EeePC (900A) and all was going splendidly.

Within the past week or two - I cannot pinpoint it exactly - I noticed that the keyboard mapping seems to have spontaneously disappeared. I can still type with all the letter keys and the space bar, but the tilde key, the pipe key, and the function keys no longer work. *poof* I cannot even [SHIFT] + [INS] because the [INS] doesn't work.

I neither added no subtracted anything from the configuration. I changed no configuration files. I didn't install any new programs. My computer has been as it was for at least two months prior with no problems until the mysterious key disappearance. I have a keyboard cover on the keyboard to keep out moisture and dirt so nothing physical altered anything.

I've already gone in and used the keyboard setup wizard to set it back to "english (US)". This did not fix the problem.

I have no idea where to even start putting this right. I really miss my [SHIFT] + [INS] because as anyone else with an EeePC can tell you, the mouse buttons have a breaking-all-the-time problem so I long ago gave up on fixing them yet again and have just tapped to left-click and two-finger-tapped to right-click so [SHIFT] + [INS] is my only way to paste into terminal.

Last edited by theinfamousj on Mon 12 Mar 2012, 02:01; edited 1 time in total
Back to top
View user's profile Send private message 
theinfamousj

Joined: 03 Sep 2006
Posts: 88

PostPosted: Sat 25 Feb 2012, 00:22    Post subject:  

Here is what xorg.conf says about the keyboard, currently. I'm not sure if this has changed since I didn't look at it before when the keyboard was working.

Code:
Section "InputDevice"
   Identifier  "Keyboard0"
   Driver      "kbd"
   Option      "XkbRules" "xorg"
   Option      "XkbModel" "pc102"
   Option      "XkbLayout" "us" #xkeymap0
EndSection
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Sat 25 Feb 2012, 15:41    Post subject:  

Yes, it is rather a puzzle.

Have you ensured that it is not a hardware problem? If not, try booting with another OS, or try booting from your Puppy CD and issue the puppy pfix=ram command at the boot prompt.

If this shows that the hardware is working fine, reboot normally so that the problem returns, and please answer the follow questions:

What Puppy flavor and version?

What is the output from the following command?
Code:
setxkbmap -print -v 8


Try the following command and press/release the keys that aren't working.
Code:
xev

For instance, if you had a working tilde key, you would see something like this:
Code:
KeyPress event, serial 32, synthetic NO, window 0x1e00001,
    root 0xaa, subw 0x0, time 249748840, (151,483), root:(491,527),
    state 0x1, keycode 49 (keysym 0x7e, asciitilde), same_screen YES,
    XLookupString gives 1 bytes: (7e) "~"
    XmbLookupString gives 1 bytes: (7e) "~"
    XFilterEvent returns: False

Note that I get "state 0x1, keycode 49" for this key. What state and keycodes, if any, do you get for each of your problem keys?

To exit the test, close the "Event Tester" window.

I noticed that you didn't mention the grave accent or backslash. On my keyboard those share the same keys as the tilde and vertical bar. Do they on your keyboard, and do they work or not?

With luck, those answers will get us headed in the right direction.
Back to top
View user's profile Send private message 
theinfamousj

Joined: 03 Sep 2006
Posts: 88

PostPosted: Sat 25 Feb 2012, 17:04    Post subject:  

npierce wrote:
Yes, it is rather a puzzle.

Have you ensured that it is not a hardware problem? If not, try booting with another OS, or try booting from your Puppy CD and issue the puppy pfix=ram command at the boot prompt.

If this shows that the hardware is working fine, reboot normally so that the problem returns, and please answer the follow questions:


I can confirm that this is not a hardware problem. I have rebooted to pfix=ram with a fully working keyboard.

Quote:
What Puppy flavor and version?


Lupu 5.2.5

Quote:
What is the output from the following command?
Code:
setxkbmap -print -v 8


Code:
# setxkbmap -print -v 8
Setting verbose level to 8
locale is C
Applied rules from xorg:
model:      pc102
layout:     us
Trying to build keymap using the following components:
keycodes:   xfree86+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc/pc(pc102)+pc/us
geometry:   pc(pc102)
xkb_keymap {
   xkb_keycodes  { include "xfree86+aliases(qwerty)"   };
   xkb_types     { include "complete"   };
   xkb_compat    { include "complete"   };
   xkb_symbols   { include "pc/pc(pc102)+pc/us"   };
   xkb_geometry  { include "pc(pc102)"   };
};



Quote:
Try the following command and press/release the keys that aren't working.
Code:
xev

For instance, if you had a working tilde key, you would see something like this:
Code:
KeyPress event, serial 32, synthetic NO, window 0x1e00001,
    root 0xaa, subw 0x0, time 249748840, (151,483), root:(491,527),
    state 0x1, keycode 49 (keysym 0x7e, asciitilde), same_screen YES,
    XLookupString gives 1 bytes: (7e) "~"
    XmbLookupString gives 1 bytes: (7e) "~"
    XFilterEvent returns: False

Note that I get "state 0x1, keycode 49" for this key. What state and keycodes, if any, do you get for each of your problem keys?


The problem keys that I know of are the tilde/accent grave key, the pipe/backslash key, [INS], [F3], [F4] and [F5]. I am simply assuming that the remainder of my function keys are off, as well, though I haven't had the honor of being in a program where I already know the expected behavior and was surprised by a different behavior.

I received absolutely NO response when I pressed the tilde/accent grave key, the pipe/backslash key, nor [INS]. Nothing. It was still waiting for me to press a key, apparently.

For [F3], [F4], and [F5], respectively, I was given:

Code:
# xev
Outer window is 0x1c00001, inner window is 0x1c00002

PropertyNotify event, serial 8, synthetic NO, window 0x1c00001,
    atom 0x27 (WM_NAME), time 59773434, state PropertyNewValue

PropertyNotify event, serial 9, synthetic NO, window 0x1c00001,
    atom 0x22 (WM_COMMAND), time 59773434, state PropertyNewValue

PropertyNotify event, serial 10, synthetic NO, window 0x1c00001,
    atom 0x28 (WM_NORMAL_HINTS), time 59773434, state PropertyNewValue

CreateNotify event, serial 11, synthetic NO, window 0x1c00001,
    parent 0x1c00001, window 0x1c00002, (10,10), width 50, height 50
border_width 4, override NO

PropertyNotify event, serial 14, synthetic NO, window 0x1c00001,
    atom 0x10d (WM_PROTOCOLS), time 59773435, state PropertyNewValue

MapNotify event, serial 15, synthetic NO, window 0x1c00001,
    event 0x1c00001, window 0x1c00002, override NO

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x171 (_OB_APP_ROLE), time 59773436, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x172 (_OB_APP_NAME), time 59773436, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x173 (_OB_APP_CLASS), time 59773436, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x174 (_OB_APP_TYPE), time 59773436, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x144 (_NET_WM_VISIBLE_NAME), time 59773437, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x157 (_NET_WM_VISIBLE_ICON_NAME), time 59773437, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x116 (_NET_WM_ICON), time 59773438, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x1c00001,
    atom 0x159 (_NET_WM_ALLOWED_ACTIONS), time 59773438, state PropertyNewValue

ReparentNotify event, serial 18, synthetic NO, window 0x1c00001,
    event 0x1c00001, window 0x1c00001, parent 0x81ee5d,
    (0,0), override NO

PropertyNotify event, serial 20, synthetic NO, window 0x1c00001,
    atom 0x11b (_NET_WM_STATE), time 59773439, state PropertyNewValue

ConfigureNotify event, serial 20, synthetic NO, window 0x1c00001,
    event 0x1c00001, window 0x1c00001, (0,0), width 178, height 178,
    border_width 0, above 0x81ee89, override NO

ConfigureNotify event, serial 20, synthetic NO, window 0x1c00001,
    event 0x1c00001, window 0x1c00001, (2,25), width 178, height 178,
    border_width 0, above 0x81ee89, override NO

PropertyNotify event, serial 20, synthetic NO, window 0x1c00001,
    atom 0x112 (_NET_FRAME_EXTENTS), time 59773440, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x1c00001,
    atom 0x15a (_KDE_NET_WM_FRAME_STRUT), time 59773440, state PropertyNewValue

ConfigureNotify event, serial 20, synthetic YES, window 0x1c00001,
    event 0x1c00001, window 0x1c00001, (113,205), width 178, height 178,
    border_width 2, above 0x0, override NO

PropertyNotify event, serial 20, synthetic NO, window 0x1c00001,
    atom 0x115 (_NET_WM_DESKTOP), time 59773440, state PropertyNewValue

MapNotify event, serial 31, synthetic NO, window 0x1c00001,
    event 0x1c00001, window 0x1c00001, override NO

VisibilityNotify event, serial 31, synthetic NO, window 0x1c00001,
    state VisibilityUnobscured

Expose event, serial 31, synthetic NO, window 0x1c00001,
    (0,0), width 178, height 10, count 3

Expose event, serial 31, synthetic NO, window 0x1c00001,
    (0,10), width 10, height 58, count 2

Expose event, serial 31, synthetic NO, window 0x1c00001,
    (68,10), width 110, height 58, count 1

Expose event, serial 31, synthetic NO, window 0x1c00001,
    (0,68), width 178, height 110, count 0

PropertyNotify event, serial 31, synthetic NO, window 0x1c00001,
    atom 0x133 (WM_STATE), time 59773449, state PropertyNewValue

FocusIn event, serial 31, synthetic NO, window 0x1c00001,
    mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  114 0   0   0   16  0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 35, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59773503, (420,275), root:(535,482),
    state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
    XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59775651, (420,275), root:(535,482),
    state 0x0, keycode 70 (keysym 0xffc1, F4), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59775793, (420,275), root:(535,482),
    state 0x0, keycode 70 (keysym 0xffc1, F4), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59778401, (420,275), root:(535,482),
    state 0x0, keycode 71 (keysym 0xffc2, F5), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59778513, (420,275), root:(535,482),
    state 0x0, keycode 71 (keysym 0xffc2, F5), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59780631, (420,275), root:(535,482),
    state 0x0, keycode 72 (keysym 0xffc3, F6), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x1c00001,
    root 0x66, subw 0x0, time 59780771, (420,275), root:(535,482),
    state 0x0, keycode 72 (keysym 0xffc3, F6), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


Quote:
I noticed that you didn't mention the grave accent or backslash. On my keyboard those share the same keys as the tilde and vertical bar. Do they on your keyboard, and do they work or not?


If you see my previous answer you will see that they share keys with the ones I have listed and that they do not work, either.
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Sun 26 Feb 2012, 09:12    Post subject:  

The output from setxkbmap looks normal, and matches the entry in xorg.conf. So the X keymap is probably OK. (It is possible that one or more files in the xkb database are corrupt, but that seems unlikely. We can revisit that later if we don't find the answer elsewhere.)

The fact that xev doesn't respond to keypresses from your grave, backslash, and Insert keys could be caused by (at least) a couple of things:

1. Some process may be grabbing those keypresses and not passing them on. Do you know if you happen to be running xbindkeys? What window manager are you using?

2. X may not recognize the keycodes passed to it by the kernel. We can test that:

Exit X (Menu -> Shutdown -> Exit to prompt) (Normally you could just switch the virtual console, but if your F4 key isn't working you couldn't get back to X.)

After you have exited X, try these commands and press/release your problem keys:
Code:
showkey -s
showkey -k

(The utility will self-terminate ten seconds after you stop pressing keys.)

What codes, if any, did you get?

The results from testing F3, F4, and F5 with xev are certainly strange. Perhaps I have misunderstood you, but it looks like F3 is sending the keycode for F4 (70), F4 is sending the keycode for F5 (71), and F5 is sending the keycode for F6 (72). Is that consistent with the problem you are having? Does F3 behave as F4, F4 as F5, and F5 as F6?

Sorry for not getting back to you sooner, but I try to spend less time in front of a computer on weekends. Smile
Back to top
View user's profile Send private message 
theinfamousj

Joined: 03 Sep 2006
Posts: 88

PostPosted: Mon 12 Mar 2012, 02:00    Post subject:  

A computer engineer came over to my house a few days ago and figured out what had happened. I lost a resistor and so I lost a bit, and having the corrupted bit due to the burnt out resistor means that the F keys shifted one to the left and I lost the first and last key on that byte.

So it turns out that it IS a physical problem albeit a really weird one. Apparently the resistor was dodgy for a while and so I didn't think it was physical and now it is completely gone.

So, I ordered a new keyboard for my netbook and am waiting for it to arrive in the mail. In the mean time I will just have to live with the weird keyboard setup.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [6 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0576s ][ Queries: 11 (0.0077s) ][ GZIP on ]