Ordering version for coreboot

How to order Framework to run coreboot?

Ultra 3 versions have Coreboot support in mainline. I’m already experienced in coreboot building and deployment, but in newer CPU generations - I need to get laptop with non-fused CPU (CPU is typically fused in the first boot with bios that require fusing).

What is the status in the Frameworks and if it’s fused by default, how to buy unfused?

The closest device to working is the Framework 16, see this long thread:

The question on whether you can re-flash the BIOS with a custom build, and the fused status, could be asked via a support ticket (someone may know here, but you may wish to obtain an official/staff answer).

There is currently no method in which you can buy an Intel Mainboard that will run Coreboot with the sole exception of the 12th Gen Chromebook version that has long been since discontinued. If you want Coreboot, AMD is currently your best bet as @Squiggler has indicated.

No so bad - for example novacustom have options with Boot Guard off.

Question is - why Framework refusing this?

Go ask Framework. To be clear, I know there are laptops with Intel CPUs and Coreboot. I just meant there are no Framework laptops as such.

Framework sent some unfused BootGuard disabled laptops to some developers to port Coreboot. To my knowledge they all got bricked and that was that. Matthew Garrett was among them but I don’t know any of the others.

Your verb is doing a lot of work here. Most decisions by a business are business decisions: they are a complex mix of trade-offs made in order to try to keep costs going out lower than payments coming in.

It is said on the other thread that the cost of a commercial BIOS is obscenely high, so there is likely to be good business reasons to switch, but I should think commercial licensing for hardware drivers, lock-in effects of existing BIOS licensing, and availability/stability of CoreBoot are all factors.

For what it is worth, I’d reflash my 13 Pro with CoreBoot if doing so was supported and I knew this BIOS to be stable and maintained. But that’s not the situation we have at present.

But that situation cannot really develop when the laptops are locked down in the first place.

Framework has built much of its identity around openness, yet this decision actively undermines that principle. And my question is: why?

The cost of allowing an unlocked platform should be minimal. From a manufacturing perspective, it essentially comes down to offering an alternative factory firmware and Boot Guard provisioning configuration, rather than permanently locking the platform through irreversible fuses.

Nobody is asking Framework to develop or maintain Coreboot themselves. The community can do that. Quite possibly including me - I’m currently porting Coreboot to my own hardware and already have a corporate NDA with Intel.

Maybe it wouldn’t happen immediately. Maybe it wouldn’t be suitable for everyone. But Framework would eventually benefit from a community-supported firmware alternative, attracting more technically minded customers and gaining an excellent marketing opportunity. At very little cost to the company.

And Intel is actually far more Coreboot-friendly than AMD. Intel provides FSP, contributes its own reference platforms and development board ports to upstream Coreboot, and generally offers a much more accessible environment for independent firmware development. AMD, by comparison, is practically a desert in this regard. The difference is striking once you start working with these platforms yourself.

What I would genuinely like to understand is why Framework insists on enforcing Intel Boot Guard in the first place.

Intel doesn’t require it. They provide the mechanism, but the decision to enforce it rests with the manufacturer.

Is it about maintaining control over the platform? If so, why? Especially for a company that makes openness such a central part of its identity?

At this rate, Framework might actually convince me to build an open motherboard for their chassis instead of buying one of their laptops. Not exactly the outcome they were aiming for, I imagine.

I’m already working on my own hardware design, although currently only around the Intel N300. The problem is that I genuinely can’t find a laptop worth buying: the manufacturers offering more open platforms tend to have mechanical designs that really don’t meet my expectations.

And I suspect I could find at least a few other people interested in a genuinely open motherboard that fits a well-designed Framework chassis.

It would be rather ironic if Framework’s biggest contribution to open laptops ended up being the chassis, while the community had to replace the motherboard to get the openness.

I think you’ve got it into your head that FW’s decision here is wilful or obstinate: your word choices indicate that you believe they’re acting in bad faith. I think it is far more likely that this decision is the outcome of a complex set of trade-offs.

Do have a read the other thread. Elly is permitted by their employer to spend some of their time on a CoreBoot port for the FW 16. At one point they were being helped by a FW technical employee; I had surmised that FW staff don’t have a specific CoreBoot project signed off, but there is no explicit prohibition on their giving a steer here or there.

FWIW, I am guessing that FW laptops will get CoreBoot eventually. I suspect it will get into a decent shape by slow external efforts, and FW will pick up the final integration work. We’d all like it tomorrow of course, but I’d also like a Lamborghini. :squinting_face_with_tongue:

I think you’ve misunderstood my point.

I’m not suggesting that Framework is acting in bad faith, nor am I attributing any malicious intentions to anyone. I’m simply saying that I genuinely don’t understand this particular decision, because it doesn’t seem to make much sense.

External contributors cannot meaningfully work on a Coreboot port if the hardware they can actually buy has Boot Guard permanently enforced through blown fuses. That’s the fundamental obstacle I’m talking about.

