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?