Windows is more than likely the culprit here.
I cannot imagine a sensible reason why ethernet would not work even on live USBs.
Probably some recent update messed something up?
However I don’t recall updating Windows around that time (I could be wrong, though).
Now that you mention it, the ethernet adapter on my system always breaks after I’ve logged into Windows.
I use both OSs on a daily basis and when I manage to fix linux (by pure chance), the next time I log in (which will more than likely be after also booting on Windows) the ethernet is broken again.
As you can see by this thread, I’ve been facing this problem for 3-4 days now.
When it works it is purely random.
@SlapGas
Could you both run a test regimen to establish the source of the problem by exclusion?
Do each of those steps alone and see if anything changes.
Turn of the PC and leave it turned off for 5 minutes. Then turn on again.
Do the same with the router.
Hard configure the IP addresses in the router and the devices.
This is for sure a very curious behaviour you both are describing here.
For once, I can safely guarantee you that step 1 does not work; I turn the PC off every night and power it on the next afternoon (when I get back home from work). Thus it remains powered off for like 16-17 hours.
I will give a shot at restarting the router and configuring the IP manually (I’m gonna be pretty rusty on the latter, it’s been a while since I had to manually set up and internet connection).
I did not turn “fast boot” off in BIOS and, to be honest, I don’t even know if it is on or off right now.
What I do know though is that I certainly did not change anything in BIOS when the problem appeared.
Reboot into Windows --> Ethernet always works there
Reboot into Manjaro --> Ethernet broken
So, the problem appears after logging into Windows.
Fun fact:
Yesterday evening around 2 a.m. we had a minor power outage here in the neighborhood.
Not too long, probably was around 5 minutes.
I was finishing some stuff when the power went out.
So I figured I’d call it a day.
This afternoon when I came back from work and logged into linux, guess what happened?
Ethernet was working fine.
This means that the power outage was someway/somehow able to “reset” the whole issue.
So I used this opportunity to work on linux, reinstall some stuff etc etc.
I rebooted many times from linux to linux, not a single problem.
As soon as I booted into Windows (for like 20 seconds) and rebooted into linux, ethernet broke again.
I fully shut down the PC, waited for like 5 minutes and then logged into linux again.
Ethernet still broken.
Fully shut down the PC and the router, opened them up and then logged into linux.
Ethernet still broken.
The only thing I did not try thus far (in hopes of “mimicking” the power outage) is switching off the PSU and taking the power cable off.
Read through that thread and tried replacing the ethernet cable.
I have 3 different ethernet cables, which all work on Windows.
Tested all 3, the connection problem was not fixed.
I also tried different router ports, with similar results.
The only thing that “works” reliably thus far is shutting off the PSU.
The problem persists, I haven’t been able to figure out what’s wrong.
The only way I am able to get ethernet to work on Linux is by shutting off the PSU for a couple minutes after I have logged into Windows.
This way, I am able to get normal ethernet connection on Linux.
It’s kinda annoying, but at least it is something simple that does the trick.
Would love to find out what’s causing the problem though.
/sys/kernel/debug/dynamic_debug does not exist on my system (I did not take the extra step to create it).
echo '0000:00:10.0' | sudo tee /sys/bus/pci/drivers/e1000e/unbind
0000:00:10.0
tee: /sys/bus/pci/drivers/e1000e/unbind: No such device
echo '0000:00:10.0' | sudo tee /sys/bus/pci/drivers/e1000e/bind
0000:00:10.0
tee: /sys/bus/pci/drivers/e1000e/bind: No such device
The workarounds suggested have been tried in previous steps. In addition, my problem is not WiFi related so I could not try the WiFi specific remedies.
THIS WORKED!!!. Ethernet started working after the suggestion in step 7!!!
Wow, thanks a lot!
By means of the working solution, what seems to be the problem?
I am genuinely curious.
Ninja edit:
I just realised I did not provide a complete answer for your 4th suggestion (since I’d have to also provide the dmesg output when the Ethernet works). Apologies. However, I don’t think it matters since I guess we were able to kinda track the problem down.
Well, it should. /sys/kernel/debug/ can only accessed by root, so if you tried tab completion in the shell, it won’t work.
You seem to have used “0000:00:10.0” instead of “0000:00:19.0” when testing the fifth point.
I believe the device is in a state after the Windows shutdown that the Linux driver cannot handle properly. It seems a PCI reset helps. This was suggested in comment 55 of bug 201319, I just adapted it to your configuration.
I think Windows 10 no longer does a proper shutdown, it suspends to disk if I’m not mistaken. This would explain having to kill the power to the machine manually.
If you’re still having this problem, I found a solution.
Okay, so after a lot of trial and error, I finally figured out how to solve this. I had the exact same error as you. Live USB wouldn’t work, install wouldn’t work, these solutions wouldn’t work. Almost everything I tried just didn’t work. Tried all these great solutions posted here as well. Thank you @pobrn wouldn’t have gotten close without you!
Semingly the issue is that with the Intel PRO/1000 Network Driver something changes the defaults of the controller(driver). This had no effect on my windows boot before or after. You need to reset them all to default. You can do that in Arch/Ubuntu/Windows using Intels utility found here:
I cannot post links yet, but It is downloadcenter.intel dot com /download/29137?v=t
One could also google intels network utility as well.
You’ll need to have fast boot disabled in Windows and BIOS if you’re dual booting as well. For reference I am running an MSI z390 Pro Carbon Mobo. This seems to be a problem with the specific default driver for ASUS/MSI mobos.
I haven’t been on Linux in over 10 years so hopefully this makes sense and can help someone in the future! Thanks to everyone in this thread!