firmware
firmware copied to clipboard
MrChromebox
Cant boot any OS
I keep getting failed verify its a contains a 64bit UEFI OS but i know it's 64 bit UEFI os because it worked before
ok? You can't provide a half-assed error description and expect anyone to be able to help. Some basic info would be nice, such as:
- device you're using
- firmware version from UEFI menu
- exact steps you're taking
- full and exact error message (pic is fine)
OP probably ran some Linux distro from a USB which, upon installation, failed to boot up from the internal drive (hence the phrase "because it worked before"):
I'm met with the same problem on my Chromebook Plus 515 (CB515-2H-31NY) with board name OMNIGUL. Tried multiple distros (Ubuntu 23.10, EndeavourOS, Manjaro) with and without using Ventoy, but the outcome was the same regardless: the EFI partition showed up in the boot menu (path: \EFI\[distro name]\grubx64.efi) but it produced the above error message when selected, followed by this message in the UEFI shell:
map: No mapping found
I would also like to add that there weren't any installation errors, and can confirm that the EFI and root partitions were visible and accessible from the live USB session.
Here's the cbmem logs: cbmem.log
@micmalti boot to the UEFI boot menu. If there's no entry present for the internal storage, then that's your problem -- edk2 doesn't recognize it, and so the 'Manjaro' boot entry points to a device/path that doesn't exist.
You mean checking for entries in Boot Manager → Boot From File, as it says in the FAQ? It's empty. I'm not sure how I can add the entry manually.
no, literally press ESC then select Boot Menu. It should list the UEFI shell, the internal storage, and any boot entries added by the OS (eg, 'Manjaro')
Yes, there's an entry but it produces the same error message when selected.
no. post a pic of your boot menu, as well as the Boot From File options
Please note that only one distro is visible in the boot menu since I had previously removed the others:
it's exactly as I said before:
If there's no entry present for the internal storage, then that's your problem -- edk2 doesn't recognize it, and so the 'Manjaro' boot entry points to a device/path that doesn't exist.
your internal storage is not recognized by edk2, so it's not bootable.
Is there a way that I can specify the path manually without using efibootmgr? My understanding is that the solution in the FAQ only works if the EFI partition is already visible in the File Explorer.
there is no workaround, other than booting from removable media.
The Manjaro entry already specifies a path -- that path doesn't exist because your internal storage doesn't exist.
edk2 needs to be updated/fixed to support UFS boot media
Then it seems I have to revert back, unless there's a fix in the near future. Too bad.
No, but I'll try to find one. I've seen a tutorial on how to make one but I'm not sure that I can do it.
I think that in the meantime, it's a good idea to specify in the docs that devices with UFS media are currently unsupported.
I think the UFS drivers were simply not being compiled into edk2, ping me on Discord for a test build with them enabled
My Acer 515 chromebook arrived yesterday, and this issue also affects me. Any idea when the test build will be released?
Thank you.
there will be no test build released, the solution I tried did not work. Need to get my hands one for testing
Thank you for the quick reply. Apart from the HD not being detected, I like the machine. For now, I can boot off another USB. Keep up the great work, by the way. I've had Linux running on my older Acer for years.
I'd be happy to test any builds, if that would help? My intention is never to use the CB as a CB anyway, so I'm not at any loss to rinse and repeat.
Let me know.
Is the current workaround to boot off USB, but then the rootfs can still be on a UFS device? Since I had issues with a different device, I have one of these (CB515-2H) on order, because I thought it was supported and inexpensive...and now see this bug. :)
I can certainly deal with the USB workaround for now, and would definitely be up to helping test / attempt to contribute as well. I have another Linux laptop and server that I can set up a dev environment if pointed to some docs.
-Matt
I've got a fix for UFS-equipped devices, just need to push updates - will try to do so later tonight/tomorrow morning
Booting directly from UFS is currently possible, but you need to manually install the missing UFS modules. Something that I've yet to solve is the boot time which takes about 2min (probably a non-critical module that's failing to load). I'll try to test the update and check whether it addresses this issue as well.
I've got a fix for UFS-equipped devices, just need to push updates - will try to do so later tonight/tomorrow morning
Awesome! Thanks for all your work.
-Matt
This is super news! Maybe now I can make use of my Acer Plus Chromebook! Thank you SO MUCH for your work.
-Keith
Hi. I might be doing something wrong, but I updated the firmware to the latest version, and tried to install OpenSuSE and Void Linux, but neither see the UFS disk.
When you say "Booting directly from UFS is currently possible, but you need to manually install the missing UFS modules"...how does one go about that, or is it not related to my issue?
Thank you very much.
-K