Quick Answer: A company's Framework Laptop 16 arrived with a faulty keyboard module, and three months of support failed to fix it. Support swapped the wrong part, then closed the case as "No Fault Found." For Framework laptop support problems like this, expect long delays, and check the escalation path before you standardize on fleet hardware.
Framework laptop support is the part of the buying decision most reviews skip. Spec sheets tell you about repairability and modularity. They don't tell you what happens when the box arrives broken and the vendor's script takes three months to reach the actual fault. One small engineering team learned this the hard way. They bought a Framework Laptop 16 for a new developer, around 3,000 EUR once configured, and the machine failed before any operating system loaded. The original post lays out the full timeline. Here's what it teaches about buying modular hardware.
The Fault That Hid Behind a Workaround
The laptop greeted the user with a "missing input module" screen, before the BIOS and before any operating system. The keyboard wasn't detected in its normal position. Moved to the left, it appeared as a numpad. Nothing worked: no keyboard, no touchpad, no numpad.
The BIOS offered a fix: a "Force Power for Input Modules" option that bypasses module detection. With it enabled, everything worked. Framework's own documentation says not to leave it on permanently because it may be harmful to the hardware.
Here's the counter-intuitive part. The workaround masks the fault. When the team shipped the laptop to Framework's repair center, the option was still enabled, so the technicians were testing a machine where the failure was hidden. Support had asked for that workaround as a troubleshooting step, and it became the reason the fault was hard to see later. If you're evaluating any modular laptop, ask the vendor what their diagnostic process looks like when a documented workaround is active.
Why the Diagnostic Mattered More Than the Parts
This is where the team's engineer did the work support should have done. He updated the keyboard firmware, which only worked with Force Power On, and ran Framework's own framework_tool with the input deck option. The output was specific: the keyboard module reported the ID of a numpad, which the firmware read as two numpads and no keyboard. That made the input deck look incomplete, so the firmware never enabled the power rail for the input modules.
He then isolated the variables. The keyboard misidentified itself in every slot. The numpad identified correctly in the same slot. With everything removed, the baseline was clean. The wrong ID followed the keyboard, not the slot or the cable.
That's a reproducible result, and it's the kind of isolation you want from any hardware investigation. The practical lesson: when you report a hardware fault, include the exact command, the output, and the swap matrix. A one-line reproduction case is much harder to ignore than a set of photos. Here's the catch, though. Support's next action was to replace the midplate. Not the keyboard, the only component the diagnostic pointed at. The midplate arrived a week later, and the fault remained.
The Cost Nobody Puts in the Spec Sheet
Support tickets rarely fail in one dramatic moment. They fail through accumulation. The timeline below comes from the post:
| Stage | Date | What happened |
|---|---|---|
| Out-of-box failure | Early August | Laptop shows "missing input module" before BIOS |
| First ticket | August 13 | Two weeks of scripted steps, photos, and BIOS reinstalls |
| Escalation request | August 24 | Manager requested; team asked for the same midplate photos again |
| Address check | Late August to early September | Ten days of "verify the shipping address" after a colleague replied on the thread |
| Diagnostic report | August 28 | Full framework_tool report sent with reproduction command |
| Wrong part replaced | September 7 onward | Midplate replaced; fault persisted |
| Keyboard replaced | October 8 | New keyboard detected, but a new bug appeared |
| Repair center verdict | November 20 | "No Fault Found," blamed on keyboard layout |
Notice the pattern. Each reply came from a different agent. Each asked for information already provided. And each escalation carried a warning that it "may take 5 to 7 working days." If you're buying for a team, budget for that latency. A single laptop out for three months is a real cost, and a colleague without a usable machine is a cost you'll feel every day.
The C Key That Sent a Delete
After the keyboard swap, the new module worked, but pressing C sent a lowercase c followed by an escape sequence that the terminal reads as Delete. The team captured it with showkey, a Linux console tool that prints raw keycodes:
$ showkey -a
c 99 0143 0x63
^[[3~ 27 0033 0x1b 91 0133 0x5b 51 0063 0x33 126 0176 0x7e
An external keyboard on the same machine produced a single c. That comparison is the key evidence. It rules out the operating system as the cause and points at the hardware.
This is also where the common advice fails. Most people test a keyboard by typing a sentence and reading the result. A spurious Delete at the end of a line deletes nothing, so you'll never notice it. Type a word with a c in the middle, though, and the next character disappears. That's the test that matters. For a more formal check on Linux, use showkey -a or evtest to see the raw events rather than the rendered text.
The Verdict and the Layout Argument
The repair center concluded "No Fault Found" and suggested the problem came from installing the wrong keyboard layout. That explanation falls apart on two points. The first failure happened before any operating system existed, at the "missing input module" screen. A layout is an OS-level mapping from keycodes to characters, so it can't affect a machine that hasn't booted. The second failure happened in GRUB, before the kernel loaded, and on a live USB with both QWERTY and AZERTY layouts, the C key still misbehaved.
A layout maps a key to a character. It doesn't make one physical key emit two scancodes. That distinction is the whole argument, and it's a clean one to bring into any vendor conversation.
To be fair, a support team can make honest mistakes, and no vendor is immune to DOA hardware. Every hardware company ships some broken units. The issue here isn't that a part failed. It's that the process didn't read the evidence, and the final conclusion contradicted facts in the ticket from the first day.
Modular Hardware: When the Trade-off Makes Sense
Modularity is a real advantage in some settings. A modular laptop lets you swap a keyboard deck, a battery, or a port module without replacing the whole machine. That's valuable in a repair shop, a lab, or a team that already keeps spare parts. It also means more connectors, more firmware interactions, and more places where a fault can hide.
The trade-off looks like this:
- Choose modular when your team has in-house repair skill, keeps spare modules, and values the ability to diagnose and swap parts without a vendor round trip.
- Choose integrated when you need a predictable warranty turnaround, a single-vendor support queue, and a machine you can replace in a day.
Neither option is free. The question is which failure mode you can tolerate more easily.
What to Check Before You Standardize on Any Vendor
Before you order a fleet, run a short acceptance test on one unit. Here's a practical sequence:
- Boot to BIOS with no workarounds enabled and confirm every input device is detected in its normal position.
- Test the keyboard with
showkey -aon Linux, typing words with repeated letters, not just full sentences. - Ask the vendor for their escalation path in writing, including the named owner for a ticket and the expected turnaround.
- Record the serial number, purchase date, and firmware version before anything goes wrong.
- Keep a log of every diagnostic command and its output so you can reproduce the fault for a new agent.
Red flags to watch for: support that asks for information you already sent, a request to reset or reinstall drivers for a problem that happens before the OS loads, and a closure that depends on a fault the vendor never tested. If you see two of these in the first two weeks, escalate early rather than waiting for a third.
Frequently Asked Questions
What is the Framework Laptop 16 input module problem?
The Framework Laptop 16 uses a modular input deck. If the firmware misidentifies a module, such as reading a keyboard as a numpad, it won't enable power for the input modules. The machine then shows a "missing input module" screen before the BIOS. The BIOS option "Force Power for Input Modules" can bypass detection, but it's not meant to stay on permanently.
How do I test a laptop keyboard for extra key codes on Linux?
Run showkey -a in a virtual console, then press keys and watch the raw output. Type words containing repeated letters, such as "cc" or "hello," rather than just a sentence. Compare the results with an external keyboard. A single key that emits extra escape sequences, like ^[[3~ for Delete, points to a hardware or firmware fault.
Why does my keyboard send a Delete key when I press one letter?
This usually means the keyboard is emitting an extra escape sequence along with the letter. A layout can't cause this, because layouts map keycodes to characters and don't change what a key sends. Test the hardware with raw keycode tools first, then check whether an external keyboard behaves the same way.
Is Framework laptop support good enough for a company fleet?
It depends on your tolerance for delays and your in-house skills. The source team had a reproducible diagnosis that support didn't act on, and a repair cycle that stretched past three months. If you buy modular hardware, plan for longer turnaround times, keep spare parts on hand, and run an acceptance test before you commit.
Framework laptop support is only as strong as the process behind it, and you can't judge that from a spec sheet. Before you standardize on any laptop, run a short acceptance test on one unit and write down your escalation path. Pass this checklist to whoever is about to order hardware for a team, and ask them to run showkey -a on the keyboard this week and note the result.