Coreboot Improvements Land For Lenovo Laptops

[phoronix]

Phoronix: Coreboot Improvements Land For Lenovo Laptops

It's been an exciting past few weeks for the open-source Coreboot project. After 2013 was ended by the FSF endorsing its first (Coreboot-powered) laptop and Google landing a lot of Coreboot changes to benefit the increasingly popular Chromebooks, January already got off to a good start with AMD Gizmosphere support coming to mainline Coreboot and Allwinner A10 / Cubieboard support. The latest work in the Coreboot world are Lenovo laptop improvements...

http://www.phoronix.com/vr.php?view=MTU2OTA

[mark45]

In layman's terms, can Coreboot be used on new (year 2008+) motherboards?

If not, because it lacks support (to be developed) or because it's impossible?

[GreatEmerald]

In layman's terms, can Coreboot be used on new (year 2008+) motherboards?

If not, because it lacks support (to be developed) or because it's impossible?

I think the answer to the first question is "maybe". Nobody really knows until it's tested, and nobody really wants to test because there's a fair chance of bricking the hardware. And I think the answer to the second question is "it depends", as some boards have certain features that makes it hard to flash them with Coreboot (but not all of them).

[curaga]

The e350m1 is a 2011 mobo and fairly well supported.

[boltronics]

Looks like the Lenovo X201 (2010 12" 1280x800 LCD, i5-540M CPU, 4G RAM) is starting to get some support.

http://www.coreboot.org/Supported_Motherboards

The current flashing procedure will scare a lot of folk away though. Hopefully someone can figure out how to work around the bootblock lock so disassembly is no longer required. Further down the wiki page suggests some progress has been made in this direction already.

[r_a_trip]

Coreboot is one of those projects thats always interesting. A project which is attractive from a security and FOSS standpoint. But also a project that seems to be perpetually in catch up and only seems to support a limited catalog of hardware and almost all of the time not the hardware you happen to have or fancy. Combine that with a fairly hands on approach, no ready to go images and a very real chance to bork your hardware and it simply isn't a project suitable to the casual end-user.

The only way to get your hands on a hassle free Coreboot machine is to get a Chromebook and anchor your fate to Google. I know you can futz about with developer mode on a Chromebook and install certain Linux distro's, but it doesn't have the same range of ease of use one of those evil proprietary BIOSes or UEFI's has.

[chithanh]

Coreboot is one of those projects thats always interesting. A project which is attractive from a security and FOSS standpoint. But also a project that seems to be perpetually in catch up and only seems to support a limited catalog of hardware and almost all of the time not the hardware you happen to have or fancy.

You could have said this about that whole Linux thing not too long ago. Currently you need to shop for hardware that is coreboot compatible. This may or may not improve, as it did with Linux.

The only way to get your hands on a hassle free Coreboot machine is to get a Chromebook and anchor your fate to Google. I know you can futz about with developer mode on a Chromebook and install certain Linux distro's, but it doesn't have the same range of ease of use one of those evil proprietary BIOSes or UEFI's has.

I don't think that these assertions are based in facts.

Did you ever try to install Linux on a fast boot enabled UEFI system? You can't even enter the UEFI setup menu, because fast boot will not even initialize the keyboard and mouse before the OS loads. You need to boot Windows and follow an 8-step procedure in order to make the setup appear on next boot. Entering developer mode and disabling verified boot on Chromebooks is usually two or three steps.

[pgeorgi]

Coreboot is one of those projects thats always interesting. A project which is attractive from a security and FOSS standpoint. But also a project that seems to be perpetually in catch up and only seems to support a limited catalog of hardware and almost all of the time not the hardware you happen to have or fancy. Combine that with a fairly hands on approach, no ready to go images and a very real chance to bork your hardware and it simply isn't a project suitable to the casual end-user.

Sounds about right. The image situation is partly because we relied on the VGABIOS for long. On some models, we could provide freely redistributable images since that changed for some chipsets where coreboot provides native graphics init. It's still not the ordinary end-user project. All the FUD about "don't install Linux, it might break your computer" that was popular in the late 90s certainly applies once you replace Linux with coreboot.

Maybe we'll get some vendor support in the future (since they could reduce the BOM costs by ~$5, or whatever BIOS vendors demand these days), but we have that hope for a number of years now. But there are now also some embedded teams at companies using coreboot, so maybe it's really starting now?

The only way to get your hands on a hassle free Coreboot machine is to get a Chromebook and anchor your fate to Google. I know you can futz about with developer mode on a Chromebook and install certain Linux distro's, but it doesn't have the same range of ease of use one of those evil proprietary BIOSes or UEFI's has.

Developer Mode is ChromeOS developer mode, and so it's relatively inconvenient if you're actually want to use the system as an ordinary computer. If you want to break all ties to Google on a Chromebook, go the procedure documented by Google to tighten a screw and use the coreboot code provided and upstreamed by them to install an alternative firmware yourself.
No, it's not simple, but Chromebooks are primarily sold for ChromeOS - I'm still glad that there's a vendor that provides a hackable system in the first place. Apart from bugs, none of the proprietary BIOSes or UEFIs provide that level of access (eg. it's much harder to install coreboot on those lenovos, even if you have a premade image)

The "turn a screw" model (which is an adaptation of the old "use jumper to unlock write-protect") really gets a bad rap these days, even though it's the only way to keep the firmware safe from unintended modification (be it corruption or malware). As a vendor they don't want people to brick their systems in large numbers by using joe random's m0dding tool ("makes your computer 2% faster!!!11") found on some obscure website. And as the go-to guy for computer issues for people in my peer group, I agree...

[GreatEmerald]

Did you ever try to install Linux on a fast boot enabled UEFI system? You can't even enter the UEFI setup menu, because fast boot will not even initialize the keyboard and mouse before the OS loads. You need to boot Windows and follow an 8-step procedure in order to make the setup appear on next boot. Entering developer mode and disabling verified boot on Chromebooks is usually two or three steps.

Pulling out the hard drive is just as much work (sometimes less) as turning a screw. Unless you're unlucky enough to have bought a laptop with a soldered drive.

[Knopornef]

The current flashing procedure will scare a lot of folk away...

Then again Lenovo itself seems capable of bricking its Thinkpads with bad BIOS updates (T430 Failed Bios Update. Five Beeps, Blank Screen.) . I have a Thinkpad that has been sitting in a drawer for a month, waiting for Lenovo to fix the BIOS. Maybe it is time I try Coreboot!