HP Chromebook Plus (YAVIKS) stuck on coreboot logo while attempting to legacy boot EndeavourOS LiveUSB

Trying to test out Linux before I decide to buy a SuzyQ. However, I’ve come across problems. Firstly, pressing Ctrl+L on the devmode boot screen after patching the RW_LEGACY firmware will result in “Something went wrong launching the alternate bootloader. View firmware log for details.” (I don’t know where firmware log is found.) So I instead use the GUI option “Select alternate bootloader.” After this, I select edk2. It goes to the coreboot logo. There are three cases:

  1. EndeavourOS LiveUSB made via dd - Freezes immediately on coreboot logo.

  2. EndeavourOS LiveUSB made via ventoy - Coreboot logo and instructions for boot options appear. When instructions disappear, freezes on coreboot logo.

  3. No USB plugged in - Works normally. Pressing escape brings me to boot options. Not pressing escape brings me to UEFI shell. Typing ‘exit’ returns me to boot options. Can insert USB at this point and it will be picked up by the menu. HOWEVER, attempting to boot from it results in a black screen.

Anyone know what’s happening here?

EDIT: Additionally, the LiveUSB is confirmed to work on another laptop. Both dd and ventoy methods were tested. Neither show up on my main computer that has CSM disabled.

EDIT2: I found the firmware log. Not sure if I can copypaste it and it’s a real pain in the ass to read. Here are a couple things that come after initiating the depthcharge, though:

CBFS: 'rw_locale_en.bin" not found.
load_archive: Failed to load rw_locale_en.bin (dir: 0x0, size: 806262984)

7 lines down:

payload_get_altfw_list: Supported alternate bootloaders:
1 edk2 altfw/edk2 edk2 UEFI bootloader
developer_boot_altfw_impl: Try booting from bootloader #0
CBFS ERROR: ‘payload’ not found in ‘RW_LEGACY’
Could not find ‘payload’.
payload_run_altfw: Could not find default altfw payload
payload_run_altfw: Could not find bootloader #0
developer_boot_altfw_impl: ERROR: Alternate bootloader failed

I don’t see anything of note in the rest of the log. Perhaps this helps someone more knowledgeable than me figure out what’s gone wrong.

there’s no log entries written for the edk2 payload, so looking at the cbmem log isn’t going to tell you anything.

sounds like you might have a device with UFS storage and no UFS support in the Live USB.

Can you boot Ubuntu 2404 written via dd?

Sorry for the wait. Was sleeping and then it took a while to get the LiveUSB made. Attempting to boot a Ubuntu 2404 LiveUSB made via dd has the same effect as attempting to boot the EndeavourOS LiveUSB made via dd. Worth noting that Ctrl+L still doesn’t work and I had to select the bootloader manually via GUI.

Just attempted with the latest OpenSUSE Tumbleweed as well. According to various online sources, OpenSUSE should have UFS R/W support. However, the behaviour is identical to the other LiveUSBs made with dd. Is it the case that no LiveUSB has UFS support?

no idea, it was a stab in the dark. There’s no way to get logging/debug info out of a payload with RWL/AltFw unless you have a serial/debug build of the stock firmware as well (which only exist inside Google)

Darn, okay. Well, Costco has a good returns policy. Might plonk this back over to them, see if I can find something more suitable for a similar price. Half the reason I bought this was for the high quality webcam since I have some teleinterviews coming up lol.

it’s possible it might work with the UEFI Full ROM, but hard to say.

can you pastebin the entire bios boot log from ChromeOS? can get it via chrome://system

If you are talking about HP Chromebook Plus 15.6 inch model 15anb Board Yaviks cpu Intel Core i3-N305 Alder Lake LPDDR-5 8Gb WiFi-6, first you have to choose the right firmware (coreboot.rom). That machine is one of the best chromebook for linux so far.

In this particular laptop the best distro match is MxLinux-ahs-23.5 xfce version because its light and install every thing. you can install linux under “live” iso session then calamare can identify the UFS disk but no way when you try to use non-live graphical or clic installers. After installation during boot time have to press Scape to enter UEFI Bios and go to /Boot-Manager/Using-File/boot/grub/x86_64-efi/grub.efi for boot properlly then after login have use an MxTool called Mx-Boot-Option to choose grub.efi as default to boot automatically next.

I just recommend after security setup and install updates immediatelly switch kernel from “liquorix” to “amd64 SMP PREEMPT_DYNAMIC Debian”. The reason is because liquorix gobernor focus on performance and make laptop cpu extremely “hyper” and “hot” about 95 C; instead debian kernel allow you to choose for cpu powersafe gobernor; even more if you edit /etc/tlp.conf file you can set all cpu speed on 800 MHz; it will allow you to remove the FAN and increase battery life; my machine actually runs fanless set cpu at 8 x 800 MHz and GPU 200-750 MHz at temperature min 43 C and max 55 C on multitask; while on not heavy costume tasks on continue use battery can live up to 14 hours.

The only issue with debian kernel is about USB Type-C port, they are only available if the device is present from booting time but ports will NOT work if the device is plug-in after boot; it means on linux already running to make usable USB Type-C ports you have to plug-in the device and reboot; I did my best to figure out why it happens but still no solution found.

SOLVED !!!
Good day guys HELLOoooUUUuuuu !!! is me again.
I came back with good news for all of yours getting trouble installing linux on HP Chromebook Plus 15" Yaviks with cpu Intel Core i3-N305 Alder Lake. I am really happy after I fully 100 % succeed and you can do it also; Easy.
To remove RW I just enter on developer mode, remove the battery connection and use the power cord; very probably you will be forced to repite de process of enter code on flashrom even if you type perfectly right; you may will use all TTY as TTY1, TTY2, TTY3 and TTY4 swiftching on cycles from one TTY to the nextone about 3 or 4 times; something important first of all to gain root access DO NOT USE “su” nor “-s” nor “-i”… instead type “sh” press enter and following “bash” and press enter; this is the only way that will make flashrom works properlly. The process to remove RW is already well described by MrCromboxTech … but if someone is instresting on details how I did let me know.
After RW removed, use MrChromeboxTech scrip follow his method as described.
After flash the coreboot.rom you can reconnect the battery but I recommend you don’t do it yet, better wait after LinuxOS installation is completed.
HERE IS THE GOOD NEWS !!! The best Linux distro for that Chr-Laptop in particular is Loc-OS ASH for new machines Live version so far, it is a light weight distro, highly optimized, boots at once, install every thing, and USB-TYPE-C ports works perfect, sensor temperature report very good…
After Loc-OS Linux installed you can connect back the battery. I advice to install “TLP” and go to /etc/tlp.conf file to edit it for max powersave efficiency, just use your common sense but if someone need help and is instresting on details how I did let me know.
Before I was using MxLinux but Liquorix Kernel cause extreme cpu heat and otherwise if you switch to PREEMT-DYNAMIC kernel it is unable to access to USB-TYPE-C after boot time; so I try with Loc-OS a V-init kernel distro that proved is costumized for this coreboot BIOS, my modest opinion is that looks like current systemd kernels can NOT control this coreBIOS yet or are in conflict with.