Using Keyrah V3 (Amiga 500 keybord) with Amiga OS 4.1 (X5000)?

Hi,

I am trying to use a Samsung A500 keyboard with my X5000. But it seems that Amiga OS 4.1 USB stack has some issues with the Keyrah.

Amiga OS 4.1 will not detect the Keyrah when plugged in after booting. Restarting the machine will also not detected it. The only way to make it work is to shutdown the X5000, wait a bit, and then start the OS while the Keyrah is attached. Even then it only works 1 in 3 tries. Either the Keyrah is not detected at all, or even if it is detected the OS does not register any key presses.

I do not see any messages on the serial debug when plugging in Keyrah.

When the Keyrah is detected and working, I see the following USB device in SysMon:



Keyrah works fine with the other machines (A600GS, two Windows laptops and a Raspberry Pi5).

Any ideas how to make the Keyrah V3 more reliable on AOS 4.1?

Thanks a lot,
Josef

System:
AmigaOne X5000/20
AmigaOS 4.1 FE Update 2
Enhancer 2.2

Hi Flynn

To try and figure out what goes wrong (I don't have a Keyrah in any version myself) I have a coupe of questions/requests for you:

1) What are the version numbers of your USB modules (version full <modulename>)?
- usbsys.device
- usbresource.library
- ehci.usbhcd
- ohci.usbhcd
- hub.usbfd
- bootmouse.usbfd
- bootkeyboard.usbfd
- hid.usbfd
- usbhidgate.library

2) Please enable all USB logging on your system for testing:
setenv usb/system/LOGINFO 1
setenv usb/system/LOGWARNINGS 1
setenv usb/system/LOGERRORS 1
setenv usb/system/LOG_ATTACHMENT 1
setenv usb/system/LOG_HCDCALLS 1
Then open USB prefs and press the "Use" button. That will get the USB stack to reload its settings from ENV:

3) With logging enabled as mentioned in point 2, please record the following for a successful attachment of the Keyrah:
- T:usb.log
- output of command "usbinfo tree" (if you have it - your USB stack may be of a release which has it in the SDK and not the user install)

4) Record info as in pont 3, only for the case of a failing attachment of the Keyrah

----

If possible, please reset the OS before each test to get a clean state to test from.

So, collect this info
- USB module versions
- T:usb.log (and perhaps usbinfo) for successful attach
- T:usb.log (and perhaps usbinfo) for failed attach
in an archive and pass it on to me.

This will give me a good bunch of information to try and wrap my head around what might be going wrong.
I'm not sure if this is the right place for such large text content, so perhaps PM me a download link via wetransfer.com or similar, or ask here and I can give you my email address in PM.

Hi Thomas,

thanks a log for your help on this.

I don’t have usbinfo available — neither on Workbench nor in the SDK.

I’ve prepared the requested files as follows:

- usb_versions.txt – contains the version numbers of all the USB modules you listed.
- usb_success.log – logs from a successful attach of the keyboard. For this to work, I had to completely shut down the X5000 and disconnect the keyboard for more than 5 seconds before powering back on.
- usb_failed.log – logs from a failed attempt after a cold reboot.
- usb_detach_and_attach.log – after the successful attach (as in usb_success.log), I unplugged and re‑plugged the Keyrah. The attach failed again in this case.

Please check if you can access the archive from OneDrive:
usb_logs.lha

Best regards,
Josef

Hi Josef

Just to pick up on your logs.
Am I right in my interpreting your USB topology, where the Keyrah attaches, like this:

Rear USB
+ Port 1: Hub 1
..+ Port 1: MidiMate device
..+ Port 3: Hub 2
....+ Port 1: (in the failure log this holds the Keyrah)
....+ Port 2: Optical mouse
....+ Port 3: (in the success and detach-and-attach logs this holds the Keyrah)

And am I also right in interpreting from the logs that you're not really detaching/attaching the Keyrah but actually "Hub 2"?
Just trying to understand the scenario.

Also, from the "detach and attach" it looks like the Keyrah actually attaches correctly. But I can't see from the log that any drivers were launched on it. Could that align with what you experience?

My initial though is that Hub 2 port 1 may be faulty - but the I have not enough data to back that up. Is it consistent that it will fail in port 1 and work in port 3?
Just trying to rule out causes to simplify what I have to evaluate :)

Hi Thomas,

Yes, I connect the Keyrah 3 via a KVM switch. But I also tried to plug Keyrah into one of the USB slots on the backside of the X5000. No difference.

And the port is fine because the other machines (Raspberry Pi 5, two Windows laptops) do not have any issues when attach/detaching Keyrah. Or switching between the hosts with the KVM switch.

But I can create another set of logs using one of the backside USB ports (and detach all other USB devices but the mouse) if this would help you.

Hi Josef

No need to do new logs for now. And good to hear you don't have flaky USB ports - they're a nuisance to have ;)

Can you send me a PM with your email address? I'd like to send you something for testing, if you're up for it. Your problem may correlate with some fixes I have queued up.