• [deleted]

  • Post #29

WetGeek So full install, minimal, netinstall and server 😉

      [deleted] You know, a headless version wouldn't be a bad idea. It would be a good way around having dated packages bork installs like with the current issue with some Nvidia cards. That way a person could just install, update from CLI, then install the DE of their choice.

        [deleted] So full install, minimal, netinstall and server

        What DE would your full install come with?

            Solus Pantheon.

            I've been using Elementary for a week but I'm starting to miss Solus' speed.

              @darkness @siru There's a tracking task for the FDE issues here. I'm going to create some test kernels with potential fixes shortly, but I do need additional information to make sure I get the right drivers rebuilt for you (I'll post it there).

              riffer I've been using Elementary for a week but I'm starting to miss Solus' speed.

              What are you waiting for!? Switch back asap! We have a new shiny kernel here! 😏

                  Folks, could we keep this thread mostly on track please? I'm reading every entry looking for issues and the less noise around that the better. Feel free to open a new thread if you want to talk about future ISO ideas.

                  Solarmass I know, my Keychron keyboard will finally work properly. I still have Solus on my other drive so I'll take a look next week.

                  Oops sorry. Back to Kernel issues.

                    Update went smooth on my four Solus computers ! Great work, thank you very much, the Solus team !

                    Successful update here. Happy to rock with the new AMD drivers!

                    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.