Page MenuHomeSolus

UEFI Solus refuses to boot on my Lenovo 100S laptop
Closed, LockedPublic

Description

Hey I have been a long time Xubuntu user and have been using Xubuntu on this laptop but was realy enjoying Solus so I wanted to install it but it refuses to boot with EFI and doing sudo clr-boot-manager update when chrooted in on the live cd gave me this error.

root@solus / # sudo clr-boot-manager update
[FATAL] cbm (src/bootman/update.c:L85): Cannot determine boot device

the only way I could actually get it to boot was by installing it with legacy but I had to use Super Grub2 liveCD to even get it to boot and clr-boot-manager would give a warning that it can't update and I cannot update the ot the newest installed kernel.

Could I get some help please.

Event Timeline

This appears to be from the SystemD-boot not working with eMMC, out of my diagnosis.

Idepad 100S require hybrid 32bit and 64bit image. The UEFI only support 32bit, but the processor actually support 64 bit. That's why usually Ideapad 100S is preloaded with Windows 10 32bit

EDIT:
For source, I have a friend with the same laptop. And there some info online regarding this.

Hmm I see well Ubuntu and Manjaro boot after being installed on the Ideapad 100s, I didn't even bother to boot Windows 10 when I got it as I just just wiped it as soon as I got it and installed Xubuntu 16.04 LTS when I originally got it in 2016 no problems but as pcwizzy37 said which got to look int into my install and try and manually get systemd to set a boot device in my bios and be bootable but wasn't successful as it seems to not work with eMMC from his diagnosis and he is much more knowledgeable in systemD than me.

DataDrake added a subscriber: DataDrake.

it's not an issue with systemd. We can't boot 32-bit UEFI because we don't support 32-bit architectures. plain and simple.

But I'm not using a 32bit laptop? it's a 64bit laptop but does it have to do wit the bios itself being 32bit dispute the laptop being 64bit? could there be an exception to a weird case like this because it uses a 64bit OS which is due to Lenovo's decisions and not supporting it or other laptops from other companies who do weird stuff like this on 64bit laptops will only stop using this great OS and will effect the amount of people wanting to use this OS if you could imagine the amount of low end 64bit notebooks that might have this weird 32bit bios on it and a new user not even knowing this after buying a laptop to use Solus.

But I'm not using a 32bit laptop? it's a 64bit laptop but does it have to do wit the bios itself being 32bit dispute the laptop being 64bit? could there be an exception to a weird case like this because it uses a 64bit OS which is due to Lenovo's decisions and not supporting it or other laptops from other companies who do weird stuff like this on 64bit laptops will only stop using this great OS and will effect the amount of people wanting to use this OS if you could imagine the amount of low end 64bit notebooks that might have this weird 32bit bios on it and a new user not even knowing this after buying a laptop to use Solus.

Some Laptops ship with 32bit UEFI while having a 64bit processor, that is the problem here. I had the same issue on one of my older laptops...

That's true but that's a companies decision to do that not the users, they shouldn't be punished for stupid company decisions also my laptop is from 2016 it isn't that old and we shouldn't limit users and should have an exception for this scenario, I'm not saying 32 bit support for the OS needs to be done I mean I can understand why it's being dropped as 64bit is far better and the norm but if a 64bit laptop has a 32bit OS that's a different story and the 32bit bios should be supported as many laptops old and still new might do this.

JoshStrobl changed the task status from Wontfix to Locked.Mar 1 2019, 3:56 PM
JoshStrobl added a subscriber: JoshStrobl.

Closed. Response was provided by @DataDrake.

This task has been locked.