Quote:
Originally Posted by NiLuJe
I wouldn't mind taking a look at that specific file (bundled with its sdr folder, in case it's settings-specific).
As for the affected keyboards, anything particular about them? (verbose debug logs would be helpful there.)
IIRC, I pulled a few keycodes from a random old (PS/2!) Logitech board... but an AZERTY one. I wouldn't think it could affect KP scan codes, but... who knows ;o).
|
Well I retried the installation of OCP-KOReader-v2023.06 but this time saving my files, deleting the koreader directory, and doing a fresh install from the zipfile.
And opening PDF files worked, until I copied back one too many of my backed up files - probably a settings file, since copying back my saved libs and scripts didn't mess anything up.
***
Did clean reinstall and 3 power cycles, and it opened PDF files each time.
So I'm pretty sure it was a "me" problem!
As for the the keyboards...
These are the dmesg outputs when hotplugging the two USB keyboards to the Clara HD while in KOReader:
931-usb plugged 257
932-usb 1-1: new full-speed USB device number 2 using ci_hdrc
933-PMU:_config_ricoh619_charger_params set SDP 500mA charging.
934:input: HP HP Wireless Mini Keyboard as /devices/platform/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.0/0003:03F0:A107.0001/input/input2
935:hid-generic 0003:03F0:A107.0001: input: USB HID v1.11 Keyboard [HP HP Wireless Mini Keyboard] on usb-ci_hdrc.0-1/input0
936:input: HP HP Wireless Mini Keyboard as /devices/platform/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.1/0003:03F0:A107.0002/input/input3
937:hid-generic 0003:03F0:A107.0002: input: USB HID v1.11 Mouse [HP HP Wireless Mini Keyboard] on usb-ci_hdrc.0-1/input1
---
1599-usb 1-1: new full-speed USB device number 3 using ci_hdrc
1600-input: iPazzPort iPazzPort as /devices/platform/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.0/0003:0168:1898.0003/input/input4
1601-hid-generic 0003:0168:1898.0003: input: USB HID v1.11 Mouse [iPazzPort iPazzPort] on usb-ci_hdrc.0-1/input0
1602-input: iPazzPort iPazzPort as /devices/platform/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.1/0003:0168:1898.0004/input/input5
1603:hid-generic 0003:0168:1898.0004: input: USB HID v1.11 Keyboard [iPazzPort iPazzPort] on usb-ci_hdrc.0-1/input1
---
These were the keycodes obtained for the HP Keyboard (obtained via "xev -event keyboard" when in an Alpine Linux chroot on the same device):
https://www.mobileread.com/forums/sh...5&postcount=47
Note that in the case of the chroot, simply installing the eudev hardware database, resolved the misinterpreted key issue:
https://www.mobileread.com/forums/sh...0&postcount=48
Xorg.0.log output from the Alpine chroot:
[ 61.766] (**) HP HP Wireless Mini Keyboard: Applying InputClass "evdev keyboard catchall"
[ 61.766] (**) HP HP Wireless Mini Keyboard: Applying InputClass "libinput keyboard catchall"
[ 61.766] (II) Using input driver 'libinput' for 'HP HP Wireless Mini Keyboard'
[ 61.766] (**) HP HP Wireless Mini Keyboard: always reports core events
[ 61.766] (**) Option "Device" "/dev/input/event2"
[ 61.766] (II) libinput: HP HP Wireless Mini Keyboard: is a virtual subdevice
[ 61.767] (**) Option "config_info" "udev:/sys/devices/platform/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.0/0003:03F0:A107.0001/input/input2/event2"
I couldn't find which database entry was being used.
The following command lists a bunch of HP devices including keyboards, but not the 03F0:A107.
# grep -n -C 1 03F0 /etc/udev/hwdb.d/*
So both keyboards are working perfectly in the chroot, but I can't identify any specific database entry associated with them.