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!
Thank you, J. Reddit is a pile of garbage that does not support open conversations. I hope something can be built here, or anywhere open conversation can take place.
I forgot that I reset the BIOS, not long before the cooler change. Previously, the system hat a 0.35v undervolt. That had been removed in the BIOS reset.
With the 0.35v undervolt restored, the D15 performance is essentially identical to the iCan dual tower cooler.
I pulled the D15 and discovered it was not interfacing with the CPU in the center in the block. The mounting brackets have two sets of holes so I shifted it to put the heat closer to the center of the cooling block.
It didn't make much difference. I won't know until I've run my entire test suite. I hate to jump to any conclusions after 15m of testing. So far, it's hitting 5.14 GHz, where it was not quite hitting 5GHz before.
I'll let it run some benchmarks overnight and then analyze the speeds and temps.
Thank you for the ideas and advice. I really appreciate it.
This is such a great idea. When I installed the D15, I looked at the pad on the interface block for a while. It is so shiny, I thought it was plastic. After a minute of trying to peel it off with my nail, I figured it was aluminum that is really, really beautifully finished. It must be machine ground with a diamond hone and maybe even lapped or polished.
When I read your comment, I figured it must be plastic. I went at it with a razor knife but it simply isn't plastic. If I had left the plastic protector on, it wouldn't be the dumbest thing I've ever done. Not by a long shot.
Great idea. Just not the problem in this situation.
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!