-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network install doesn't start with wireless keyboard/trackpad #574
Comments
Please could you supply boot loader uart logs and full details of the Logitech ie Amazon (or similar) link to verify exact model etc |
This sounds a bit like the issue I reported in the beta forum a while ago https://forums.raspberrypi.com/viewtopic.php?p=2186020#p2186020 Here's the report with logs (I haven't tested with newer bootloaders yet): There seems to be some issue with HID detection / handling: Using a Logitech K400 plus (also tested with the original K400 version) and it's unifying receiver the net install screen doesn't come up, only the "black" detail status screen. On an RPi4 those Logitech keyboards work fine and I can initiate netinstall by pressing shift. Using a plain wireed HP USB keyboard on RPi5 brings up the netinstall screen though and I could install LibreELEC just fine. With the Logitech keyboard I see the bootloader registering a HID device in the UART log:
According to lsusb the logitech unifying receiver has 3 HID endpoints (keyboard, mouse and "unknown"):
|
lsusb shows the exact same information for me, including the same PID/VID for the root device(Which would make that it's the same "unified receiver" for the K400r and K400+. The only exception is the iConfiguration: Under the BOOT_UART setting description, the documentation makes no mention of using the jst uart port. Maybe it should make that distinction. Since opening this issue, I've set NET_INSTALL_KEYBOARD_WAIT=4000 https://www.amazon.com/Logitech-Wireless-Keyboard-Touchpad-Transceiver/dp/B008QS7TRK |
That looks familiar I found one in my attic :) |
Yes, I can reproduce this. Works on Pi4 but not Pi5 |
* Add preliminary support for booting NVMe devices behind PCIe switches. See: raspberrypi/firmware#1833 * Fix MAX_RESTARTS parameter See: raspberrypi#576 * arm_dt: Support HAT EEPROM dtparams * Fix reporting of the partition number via DT See: raspberrypi#575 * Resolve HID counting bug which caused Network Install to fail on some keyboards See: Fixes raspberrypi#574 * Pull PCIE DET_WAKE high by default on CM5
Describe the bug
I've seen others having the same issue. It works as expected with a HP wired keyboard, never shows the red splash screen when I have Logitech K400r plugged in.
Steps to reproduce the behaviour
Plug in and boot with a Logitech K400r (probably other K400 variants) with no boot device.
Device (s)
Raspberry Pi 5
Bootloader configuration.
#vcgencmd bootloader_version output
2024/04/20 11:53:30
version d1744d218076d7eee7c14763bbf3d3cf6278191a (release)
timestamp 1713610410
update-time 1714182005
capabilities 0x0000007f
#rpi-eeprom-config output
[all]
BOOT_UART=1
POWER_OFF_ON_HALT=0
BOOT_ORDER=0xf461
NET_INSTALL_ENABLED=1
System
No response
Bootloader logs
No response
USB boot
No response
NVMe boot
No response
Network (TFTP boot)
No response
The text was updated successfully, but these errors were encountered: