Latest update broke the internet (9/23/21)

Not sure if anyone else has reported it, but the latest update broke the internet (ethernet/wifi).
Was able to restore the system via snapshot, but the whole net went down, module and all. Since the laptop doesn’t even have an ethernet port you could see the problem I was facing here, luckily btrfs was there for the rescue (lmao).

Anyhow, thought I’d let you guys know about it.

1 Like

So a couple things

First, this doesn’t provide any information that could be used to figure out why this happened. Just saying the internet broke isn’t specific enough. You’ll need to included system info, detailed description of the issue, logs, steps to reproduce, etc

Next is EOS devs generally don’t maintain upstream (as in packages are from Arch Repos not maintained by EOS). If packages break the system figuring out which one and reporting to the maintainers will provide better results.

If you could provide more we might be able to pin down the issue.

Same thing happens with me,

Thank god, i had snapshot

Now i am thinking about to move to Manjaro

Would be good to know what packages related to connectivity was updated then forum users can watch out if it affects them :slight_smile:

i.e. r8168 was updated for me recently and no problem.

Always have backup. WiFi card in a desktop for hotspot or USB to Android to hotspot

You can, of course, but manjaro breaks too… better to troubleshoot to master your system rather than the system mastering you :wink:


I’m going to go on a limb and say you’re very likely using the latest kernel, and you likely also don’t have the LTS kernel installed.

You should (in my opinion) carry at least one extra kernel, and unless your computer is literally brand new, one should be it LTS.

These things break on latest and even LTS occasionally. It’s part of Arch/EOS.

It’s very very likely a kernel update, and could be fixed in the next update again.

For whatever it’s worth, I’ve had far less issues with Arch/Endeavour than Manjaro. There’s a LOT of folks who have no issue running it daily, so your results may vary. If you decide to head that way, it’s a solidly good distro. Their community is nothing like here (many of us came from there with the last change), so if you like our community, fair warning, it’s not what you’re used to. Their forum is help only.


Very possible, but without more info who knows? :man_shrugging:

I had an update in progress when I read this thread.
Rebooted as recommended after the update and booted using latest kernel.
I am now posting from the session, so if there was an issue it isn’t present at the moment,
or the issue is related to your hardware - by which I mean drivers

Your report is not very helpful. It does not tell which hardware failed and which kernel caused it.

Which kernel did you use? Did kernel 5.14 break for you or 5.10? You should always have 2 kernels installed so that you can switch during boot. And linux-lts kernel is a must have.

And this is not different with Manjaro by the way.

But what happens if Manjaro breaks, move onto Arco Linux? Not convenient to rotate distros per breakage basis :smiley:

Also I am not sure as have not used in a while but they delay Arch repo packages for a week but not AUR so there are problems with libraries. I may be wrong and perhaps now they give people “choice” to go latest as they please, but advise research.


:clap: well said

You are correct. Couldn’t add any logs since it all got erased when I snapshotted back. But most likely was a kernel update I pressume.

Latest kernel and yes, it’s the only one I use. Most likely had to do with a kernel update as you mentioned.

I’d definitely take the Vegas odds in this one. I’ve seen it A LOT. Especially since:

Best practise is to have at least two kernels installed. E.g. linux and linux-lts


@XuLin Also remember some drivers might be needed for the LTS as well i.e. nvidia-lts, r8168-lts etc where applicable.

Yep. Got a spare kernel installed now :smiley:

Did you work out which bit actually broke? Is it working again now?

Yes, needed a kernel module but we’re good now.