Keyboard backlight control buggy?

[O.o]

Before I start debugging the keyboard firmware, can someone try this sequence of commands (as root)?

printf "xLRGB\xff\x00\x00" > /dev/hidraw0   # Keyboard backlight turns blue and stays blue```
printf "xLRGB\x00\xff\x00" > /dev/hidraw0   # Keyboard backlight turns green and stays green
printf "xLRGB\xff\xff\xff" > /dev/hidraw0   # Keyboard backlight turns white, then after 5 seconds, turns red

After that sequence (in fact, really after setting any color with a high red value as far as I can tell, but I figured I’d post a reference “problem” sequence to narrow down the issue) all the colors are messed up until ◯-F1 / ◯-F2 are used, that seem to unscramble the keyboard driver’s brains. But setting the color programmatically never seems to work correctly anymore until the keyboard is reset.

Note that this is on a classic Reform, not the Pocket.

[josch]

@O.o

After that sequence (in fact, really after setting any color with a high red value as far as I can tell, but I figured I’d post a reference “problem” sequence to narrow down the issue) all the colors are messed up until ◯-F1 / ◯-F2 are used, that seem to unscramble the keyboard driver’s brains.

I ran your commands and am not seeing this effect.

@O.o

Note that this is on a classic Reform, not the Pocket.

You posted in the right forum for that but the essential information that this requires keyboard v4

[O.o]

@josch

this requires keyboard v4

Yeah sorry, I should have specified this - and also that it might require the latest driver firmware to reproduce.

[josch]

@O.o

and also that it might require the latest

Latest from git? Latest release?

@O.o

driver to reproduce.

Driver as in firmware?

I tested with a freshly flashed system image and I have the latest git tag flashed. I can flash the latest git commit if that’s what it takes?

[O.o]

Yeah firmware. Sheesh… I’m really not good at being clear.

And yes, the latest from the reform git repo in reform2-keyboard4-fw - currently 3cc6fbb9.

I’m not sure that’s what it takes tbh, but that’s what I’m rocking and it ain’t working right for me.

[O.o]

I rebuilt the firmware from scratch (without any modification), reflashed it and now it behaves almost completely correctly.

There’s something very fish, either with my keyboard, or there’s a really subtle bug that isn’t easy to reproduce predictably…