![]() ![]() |
Jul 26 2007, 12:17 PM
Post
#1
|
|
![]() Group: Members Posts: 52 Joined: 7-April 05 Member No.: 6,808 |
Hi, good day.
Recently I updated my Z to pdaXii13, I have installed the Zkbdd (driver for IR keyboards). The drivers works in test mode, but when I launch it in normal mode it does not do anything. I thought that perhaps it was a problem with the Palm driver config file but I tried with the other drivers and I got the same result. Besides I searched on the forums and I found that another user got the same problem with other IR model keyboard. http://www.oesf.org/forums/index.php?showt...=18662&hl=zkbdd I will really appreciate any advice about this, I do not know what could be wrong. Best Regards, Daniel. Console output: CODE # zkbdd -t palm_3169ww -d
driver_setting_num(description) = Palm 3169WW Universal Wireless Keyboard Driver driver_setting_num(version) = 0.3 Zkbdd using driver: Palm 3169WW Universal Wireless Keyboard Driver, version 0.3 driver_setting_num(scancode_fn) = 101 driver_setting_num(scancode_punc) = 0 driver_setting_num(scancode_num) = 0 driver_setting_num(scancode_shiftl) = 117 driver_setting_num(scancode_shiftr) = 62 driver_setting_num(scancode_caps) = 63 driver_setting_num(has_num_lock) = 0 driver_setting_num(has_punc_lock) = 0 driver_setting_num(has_fn_lock) = 0 opening /dev/ttyS1 lookup_scancode(map_normal, 0x7b) keycode: 0x01 press 01 0x00000002 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 lookup_scancode(map_normal, 0x7b) keycode: 0x01 release 01 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 zkbdd shutting down # |
|
|
|
Jul 26 2007, 08:48 PM
Post
#2
|
|
![]() Group: Members Posts: 2,808 Joined: 21-March 05 From: Sydney, Australia Member No.: 6,686 |
QUOTE(Leinadmx @ Jul 27 2007, 06:17 AM) Hi, good day. Recently I updated my Z to pdaXii13, I have installed the Zkbdd (driver for IR keyboards). The drivers works in test mode, but when I launch it in normal mode it does not do anything. I thought that perhaps it was a problem with the Palm driver config file but I tried with the other drivers and I got the same result. Besides I searched on the forums and I found that another user got the same problem with other IR model keyboard. http://www.oesf.org/forums/index.php?showt...=18662&hl=zkbdd I will really appreciate any advice about this, I do not know what could be wrong. Best Regards, Daniel. Console output: CODE # zkbdd -t palm_3169ww -d driver_setting_num(description) = Palm 3169WW Universal Wireless Keyboard Driver driver_setting_num(version) = 0.3 Zkbdd using driver: Palm 3169WW Universal Wireless Keyboard Driver, version 0.3 driver_setting_num(scancode_fn) = 101 driver_setting_num(scancode_punc) = 0 driver_setting_num(scancode_num) = 0 driver_setting_num(scancode_shiftl) = 117 driver_setting_num(scancode_shiftr) = 62 driver_setting_num(scancode_caps) = 63 driver_setting_num(has_num_lock) = 0 driver_setting_num(has_punc_lock) = 0 driver_setting_num(has_fn_lock) = 0 opening /dev/ttyS1 lookup_scancode(map_normal, 0x7b) keycode: 0x01 press 01 0x00000002 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 lookup_scancode(map_normal, 0x7b) keycode: 0x01 release 01 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 zkbdd shutting down # did you follow this: http://kopsisengineering.com/kopsis/ZkbddUsersGuide this is also a nice read up http://kopsis.blogspot.com/2005/10/zaurus-...rd-drivers.html |
|
|
|
Jul 27 2007, 10:32 AM
Post
#3
|
|
![]() Group: Members Posts: 52 Joined: 7-April 05 Member No.: 6,808 |
QUOTE(Meanie @ Jul 26 2007, 10:48 PM) did you follow this: http://kopsisengineering.com/kopsis/ZkbddUsersGuide this is also a nice read up http://kopsis.blogspot.com/2005/10/zaurus-...rd-drivers.html Hi ! I checked up the Zkbdd Users guide, mmm but it's funny, the document mention that the keybdev module is already loaded for new Zaurus like C1000 or C3100 but if you check the kernel version you will get just "2.4", the point is with the minor version, I guess that pdaXii13 uses a <2.4.20. I guess that because the problem with the zkbdd was solved when I loaded the keybdev module. Thanks a lot |
|
|
|
Aug 11 2007, 10:04 PM
Post
#4
|
|
![]() Group: Members Posts: 2,808 Joined: 21-March 05 From: Sydney, Australia Member No.: 6,686 |
QUOTE(Leinadmx @ Jul 28 2007, 04:32 AM) QUOTE(Meanie @ Jul 26 2007, 10:48 PM) did you follow this: http://kopsisengineering.com/kopsis/ZkbddUsersGuide this is also a nice read up http://kopsis.blogspot.com/2005/10/zaurus-...rd-drivers.html Hi ! I checked up the Zkbdd Users guide, mmm but it's funny, the document mention that the keybdev module is already loaded for new Zaurus like C1000 or C3100 but if you check the kernel version you will get just "2.4", the point is with the minor version, I guess that pdaXii13 uses a <2.4.20. I guess that because the problem with the zkbdd was solved when I loaded the keybdev module. Thanks a lot pdaXii13 is using 2.4.20 kernel. The documentation for zkbdd is assuming that keybdev module is automatically loaded which is not always the case unless the hotplug scripts are not updated to do it. |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 18th June 2013 - 11:21 PM |