Hi everyone. I’m in search of a replacement for my aging chromebook and came across this listing from Acer. My intention is to convert the chromebook to Manjaro Linux but I’m worried that this won’t be possible since the device isn’t listed here.
What do you think?
I don’t see it listed on Supported Devices and Platforms | Chrultrabook Docs either. Can you visit chrome://system from ChromeOS system and check the board name? (first word in HWID row)
Unfortunately, this isn’t possible as I haven’t purchased it yet. The only information that I could find is from the developer information page for ChromeOS devices.
The Acer Chromebook Plus 515 (CB515-2H, CB515-2HT) is listed under code name Omnigul with Brya as its board name.
From what I see, there are Coreboot+UEFI builds for other Brya-based Chromebooks, such as Crota (Dell Latitude 5430), so there’s a high chance that after building Coreboot+EDKII for Omnigul things might mostly work - but it would require some testing.
I’ll pass this thread to developers.
Much appreciated. I’m tempted to buy it and then test it myself but frankly, I don’t have any experience debugging coreboot.
it’s an ADL/brya based board, so trivial to add support for it. It probably wasn’t released when I added brya support originally
That’s completely understandable. The model was released last October.
Thank you for building such an amazing community that has helped countless people, like myself, in extending the life of their Chromebooks.
Happy new year!
I went ahead and bought this model. Since the firmware script will quite possibly fail on this one, I was wondering whether/how I can modify the script to make it work.
you can’t. but you can tell me the board name as identified by the script, and I can add support
Thanks. I suppose this is an alternative way of finding the board name other than the one suggested in the docs, right? I’ll get back to you with a name as soon as it arrives as I’m still waiting for my courier to deliver it (ordered two weeks ago 
).
Can confirm that it’s Omnigul, with hardware ID: OMNIGUL-FUQB D4B-D4E-16C-E36-J6A-A7G
However, I had an issue with running the script (similar to #555), so I had to resort to using the crossystem hwid command instead. Won’t get into much detail here since I wish to keep this thread on-topic, but I’ll just say that from the logs, it seems to be a flag mount issue.
I know the issue has been followed in another thread, but I think my question is more appropriate here.
@micmalti Could you please tell me whether you had to disable hardware write protection using the CR50 jumper method? If so, could you please hint me at where you learned how to do it?
After reading the page about Firmware Utility Script I was under the impression that enabling UEFI boot can be achieved without touching the hardware, yet reading the firmware write protect page suggested me otherwise. From the other thread I know you didn’t yet have the SuzyQ cable at the install time, so you must have used the CR50 jumper method or haven’t touched the hardware at all. I will appreciate any guidance.
I disconnected the battery, which is fairly easy once you manage to open the device (which in my case wasn’t 
).
However, do note that, currently, booting is only possible via USB since the internal UFS medium isn’t being detected. Follow issue #572 for future updates.
Thank you very much for answering. And so quickly too, I greatly appreciate it.
Oh, great, I’ve expected to have to open the device, so I’m glad to hear that disconnecting the battery will be enough (contrary to the information that this method works only on not so new devices).
I sure will keep my eyes on it, thank you.
On Raptor Lake Acer CB515-2H-34YL (omnigul)
After flashing RW_LEGACY firmware, Ctrl+L or selecting edk2 from alternate bootloader gives error-
“Something went wrong launching the alternate bootloader. View firmware log for details.”
Anybody else, faced the same error ? Or help me to resolve this error… I do not have suzy cable.
I think newer CB515-2H have slight variation, eg- it features nvme instead of UFS, though still have the same brya boardid.
these details might be useful in troubleshooting the problem…
How to share these logs?
Can you please share the name of file from /var , which I can share?
LMGTFY:
To view the firmware log on a ChromeOS device, navigate to the address “chrome://system” in your Chrome browser, which will display detailed hardware information including potential firmware logs; for more detailed troubleshooting, you can also access system logs directly by typing “file:///var/log” in the address bar, but this requires a deeper understanding of log files
Hello, I have been having the same issue as @abhijeet (might be best to split the topic from that post onwards). I cannot access the alternate bootloader and get a PC speaker beep, as well as the same error. My HWID is OMNIGUL-FUQB-D4C-D4F-I7I-E36-I4Q-A6L, which is a bit different to the that of others’ on this topic.
I followed the Chrultrabook guide to the letter with the battery plugged in, meaning Write Protection was enabled.
I’m a full-time Linux user and occasional FOSS contributor and I’m keen to get this resolved for myself and other users, so if you could narrow down the scope of the logs you are asking me to look at (to properly diagnose the issue), I am keen to do so. I made a best effort below.
From # cbmem -t -c - note I extracted the text using Google Lens and cleaned it up manually, but there may still be some small errors. Notably, a lot of underscores and equals signs did not come in. The filesystem was laid out a little differently to what I am used to so I wasn’t sure of anywhere I could place these files but still be able to access them within ChromeOS to make this post.
I included a longer log than I might have otherwise, as I was under the impression the 256GB model I have had UFS storage, but the cbmem output implies it’s actually NVMe. I have separate output from dmesg later on though which disagrees, in case that matters.
tpm_get_response: command 0x14e, return code 0x0
Calling VoSelectAndLoadkernel().
pbelecternal.andkernel: GBB flags are 0x0
vezaniec sync: ED software sync already performed this boot, skipping ps8815 1: vendor 0x1da0 product 0x8815 device 0x0003 fw_rev 0x30
ut loop_Impl: <Developer mode> menu Item <Boot from internal disk> ul
display: screen 0x300. locale=0, selected_Item=4. disabled_item_mask=0x0, hidden_item_mask=0x8, timer_disabled=8, current_page=0, errог=0x0
get_locale_data: Supported locales: en bn ca da de et es es-419 fil fr hr id it lv lt hums nl no pl pt-PT pt-BR ro sk sl fi sv vi tr cs el bg ru sr uk helr
get CBGFX: cbgfx initialized: screen:width=1920, height=1080, offset=0 canvas:width=1080, height=1080, offset=420
display: display init called but not implemented.
display backlight update called but not implemented.
load_archive: Loading vbgfx.bin
load_archive: Loading locale_en.bin
load_archive: Loading rw_locale_en.bin
load_archive: Failed to load rw_locale_en.bin (dir: 8x8, size: 806237184)
load_archive: Loading font.bin
ul_loop_impl: <Developer mode> menu item <Select alternate bootloader>
ul display: screen 0x300 locale=8, selected_item=4, disabled_item_mask=0x0, hidden_item_mask=0x0, timer_disabled=1, current page=0, error=0x0
ul menu select: Menu item <Select alternate bootloader> to target screen 0x340
get altfw list: Supported alternate bootloaders:
0 edk2 altfw/edk2 edk2 UEFI bootloader
1 edk2 altfw/edk2 edk2 UEFI bootloader
get_bootloader_menu: num_bootloaders: 1
get bootloader menu: Bootloader: filename=altfw/edk2, name=edk2. desc=edk2 UEFI bootloader, seqnum=1
get bootloader_menu: Cached with 4 item(s)
ul_loop_Impl: <Select alternate bootloader> menu item <edk2>
ul get bootloader_menu: num_bootloaders: 1
display: screen-8x348, locale=8, selected_item=1, disabled_item_mask=0x0, hidden_item_mask=0x0, timer_disabled-1, current_page=8, error=x8
get bootloader menu: Bootloader: filename=altfw/edk2, name edk2. desc edk2 UEFI bootloader, segnum=1
get_bootloader menu: Cached with 4 item(s)
ul_menu_select: Menu item <edk2> run action
developer_boot_altfw_impl: Try booting from bootloader #1
Running bootloader 'edk2: edk2 UEFI bootloader'
Loading altfw/edk2 into RAM
segment type 45444f43 not implemented. Exiting
Falled: erroг -1
developer_boot_altfw_impl: ERROR: Alternate bootloader failed
get bootloader menu: Cached with 4 item(s)
ul_loop_impl: <Select alternate bootloader> menu item <edk2>
ul get_bootloader_menu: num_bootloaders: 1
display: screen 0x340, locale=0, selected_item=1, disabled_item_mask=0x0, hidden_item_mask 0x0, timer disabled=1, current_page=0, error=0x9
get_bootloader menu: Bootloader: filename=altfw/edk2, name edk2, desc edk2 UEFI bootloader, seqnum=1
ul_display screen: Something went wrong launching the alternate
bootloader. View firmware log for details.
get bootloader menu: Cached with 4 item(s)
ul_loop_impl: <Select alternate bootloader> menu item <edk2>
ul display: screen 0x340, locale=0, selected_item=1, disabled_item_mask=0x0, hidden_item_mask 0x0. timer disabled=1. current page=0. еггог=0x0
get bootloader menu: num_bootloaders: 1
get bootloader menu: Bootloader: filename=altfw/edk2, name=edk2, desc=edk2 UEFI bootloader, segnum=1
get bootloader menu: Cached with 4 item(s)
get_bootloader_menu: Cached with 4 item(s)
ui_loop_impl: <Select alternate bootloader> menu Item <Back>
display screen 0x300, locale=0, selected_item=2, disabled_item_mask=0x0, hidden_item_mask=0x0, timer_disabled=1, current_page=0, error 0x0
get_bootloader_menu: num_bootloaders: 1
pet bootloader menu: Bootloader: filename=altfw/edk2, name=edk2, desc edk2 UEFI bootloader, seqnum=1
get bootloader menu: Cached with 4 item(s)
ul_menu select. Menu item <Back> run action
ui_loop_impl: <Developer mode> menu item <Select alternate bootloader>
display screen 0x300, locale=0, selected_item=4, disabled_item_mask=0x0, hidden_item_mask=0x8, timer_disabled=1, current_page=0, error 0x0
ui_loop_impl: <Developer mode> menu item <Boot from Internal disk>
ul display: screen 0x300, locale=0, selected_item=2, disabled_item_mask=0x0, hidden_item_mask=0x8, timer_disabled=1, current_page=8, error=0x0
ui menu_select: Menu Item <Boot from internal disk> run action
UFS Controller not found 08:12:07
Updating storage controller failed.
Initializing NVMe controller 15b7:5017
Identified NVMe model WD PC SN748 SDDQNQD-2560-1014
Added NVMe drive "NVMe Namespace 1" Ibasize: 512, count: 0x1dcf32b0
VbTryLoadKernel Impl: trying disk 0
GptNextKernel Entry: GptNextKernel Entry looking at new prio partition 2
GptNextKernel Entry: GptNextKernel Entry s1t0p1
GptNextKernel Entry: GptNextKernel Entry looking at new prio partition 4
GptNextKernel Entry: GptNextKernel Entry s1 t0 p2
GptNextKernel Entry looking at new prio partition 6
GptNextKernel Entry: GptNextKernel Entry s0 t15 p0
GptNextKernel Entry: GptNextKernel Entry likes partition 4
LoadKernel: Found kernel entry at 8859648 size 65536
From $ dmesg, within crosh, showing how ChromeOS was booted:
2025-03-13T05:55:08.054237Z INFO fwupd[4100]: FuDevice failed on try 1 of 5: failed to open /dev/nvme0: Permission denied
2025-03-13T05:55:08.554565Z INFO fwupd[4100]: FuDevice failed on try 2 of 5: failed to open /dev/nvme0: Permission denied
2025-03-13T05:55:09.054757Z INFO fwupd[4100]: FuDevice failed on try 3 of 5: failed to open /dev/nvme0: Permission denied
2025-03-13T05:55:09.555042Z INFO fwupd[4100]: FuDevice failed on try 4 of 5: failed to open /dev/nvme0: Permission denied
2025-03-13T05:55:10.055298Z INFO fwupd[4100]: FuEngine failed to add device /sys/devices/pci0000:00/0000:00:1d.0/0000:01:00.0/nvme/nvme0: failed to retry subclass open: failed after 5 retries: failed to open /dev/nvme0: Permission denied
2025-03-13T05:55:10.061880Z INFO fwupd[4100]: FuPluginScsi found ufshci controller at /sys/devices/pci0000:00/0000:00:1d.0/0000:01:00.0
Thank you for your assistance.
A quick search reveals this user had the same issue: