I think EoL Chromebooks are a good opportunity for Coreboot to present
itself to end users.
Right now Chromebooks use Coreboot but nobody knows that.
But once a Chromebook reaches EoL people will either throw it away or use
it with the insecure and outdated browser version they have until it
well, in order for that to happen, someone would have to take ownership of
that - are you volunteering? =)
There's also the issue of blobs that can't be redistributed, which is AIUI
one of the reasons why coreboot doesn't offer compiled firmware.
Additionally, some models (ie, Chomeboxes)
Emi,
I think this is what you're looking for:
https://www.coreboot.org/Supported_Motherboards
It contains the commit hash, build config, and a few other logs for each
device/commit. It is user submitted though, since there doesn't exist a
test setup for every supported device.
Right now, I'm
but then you get into the situation where coreboot (org) is providing
hashes for binary firmware it didn't build / isn't providing / can't easily
validate. And pulling that from a live system like is done with board
status isn't easily done, for multiple reasons. That's one of the reasons
for
Does anyone have one of the Thinkpads with Bootguard enabled that
prevented coreboot installation? I'm interested in poking at the full
firmware image (including the ME region) to verify my understanding
of how it is implemented.
--
Trammell
--
coreboot mailing list: coreboot@coreboot.org
> John Lewis has some upstream firmware for the older SandyBridge/IvyBridge
models,
> but his Haswell firmware is build from Google's tree/branches not
upstream.
> He also has no plans for any future upstream firmware.
Once upon a time when John worked for SAGE Electronics. I remember this
time,
Just listing SHA hashes of the recommended ROMs for a given Chromebook
would be an improvement.
The hash is sufficient to verify a build / download. But it has to come
from Coreboot.
Actually, this would be a nice project for someone from Google.
I can only volunteer testing a build on my Acer
Hello Mohan,
On 13.10.2016 09:14, Mohan Shanmuga Sundaram wrote:
> Dear Coreboot Community!
> I have modified the following CMOS option table bit using 'nvramtool'
> utility from Ubuntu:
> 384 1 e 4boot_option
>
> Its default value was 'Normal', which I modified to
Sad to hear Coreboot cannot provide this info. Is there some downstream
project I don't know about that could provide this?
Maybe Google will take pity on the poor Chromebooks and provide some kind
of firmware update themselves after the EoL.
--emi
On Thu, Oct 13, 2016 at 10:35 PM, Matt
Dear Coreboot Community!
I have modified the following CMOS option table bit using 'nvramtool' utility
from Ubuntu:
384 1 e 4boot_option
Its default value was 'Normal', which I modified to 'Fallback'. After
rebooting, the coreboot seems to be not loading the default
Hello,
Now that Coreboot has reproducible builds, could you provide a list of
build hashes for Chromebooks that are or will soon reach End of Life?
I see on https://support.google.com/chrome/a/answer/6220366?hl=en that 2
Chromebooks will reach End of Life in 2016 and 3 more in 2017 then 7 in
11 matches
Mail list logo
