Ir Keyboard Drivers - Alpha Release

[kopsis]

* Somehow I am unable to type '~'. 'Shift-`' gives back '`'.

I'll look into that one.

* I would like to be able to use the driver as non-root also, however ...

Try the following (as root):

Code: [Select]

# chmod 666 /dev/misc/uinputThat should allow non-root users to open the uinput device.

* How could the driver be nicely stopped? 'Kill -9' brings an infinite loop in aterm with no further input possible, so I need to kill the terminal window.

Yeah, I ran into that last night. The trick is to kill zkbdd from the built-in keyboard (a standard "kill" should do it -- no need for "-9") otherwise it will die before sending the last "key up" message to the kernel and the kernel's keyboard logic will get a bit lost. I'm working on a way to fix this in the next release.

[kopsis]

Ok, time for you brave C1000/C3100 owners to get into the act  You lucked out on the kernel modules! It turns out Sharp builds "input" and "keybdev" into the 2.4.20 kernels. That worried me because I had to hack up "keybdev" on the 2.4.18 kernel to get it to cooperate. Luckily I found that Sharp already made almost the exact same changes in their own 2.4.20 version.

Installation on C1000/C3100 is pretty similar to what I posted earlier:

* Backup, backup, backup!

* Install the kernel-modules-input and zkbdd IPKs from my feed at http://kopsisengineering.com/rc11/Zaurus-C1000-C3100/feed/ (note that this is different than the feed for the 7x0-860 version).

* From an Aterm or the console do a "modprobe uinput" (no need to modprobe keybdev, it's in the kernel)

* From an Aterm or the console do an "lsmod" and make sure the uinput module is listed

* From an Aterm or the console run "zkbdd -h" to get the help page for launching the driver. The general form of the command is "zkbdd -t kbtype".

* Launch the driver (eg. "zkbdd -t pocketop &")

* Start typing on the keyboard

* Post your results here -- good or bad. Note that I can't test this myself so I'm relying on you folks to tell me if it works. When posting your results please include your Zaurus model and keyboard model so I can start checking combinations off my scorecard.

If all goes well, next week I'll release version 0.2 of Zkbdd. There will be no changes to the kernel modules, but the keyboard driver app gets a major rework.

[cal]

On a C1000 with a Belkinf8

failed to open uinput device: No such file or directory
init uinput failed

lsmod shows uinput loaded...  



-t test 9600 gets the same error.

[kopsis]

Could you try an "ls -al /dev/misc/uinput" and let me know what you see?

[Srono]

Hi kopsis,

I am using Palm IR keyboard on SL6000(http://www.palm.com/us/products/accessories/peripherals/3169WW.html). However, zkbdd is not working for me.
+ lsmod shows that both uinput and keybdev were loaded.
+ nothing appears on the terminal when i type
+ i tried "zkbdd -d -t palm": i still can see the debug lines on screen  
+ i tried "zkbdd -t pocketop": i can type some character although the keymap is not correct for palm (of course )
Can you help me how to fix it? Thanks alot

[kopsis]

Can you help me how to fix it? Thanks alot
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Actually, you can help me fix it

I'm working on some [a href=\"http://kopsisengineering.com/kopsis/ZkbddAddingKeyboards]instructions for creating keyboard drivers[/url]. If you follow the first part (Reverse Engineering your Keyboard) and send me the information, I can use that to debug the driver. I don't need you to go through every key just yet. For now if you get data on three or four keys that should be enough to get me started debugging.

[cal]

Could you try an "ls -al /dev/misc/uinput" and let me know what you see?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99539\"][{POST_SNAPBACK}][/a][/div]

-edit Removed -

Ok I think I made a mistake...  When you first made your post, I added the first feed to my ipkg.conf and updated.  I noticed what I did and, changed the feed to the correct C1000-C3000 feed. I may not have updated again, and then installed the wrong version.  I don't have a wireless conection at work, so I will try to fix all this when I get home today.

[willgan]

i have tried the driver with my C1000... with pockettop ir keyboard

I rebooted my machine...
modprobe uinput ... loaded ok... lsmod shows the driver loaded
running zkbdd gives this result

failed to open uinput device: No such file or directory
init uinput failed

There is no /dev/misc/uinput created...

[kopsis]

Ok, looks like C1000/C3100 users need to open a terminal as "root" and do the following:

Code: [Select]

# mknod /dev/misc/uinput c 10 223
# ln -s /dev/misc/uinput /dev/uinputThat should get things working. If you want to run zkbdd as a non-root user you should also set the permissions on /dev/misc/uinput to something like 666.

[cal]

Ok, looks like C1000/C3100 users need to open a terminal as "root" and do the following:

Code: [Select]

# mknod /dev/misc/uinput c 10 223
# ln -s /dev/misc/uinput /dev/uinputThat should get things working. If you want to run zkbdd as a non-root user you should also set the permissions on /dev/misc/uinput to something like 666.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99582\"][{POST_SNAPBACK}][/a][/div]

I get a no file or directory error on mknod /dev/misc/uinput c 10 223

[willgan]

kopsis,

I've tested again on my C1000 and pocketop..

With the mknod step..
Confirm... work..

But only when i use -d... the keycode will come out... when i press keys at my pocketop...
Does it work with programs like abiword?

[willgan]

Ok, looks like C1000/C3100 users need to open a terminal as "root" and do the following:

Code: [Select]

# mknod /dev/misc/uinput c 10 223
# ln -s /dev/misc/uinput /dev/uinputThat should get things working. If you want to run zkbdd as a non-root user you should also set the permissions on /dev/misc/uinput to something like 666.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99582\"][{POST_SNAPBACK}][/a][/div]

I get a no file or directory error on mknod /dev/misc/uinput c 10 223
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99593\"][{POST_SNAPBACK}][/a][/div]

# mkdir /dev/misc
# mknod /dev/misc/uinput c 10 223
# ln -s /dev/misc/uinput /dev/uinput

[cal]

Ok, looks like C1000/C3100 users need to open a terminal as "root" and do the following:

Code: [Select]

# mknod /dev/misc/uinput c 10 223
# ln -s /dev/misc/uinput /dev/uinputThat should get things working. If you want to run zkbdd as a non-root user you should also set the permissions on /dev/misc/uinput to something like 666.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99582\"][{POST_SNAPBACK}][/a][/div]

I get a no file or directory error on mknod /dev/misc/uinput c 10 223
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99593\"][{POST_SNAPBACK}][/a][/div]

# mkdir /dev/misc
# mknod /dev/misc/uinput c 10 223
# ln -s /dev/misc/uinput /dev/uinput
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99596\"][{POST_SNAPBACK}][/a][/div]

I actually tried that...  I think I must have some left over messyness from earlier.  I'm going to try again on a fresh RC12 install.

[cal]

Just tried on a clean RC12 install (C1000)...  I can see the scan codes with the test9600 keyboard, but it doesn't seem to work anywhere else.

[jfv]

Willing, eager to alpha/beta test a Targus keyboard on a 5000D. Let me know when you have a version for it.

Felipe