And I’m actually one of those people who might otherwise contribute. I’m currently porting Coreboot to my own hardware, so this isn’t just a theoretical interest.

I’m not asking Framework to fund, develop, or maintain Coreboot. I’m asking why they don’t simply make unfused boards available to people willing to do that work themselves.

The incremental manufacturing cost of offering such a configuration should be minimal. Framework wouldn’t have to promise support or guarantee that Coreboot would ever work. The community could take the initiative, experiment, and gradually build something useful.

Framework has very little to lose and potentially quite a lot to gain - community contributions, additional customers, and a stronger reputation for openness.

I fully understand that business decisions involve trade-offs. But that doesn’t mean every decision automatically makes sense. I’m asking what the actual trade-off is here, because I can’t see one that justifies permanently preventing owners from running alternative firmware.

That would be because all evidence points to that conclusion.

@Petr99 is correct in both asking the question and questioning the validity of the answers given. Go ahead and read the thread linked in my bio @Squiggler . I asked those questions too and got shut down hard. Framework twisted my words or at a minimum did not understand what I was trying to say and misconstrued my statements in the worst possible light.

Additionally, the very existence of both the 12th gen Chromebook model (running Coreboot!) and numerous other vendors running modern Intel CPUs with Coreboot gives away the lie that it’s some particularly difficult challenge when those vendors are significantly smaller than Framework is.

The willful ignorance of ignoring the link between hardware and software is pathetic and Framework does not deserve your defense in this particular case.

I hang around because I like the community well enough and I like the hardware. It wasn’t for nothing that I said that I got burned on firmware. Also, it would be far more defensible to use properitary firmware if it weren’t so f$&king bad to use. How many generations of boards have suffered from the bug that locks the CPU to some absurdly low clock? I think it’s been literally every generation. Or the inability to explain why fwupd isn’t properly supported on some models?

I don’t think you’ve been on the forum as long as I have. Framework has not covered themselves in glory when it comes to firmware.

True. FW tends to be a bit tight-lipped about why this or that decision was made, and I don’t suppose this thread will uncover it. I am not thrilled about that, but it is what it is. The lack of information on this is likely to be a commercial decision too.

I don’t know the answer to this, but in general I tend to regard this as an NDA/restriction foisted upon a hardware maker from a third party (commercial BIOS author, radio board manufacturer, etc).

I don’t have any views about FW’s choice of BIOS partner, but I do think commercial BIOS makers in general would try to sabotage competing efforts through legal mechanisms. Computer makers may be coerced into this by the realities of the market: too few choices for there to be decent choice and competition.

Step back and look at the other vendors Framework needs to put a product to market for just the main board.

Now try to convince each one of those companies legal teams to open up their IP so something like coreboot would be possible. Most of them will stare with blank faces while the others who even know what coreboot is will just smugly say that is not currently feasible.

The issue is way above Framework and is being driven by the companies that are licensing their technology for Framework to use.

This is similar to asking GM or Honda to open source their whole automotive platform so people can tinker with parts they may or may not want people to play with. There are legal ramifications in the automotive world even if there were sign offs and disclosures; someone would come back and say well they allowed X to happen and now that caused Y for which the manufacturer would be sued for because it is their name on the end product.

Don’t be such an apologist. This has been a desire for literal years. How much effort do you think it would be for Framework to purchase just one laptop that supports Coreboot and identify the various ICs necessary and integrate them into the next iteration of board design? The audio chips, etc.

We are all very aware of the pervasive use of NDAs. But the fact that smaller companies have accomplished this task is proof enough that it’s possible. Clearly those companies were able to find the suppliers they needed. And not all of those designs are Clevo rebadged laptops! Some of them are bespoke like Framework!

Framework’s special sauce is in repairable hardware. Nobody is going to question nor care about switching suppliers for how they provide audio or the webcam or any number of other chips on the board. There is no special software integration that makes a Framework laptop, which is very different from a MacBook Pro. Those have bespoke unique chips with their own special quirks and I do not envy the work that the Asahi team has put in for compatibility. No Coreboot port would approach that level of effort.

Not much different to companies trying to stifle R2R is it? Yet the FW laptop exists…

It can be done. Framework refuses to do so and will not truly explain why. That’s their perogative. Let’s not extrapolate further about potential technical difficulties or legal quagmires. That’s just speculating a defense out of nothing. They won’t say why they refuse, it’s just a quiet refusal. That’s all. Not much different than any other customer hostile company in that regard. Framework isn’t anyone’s friend and that’s fine. We should all treat them as such.

This reminds me of other threads where, for example, we want things like multiple screens for one laptop to pick from, or to be able to get the other upgraded parts when we order an upgraded mainboard (e.g., we can order the new Core mainboards, but not the fingerprint reader or backlit keyboard yet; &c.).

+1 Coreboot and infinity for Open Source Hardware! Hopefully more in time. I still haven’t gotten a 13 chassis and the RISC-V to play with, but with prices all around these days, it’s on hold for me. :-1: :frowning:

:victory_hand: :smiley: