Horror story for me today with my Solus GNOME, lads :[
After reboot I cannot log in anymore, neither with the latest kernel nor with the previous one.
The system freezes during the login step due to a kernel panic and some syncing problem, according to TTY. Said TTY displays the aforementioned information but then freezes too.
Fortunately I could back up my data thanks to dual boot so I could reinstall, but I'd rather avoid that if there's any way. Is there? T.T

It says Kernel panic - not syncing: Fatal exception in interrupt

Ok, I'll try that. It's a laptop old enough for its graphics card not being supported by the NVidia proprietary driver anymore, it should be ok.

I'm getting the same issue.
It seems to come from broadcom-sta.
Booting in runlevel 1, I removed it, then I'm able to boot (so no more using wifi but via network cable).

    stephanedr It seems to come from broadcom-sta.

    Yep, coming back from the chroot path, I can confirm. lol

      Please make an issue for this here and we'll get to the bottom of it.

      Hi - Same problem on my MacBookPro 9,2 and an older MacBookPro - but I'm not sure what files to delete to be able to boot again.
      Did you delete the broadcom files in lib/modules/6.5.7-259.current/kernel/drivers/net/wireless/broadcom or some other directory? Or is there an easier way to delete the files once in the chroot path?
      Thank you for the help!

        tonyk

        Now that I know better, I would avoid the chroot and do the following:

        • at boot, when selecting which kernel to boot Solus with, press e to edit boot options
        • add the single option and boot
        • run the checks (or whatever it's called, I don't remember)
        • once logged as root, eopkg rmf broadcom-sta (hit tab for autocompletion)
        • reboot with a network alternative to the removed wifi (I had a spare wifi dongle)

            ReillyBrogan

            No, doesn't work with LTS kernel.
            After removing the broadcom-sta files as above, booted with LTS kernel and installed broadcom wifi files, then rebooted to LTS kernel - everything froze soon after logging in.

            Thank you for looking into this!

              Yes, you need to install the broadcom-sta package along with linux-lts, then you should be able to switch to the linux-lts kernel on boot up.

                ReillyBrogan
                Not sure if I caused any confusion while listing the files I deleted. My steps were as follows:

                1. After week 41 update, system locked up after rebooting and logging on.
                2. Deleting all traces of broadcom-sta (broadcom-sta, broadcom-sta-common, broadcom-sta-current) as described by plutuplutu allowed system to reboot without locking up after log on.
                3. Switched to LTS kernel (after Reilly Brogan's query) and installed broadcom-sta (not current) - and system locked up again after log on using LTS kernel.
                4. Switching back to current kernel, booting and logging on does not cause any lockup, as the broadcom-sta-current is not installed. Once broadcom-sta-current is installed (using doflicky or via terminal - eopkg it broadcom-sta-current), system locks up after log on.
                  This is on a MacBook Pro 9,2 with a Broadcom BCM4331 wifi card.
                  Thank you.

                  I can confirm that both kernels panic with their respective drivers.
                  Wifi card: Broadcom BCM4352, lenovo laptop.

                  Do you happen to have the kernel panic from the logs? You can see the logs from a previous boot by using sudo journalctl -b-$number where $number is the number of boots in the past you're trying to retrieve logs for. So the previous boot would be -b-1. I'm able to load the kernel module in a VM, I was hoping the crash would be in the init logic but since I don't have matching hardware I'm not able to reproduce a crash in hardware init.

                    ReillyBrogan I reinstalled the driver, rebooted -> frozen.
                    Rebooting in runlevel 1, I deleted the driver then rebooted.
                    I captured sudo journalctl -b-1.
                    But I'm not able to upload it Uploading files of this type is not allowed., I tried with .txt, .log, .dat.
                    Anyway looking at the content, I don't see anything relevant around the crash...

                      Toss it in hastebin/pastebin and paste the link instead.

                      Which kernel modules besides broadcom-wl are you using?

                      stephanedr Well, I mostly mean the addon kernel modules (like Nvidia built-in ones). But it looks like you're only using broadcom-wl and the default linux-current.

                      Would you be willing to try the unstable kernel? I'm not 100% certain that it will work (we've updated glibc and a bunch of other things in unstable, but that shouldn't affect the initramfs probably) but if it doesn't you can just roll back to the previous 6.5.7 kernel.

                      sudo eopkg it https://cdn.getsol.us/repo/unstable/l/linux-current/linux-current-6.5.8-260-1-x86_64.eopkg https://cdn.getsol.us/repo/unstable/b/broadcom-sta/broadcom-sta-common-6.30.223.271-370-1-x86_64.eopkg https://cdn.getsol.us/repo/unstable/b/broadcom-sta/broadcom-sta-current-6.30.223.271-370-1-x86_64.eopkg

                          ReillyBrogan I did the test -> the boot freezes.
                          Note that I removed broadcom-sta-* and the system boots fine with the "unstable" kernel (so with all other packages from the stable repo).

                          Do you suggest me to remove the "unstable" kernel (for clean next update from stable repo)?
                          If yes, can I use eopkg history -t ...? Will it run clr-boot-manager?

                            You don't need to manually remove the unstable kernel if it's working for you (sans broadcom support though). It's the exact same kernel package you would have received next sync anyway.

                            Unfortunately, we've been doing too many changes this sync cycle for me to easily troubleshoot your issue, but once the sync happens I'll build some test kernels for you and we can try to get to the bottom of what's happening here.

                            4 days later

                            ReillyBrogan Yes.
                            I also created a partition where I installed Solus 4.4 from the ISO.
                            From this fresh install, I performed the update and installed the broadcom driver.
                            It freezes during boot, both with current and LTS.

                              ReillyBrogan

                              Same result as stephanedr - updated, then installed the Broadcom driver and the system locked up as before.
                              Thank you.

                                Hello all, posting here as well in case the people affected with this issue are not all subscribed to the Github issue. I have built several batches of test kernels in order to pinpoint which part of the updates is at fault. Please go to https://github.com/getsolus/packages/issues/583 and follow the instructions on my most recent post. Once I have some feedback on what works and doesn't work I can narrow it down even further with additional batches of kernels.

                                10 days later

                                Bumping this just to let anyone not subscribed to the Github issue know that this is resolved. You should fully update your system, reinstall the broadcom drivers (if you removed them), and then run sudo depmod -a from the command line. Upon a reboot you should have a system that boots along with working wifi.