Keyboard and trackball unresponsive

MNT Pocket Reform
21

Positive news: since the April 2025 firmware update I haven’t seen any keyboard freezes.

Occasionally I still have an issue where I can’t enter the decryption password at boot although the OLED menu is working.

The workaround that works there for me is:

  1. HYPER+ENTER R (reset keyboard)
  2. HYPER+ENTER (hold until keyboard backlight comes back on)
2 Likes
22

Thanks for the feedback! It’s very interesting that resetting the keyboard helps here.

23

For what it’s worth, I used to have this problem which was exacerbated by the accelerometer hack and by plugging and unplugging power. Newer keyboard firmware fixed it for me for the most part. I still have occasional times where the keyboard and trackball inputs are not being registered, and I almost universally go for the new option in the OLED to reset USB instead - works every time pretty much instantly, and you don’t have to convince the keyboard that you’ve already turned the device on after resetting it.

24

To be clear: with the full freezes I encountered earlier during normal operation, resetting wasn’t possible because the OLED menu was also unresponsive. The reset workaround only works when the keyboard is unresponsive at boot when entering the encryption password

1 Like
25

I’d like to try this as well but running the script tells me that -s is illegal on which and that the dependecies can’t be found. picotool and reform-tools, etc. are all installed. I am running Debian stable and I think this is why. But if I could get this script working for the sys and keyboard controller I think it might fix the issues I am having as well.

edit: @josch was able to help me with this because the dude is a serious rock star. Basically the -s option used with which in the scripts doesn’t work due to a which being a different version on Debian stable. After removing it the script works beautifully. I really suspect that this may fix the keyboard resetting and disconnecting.