Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

49% Positive

Analyzed from 2034 words in the discussion.

Trending Topics

#framework#bios#battery#laptop#years#warranty#update#firmware#should#more

Discussion (19 Comments)Read Original on HackerNews

SCdF•about 1 hour ago
I agree with their conclusion.

I somewhat regret buying my framework laptop at this stage, because the answer to every fault is "buy a new component, from framework".

I'm not sure I blame them for this really, but there is no competitive market of parts (or really any market at all), which means that the reality is that you're just locking your money to them. They also often have stock issues, so woe betide you if your component fails at the wrong time.

It's very hard to predict costs here, but framework laptops do seem to fail more than other brands, and their laptops do tend to be more expensive. In comparison to MacBooks I've used over the years, which other than screen delaminating, have been faultless, at least.

beanjuiceII•41 minutes ago
having 2 fw 13s this is my experience as well (and also friends who bought into FW); i was willing to give the 13 pro a try until they downgraded my order. I inevitably cancelled and went with a dell xps14 and its a fantastic laptop. I am unsure bout any future fw purchases. also my m1 macbook pro is made so well I've abused this to the cows come home and i feel like it still has another 3+ years to it..

everytime someone brings up the e-waste aspects of fw, i don't know if its that simple...because i've definitely already generated much more e-waste with my frameworks than any other laptop i've bought in the last decade

that being said, i do like the fw vision, but they might be trying to do TOO much that their quality is suffering for it

throwuxiytayq•16 minutes ago
> because i've definitely already generated much more e-waste with my frameworks than any other laptop i've bought in the last decade

How so? Most FW parts seem quite resellable, did you just throw them away after upgrading or something?

anthonj•31 minutes ago
My conspiracy theory is that selling parts is pretty much their main business case.

A modular gpu using a new standard that is form-factor specific for only a specific model? Matte panel released a few months after the first 13.5 model was released with glossy panel as only option?

It sounds a bit fishy to me. But maybe I'm just a bit too cynical .

SCdF•16 minutes ago
> My conspiracy theory is that selling parts is pretty much their main business case.

I think this is absolutely what you sell to investors. For it to be attractive to consumers though (and thus attractive to investors, since people actually need to buy the thing), there has to be a balance. They haven't even managed to conjure up a market for third party expansion cards, which feels like the lowest of hanging fruit.

At the moment they are living on borrowed time and good will from the tech / hippie community who want to be more sustainable and customizable. I think they have likely lost me at this point. I don't know how close they are to losing everybody else.

throwuxiytayq•15 minutes ago
Manufacturer forces you to throw away previous device and buy a new one: it's a conspiracy to make money

Manufacturer lets you replace each part separately: it's a conspiracy to make money

anthonj•about 2 hours ago
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?
benjojo12•about 1 hour ago
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 used with their stuff.

Gormo•about 1 hour ago
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.
mananaysiempre•about 1 hour ago
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”.

allenbina•about 1 hour ago
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.
drdexebtjl•about 1 hour ago
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.

quantum5•27 minutes ago
Original author here, and I agree. When overclocking, the most important feature is probably resetting the CMOS with one easy to reach button.

I was testing ECC previously in https://qt.ax/ecc and was trying to overclock the RAM to induce faults to confirm ECC was fixing them. Since I was using a cheaper board, I had to use keys to short the CLR_CMOS header and that got old really quick... I didn't ultimately succeed in creating a barely stable overclock that generated a ton of ECC errors, but that was a very awful experience.

Having some sort of BIOS recovery is definitely the baseline I'd expect these days, and having two BIOS chips so you can just keep using the device as if nothing had happened is the best solution.

gonzalohm•about 2 hours ago
A bit off-topic, but kind of relevant. I firmly believe that if installing custom firmware voids the warranty of a device, installing official updates should extend the warranty.

I'm tired of sloppy updates or change of behavior that mess with how I use MY device.

At this point, I'm convinced Google is doing this on purpose. My Google TV has become slow since the Gemini update, which I wasn't asked if I wanted it. My pixel battery life gets worse with every update, etc.

dd8601fn•about 2 hours ago
I’ve had that problem with Roku, Google, and Vizio updates too, over the years.

At this point I’m comfortable saying that on device “Smart TV” software is a crime against humanity, full stop.

dec0dedab0de•about 2 hours ago
Google bricked all of the old fitbit scales with a firmware that glitches out and drains the battery. There were tons of reports at the time, but the devices were out of warranty so they didn’t fix it.
markbnj•about 2 hours ago
Good story, and surprising that there was so little assistance from the OEM. As an aside, I got to test out Asus crash free BIOS a couple of weeks ago. A strong thunderstorm hit and before I could get to my office a rapid series of deep voltage drops occurred. I shut down my systems and waited out the storm. When I powered my Asus tower back on it failed to POST, automatically restarted, recovered the BIOS (CMOS settings I assume), restarted again and booted Windows. Pretty slick, and instantly removed that cold lump of lead that had formed in my gut.
semiquaver•about 1 hour ago
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.
mananaysiempre•about 1 hour ago
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+...

