Keyboard characters (mapping) reversed Pup 2.10 microsoft
Keyboard characters (mapping) reversed Pup 2.10 microsoft
Keyboard setting
US english QUERTY
Hi,
I have 2 characters reversed on the key board when using puppy @and " . Pressing " on the keyboard produces @ and vice versa.
I have run Puppy 2.10 seamonkey on other computers with no similar keyboard problems, so I assume this is a hard ware/driver issue. Is there a line in a file I can change or similar to correct this?
thanks,
Alasdair
US english QUERTY
Hi,
I have 2 characters reversed on the key board when using puppy @and " . Pressing " on the keyboard produces @ and vice versa.
I have run Puppy 2.10 seamonkey on other computers with no similar keyboard problems, so I assume this is a hard ware/driver issue. Is there a line in a file I can change or similar to correct this?
thanks,
Alasdair
i suspect you have the wrong keymap for your keyboard, but this simple workaround should work anyway:
copy these lines one at a time (select the text with the left mouse button):
xmodmap -e 'keycode 11 = 2 at'
xmodmap -e 'keycode 48 = apostrophe quotedbl'
and paste them into a command line console (click the middle mouse button)
or just type them in
your keys should work properly ... if they do, you can put those lines in .xinitrc, in /root
or you can make a file called .Xmodmap in /root, and put these lines in it:
keycode 11 = 2 at
keycode 48 = apostrophe quotedbl
copy these lines one at a time (select the text with the left mouse button):
xmodmap -e 'keycode 11 = 2 at'
xmodmap -e 'keycode 48 = apostrophe quotedbl'
and paste them into a command line console (click the middle mouse button)
or just type them in
your keys should work properly ... if they do, you can put those lines in .xinitrc, in /root
or you can make a file called .Xmodmap in /root, and put these lines in it:
keycode 11 = 2 at
keycode 48 = apostrophe quotedbl
Last edited by GuestToo on Mon 09 Oct 2006, 13:38, edited 1 time in total.
-
- Posts: 622
- Joined: Wed 05 Apr 2006, 20:43
Hi,
Guest Too I tried your suggestions and they worked.
MarkSouth2000,
Alasdair
Guest Too I tried your suggestions and they worked.
What does the operator "-e" do? Does it set up a sort of virtual Xmodmap?xmodmap -e 'keycode 11 = 2 at'
xmodmap -e 'keycode 48 = apostrophe quotedbl'
MarkSouth2000,
This is not the case I fiddled around endlessly with the possible combinations and it didn't make any difference, hence my request here. I think perhaps it maybe something to do with my individual keyboard.It is a "Microsoft Internet Keyboard" Model no RT9443 V56TWL purchased in Australia . I doubt that it is any different to hundreds used by members of this forum, just an odd bug in this one I guess.The US keyboard is QWERTY. Sounds like you have a UK keyboard with a US keymap or vice versa.
Alasdair
xmodmap man page:
-e expression
This option specifies an expression to be exe cuted. Any number of expressions may be specified from the command line.
basically, you can use xmodmap to execute "expressions" that define the behaviour of the various keys and mouse buttons
-e expression
This option specifies an expression to be exe cuted. Any number of expressions may be specified from the command line.
basically, you can use xmodmap to execute "expressions" that define the behaviour of the various keys and mouse buttons
-
- Posts: 88
- Joined: Sun 03 Sep 2006, 12:54
Edit Problem solved! I'm listing the problem and solution here in case it helps anyone else.
I had what appeared to be the same troubles as the above poster with regard to different keys being all switched up. I was running the US QWERTY keyboard (or so I thought) with an unchanged configuration but all of a sudden, keyboard confusion had befallen me.
The contents of my /etc/keyboard file correctly identified my map as us.
I went through the puppy keyboard wizard several times in all of the possible permutations in order to correct the problem, but to no avail.
After a fruitful search for where puppy hides the actual keyboard maps, I stumbled upon the idea to check my xorg.conf file.
/etc/X11/xorg.conf revealed on line 86 (in geany):
So I changed it manually to "us". Saved and rebooted the machine and presto. Magic!
Now I just have to interrogate all of those who also use this machine to find out how it could have been changed to Brazilian to begin with.
I had what appeared to be the same troubles as the above poster with regard to different keys being all switched up. I was running the US QWERTY keyboard (or so I thought) with an unchanged configuration but all of a sudden, keyboard confusion had befallen me.
The contents of my /etc/keyboard file correctly identified my map as us.
I went through the puppy keyboard wizard several times in all of the possible permutations in order to correct the problem, but to no avail.
After a fruitful search for where puppy hides the actual keyboard maps, I stumbled upon the idea to check my xorg.conf file.
/etc/X11/xorg.conf revealed on line 86 (in geany):
My problem is highlighted in green. "br?" thought I, "How odd."Option "XkbLayout" "br" #xkeymap0
So I changed it manually to "us". Saved and rebooted the machine and presto. Magic!
Now I just have to interrogate all of those who also use this machine to find out how it could have been changed to Brazilian to begin with.