Nvidia driver Updating clr-boot-manager failed

Da_Zims

Hi!
I run into this issue while installing Solus on a new machine.
-Clean new install on a ssd.
Install Solus then upgraded everything through the software center.
Unfortunately the rtx card and the freesync monitor did not want to play nice.

I then install NVIDIA proprietary driver.
After reboot i was welcome by a black screen.
Got into terminal and then roll back the driver install with de eopkg history.
and this happened.

any idea?

thanks in advance!

CorvusRuber

Are you sure that your EFI partition is at least 512Mb ?
Other question: how did you install the driver ? Manually or via DoFlicky ?

Girtablulu

can you run sudo clr-boot-manager update and post the output?

Da_Zims

OK some update I started from scratch.
-Set my own partition EFI have 5 gig just in case.
-Turn out the nvidia driver have nothing to do with this.
I got the same error doing my initial update using the terminal.

clr-boot-manager update return.
[FATAL] cbm (../src/bootman/bootman.c:L477): Cannot determine boot device

Lsblk return
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 4.9G 0 part
├─sda2 8:2 0 31.3G 0 part [SWAP]
└─sda3 8:3 0 187.4G 0 part /

sda1 being my efi partition should it be mounted at /boot/efi ?

kyrios

Does your EFI partition has the boot and esp flags ?
Is it formatted in fat32 ?

PS: 5Gb is huge. Solus recommends 512Mb

Da_Zims

yes the EFI partition has the esp and boot flag and formatted in fat32.

I know 5 gig is way over but when this issue get resolve i will do a "proper" install i just did not want the size to be a issue

Ok more update! Got this thing working

i forceful mount my EFI partition with fstab.
got the idea from this guy on reddit

update go on smooth after.

kyrios

Da_Zims clr-boot-manager should take care of mounting and unmounting the partition during the boot or update process.

You can prefix the command with CBM_DEBUG=1

But before trying further, make sure your system is fully up-to-date sudo eopkg up -y

JacekJagosz

If anybody had this problem in the future, I fixed it a few months ago: I noticed I had a /boot directory, which was updated by clr-boot-manager, but the actual boot partition had old contents different from the /boot. All I had to do is to remove /boot and then do sudo clr-boot-manager update. I don't know how that happened, I couldn't figure it out for so long and had to perform boot repair via the LiveUSB many times.