ReillyBrogan I thought about this as well and tried to clean up. Here is my EFI folder

-rw-r--r-- 1 minh minh 928K 13. Jul 22:32 bootloaderx64.efi
-rw-r--r-- 1 minh minh  152 13. Jul 22:32 BOOTX64.CSV
-rw-r--r-- 1 minh minh  74K 13. Jul 22:32 grubx64.efi
-rw-r--r-- 1 minh minh  71M 13. Jul 02:04 initrd-com.solus-project.current.6.9.8-294
-rw-r--r-- 1 minh minh  40M 13. Jul 02:04 initrd-com.solus-project.current.6.9.8-294.nvidia
-rw-r--r-- 1 minh minh  13M 13. Jul 02:04 kernel-com.solus-project.current.6.9.8-294
-rw-r--r-- 1 minh minh 829K 13. Jul 22:32 mmx64.efi

I do dual boot with Win11 and dare not to resize the NTFS partition next to it. Should I?

    Hmm that should be big enough, and you have enough space for the new nvidia initrd extension. Does sudo usysconf run -f help at all?

    • minh replied to this.

      ReillyBrogan I did that as well, no luck. I managed to set up a second 1G EFI partition and add new EFI boot entry use efibootmgr. Then install the driver and reboot. Same error

          Hey there, 1st time poster please be gentle. I’ve also had the same issue as user minh concerning the Nvidia driver conflict. The boot error is very quick & reads as “Error preparing initrd: Device Error” in red then quickly flashes to “start_image() returned Device Error” & then proceeds to boot into my second physical drive with windows

          I rebooted & had to be quick to Ctrl+Alt+F2 which gave me the options to boot into the current kernel or the previous kernel. Using the previous kernel it didn’t boot but was able to tty & rollback. Obviously I got curious, I just backed up all my application configs & decided to bork it & do a fresh install from the 4.5 ISO

          After the fresh install I purposely did NOT install the Nvidia drivers & just updated the OS. I rebooted & ran the eopkg check which reported three broken packages cups-browsed, apparmor & linux-current-6.9.8-294-1-x86_64 (which is of most concern). I followed the troubleshooting page & it fixed cups-browsed, apparmor but not the kernel itself

          I rebooted & tried again via the ‘grep broken’ command, it now shows clr-boot-manager failed

          I did note the error is on the boot partition nvme0n1p1 (as it’s now a fresh install so the boot EFI partition size is now 1GB). So I rebooted & mounted nvme0n1p1 & ran the ’grep broken’ command again & got;

          Which give it the all clear, however upon reboot & eopkg check it still gives me the linux-current as broken so the fix did not stick? I even ran ‘sudo usysconf run -f’ to be on the safe side but no joy upon another reboot
          I again was curious so I doflicky'd the Nvidia driver install & I end up with the original error “Error preparing initrd: Device Error” again
          I have an Nvidia GTX 980 & my specs are below

          Thankfully I’ve got an integrated GPU on the CPU so I’ll make do with that for now...very curious

            asianbullet The boot error is very quick & reads as “Error preparing initrd: Device Error” in red then quickly flashes to “start_image() returned Device Error” & then proceeds to boot into my second physical drive with windows

            I have exactly the same error. I think it's something to do with Nvidia driver, I tried previous boot kernel (6.8) as well. Mine has an integrated GPU as well, but I just stay with nouveau in the meantime.

              It would be useful if people with this issue would hop into Matrix so we can debug it interactively

                ReillyBrogan Hi Reilly, I'm not au fait with matrix but once I set it up on my end. I'll pop on over onto matrix, thanks for the reply

                  113 Solus updates processed (1,51 GiB) and and nothing special to report, except this concerning Firefox.

                  I am a french user of Budgie Desktop.
                  I noticed that after changing Firefox version number (e.g. from v.127 to v.128) during a update Solus, the Firefox window appears in English when starting, and not in French.
                  But, when I update adds-on, the Firefox windows then appears in French:
                  -> Menu Adds-on and Themes, then Check for Updates, then the message Update adds-on become Vos modules ont été mis à jour.

                  It's manageable (and I'm okay with it), but it seemed interesting to me to bring up this information, I already noticed it during the two previous updates of Firefox.

                  • [deleted]

                  • Post #24

                  I'm back in Wayland (Plasma) and I'm not experiencing stuttering anymore. All looks good!

                  Thank you for the great update! : )

                  After installing the update I got a lightdm error as that had failed to load. Using the command line I ran the update again and then rebooted the system. This only made things worse. Now I am receiving a different error "start_image() returned device error". And I can't even get to the command line anymore.

                  So I booted into the old kernel (6.8) to try to recover things by rolling everything back. Rolled the system back and now the 6.8 kernel is also showing "start_image() returned device error"

                  At this point should I just go for a fresh install? I have solus on a usb stick, but I am not sure how to recover using it. I would really prefer to keep my system rather than need to wipe it

                  Cherry-picked discord 0.0.60

                  Cherry-picked a change to nvidia-glx-driver* that should fix some issues experienced by nvidia users. (Thanks Reilly).

                  almost forgot, kernel 6.9! nice! 😃 👍️

                  EbonJaeger unstickied the discussion .