lds-lds Does appending module_blacklist=simpledrm to your kernel command line help at all? To do this mash the down key while booting until you see the boot menu. Then hit e over the linux-current kernel entry to edit the command line and hit enter when you're done.

If that doesn't help you can always install the LTS kernel as a temporary fix. To do this from the TTY do a sudo eopkg it linux-lts nvidia-glx-driver (assuming you are on the normal Nvidia driver, you haven't provided your hardware details so I can't be sure). If you have other kernel packages installed be sure to install the LTS version of them (this is always the package name with -current removed, so for broadcom-sta-current the LTS version is broadcom-sta).

    darkness If stat /lib/modules/6.0.10-224.current/kernel/drivers/video/nvidia.ko.zst prints any kind of "not found" message then you need to re-install the driver per those instructions.

        Thanks ReillyBrogan ! I did not see your latest comment so I reinstalled them. It worked 🙂 .
        Somehow I did not receive or notice an email about that latest comment in the issue tracker.

          ReillyBrogan just wanted to confirm that the luks passphrase screen is showing again.
          My graphics card is an NVIDIA GeForce GTX 1650 SUPER and benefits from the driver updates.

          tonyk also my wifi is working again with kernel 6.0.10 (it stopped working with kernel 6.0.9).
          As far as I can tell from dmesg output, my wifi hardware is rtw_8822ce - probably different from yours.

          Thanks a bunch for this intermediate update!

              ReillyBrogan I updated with the latest updates and as you predicted, I had to manually decompress the wl.ko.zst file in the new kernel directory to get the wifi working again.
              Went through your latest requests - output follows:

              ls -ahl /sbin |grep mod
              lrwxrwxrwx 1 root root 9 Jun 22 23:34 depmod -> /bin/kmod
              lrwxrwxrwx 1 root root 9 Jun 22 23:34 insmod -> /bin/kmod
              lrwxrwxrwx 1 root root 9 Jun 22 23:34 lsmod -> /bin/kmod
              lrwxrwxrwx 1 root root 9 Jun 22 23:34 modinfo -> /bin/kmod
              lrwxrwxrwx 1 root root 9 Jun 22 23:34 modprobe -> /bin/kmod
              lrwxrwxrwx 1 root root 9 Jun 22 23:34 rmmod -> /bin/kmod

              /lib/ld-linux-x86-64.so.2 --list /bin/kmod
              linux-vdso.so.1 (0x00007ffd61bbf000)
              libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007fe87949b000)
              liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007fe879472000)
              libz.so.1 => /usr/lib/libz.so.1 (0x00007fe879457000)
              libc.so.6 => /usr/lib/libc.so.6 (0x00007fe879200000)
              /usr/lib64/ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x00007fe8795aa000)

              Then ran the additional commands to replace the wl.ko file with wl.ko.xz. Unfortunately, no wifi after reboot until I manually uncompressed the wl.ko.xz file. Once that is completed, I have wifi again.

              Thank you for continuing to troubleshoot this!

                ReillyBrogan Thanks for the solution. I have the same problem and solution as tonyk.
                As you said after updating the kernel I need to re-decompress the new module.
                I can do this for each update. But I'm available to investigate why it isn't working with zstd modules, just said me what to do.

                    so, its ok when maj + boot on 5.15.80-192.lts
                    module_blacklist=simpledrm does not help

                    lspci |grep NVIDIA
01:00.0 VGA compatible controller: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1)

                      lds-lds if you boot back into 6.0 can you do a sudo systemctl restart lightdm from another try and then switch back? Does that help?

                          BlolPloop @darkness tbh I'm at a loss as to why it's not working for you. The output from the last commands I had @darkness do look correct, there's no reason sudo modprobe wl shouldn't be working that I can see. Your systems are clearly working just fine with zstd-compressed modules in general since we now compress ALL kernel modules with zstd. My only guess is that something somewhere is hard-coded to use wl.ko and only wl.ko but given that we're talking about like 70kb of space savings here I'm just going switch the Broadcom kernel modules back to uncompressed (should be in the next sync).

                          If anyone else wants to further dig into this particular issue feel free, it's probably something hard-coded in a udev rule, modprobe entry, hw database something like that.

                            @BlolPloop @darkness Does this work?

                            sudo eopkg it https://mirrors.rit.edu/solus/packages/unstable/b/broadcom-sta/broadcom-sta-current-6.30.223.271-339-1-x86_64.eopkg https://mirrors.rit.edu/solus/packages/unstable/b/broadcom-sta/broadcom-sta-common-6.30.223.271-339-1-x86_64.eopkg

                              hegetam remuwon Which issue are you responding to? I assume the broadcom issue?

                              EDIT: Oh never mind I just noticed that your comments were replies to my own sorry.

                                    ReillyBrogan
                                    Adding that it works for me as well - I think you may have been replying to me about the broadcom wifi. Removed the "wl.ko" file and ran the eopkg file you listed under "Does this work?" - the wl.ko file was written back into the directory without manually decompressing the file and my broadcom wifi works.

                                    Thank you

                                        tonyk perfect. Yeah that update will be in the upcoming sync for everyone and I've left a note in the package build scripts not to try compressing the module again.

                                          lds-lds Does it work if you use an alternate session manager like GDM?

                                          Also, on one of these failed starts could you give me the output of sudo lsmod?

                                            11 days later