OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: desertrat on January 10, 2006, 03:54:05 pm

Title: Weird Keyboard Problem
Post by: desertrat on January 10, 2006, 03:54:05 pm
C3100 / 1.1.0beta1

For some bizarre reason my period key (ie the key for the characters . ? >) stopped working when in the console. In X it works fine.

Any ideas?

-- cheers
Title: Weird Keyboard Problem
Post by: 0xDEADBEEF on January 10, 2006, 05:24:44 pm
Quote
C3100 / 1.1.0beta1

For some bizarre reason my period key (ie the key for the characters . ? >) stopped working when in the console. In X it works fine.

Any ideas?

-- cheers
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=110327\")

The same problem exists in rc12 on my C3100.
I think it was already posted in bug database [a href=\"http://www.pdaxrom.org/buglist.php?doaction=showbug&bugid=332]http://www.pdaxrom.org/buglist.php?doactio...owbug&bugid=332[/url]

It is quite annoying.
Title: Weird Keyboard Problem
Post by: plcg on January 11, 2006, 01:26:21 am
Quote
Quote
C3100 / 1.1.0beta1

For some bizarre reason my period key (ie the key for the characters . ? >) stopped working when in the console. In X it works fine.

Any ideas?

-- cheers
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=110327\")

The same problem exists in rc12 on my C3100.
I think it was already posted in bug database [a href=\"http://www.pdaxrom.org/buglist.php?doaction=showbug&bugid=332]http://www.pdaxrom.org/buglist.php?doactio...owbug&bugid=332[/url]

It is quite annoying.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110341\"][{POST_SNAPBACK}][/a][/div]
Hi,

Can you tell us what's in the file "/etc/sysconfig/keyboard/kernel.map" ?
Thanks.

It happened to me this morning and i replaced this file by the one i saved just after i reflashed one week before.
And now, my "period" and "right shift" work !
Something changed this file but what ?

plcg
Title: Weird Keyboard Problem
Post by: desertrat on January 11, 2006, 03:40:15 am
Quote
Can you tell us what's in the file "/etc/sysconfig/keyboard/kernel.map" ?

It happened to me this morning and i replaced this file by the one i saved just after i reflashed one week before.
And now, my "period" and "right shift" work !
Something changed this file but what ?

Yep my right shift button has no effect either (in both console and X). OK contents of my /etc/sysconfig/keyboard/kernel.map
Code: [Select]
keycode 65 = Tab
        alt     keycode 65 = Caps_Lock
        shift   keycode 65 = Caps_Lock
        control keycode 65 = Caps_Lock
keycode 27 = Shift
keycode 30 = Alt
keycode 88 = Control
keycode 89 = Alt
keycode 90 = nul
keycode 40 = nul
keycode 121 = nul
keycode 122 = nul
keycode 103 = Shift

grepping the ipkg *.list files I see only one package which claims responsibility for that file, vendor-tweaks.  I dissected that package and its kernel.map contains:

Code: [Select]
keycode 65 = Tab
    alt     keycode 65 = Caps_Lock
    shift   keycode 65 = Caps_Lock
    control keycode 65 = Caps_Lock
keycode 27 = Shift
keycode 89 = Alt
keycode 88 = Control
keycode 112 = Shift

So I replaced my kernel.map with that then did:

Code: [Select]
/usr/bin/loadkeys /etc/sysconfig/keyboard/kernel.map
Now my right shift works but the period key is still non-functioning. Then I remembered that I had made a backup of /etc when I upgraded from rc12 to 1.1.0beta1. But it turns out that the kernel.map is just the same as from the vendor-tweaks package.

So basically now I am using the same kernel.map as I had been doing under rc12, but why isn't the keyboard functioning the same? BTW as you apparently have a working kernel.map please post contents


-- cheers
Title: Weird Keyboard Problem
Post by: desertrat on January 11, 2006, 03:49:15 am
Quote
So basically now I am using the same kernel.map as I had been doing under rc12, but why isn't the keyboard functioning the same? BTW as you apparently have a working kernel.map please post contents

OK scratch that. I did a windoze and rebooted, now the period key works

But I'm still curious to know why the "/usr/bin/loadkeys /etc/sysconfig/keyboard/kernel.map" didn't restore keyboard and I had to reboot.

-- cheers
Title: Weird Keyboard Problem
Post by: plcg on January 11, 2006, 08:09:56 am
Quote
Quote
So basically now I am using the same kernel.map as I had been doing under rc12, but why isn't the keyboard functioning the same? BTW as you apparently have a working kernel.map please post contents

OK scratch that. I did a windoze and rebooted, now the period key works

But I'm still curious to know why the "/usr/bin/loadkeys /etc/sysconfig/keyboard/kernel.map" didn't restore keyboard and I had to reboot.

-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110387\"][{POST_SNAPBACK}][/a][/div]
Ooops, I forgot to tell you that...
I don't know either why loadkeys doesn't work.

Now, I want to find which software modifies "kernel.map" !

plcg
Title: Weird Keyboard Problem
Post by: 0xDEADBEEF on January 11, 2006, 03:25:55 pm
Quote
Code: [Select]
keycode 65 = Tab
    alt     keycode 65 = Caps_Lock
    shift   keycode 65 = Caps_Lock
    control keycode 65 = Caps_Lock
keycode 27 = Shift
keycode 89 = Alt
keycode 88 = Control
keycode 112 = Shift

I replaced my kernel.map with this map, rebooted and keyboard works fine now.
Thank you!

Now we have to figure out what breaks the keyboard map.
Title: Weird Keyboard Problem
Post by: plcg on January 11, 2006, 03:57:16 pm
Quote
Quote
Code: [Select]
keycode 65 = Tab
    alt     keycode 65 = Caps_Lock
    shift   keycode 65 = Caps_Lock
    control keycode 65 = Caps_Lock
keycode 27 = Shift
keycode 89 = Alt
keycode 88 = Control
keycode 112 = Shift

I replaced my kernel.map with this map, rebooted and keyboard works fine now.
Thank you!

Now we have to figure out what breaks the keyboard map.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110523\"][{POST_SNAPBACK}][/a][/div]
I've found it !
It's "Input setup" that breaks this map.
I simply changed my configuration of "Right mouse" and kernel.map has been modified.

plcg
Title: Weird Keyboard Problem
Post by: desertrat on January 11, 2006, 04:04:05 pm
Quote
I've found it !
It's "Input setup" that breaks this map.
I simply changed my configuration of "Right mouse" and kernel.map has been modified.

Good work. No doubt you filed an official bug report

I was fiddling about with "Input setup" under Matchbox yesterday, trying to get the silkscreen buttons (to no avail). So that's what broke my keyboard.

-- cheers
Title: Weird Keyboard Problem
Post by: desertrat on January 11, 2006, 04:08:09 pm
Quote
I don't know either why loadkeys doesn't work.

According to "man loadkeys":

The option -s (or --clearstrings ) clears the kernel string table. If this option is not given, loadkeys will only add or replace strings, not remove them.  (Thus, the option -s is required to reach  a well-defined  state.)

-- cheers
Title: Weird Keyboard Problem
Post by: plcg on January 11, 2006, 04:28:52 pm
Quote
Good work. No doubt you filed an official bug report
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110534\"][{POST_SNAPBACK}][/a][/div]
Done  
Title: Weird Keyboard Problem
Post by: km2783 on January 25, 2006, 11:00:22 am
Quote
Quote
Quote
Code: [Select]
keycode 65 = Tab
 Â   alt     keycode 65 = Caps_Lock
 Â   shift   keycode 65 = Caps_Lock
 Â   control keycode 65 = Caps_Lock
keycode 27 = Shift
keycode 89 = Alt
keycode 88 = Control
keycode 112 = Shift

I replaced my kernel.map with this map, rebooted and keyboard works fine now.
Thank you!

Now we have to figure out what breaks the keyboard map.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110523\"][{POST_SNAPBACK}][/a][/div]
I've found it !
It's "Input setup" that breaks this map.
I simply changed my configuration of "Right mouse" and kernel.map has been modified.

plcg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110532\"][{POST_SNAPBACK}][/a][/div]

Hmm, I think that is what "broke" mine too, but changing right mouse to something else didn't get my Right Shift back.  My period works, though.   I did edit my kernel.map file to enable R-Shift to work again, though   It is almost like you can tell it to remap R-Mouse to R-Shift, but nothing tells it to change R-Shift back to it's original function when/if you change R-Mouse.

**edit** I just used Input Settings, set R-Mouse to R-Shift, and it closed X, I started X again, opened AbiWord, and R-Shift worked    Also, kernel.map now shows keycode 103 to shift on the last line (instead of 112 like above), but R-Shift still works
Title: Weird Keyboard Problem
Post by: km2783 on January 25, 2006, 01:56:35 pm
My period key just crapped out, X was not running when I noticed it.  I was wanting to cat /etc/sysconfig/keyboard/kernel.map and I couldn't type the period, though R-Shift still worked.  A reboot fixed this.  I would make a bug report, but like I said, there is one, and I can't figure out how to duplicate the cursed problem, though I am trying   If I can, I'll post a new bug report to pdaXrom with what I manage.
Title: Weird Keyboard Problem
Post by: km2783 on January 25, 2006, 02:24:15 pm
typing up a bug report, now.  I can duplicate the period key ceasing to function, and the fix.

Under X, I go to System Tools, then Input Setup.  Change Right Mouse Button to R Shift, then select Okay and exit.  Restart X.

But then you decide you want to use R Shift to type Caps, like I did, because it is awkward to use L Shift all the time.  Well, you go back, you change it to the Fn it was defaulted at.  Exit X and save.  Oh noes!  The period key doesn't work anymore!

To fix it, I started X again, opened kernel.map in SciTE, changed the last line to read keycode 112=Shift, saved it, exited X, and reboot.  Then the period works again

Crap, I forgot to add to the report that I use the SL-C3100   It is Bug Report #357
Title: Weird Keyboard Problem
Post by: MarcusKracht on February 01, 2006, 04:08:34 pm
I have the same problem without tampering with the keymap. Can someone be
so kind to tell me what to do now? As far as I can see it is a matter of changing
the content of /etc/sysconfig/keyboard/kernel.map and rebooting. What should
be in this file to get a good result?

-- Marcus
Title: Weird Keyboard Problem
Post by: Antikx on February 01, 2006, 04:25:22 pm
Quote
I have the same problem without tampering with the keymap. Can someone be
so kind to tell me what to do now? As far as I can see it is a matter of changing
the content of /etc/sysconfig/keyboard/kernel.map and rebooting. What should
be in this file to get a good result?

-- Marcus
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113310\"][{POST_SNAPBACK}][/a][/div]
Maybe I'm missing something, but have you tried what is in the replys of three post above by km2783?
This works for me and stays working untill I go back into the Input Helper.... then I have to go back and edit kernel.map again.
Title: Weird Keyboard Problem
Post by: daniel3000 on January 25, 2007, 10:38:12 am
Does anyone know the correct entry for kernel.map to swap slash and comma on the console?

Or, how do I get the keycode of a key?
And which strings are allowed as key identifiers on the right side?
Knowing that, I can create my own entries.

daniel
Title: Weird Keyboard Problem
Post by: wyvvie on January 25, 2007, 08:52:27 pm
Fire up 'xev' from the terminal, press the key you wish to know the code for, and then check the output xev gives you.
 
You'll see something like this:
Code: [Select]
KeyPress event, serial 30, synthetic NO, window 0x1800001,
    root 0x46, subw 0x1800002, time 1544556304, (23,45), root:(342,386),
    state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
It's the bit after 'keysym 0xffex2' (Shift_R) that tells you the valid key code, and this is acceptable to put in your keymap/kernel.map file.

It works the same when pressing two keys (e.g, the 'Function' and '?.>' keys), telling you what each combination results in. (In that case 'Mode_switch', and '>').

I know I tend to over-simplify things, so  I apologise in advance

Hope this helps