Been running endeavour pretty happily for the last couple years. Last night tried to update system at a bad time and OOM kiiler hit something… bad.
Not sure what, but wi-fi/bt is totally gone now. I’m hoping it isn’t a hardware issue - at this point I think it is, somehow.
I fresh installed Endeavour and the same issue happens on both the live cd and the installed OS. I even tried a pop! Os cd for the heck of it and the same thing pops up in dmesg logs exactly.
Have you tried to boot from the fallback kernel image from your bootloader menu? Does it work.
If it does, rebuilding your kernel images may help: sudo dracut-rebuild
If it doesn’t and the update was interrupted by something leading to a broken system, I think one thing you can try is to chroot and run the update again. Also rebuilding your kernels could be a good idea.
Well, at this point I’ve nothing to chroot into. I was considering a fresh install anyway, so I‘ve got a brand-new (offline, since no wifi) installation of EOS with an install disk I made using another working system.
I did try dracut-rebuild at your suggestion but it’s not changed the behavior at all.
The kernel version Pop provided was as far back as 6.9 (.14? Don’t recall exactly), so it doesn’t appear to be related to the kernel version.
I am just curious and hope an expert or somebody following the updates tell us.
I read another thread here same time as well another user saying he had the same problem with WiFi.
Maybe it was an update that caused this and once reported it got fixed?
Can an expert confirm if this was the case or just a coincidence?
If there really was a update that caused this , I think this forum would be full of users stating they had a problem. Also the topic starter mentioned a old popos kernel version 6.9.(14) . Now maybe the 14 was a hint to 1-4-2025 ?. Also the second user reporting the incident was a newly created account, maybe to create confusion. Ofcourse this is just a theory like any others.
Having slept on it, I realized it’s far more likely that when my update “failed”, it triggered a bug in the intel blobs and not the kernel.
6.9 downgrade didn’t do anything, and I am presently running the latest kernel in my new install with zero problems.
Also, I got the idea to run Debian Bullseye specifically because I was complaining to a friend on a diff Arch derivative who explained he’d had the exact same issue last year, and fixed it the exact same way. So whatever happened to me isn’t new.
Also, the user in the other post described that their wi-fi hardware wasn’t being enumerated by an lspci, so they either did it incorrectly, which didn’t appear to be the case, or had an unrelated issue.
Hey, I think it’s a strong credit to EOS that I’ve ran for as long as I have without needing help! When I checked just prior to reinstall, my hosts file reported it was created in july 2023. And before that, I’d had another install I ran for eight months and only lost due to triggering a partial update.
Don’t drink and root.
I could’ve salvaged this install, but I’ve been having freezes on and off for a long time and I wanted to try another desktop, so I’m hoping XFCE with a swap partition will treat me better than KDE without one.
