Thanks, have that a try, but no luck. I’ll wait to see if someone reaches out and the. Figure out how we can identify the case if needed
I followed the instructions provided on the framework page about updating the firmware. These issues started well before that though
Sure, here’s the link to the same video I sent to support:
Sounds good. When a solution is found I’ll make sure to update the thread!
Would you list them? It can be relevant if they are in a line, as it might point to a connection fault in how the grid of connections is electrically scanned.
Can you explain what happened when you installed the new FW16 keyboard?
Were exactly the same keys failing?
Was the failure immediate, or was there some delay before it failed again?
I am thinking, no matter how unlikely it is, that the replacement keyboard was faulty as well, so maybe getting a second replacement keyboard will help.
As some background to the USB protocol.
The CPU sends an URB Interrupt IN request to the keyboard over USB.
The keyboard waits until a change in state happens.
When the change happens (you press a key), the keyboard sends a URB Interrupt IN response to the CPU. The response just contains a bitmap of every key on the keyboard. No scan codes or anything like that. The CPU then sends a new URB Interrupt IN request and the keyboard waits again until something changes.
The CPU or OS kernel then converts that to scancodes so the GUI can understand it.
So, you can see from that, the fact it is sending some keys and not others generally means the keyboard microcontroller and usb cables are working fine. It is just the detection of the key that is not being forwarded over the USB.
Causes:
- The keyboard has been programmed to ignore that key.
- The keyboard is faulty.
With the install of a new keyboard, it has not had time to be programmed to ignore a key, so the software config/programming cannot cause the problem.
So, you can see, depending on the answers to the 2 questions at the top of this message, they will most likely point to (2).
And in this case, both the old and new keyboard are faulty. Rare I know, but possible.
Hey guys, sorry for the delay. I was put on temporary time-out because I’m a new user and I was being too active lol
Framework support did respond last night! Not sure if that’s just because they cleared the backlog or because catastrophic (sorry, new user so I can only tag 2 people in a post) looked into it, but I appreciate everyone’s help regardless; Thank you!
To answer the questions previously asked:
@Squiggler The following keys do not respond:
Q,w,e,g,h, fn(function key), f2, f4,f6, f7, f10, back slash key, right arrow key
@James3 When I installed the new keyboard (V2, so no firmware update needed), it was the exact same keys, and it was also immediate. That would definitely be a wild scenario if the second keyboard I bought was also faulty 
But as you said, not entirely impossible.
Framework Support has actually asked me to send my laptop in to them so they can preform a full diagnostic since none of the assumed fixes are working. I will be taking the laptop (and a small Bluetooth keyboard) with me next week while I visit some family, so I can continue trying any fixes until I’m back the following week and can send it out.
Thanks again to everyone!
Thanks for adding in the problematic keys. I defer to @James3 as to whether they form enough of a pattern to give some fault clues. Q-W-E looks like a line.
@catastrophic - the OP wished to tag you earlier. JFYI, I think.
Thanks for the tag! @chunkeylover59 I bumped up your trust level from 0 to 1 so you should have more perms moving forward.
@chunkeylover59
Once you do send the laptop back, I would be interested to find out what they find is wrong with it.
It is definitely a strange problem with no obvious cause, or at least no cause I can think of.
I have explained my fault diagnosis reasoning in previous messages.
Since the fw 16 keyboard uses diodes it is possible the matrix is somewhat aligned with the keys, so from the count of borked keys it could be just a single faulty row/column.
Another test.
This works on linux, i don’t know if it works on windows. There is probably a way to capture usb packets on windows.
Modprobe usbmon
Run wireshark and use it to capture usb packets.
Press working keys and see a new usb packet for each press and unpress.
Then try the non working keys and see if there are matching usb packets.
This will narrow down the problem to keyboard vs os drivers.
If you press key and there is no usb packet, it is a faulty or wrongly programmed keyboard.
If there is a usb packet, it is faulty os drivers.
When FW get the laptop back, their diagnosis should be quick.
- get one known working FW16 next to the faulty one.
- swap keyboards and see if the problem moves with the keyboard or not.
Hello everyone,
Sorry for going dark. I wanted to update that I sent the laptop off to Framework yesterday, so hopefully they will have it soon.
I’ll be sure to update you when I know more.
Thanks again for everyone help and suggestions!