[SOLVED] ethernet interface missing after booting windows

mrconfused · 2024-07-01 03:38:20

EDIT: ewallers recommendations fixed the problem

I have arch installed on an external SSD. I had just started using it with a new PC, and to get the network working all I had to do was change the ethernet interface name in /etc/systemd/network/20-wired.network to the new device, and set it to UP.

At this stage everything was working properly.

Then I booted back into windows (Windows 11, which is installed on one of the internal SSDs) used it for a while, and then booted back into Arch.

And now both my ethernet and wireless interfaces are missing:

ip link only shows the LO device, no other interfaces are listed.

Some googling suggests that it may be related to this problem: https://wiki.archlinux.org/title/Networ … OL_problem

However, none of the solutions in the above link seem applicable. Rolling back the NIC driver to pre-2007 surely can't be right. Enabling WOL in windows device manager does not seem to be an option in windows 11. There is no "Onboard LAN Boot ROM" in my bios.

lspci -v shows the Realtek ethernet controller, but there is no kernel driver or module in use for it.

Everything works fine in windows, its only arch that has the problem.

What do I try next?

Would very much appreciate some advice, thanks.

Last edited by mrconfused (2024-07-02 08:59:33)

ewaller · 2024-07-01 03:43:22

Do the version numbers reported by pacman -Q linux and uname -a agree? (Assuming you are using the stock kernel)

mrconfused · 2024-07-01 03:47:27

pacman -Q linux returns: 6.9.7.arch1-1

uname -a returns: 6.6.35-2-lts

ewaller · 2024-07-01 03:53:10

Same problem described here: https://bbs.archlinux.org/viewtopic.php?id=297270

The kernel has been updated along with the kernel modules. The boot partition still has the old kernel, but it cannot find its modules in /lib/modules because they were removed when the new kernel was installed. The boot partition needs the new kernel too. Use the solution I presented there,

Last edited by ewaller (2024-07-01 03:53:33)

mrconfused · 2024-07-01 04:56:21

Ok, what you say seem correct to me, but I think I've done something stupid because this still doesn't work.

I tried to follow the steps in the post you linked. Here's what I did:

1. Boot into arch install medium

2. Mount root filesystem to /mnt:
# mount /dev/sdb2 /mnt

3. Mount efi boot partition to /mnt/boot
# mount /dev/sdb3 /mnt/boot

4. Chroot in
# arch-chroot /mnt

5. Reinstall kernel
# pacman -S linux

6. Exit, unmount everything, reboot

But the results are the same:
pacman -Q linux returns: 6.9.7.arch1-1
uname -a returns: 6.6.35-2-lts

Previous to this problem, I converted my arch ssd install from BIOS to UEFI. During this process I did something wrong, and ended up without my kernels in my /boot dir, and so I manually copied them over from a backup dir. Maybe this broke something else?

cryptearth · 2024-07-01 05:05:45

pacman -S linux
usually re-downloads and re-installs the most recent standard kernel, copies it into /boot and generates a initramfs along with it.
Maybe you have to regenerate/update your bootloader config so it uses the new kernel and initrd.

Also: When dusl-booting with windows make sure to disable fast start in windows!

Scimmia · 2024-07-01 05:29:06

You're using linux-lts, you need to be checking that with linux -Q instead of 'linux'.

-thc · 2024-07-01 06:58:02

mrconfused wrote:

Previous to this problem, I converted my arch ssd install from BIOS to UEFI. During this process I did something wrong, and ended up without my kernels in my /boot dir, and so I manually copied them over from a backup dir. Maybe this broke something else?

Why didn't you mention this in your first post? Your first post leads everyone in a different direction:

mrconfused wrote:

Then I booted back into windows (Windows 11, which is installed on one of the internal SSDs) used it for a while, and then booted back into Arch.
And now both my ethernet and wireless interfaces are missing

You have accumulated several problems at once and a simple solution may not be possible.

So - try to retrace your steps from the last known working state to now and tell us what you have done in what order.

mrconfused · 2024-07-02 03:31:01

I apologise for not explaining things properly, I should probably have posted this in newbie corner as I don't fully understand what I am doing.

As it turns out, I forgot to switch back to the new kernel on boot, and was still booting with the lts kernel. The first part of ewallers solution does appear to have worked after all, I now have my ethernet and wireless interfaces working again.

I haven't quite finished with ewallers recommendations however: What is the proper way to add my efi boot partition to fstab? I dont know what options to set.

Again, sorry for the confusion, I very much appreciate the help.

EDIT: I will mark this as solved and ask the last question in newbie corner. Thanks everyone for the help

Last edited by mrconfused (2024-07-02 08:58:33)

Arch Linux

#1 2024-07-01 03:38:20

[SOLVED] ethernet interface missing after booting windows

#2 2024-07-01 03:43:22

Re: [SOLVED] ethernet interface missing after booting windows

#3 2024-07-01 03:47:27

Re: [SOLVED] ethernet interface missing after booting windows

#4 2024-07-01 03:53:10

Re: [SOLVED] ethernet interface missing after booting windows

#5 2024-07-01 04:56:21

Re: [SOLVED] ethernet interface missing after booting windows

#6 2024-07-01 05:05:45

Re: [SOLVED] ethernet interface missing after booting windows

#7 2024-07-01 05:29:06

Re: [SOLVED] ethernet interface missing after booting windows

#8 2024-07-01 06:58:02

Re: [SOLVED] ethernet interface missing after booting windows

#9 2024-07-02 03:31:01

Re: [SOLVED] ethernet interface missing after booting windows

Board footer