Samsung Chromebook Pro: can't boot from MicroSD


Enabled Development Mode and set boot from USB.
Booted OK from a USB and installed Manjaro onto a MicroSD.
Everything went OK with the installation.
But I can’t boot from the MicroSD.

When the Chromebook boots I press Ctrl + L and then Esc and select the only option.
It prints “Booting SYSLINUX” and then nothing happens.

Thanks in advance!

Did you install MrChromebox’s legacy payload?

No I didn’t.
As I understood, the firmware is needed only if you want to install a different OS onto the Chromebook’s internal drive.
Am I wrong?

Thanks in advance.

It’s needed to boot anything other than ChromeOS or something that supports depthcharge

1 Like

So you didn’t run the firmware utility script?

Either way, if the existing payload doesn’t work, that’s nothing to do with the chrultrabook project.

MrChromebox actually doesn’t provide the SeaBIOS payload for Skylake Chromebooks anymore because Skylake Chromebooks are EOL. You’re welcome to install MrChromebox’s full UEFI ROM instead.

If you need to dual boot ChromeOS for some reason, I suggest you check out Submarine.

First of all thanks a lot for all the replies.
No, I did not run the firmware utility script.

I thought that it wasn’t necessary to use any of MrChromebox scripts if you just want to boot from a USB or similar.
I thought MrChromebox scripts were mandatory only if you wanted to install a different OS than [or get rid] ChromeOS on the internal builtin drive.

So, if I want to install and boot another OS from a MicroSD card I need to run the MrChromebox script, thanks a lot.
Do I also need to remove the write protect screw for this?

Thank you very much.

Custom firmware is generally required on a Chromebook whenever you want to boot an OS other than ChromeOS. An explanation of Legacy Boot Mode is provided on MrChromebox’s website:

Legacy Boot support via RW_LEGACY/SeaBIOS was first added with the 2013 Chromebook Pixel (LINK), and continued with the subsequent Haswell-based devices. However, in many cases the SeaBIOS payload included with the factory firmware had severe defects, ranging from no video output to non-functional USB ports. In the case of Baytrail, Braswell, and Apollolake-based devices, the RW_LEGACY firmware was not included at all. Fortunately, an RW_LEGACY firmware update is available for most recent models which correct these defects, offer improved funtionality, and add Legacy Boot Mode capability for previously unsupported devices. See the supported devices page for details.

That is why it is still necessary to run MrChromebox’s script.

With that being said, as I said in my previous comment…

…MrChromebox no longer provides a SeaBIOS payload for your EOL Chromebook. If the existing payload in the stock firmware for your Chromebook isn’t successfully booting the Linux OS on your SD card, you can either install MrChromebox’s full UEFI ROM, which will remove the ability to boot ChromeOS (I’m guessing you don’t want to do that if you’re trying to boot Linux from external media), or use Submarine.