The problem seems to be lack of ability to give the board a magic serial number. The vial app looks for a specific string in the serial number (“vial:<anything>”) to identify a vial capable keyboard. My R75 won’t accept a serial number, no matter what I do.

Apparently, this is a limitation of some cheap USB controllers (always answer 0 to all serial requests). I don’t know if that’s true but ChatGPT tells me it’s so.

udevadm info -a -n /dev/hidraw$(ls /dev/hidraw* | tail -1 | tr -dc ‘0-9’) | grep -i serial  2 ✘ ATTRS{serial}==“00000000000000000000000000000000” ATTRS{serial}==“0000:09:00.0”

Apparently, the magic number can be coded into the UID, also. I’m working on that, too, with no success so far. Apparently, USB controllers don’t stand in for UID in any case.

I’m struggling with this. If anyone has some ideas or clear direction, I would consider it a favor. If I can manage to make it work, I’ll publish the firmware for everyone.

Even if someone got the mossbed firmware to work, that would be helpful to know. I have been banging on it for three days with no luck. This is the most expensive, cheap keyboard I’ve ever purchased. lol!

Thanks. He has the core done. It could have saved me some time. I’m quite a bit further along with auto discovery and a couple of minor conveniences.

If I can get it to install with a UDEV rule so it runs at user privilege level, it’ll be all set and I’ll push it into the AUR.

Thank you. I really appreciate it, on both counts!

deleted by creator