Number Pad Stopped Working

Framework Laptop 16 Linux
,
1

Which Linux distro are you using?
Endeavour OS (Arch)

Which kernel are you using?
6.14.10

Which BIOS version are you using?
3.05

Which Framework Laptop 16 model are you using?
7840HS w/ 7700S GPU

I’m not sure when this happened but it was either after updating to the 3.05 bios or after applying my PTM kit from Framework, but my numberpad is now completely unresponsive. The backlight is permanently on (thankfully only on the dim setting). It even remains lit while the computer is asleep.

I’ve fully updated my machine, rebooted many times, removed the module and reinserted, taken the battery out, reseated the k/b trackpad plug (with the #1 label under the keyboard) and still no response..

Anyone else had issues or knows of any way to more in-depth troubleshoot? I’m very comfortable in the terminal if needed!

2

Completely unresponsive is different, and concerning.
Sounds like you’ve tried several things, did you check that it’s alive as far as showing properly to lsusb? Or try to connect using https://keyboard.frame.work/?

Assuming it shows ok to lsusb at least, then you can see if it responds to the qmk_hid tool, github.com/FrameworkComputer/qmk_hid.

3

lsusb does not appear to see it:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 0e8d:e616 MediaTek Inc. Wireless_Device
Bus 001 Device 007: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint USB Device
Bus 001 Device 010: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 011: ID 32ac:0012 Framework Laptop 16 Keyboard Module - ANSI
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 05e3:0625 Genesys Logic, Inc. USB3.2 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

I can’t access that keyboard.frame.work site but considering that it’s not even in the lsusb list I don’t think there would be anything new to learn there..

4

Yeah… that’s certainly not good. You could still try triggering bootloader mode, though. Might not be likely to work, but worth trying. I don’t know where in the bootup sequence detection of that is. Before or after usb is brought fully up.

The methods of triggering bootloader mode for a Number pad, two methods which are left considering usb isn’t up, are

  • Hold down keys for 2 and 6 while installing the module.
  • Hold down the key at (0,0) in the matrix “(usually the top left key or Escape)” while installing the module. I believe this is the Esc key on the number pad.

If bootloader mode works then the number pad should appear to your computer as a flash drive. In which case you can try reflashing the firmware, github.com/FrameworkComputer/qmk_firmware/releases

But assuming you can’t get it into bootloader mode, frame.work/support#contact_support

5

Holding down 2 and 6 got the LED’s to stay off! No more draining my battery while asleep :sweat_smile:

No luck on spotting it as a flash drive though, at least not immediately. I’ll poke on it some more tomorrow when I’m more fresh and alert. I think this is going to have to be a support ticket though..

6

Very worrisome update, if I swap the keyboard and numpads positions then both KB and numpad work perfectly fine.. so either the midplate usb stuff is broken somehow? or more disconcerting is if there is something on the mainboard broken.

I don’t suppose theres and official way to test each of the pogo pads?

7

Oh, didn’t think it would be one of the module locations.

Official, no, haven’t seen any at least. If you had a LED matrix module, that could serve as a test of each upper module location.

The 5 upper module locations are connected to 2 4-port usb hub chips, 3 ports from one, 2 ports from the second chip. Do you use your fingerprint reader? Working ok? As that is also connected to the second chip.

8

Hmm, I’d check your midplate cable connections, both ends. There is a small connector on the underside of the midplate PCB, it has a tiny delicate black flip up latch, it should be down. The cable itself is probably stuck down to the PCB with adhesive, so as long as it looks still adhered and fully inserted, I’d leave it be. Check the ribbon cable for tears or damage, especially at the bends.

Not sure which plug you’re refering to. A pogo pin one, or perhaps the whole midplate cable? ~edit~ Oh, the midplate cable has a “1” on its label. So I assume it was that.

9

Unfortunately I don’t have any other modules to test single slots with, but I’m going to take the midplate off shortly and triple check all the cables. Here’s hoping it’s just a tiny ribbon cable that has wiggled out of alignment!

10

It’s an early christmas miracle! The numberpad is alive again!

I took off the midplane and fully removed the cable between it and the mainboard. Used some gentle compressed air to blow out any possible dust. I also pulled the battery and held down the power button because I’m old and back in the day discharging caps in a computer could sometimes fix weird issues.

Reassembled everything very carefully and voila! Number pad!

@MJ1 Thanks for walking me through troubleshooting things, I may or may not have figured it out eventually but it’s always nice to have company :sweat_smile:

3 Likes