Error preparing initrd: Device error
start_image () returned Device Error

This problem with my "NVMe SSD" boot driver is back after this update, even the kernel driver is the same. So it must be something else. Also, my PC freezes directly after update, I had to do hard reset. I have my backup boot partition on another disk (normal SSD) and it works. packages

    AlphaElwedritsch Yes that makes sense. I wonder if we are going to get 5.9 as a fix. Using an older Bluetooth mouse for the time being.

      Maybe I can try testing it later the day or tomorrow.
      One of my mice is a dual device, but I'm actually not sure if it is v5/v4 or v5/v3

      @BuzzPCSOS
      You're right
      I've updated my system again
      My MX Master mouse (v5) stops working immediately
      But the other mouse (dual V5 and V3) which I has connected as a V3 mouse to my system before I did the update keeps working without any problem.

      So, the problems is defacto there, but only for V5 devices

      I will update the issue, I#ve opened on github

      https://github.com/getsolus/packages/issues/5268

        At home I found an old small bluetooth mouse 'GENIUS' with a large bluetooth antenna, inserted batteries into it and after several manipulations connected it to Solus 4.7 What is curious is that bluetooth does not see the name of the mouse, He does not know its name! I assume it has Bluetooth version 3

        The mouse works, but on my Acer laptop it is unusual to see a large Bluetooth antenna intended for PC system units

        @WetGeek as I remember, you have a lot of Bluetooth devices. Have you any problems with your devices since the last sync update?

        minh
        Thanks for the heads up, I'm on Budgie with an NVME boot drive & Nvidia gfx card. So I did a test, I installed all updates apart from the x4 Nvidia packages. Rebooted & everything was fine...then I thought I'd 'risk it for a biscuit' & installed the x4 Nvidia packages & it borked to that same recurring error message you have. I didn't have any extra kernels installed, so I had to live usb chroot & rolled backed to before x4 Nvidia packages when all good.
        So No Visual Interface Display Is Accessible - the way it's meant to be..?

          Same issue than 2 weeks ago, previous fallback kernel did not remove itself, had to clear it manually for the new one to install correctly. Is editing the EFI partition size safe to do ? 😱

            BuzzPCSOS Fixed on unstable. Try this. sudo eopkg it https://cdn.getsol.us/repo/unstable/b/bluez/bluez-5.80-58-1-x86_64.eopkg

                ReillyBrogan Thank you for the swift response. Unfortunately that fix did not work for me. I can still connect Bluetooth V3 devices but V4 devices fail to connect.

                    BuzzPCSOS same for me. I mentioned this already yesterday in the issue on git. Maybe this fix fixes something but unfortunately not everything.

                      @ReillyBrogan

                      sudo eopkg it https://cdn.getsol.us/repo/unstable/b/bluez/bluez-5.80-59-1-x86_64.eopkg
                      cannot be installed.

                      bluez-5.80-59-1-x86_64.eopkg [cached]
System error. Program terminated.
External dependencies not satisfied: libical release >= 21

                        Harvey might as well wait for sync at this point.

                        That was exactly my thought. Especially because the sync is already due in a few hours.
                        So why bend the whole system 😉