ReillyBrogan
Below is output of sudo modinfo wl:
filename: /lib/modules/6.0.9-222.current/kernel/drivers/net/wireless/wl.ko.zst
license: MIXED/Proprietary
alias: pci:vdsvsdbc02sc80i*
depends: cfg80211
retpoline: Y
name: wl
vermagic: 6.0.9-222.current SMP preempt mod_unload modversions
parm: passivemode:int
parm: wl_txq_thresh:int
parm: oneonly:int
parm: piomode:int
parm: instance_base:int
parm: nompc:int
parm: intf_name:string

Thank you.

    tonyk So the kernel module is being picked up. Curious.

    Does sudo modprobe wl do anything? Does wl show up in the output of sudo lsmod afterwards? Any errors in dmesg after trying to run sudo modprobe wl?

    sudo modprobe wl
    insmod: ERROR: could not load module /lib/modules/6.0.9-222.current/kernel/drivers/net/wireless/wl.ko: No such file or directory
    sudo lsmod - wl is not listed.
    No dmseg errors.
    I also checked for any missing packages with "sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall" with no errors or installations.

    Thank you.

      tonyk Can you run sudo which modprobe? We updated kmod (which provides depmod, lsmod, and modprobe) to a version that supports zstd-compressed kernel modules however for whatever reason your version doesn't seem to be working with that. I wonder if your path is weird somehow and it's picking up a different version of those. The correct output of sudo which modprobe should be /sbin/modprobe.

      To test if this is the zstd compression is related to the issue you can decompress that kernel module manually.

      cd /lib/modules/6.0.9-222.current/kernel/drivers/net/wireless/
      sudo unzstd wl.ko.zst`

      And then see if that "fixes" it after a reboot. Note that this is only a temporary fix that will break the next time the kernel is updated (which is likely to happen very soon due to the FDE issue). The correct fix would be to figure out why your system isn't working with zstd modules.

        Surprise sync went through without issue here.

        ReillyBrogan - Thank you, I wasn't sure how to decompress the wl.ko.zst file - once the file was decompressed, my wifi is working again after rebooting.
        Result of "sudo which modprobe" is /sbin/modprobe

        Thank you again for getting this working! I'll update with the latest and see what happens.

          Cured an iMac 10 BT issue - well done, now I can give it back to the client.

          Hello
          Since the last update, lightdm does not launch
          I only found this error in the logs:

          /var/log/lightdm/x-0.log:(EE) event3 - SINO WEALTH USB KEYBOARD: client bug: event processing lagging behind by 32ms, your system is too slow

            Three Family Laptops updated with zero issues noted as yet.
            1 x old Asus Intel Celeron
            1 x Old Novatech Intel i5
            1 x Brand New Asus X515JAB Intel i3 (Latest Gen)
            Thanks to all those responsible for their time and effort. 😃

            tonyk Can I get the output of the following?

            ls -ahl /sbin | grep mod
            
            /lib/ld-linux-x86-64.so.2 --list /bin/kmod

            Then, I'd like to try LZMA compression with that kernel module instead of Zstandard since Arch Linux is using that and it doesn't seem like they have the same issue. Please run the following and reboot:

            cd /lib/modules/6.0.9-222.current/kernel/drivers/net/wireless/
            sudo rm wl.ko.zst
            sudo xz wl.ko

            This will delete the wl.ko uncompressed kernel module and replace it with wl.ko.xz. At this point you should have wl.ko.xz in this directory, but no wl.ko or wl.ko.zst. See if this works after a reboot. If it doesn't then you can do the following to get back to the non-compressed kernel module:

            cd /lib/modules/6.0.9-222.current/kernel/drivers/net/wireless/
            sudo xz -d wl.ko.xz

            Note that we've pushed a new kernel update, so if you've already done an update replace 6.0.9-222.current with 6.0.10-224.current in the above steps.

              I updated my main desktop last night, the one I game with. I tried to launch some Steam games this morning and no go. I was going to post here earlier, but thought I better check for updates first. There were two, one kernel and one Nvidia. I updated, rebooted and all works fine now. Thank you guys for being on top of this!

                zmaint just got the message to update. 6.0.10 kernel and a bunch of nvidia only. Rebooting now because I read your OK.

                lds-lds I have the same with 6.0.10 and Nvidia release 441. I can only get to text tty's on 6.0.10 and on 6.0.9 I can't get past a blank screen. I am kind of stuck @ReillyBrogan .

                  darkness I know you installed the experimental packages while I was testing a fix for the FDE issue. Did you re-install the Nvidia drivers per my last comment on that Phabricator issue report?

                    ReillyBrogan let me check.
                    I did notice 3 packages were installed before reboot: 1 kernel and 2* nvidia. Don't see them in eopkg.log though.

                      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.