Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fixing a bricked Framework laptop

quantum5.ca

Post reply on HN
Print view View original

21–30 of 311 posts

Re: Fixing a bricked Framework laptop

#21

Post by spacemanspiff01 »

reshux wrote: post #3

I bought a Framework 13 in 2021. I was so stoked. I used it for 5 years, and of those 5 years only 1 was heavy use. I had to replace the battery and the input cover. I never had to do that before. I never had a laptop I wasn't able to use for 5 years so the repairability was actually not that much better for me. I gave up on Framework because after 5 years they still didn't give a crap about terrible battery performa…

From reading online, linux battery seems to be a-lot better on the new intel board, and also if you configure linux with sleep to hibernate, you get really good behavioral performance. My experience is that the sleep states really drain the battery since the low power mode is not _that_ low power, at least with the ram I have.

For context I have a 13th gen intel with the old battery and only get ~4hrs of battery life, but generally go a week or 2 between full shutdowns, since I hibernate all the time. I can close the lid, throw it in my backpack, not use it for the weekend, and when I open it it is ready to go, not having lost charge.

I generally have a better experience than when I was on windows.

Re: Fixing a bricked Framework laptop

#22

Post by Gormo »

benjojo12 wrote: post #16
anthonj wrote: post #12

I really don't understand how in 2025 a competent company can't implement a trival A/B flash update. Do they depend on some obscure contractor for the firmware and have no power here?

As with many things, "It's complicated" but effectively, yes Such system firmware is generally provided by AMI / Insyde / Phoenix and similar. There are a few vendors who decide to go their own way (notably google using a fork of Coreboot for their chromebooks), but it's generally list of vendors that you can count on a single hand. If it means anything I'm pretty sure AMI provides A/B updates on most products i've u…

But that's always been the case. Phoenix and AMI have been the dominant BIOS providers for over 30 years. Both have always provided modular tookits for OEMs to customize their own ROM images, write their own ACPI tables, etc. UEFI gives even more control to the OEMs. If Framework isn't doing that properly, that's on them.

Re: Fixing a bricked Framework laptop

#23

Post by mchristen »

My support experience has been quite similar. Lots of required evidence, slow responses, and then just links to buy replacement parts in the store.

The kicker is that the things they were telling me to buy didn't even fix the problem. My fingerprint reader was very flakey, and after replacing it and all cabling connected to it, it still didn't work.

They then told me to buy a whole new input cover which was the wrong solution again. The issue was the touchpad, which routes the signal for the fingerprint sensor through its circuit board.

They also encouraged me heavily to update the BIOS and firmware of everything aggressively before really digging into any of the kernel messages I was seeing.

All that said, it's really hard to complain that for $50 and some waiting I was easily able to fix the problem.

Compared to replacing the battery on a MacBook pro which took me 5hrs and required complete disassembly of the chassis sans fans it was a dream.

Here's to hoping that framework does better, they do seem to take well to community feedback.

Re: Fixing a bricked Framework laptop

#24

Post by maeln »

I have a framework 13 for. Actually the same model as OP (AMD 7040 series). I have never been as conflicted on a laptop as this one. I do love many things about it : The whole expansion card system is awesome. It does feel a bit redundant with a simple usb-c hub that do the usual network, hdmi, usb-a, but being able to set it on the side that fit my current setup is much appreciated. I love the form factor and the screen ratio also. The linux support have been very good for me. And being able to open it up with just one tool and have detailed repair manual is amazing.

But on that last point, it's also the first laptop in a while that I had to get into to fix something. The webcam never worked. That's not a linux issue, it's just that my fw13 is a hand me down from a previous colleague who I believe borked the webcam installation. But I don't use the webcam, so I never cared. On the other hand, when I first got it, the cpu fan was emitting a constant high pitch whine. After some research I wasn't the only one affected, and the support had me do a lot of steps before sending a replacement part (which was very easy to install, but the problem should not have been there in the first place). I also had some random crashes that I was never able to debug. The mic is very meh also. I never use it in anycase with my setup but still.

But at the same time, I don't see myself switching to another laptop. Despite all, this is still the laptop that felt the most "right" to me. I do believe that Framework has to seriously step up their support and QA game. But it does feel like it's a company that is "suffering from success". They got big investment, lots of publicities in some circle and so I feel like they have to produce and sell way more computer than the rest of the business can reasonably handle. I hope it's a “necessary evil” for them to get enough customers and revenue to start being able to attract more investment and being able to invest more in the “quality” side of the biz.

EDIT: I should say, being in the E.U make it so that I have an automatic 2 year guarantee, so I didn't have to experience the whole "just buy new parts lmao"

Re: Fixing a bricked Framework laptop

#25

Post by mananaysiempre »

