My R75 works fine under via.
I'm using the R75 vial firmware located here.
https://github.com/mossbed/r75
It won't compile, as cloned. It's more than just the directory structure which is completely silly. It's not surprising it didn't work, given it's messy state. I had to modify it a bit, so it could easily be something I did.
I had to add a UID:
config.h -> #define VIAL_KEYBOARD_UID { }
and uncomment tap_dance_action in keymap.c.
tap_dance_action_t tap_dance_actions[] = {
[TD_RESET] = ACTION_TAP_DANCE_FN(safe_reset),
[TD_CLEAR] = ACTION_TAP_DANCE_FN(safe_clear),
[TD_CTL_TG] = ACTION_TAP_DANCE_LAYER_TOGGLE(KC_RCTL, _CTL_LYR)
};
That's about it.
It compiles and downloads cleanly. Via continues to work but Vial does not discover it.
This mosbed firmware extension claims to be a derivative of this work but it doesn't seem to be.
https://github.com/irfanjmdn/r65/tree/vialrgb?tab=readme-ov-file#guide
Anyone have Vial working? It's a popular keyboard so I expect someone has solved this problem. If no one responds, I'll take it on in a week or so so we can all enjoy ou R75 on linux with Vial.
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:") 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!