It's a touch-based keyboard, so no physical keys in it.Just out of curiosity, is the keyboard functioning correctly? Since the dongle itself isn't the problem, could the shift key actually be stuck on the keyboard?
A stuck shift wouldn't show too much unless you use the number keys. For capital letters you may just think you hit the caps lock by mistake, so you hit caps lock again, reversing the stuck shift key.
I know it's a bit of a long shot but those tiny rubber keys aren't the best.
It's like a big touchpad, that a keyboard is printed on it,
and you tap, and get the desired key.
The shift is working correctly.
I see.(i was involved in testing network install and "discovered" the "issues" with dual purposed dongles).
IIRC I've experienced similar behaviour to yours (probably with one of the newer mini-keyboard/touchpad devices) but, IIRC, boot was delayed (after a timeout) rather than having to "press a key". It was on either a P4B or my P5, both "testing" Raspberry PiOS "Bookworm" and, AFAIK fully updated bootloaders. However, since I don't really like touchpads (prefer a trackball equivalent), I tend to have a mouse also connected.
Hence the suggestion to examine the lsusb and usb-devices data.
Here are the results:
Code:
$ lsusbBus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 001 Device 003: ID 0c45:8101 Microdia USB DeviceBus 001 Device 002: ID 2109:3431 VIA Labs, Inc. HubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubCode:
$ usb-devicesT: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1P: Vendor=1d6b ProdID=0002 Rev=06.06S: Manufacturer=Linux 6.6.31+rpt-rpi-v8 xhci-hcdS: Product=xHCI Host ControllerS: SerialNumber=0000:01:00.0C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mAI: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hubE: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256msT: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1P: Vendor=2109 ProdID=3431 Rev=04.21S: Product=USB2.0 HubC: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mAI: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hubE: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256msT: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 3 Spd=12 MxCh= 0D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1P: Vendor=0c45 ProdID=8101 Rev=00.01S: Manufacturer=USBS: Product=USB DeviceC: #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mAI: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhidE: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1msI: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhidE: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=4msI: If#= 2 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhidE: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=2msI: If#= 3 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhidE: Ad=84(I) Atr=03(Int.) MxPS= 64 Ivl=4msT: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1P: Vendor=1d6b ProdID=0003 Rev=06.06S: Manufacturer=Linux 6.6.31+rpt-rpi-v8 xhci-hcdS: Product=xHCI Host ControllerS: SerialNumber=0000:01:00.0C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mAI: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hubE: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256msIf any other info is needed, please write.
Statistics: Posted by spaceman5 — Fri Aug 23, 2024 5:22 pm