MrChromebox / firmware

Issue tracker for firmware issues
75 stars 14 forks source link

Aleena - lost secure boot #646

Closed fargodwe closed 3 weeks ago

fargodwe commented 3 weeks ago

Just a quick overview hardware-wise:

Recent activity:

Now getting error about secure boot being disabled.

In boot options screen the secure boot will not set - it stays at standard.

As a result, can't boot the system with any OS.

Any help would be appreciated.

Thanks in advance.

Dave Eaton

MrChromebox commented 3 weeks ago

Now getting error about secure boot being disabled.

no, you're not. you're getting an error that your device failed to boot, and it's reporting the secure boot status

In boot options screen the secure boot will not set - it stays at standard. As a result, can't boot the system with any OS.

what are you expecting it to say other than standard? are you trying to use custom keys?

Also, not sure why you are trying to run Windows on the most underpowered Chromebook possible. A celeron 2955U Chromebook from 2013 runs Windows better.

report the exact error you're getting, not what you think it says.

fargodwe commented 3 weeks ago

Trying to put windows in for the heck of it - not because I have to or need to. Just wanted to see this piece of junk run Windows.

When booting, get the same message for Windows or Linux with only the Booting From'xxxx' name changed.

The below is from the microSD card that w as running fine. I have no way to copy/paste from a non-booted machine so I'll type exactly what it says on my screen. This is all rather centered in the screen:

SecureBoot status: disabled

Booting from 'Fedora' failed; verify it contains a 64-bit UEFI OS.

Press any key to continue booting...

Which results in a return to the boot menu.

MrChromebox commented 3 weeks ago

again, that msg is just telling you that booting from a particular boot menu option failed, and is reporting the secure boot status along with it. It's not telling you that the boot failed because of the secure boot status. I may have to rework this if it's not clear to others.

'Fedora' is a boot entry that points to a specific file on a specific device. If that device isn't present, can't be read, etc then you get an error. I don't think it's possible to output a more detailed message unfortunately

fargodwe commented 3 weeks ago

Yep, got that. Thing is it was doing it with all media, including media that worked before (microSD card). Just ended up redoing everything and then booting from a usb stick and reinstalling Fedora to the microSD card and clearing the emmc (chrome, also where I had tried to install Windows prior with the microSD out of the system). The boot menu didn't even show the SD card or USB stick as an option until I reset everything (via the SuzyQ cable and my other laptop). Maybe the hardware is finally starting to fail.

On a side note, I do finally have sound in linux. Had to use Fedora then a special kernel as via weirdtreething on github.

Recovered everything so back to "normal" now.

Thanks