throwaway2037•24 minutes ago
I looked at the shared link. The laptop manuf is recommending that people solder a wire between two points to eliminate a coin battery from the motherboard. Wild.
semiquaver•about 1 hour ago
Thanks, will try that.
lostmsu•about 1 hour ago
My old crappy HP laptop boots with a battery pulled out.
reshux•about 2 hours ago
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 performance on Linux distros.

I was using a Macbook Pro before. Went back to a Macbook Pro again. I don't want a Mac. I just can't find anything else remotely worth my money.

spacemanspiff01•about 1 hour ago
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.

FfejL•about 2 hours ago
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.

zvmaz•about 2 hours ago
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.

sokoloff•about 1 hour ago
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.

throwaway2037•23 minutes ago
This reply seems like a non-sequitor and does not respond to GPs concern. How would you feel if a BIOS update outside of warranty bricked your motherboard? I am sure you would not say the same.
spacemanspiff01•about 1 hour ago
I had good experience within warranty period, but there was still some funky-ness with a non-posting board... I do sometimes wonder if it was a bios corruption - It died after running the battery 100% to zero...

That being said, I think the particular bios-chip is a design flaw that they should communicate about and fix for future boards... Probably a teething issue thing, but they should fix it. Either a usable replaceable chip so they can just send out a fix, or the fallback bios chip....

alnwlsn•about 1 hour ago
I like my framework, but I do wonder if the repairability angle is overstated if you're already used to fixing normal laptops. Yes, Framework's parts are easier to find, and the laptops are easier to open, but it's not like doing any of the typical repairs - keyboard, screen, touchpad, battery - are impossibly difficult on those other guys.

Used thinkpads and the glut of EBay parts for them reach about 85% of what Framework does for me, and at half the price. But it's a different experience.

Framework does seem like better build quality than most laptops I've had, but I'm used to cheap crappy ones.

On the other hand, you do seem to find more cases of multiple people doing things like the linked bios update procedure on framework.

bodge5000•about 2 hours ago
After months of waiting on preorder (in which time I could've cancelled it), my Framework 16 finally arrived just yesterday, so this is a very unfortunately timed article for me.

Mine is using the AI 300 chip and is presumably on the latest bios so this specifically wouldn't be a problem for me, but it doesn't fill me with future confidence either, though I suppose if you look hard enough you can find similar stories about any manufacturer

Sweepi•about 2 hours ago
> For three years, the laptop has served me well, until Framework suggested via newsletter to install the latest BIOS update, version 3.20, with a bunch of security fixes. Unfortunately, the system hung and displayed a corrupt image on the screen, signifying a failed BIOS flash.

> Naturally, I reached out to Framework support, who told me to unplug the laptop, let the battery drain, and power it back on again afterwards, hoping the laptop would recover by itself. Unfortunately, it never did, and after giving Framework a bunch of information, they informed me that since my 1-year warranty has expired, I have no option but to purchase a new Framework motherboard, which will cost at least CA$500.

This is very disappointing.

  1) Framework failed in not implementing a bootloader which takes a BIOS file on a USB-Stick and flashes it w/o requiring a working BIOS/Firmware or even a CPU/RAM. Every $70 Desktop-Mainboard worth its salt has this feature.

  2) Considering 1) and that it was an official BIOS that caused the issue, Framework should repair (replacing/re-flashing the BIOS chip) for shipping fees max.

I am furious. We have recovery-bootloaders in devices with $10 bill of materials. Its not rocket science!
throwaway2037•17 minutes ago

    > bootloader which takes a BIOS file on a USB-Stick and flashes it w/o requiring a working BIOS/Firmware or even a CPU/RAM
For those unaware, this is sometimes called "BIOS recovery" or "crashfree BIOS". In short, if a BIOS update fails and bricks your motherboard, you can load the image of a known-working BIOS update onto a USB memory stick. Normally, a single USB slot on the motherboard has a special marking to indicate that it can be used to "unbrick" the motherboard. Insert the USB memory stick, start the PC, and the BIOS recovery should be automatic. I agree with the parent post: This would be an excellent feature for Framework Computer to add. From a simple Google search, it appears that their desktop computer already has this feature.
gnfargbl•about 1 hour ago
> Still, I was very disappointed that Framework chose to entrust sensitive information to a third-party who obviously couldn’t keep the data safe.

Then you're going to be very disappointed a lot. When HIBP first came out, I worried over each incident. These days, breaches of non-payment data are so common that I don't even bother to sign up for notifications.

When it comes to PII, we live in a de facto panopticon.

jcastro•about 2 hours ago
Don't bother with the motherboard, the new BIOS is worse. I have two that just randomly shut off whenever they feel like it. I just bought a thinkpad instead, shrug.
Advertisement