MrChromebox / firmware

Issue tracker for firmware issues
78 stars 16 forks source link

Unable to select TianoCore bootloader on Acer Chromebook (CB311-9H) #574

Closed leou closed 9 months ago

leou commented 10 months ago

After setting Developer Mode, I ran the Firmware Utility Script and loaded the RW_LEGACY firmware. Then I login as chronos, became superuser with the command sudo -s, then ran command crossystem dev_boot_altfw=1 and rebooted. I was not able to select the bootloader shown in the white splash screen. The screen displays the two lines shown below.

Press a numeric key to select an alternate bootloader:

2 TianoCore TianoCore bootloader

I tried pressing the number 2 on the keyboard but nothing happened, pressing Enter did nothing either. There was no visible cursor and the arrow keys did not seem to do anything.

Is this a known issue? My goal is to launch the TianoCore bootloader so that I can boot from a USB drive to then install Arch Linux.

I'd appreciate any help in resolving this issue. Leo

MrChromebox commented 10 months ago

then ran command crossystem dev_boot_altfw=1 and rebooted.

why? where in my instructions did it say to do that?

Is this a known issue?

yes, and it's documented on the supported devices page . If you're getting a menu, you didn't update the RW_LEGACY firmware.

My goal is to launch the TianoCore bootloader so that I can boot from a USB drive to then install Arch Linux.

if your goal is to replace ChromeOS with Arch, then you want the UEFI Full ROM firmware; RW_LEGACY is for dual booting

leou commented 10 months ago

I was following instructions in an Arch wiki page. I thought that RW_LEGACY was a valid option and it was the only option I could choose when I ran the Firmware Utility. I don't know how to disable the firmware write protection in order to do UEFI Full ROM update.

Thanks for the clarification.

MrChromebox commented 10 months ago

I was following instructions in an Arch wiki page

please link me so I can go update it

I thought that RW_LEGACY was a valid option and it was the only option I could choose when I ran the Firmware Utility.

RW_LEGACY is a valid option, but it's not installed on your device. Not sure why you thought it was the only option.

I don't know how to disable the firmware write protection in order to do UEFI Full ROM update.

the supported devices page on my site tells you how for every device.

leou commented 10 months ago

Arch wiki page: https://wiki.archlinux.org/title/Chrome_OS_devices

The only option I could select when I ran the Firmware Utility was: 1) Install/Update RW_LEGACY Firmware

The entry in the Supported Devices page notes that RW_LEGACY and Full ROM are supported and that the WP method is CR50 (battery). I don't have a Suzy-Q cable so I guess the only way to disable WP is by disconnecting the battery. I'll have to find out if/how I can do this on this CB311 model.

MrChromebox commented 10 months ago

The only option I could select when I ran the Firmware Utility was: 1) Install/Update RW_LEGACY Firmware

before doing anything else, please take a picture of the main menu when running my script and post it here

leou commented 10 months ago

Here is the picture. firmware-util

MrChromebox commented 10 months ago

ok, I would power off, take off the back panel, disconnect the battery cable from the mainboard, power on with AC power, then run the script again. WP will be disabled, and you can flash the Full ROM firmware (#2). After successful flash, power off (via script menu) and reconnect the battery cable, reassemble. Then boot up and install Arch from USB

leou commented 10 months ago

Thanks for your help. I did as suggested above. Full ROM was installed and Arch is up and running!

Before flashing the ROM the script created a backup in a USB drive. Is this in case I want to go back to ChromeOS? How is this backup used? Any documentation? Leo

MrChromebox commented 10 months ago

Is this in case I want to go back to ChromeOS? How is this backup used? Any documentation?

yes. run the script from linux, choose option to restore stock firmware, select option to restore from USB backup. Documented on my site.