• Support

  • Latest Kernel Update Borked Wifi

moore-bryan When you go to the Solus Help Center and look under troubleshooting and then boot management, they describe how to change to an alternate kernel and how to switch to it, using sudo clr-boot-manager update.

There is no mention of having to restart or shutdown.

That command worked for me in changing to the LTS kernel as default. I just had to run the command and then shut down the PC and after that it permanently booted into the LTS kernel with the currant kennel as an alternative.

      lekkerlinux Like I wrote above, clr-boot-manager update seems to fail. Thankfully, my pops beat into my head to RTFM & the Help Center was the first place I stopped... 🙂

          [INFO] cbm (../src/bootman/bootman.c:L482): Current running kernel: 5.5.4-148.current
[INFO] cbm (../src/bootman/sysconfig.c:L98): Discovered UEFI ESP: /dev/disk/by-partuuid/187f26e4-81ff-4471-9a54-d52f2f3a92f7
[INFO] cbm (../src/bootman/sysconfig.c:L123): Fully resolved boot device: /dev/sda1
[DEBUG] cbm (../src/bootman/bootman.c:L130): UEFI boot now selected (systemd)
[INFO] cbm (../src/bootman/bootman.c:L502): path ///usr/lib/initrd.d does not exist
[INFO] cbm (../src/bootman/update.c:L116): Checking for mounted boot dir
[INFO] cbm (../src/bootman/update.c:L149): Mounting boot device /dev/sda1 at /boot
[SUCCESS] cbm (../src/bootman/update.c:L157): /dev/sda1 successfully mounted at /boot
[DEBUG] cbm (../src/bootman/update.c:L291): Now beginning update_native
[DEBUG] cbm (../src/bootman/update.c:L300): update_native: 1 available kernels
[DEBUG] cbm (../src/bootman/update.c:L320): update_native: Running kernel is (current) ///usr/lib/kernel/com.solus-project.current.5.5.4-148
[SUCCESS] cbm (../src/bootman/update.c:L335): update_native: Bootloader updated
[SUCCESS] cbm (../src/bootman/update.c:L349): update_native: Repaired running kernel ///usr/lib/kernel/com.solus-project.current.5.5.4-148
[DEBUG] cbm (../src/bootman/update.c:L358): update_native: Checking kernels for type current
[INFO] cbm (../src/bootman/update.c:L373): update_native: Default kernel for type current is ///usr/lib/kernel/com.solus-project.current.5.5.4-148
[SUCCESS] cbm (../src/bootman/update.c:L385): update_native: Installed tip for current: ///usr/lib/kernel/com.solus-project.current.5.5.4-148
[SUCCESS] cbm (../src/bootman/update.c:L399): update_native: Installed last_good kernel (current) (///usr/lib/kernel/com.solus-project.current.5.5.4-148)
[DEBUG] cbm (../src/bootman/update.c:L410): update_native: Analyzing for type current: ///usr/lib/kernel/com.solus-project.current.5.5.4-148
[DEBUG] cbm (../src/bootman/update.c:L413): update_native: Skipping running kernel
[SUCCESS] cbm (../src/bootman/update.c:L468): update_native: Default kernel for current is ///usr/lib/kernel/com.solus-project.current.5.5.4-148
[DEBUG] cbm (../src/bootman/update.c:L479): No kernel removals found
[INFO] cbm (../src/bootman/update.c:L175): Attempting umount of /boot
[SUCCESS] cbm (../src/bootman/update.c:L179): Unmounted boot directory

          Currently, I'm unable to boot into the kernel with which wifi works because the spacebar trigger is no longer working on my system for some reason...

          EDIT: It would appear that reason is the other kernels do not appear to be present any longer. I thought the default was to keep the current kernel and the previous version... I'm installing the LTS kernel to see... The LTS kernel works, but I'm still receiving the config loading error on line 1 of clr-boot-manager update.

            moore-bryan My LTS kernel updated Friday and now some program crashes. Considering going back to boring, slow but reliable Zorin 15.1.

              The LTS works fine for me, but the 5.5.* still doesn't; in fact, 5.4.* did, so I'm not sure what's going on here and I'm not sure why this doesn't seem to be a higher priority...

                moore-bryan I'm swamped at work and haven't had any time at all to look into this further. I would suggest looking for bug reports on the kernel bug tracker or from other distros. I'm sure someone else has encountered this elsewhere. Otherwise, you'll just have to wait for me or someone else to do so.

                  Understandable, @DataDrake; my bug report on dev.getsol.us seems relatively untouched. Are you referring to the kernel.org bugtracker or is there a Solus-specific one?

                    11 days later
                    8 days later

                    I'm also experiencing strange kernel problems. On latest 5.5.7-150.current i see vertical lanes (which look like the GPU is broken) while shuting down Solus & overall Solus is signitificintly slower. On kernel 5.4.12-144.current everything was superduper nice, fast. So now I switched to LTS. On LTS Solus doesn't recognize that I'm using 23" display connected do docking station & I need to manually open laptop, change default display & it works untill reboot. On 5.4.12-144.current I had no issues.

                    Yeah, the difference between the LTS kernel (4.9.215) and the 5.4.12 is night and day. I've been able to maintain the 5.4.12-144 kernel by booting into it each time, so it doesn't get autoremoved, but that's a band-aid more than anything else...

                      moore-bryan A dangerous bandaid. If you stay on that kernel it means you have no security updates that have been applied in the current kernel.

                          Justin We all know that. But 5.5.7-150 is not working correctly. So which ,,evil" is less evil? 😉 In my case LTS is not so ,,smart" when it comes my hardware.

                            12 days later

                            The issue persists with com.solus-project.current.5.5.11-151 and I believe its directly related to iwlwifi containing bad code...

                            moore-bryan Understand that some, most, or maybe all of the devs do this in their spare time. It's not like it's their full-time job.

                            Do you have the option to use an ethernet connection until the issue gets resolved? I sometimes have to resort to using an ethernet connection when an upgrade in Debian Unstable borks WiFi. Usually it's an upgrade to the wpasupplicant package.

                              I completely get the volunteer nature... It was hard enough juggling work, family, and hobby before coronavirus...

                              Currently, I run the current kernel when I'm at home & the working 5.4 kernel when I need wifi.

                              I have reason to believe the issue is more iwlwifi related just because of my network card and there's, apparently, an upstream fix for it that hasn't been merged yet; I reference it in my bug report: https://dev.getsol.us/T8757

                              Thanks for the idea!

                                moore-bryan When was iwlwifi last updated? If you're not in the habit of running sudo eopkg dc, you might be able to install the previous version and see if that works.

                                Too bad Solus doesn't have something like the Debian Snapshot Service/Repo. I use that when an upgrade under Debian Unstable turns out to be buggy.

                                  I compiled and installed the latest from the Linux wireless git, but that didn't solve my issue; so, I assumed I didn't do it correctly.

                                  I've never tried the downgrade... But, iwlwifi isn't standalone, so I'd have to downgrade there linux-firmware package; correct?