I have a Framework 13 (11th Gen), and a few days ago I unfortunately caused some water damage. The water got in from underneath the laptop through the bottom vents.
After that, the device was completely dead β no lights, no response. It turned out to be a short circuit.
I managed to fix that fairly quickly (about 2 hours β my first time doing board-level repair!).
Now the boot diagnostic LEDs show the following pattern:
GGGGGGGGRRGG
So the red LEDs are:
9 Fan detected and spins up
I can actually see the fan spin briefly, then stop.
10 CPU reached S0 state
I couldnβt find much information about this. Could this mean thereβs still a short or fault in the CPU power supply? Is the CPU just done?
Hi, no damage to the BMS is no issue. Like i sad i fixed the shortcircut now when i connect the board to the Lab Power supply it dose not draw too much current.
I would suggest that you contact customer support. 9 and 10 being red means that those things were not detected. The CPU being able to reach S0 is the suspend state of modern standby. It in conjunction with the fan control not working speak to a power issue / damage.
Thanks for your suggestion. I wanted to give a bit more context about what happened. While debugging the short circuit on my FW13 (11th Gen mainboard), I traced the issue back to the 5V buck converter. During troubleshooting, I noticed that PLZ101 was getting quite hot, so I removed it.
Iβm not entirely sure what PLZ101 is β it seems to be an inductor (βLβ), but I accidentally lost it (it fell out of my tweezers; itβs an 0805 SMD). Removing it made the short disappear, but it looks like PLZ101 mainly bridges the 17V rail to the input side of the 5V buck converter. After carefully injecting voltage to the 5V buck converter, I identified the real shorted capacitor, but I had forgotten to bridge PLZ101.
After making the post, I realized I had wasted a lot of time troubleshooting, and then remembered that the removed PLZ101 could be the issue.
As a quick fix, I replaced PLZ101 with an SMD fuse I had on hand in the same package, acting as a temporary bridge. The laptop is now working, and Iβm writing this from my repaired FW13.
I am now coordinating with a local repair shop (whose owner I know) to get access to the official schematic, so I can replace the two components with the correct parts.