Amiga keyboard connected to RPi5 via Keyrah does not work properly on first boot-up of ReplayOS

[Realinferno]

Describe the bug
I have installed a RPi5 (running ReplayOS version 1.7.4) in an Amiga 1200 case, including an Amiga keyboard connected to the RPi5 using a Keyrah. When I start-up the RPi5, booting ReplayOS staight into AmigaVision, the keyboad usually does not work properly. For example, if I exit AmigaVision into Workbench and start-up Amiga Shell, the keys (when pressed) do not show the correct characters. I also cannot open the ReplayOS menu using the hotkey on the keyboard (set as windows (L) key, which is the left Amiga key on the keyboard).

Important note: after rebooting ReplayOS the keyboard works flawlessly again (pressing keys show the correct characters, the ReplayOS menu opens/closes when pressing the left Amiga key)! It is only on first/initial start-up that the keyboard usually (most of the times) does not work properly.

To Reproduce
Steps to reproduce the behavior:
Make sure an internal Amiga keyboard is connected to the RPi5 using a Keyrah. Start the RPi5 and boot into ReplayOS. Start AmigaVision (note: I use the AmigaVision autostart script to launch straight into AmigaVision). Exit AmigVison by selecting the option "Exit to Workbench". Start Amiga Shell. Press keys to see that incorrect characters appear. Pressing the set key to open/close the ReplayOS menu does not work.

Expected behavior
It would be nice if the Amiga Keyboard also works properly on first/initial start-up of ReplayOS.

Screenshots
I don't think screenshots are very helpfull, but I can add them upon request.

Setup:

• Device: Raspberry Pi 5 2GB, authentic internal Amiga keyboard connected to the RPi5 using a Keyrah from IndividualComputers.
• OS version: ReplayOS 1.7.4, latest verion of AmigaVision (2026.04.26) for ReplayOS
• Storage: USB
• Power adapter: official RPi5 power adapter

[rtomasa]

Thanks. I do not have a Keyrah, so I need a cold-boot vs warm-reboot comparison.

Please reproduce the bad first boot, SSH in before rebooting, and attach:

• /var/log/replay.log
• dmesg output filtered for usb/hid/input
• cat /proc/bus/input/devices
• lsusb
• the same four outputs after the ReplayOS reboot when the keyboard works

Also useful:

• Does disabling AmigaVision autostart and launching it manually after 10-20 seconds avoid the issue?
• Does a normal USB keyboard work correctly on first cold boot?
• Does unplugging/replugging the Keyrah after the bad boot fix it without rebooting?
• Which Keyrah model/revision/firmware and which Keyrah mode/DIP settings are used?

[Realinferno]

Thanks for the quick reply! See attached the requested files (4 for cold boot, 4 for warm boot).

Regarding your other useful questions/suggestions:

• Does disabling AmigaVision autostart and launching it manually after 10-20 seconds avoid the issue? -> I forgot this one. I will test this on the next cold boot and report back here.
• Does a normal USB keyboard work correctly on first cold boot? -> Yes, a normal USB keyboard does work correctly on first cold boot.
• Does unplugging/replugging the Keyrah after the bad boot fix it without rebooting? -> Yes, unplugging/replugging the Keyrah solves the issue without rebooting.
• Which Keyrah model/revision/firmware and which Keyrah mode/DIP settings are used? -> It is a Keyrah V3. I bought it in May 2023 from Individual Computers. Unfortunately, I don't have any more information than that, In ReplayOS the Keyrah keypas mappings are enabled (keyboard pass-through is disabled).

I hope this is information is enough. If you need more, just let me know.

Kind regards,
Jurian Meijering

cat procbusinputdevic_cold.txt
cat procbusinputdevic_warm.txt
dmesg_cold.txt
dmesg_warm.txt
lsusb_cold.txt
lsusb_warm.txt
replay_cold.log
replay_warm.log

[Realinferno]

In addition to my previous post, I also tested the following:

• Does disabling AmigaVision autostart and launching it manually after 10-20 seconds avoid the issue? -> No, disabling AmigaVision autostart makes no difference. The issue persists.

Kind regards,
Jurian Meijering

[Realinferno]

Update: I updated the firmware of the Keyrah to the latest version 241121-1 (21/11/2024/). I also tried different keyboard mappings (using the power button/switch on the Keyrah). It was set on the optimized "emulator" keymap (power switch in "up" position) and I changed it into the "normal" setting (power switch in "down" position).

Unfortunately, it all made no difference. On cold boot the keyboard still does not show the correct characters. On reboot everything works flawlessly.

Kind regards,
Jurian Meijering