semiquaver wrote: post #13

My framework was sitting in a drawer for two years and now will not turn on no matter how long I charge it. I assume there’s a dead coin cell in there somewhere or something that needs changed but it’s pretty disappointing.

IIRC the only Frameworks that have a coin cell in them are the 13-inch 11th-gen Intel ones (i.e. the OG model), and it should be right there staring you in the face as you lift the keyboard. There’s indeed a known design flaw[1] around that cell in that it the laptop isn’t wired to drain its own actual battery instead; an email to support or a look on the forums should allow you to sort things out.

[1] https://guides.frame.work/Guide/RTC+Battery+Substitution+on+...

Re: Fixing a bricked Framework laptop

#26

Post by semiquaver »

mananaysiempre wrote: post #25
semiquaver wrote: post #13

My framework was sitting in a drawer for two years and now will not turn on no matter how long I charge it. I assume there’s a dead coin cell in there somewhere or something that needs changed but it’s pretty disappointing.

IIRC the only Frameworks that have a coin cell in them are the 13-inch 11th-gen Intel ones (i.e. the OG model), and it should be right there staring you in the face as you lift the keyboard. There’s indeed a known design flaw[1] around that cell in that it the laptop isn’t wired to drain its own actual battery instead; an email to support or a look on the forums should allow you to sort things out. [1] https://guides…

Thanks, will try that.

Re: Fixing a bricked Framework laptop

#27

Post by [deleted] »

lostmsu wrote: post #14
semiquaver wrote: post #13

My framework was sitting in a drawer for two years and now will not turn on no matter how long I charge it. I assume there’s a dead coin cell in there somewhere or something that needs changed but it’s pretty disappointing.

My old crappy HP laptop boots with a battery pulled out.

[deleted]

Re: Fixing a bricked Framework laptop

#28

Post by drdexebtjl »

allenbina wrote: post #19
anthonj wrote: post #12

I really don't understand how in 2025 a competent company can't implement a trival A/B flash update. Do they depend on some obscure contractor for the firmware and have no power here?

I know some higher end gaming motherboards that were targeted towards the overclocking community had two bios chips for exactly this purpose and switching between them was trivial from what I remember. If you overclocked too far, you wouldn't brick your system. It seemed like overkill to me. I'm guessing this is less common than it's worth to fix in software, but then at least continue to give support for the issue.

If you overclocked too far, you could remove the CMOS battery or hold the CLR_CMOS button that these high-end boards probably had.

Two BIOS chips was supposed to protect you from bad BIOS updates or a bad BIOS mod, just like the scenario from TFA.

Re: Fixing a bricked Framework laptop

#29

Post by sokoloff »

zvmaz wrote: post #9
FfejL wrote: post #6

Was seriously considering getting a Framework to replace my aging ASUS. Upgrade- and repair-ability were my main motivations. But now I'm reconsidering. Not standing behind their own BIOS update is pretty horrible.

I had a very different experience with the Framework team. The battery died (within the warranty period), I reached out to them, they asked some questions, then sent me a brand new one. Very satisfied with my Framework laptop and the customer support. I can't imagine buying another laptop.

Replacing a battery that failed under warranty should be a baseline expectation.

Not "terrible" obviously, but a slight negative that the battery failed under warranty and a slight positive that they honored their published warranty.

Re: Fixing a bricked Framework laptop

#30

Post by mananaysiempre »

Gormo wrote: post #22
benjojo12 wrote: post #16

Earlier quoted context omitted.

As with many things, "It's complicated" but effectively, yes Such system firmware is generally provided by AMI / Insyde / Phoenix and similar. There are a few vendors who decide to go their own way (notably google using a fork of Coreboot for their chromebooks), but it's generally list of vendors that you can count on a single hand. If it means anything I'm pretty sure AMI provides A/B updates on most products i've u…

But that's always been the case. Phoenix and AMI have been the dominant BIOS providers for over 30 years. Both have always provided modular tookits for OEMs to customize their own ROM images, write their own ACPI tables, etc. UEFI gives even more control to the OEMs. If Framework isn't doing that properly, that's on them.

It appears that Framework contracted out the development of their (Insyde-based) firmware to somebody who, to put it mildly, does not treat them as a priority. Either way, Framework’s firmware is really bad, and that’s entirely on Framework; you can look around on the forums for the horror stories in the (open) EC code around power delivery for instance.

As another example of a vendor low-key screwing Framework in a way that I think it’s entirely appropriate to blame Framework themselves for, the first couple 13-inch models could charge off 5V chargers. The newer ones still have the necessary hardware, but whoever they get their power circuitry from cut that bit from the firmware on a newer chip version, and Framework obediently went “welp, guess we don’t have that feature anymore”.

Post reply on HN