You are not logged in.
Pages: 1
I am a new Arch user who is having trouble connecting to the internet through an ethernet connection. I have found that section 3.6 of this page applies to me - Gigabyte Motherboard with Realtek 8111/8168/8411.
I have followed along with the wiki and enabled IOMMU in the motherboard BIOS, and have confirmed that the r8169 module is installed and in use. However, that made no difference. I also tried blacklisting r8169 and installing r8168 with still no luck.
I am wondering if anyone has any more ideas? Can I connect to the internet using an ethernet to USB 3.0 dongle? Or will I need to go out and buy a different motherboard?
Last edited by Genje (2022-11-09 20:47:39)
Offline
Does that imply that there's a parallel windows installation?
=> 3rd link below.
I am wondering if anyone has any more ideas?
We first need to identify what the actual problem is.
lspci -k
ip a
ip r
find /etc/systemd -type l -exec test -f {} \; -printYou can redirect those outputs into a file and usb-walk them to a system w/ internet connection.
If you're dead-sure that it's down to the chip (what I'm less than convinced of), you can also https://wiki.archlinux.org/title/Tethering
Offline
I have some internet now, however it is extremely unstable. For example, it took 10 min to load google.com. I removed the Windows drive completely, so fast-boot shouldn't be an issue.
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
Kernel driver in use: pcieport
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
Subsystem: Gigabyte Technology Co., Ltd Device 5001
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
Subsystem: Gigabyte Technology Co., Ltd Device 5001
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller (rev 01)
Subsystem: ASMedia Technology Inc. Device 1142
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
Subsystem: ASMedia Technology Inc. Device 1062
Kernel driver in use: ahci
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
Subsystem: ASMedia Technology Inc. Device 0201
Kernel driver in use: pcieport
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
Subsystem: ASMedia Technology Inc. Device 3306
Kernel driver in use: pcieport
02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
Subsystem: ASMedia Technology Inc. Device 3306
Kernel driver in use: pcieport
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
Subsystem: ASMedia Technology Inc. Device 3306
Kernel driver in use: pcieport
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
Kernel driver in use: r8168
Kernel modules: r8169, r8168
06:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] (rev a1)
Subsystem: eVga.com. Corp. Device 2062
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia
06:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
Subsystem: eVga.com. Corp. Device 2062
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
06:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
Subsystem: eVga.com. Corp. Device 2062
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
06:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
Subsystem: eVga.com. Corp. Device 2062
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu
07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
Kernel driver in use: ccp
Kernel modules: ccp
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller
Subsystem: Gigabyte Technology Co., Ltd Device 5007
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
08:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
Subsystem: Gigabyte Technology Co., Ltd Device b002
Kernel driver in use: ahci
08:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
Subsystem: Gigabyte Technology Co., Ltd Device a182
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b4:2e:99:a7:e4:e1 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 metric 100 brd 192.168.1.255 scope global dynamic enp4s0
valid_lft 86253sec preferred_lft 86253sec
inet6 fe80::b62e:99ff:fea7:e4e1/64 scope link
valid_lft forever preferred_lft forever
default via 192.168.1.1 dev enp4s0 proto dhcp src 192.168.1.3 metric 100
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.3 metric 100
192.168.1.1 dev enp4s0 proto dhcp scope link src 192.168.1.3 metric 100
/etc/systemd/system/dbus-org.freedesktop.resolve1.service
/etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service
/etc/systemd/system/sockets.target.wants/systemd-networkd.socket
/etc/systemd/system/display-manager.service
/etc/systemd/system/multi-user.target.wants/systemd-networkd.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/sysinit.target.wants/systemd-network-generator.service
/etc/systemd/system/sysinit.target.wants/systemd-resolved.service
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/dbus-org.freedesktop.network1.service
/etc/systemd/system/timers.target.wants/fstrim.timer
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/user/pipewire.service.wants/wireplumber.service
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/pipewire-session-manager.service
Last edited by Genje (2022-11-09 22:44:22)
Offline
Please (edit your post and) use "code" tags, not "quote" tags.
You're running on r8168 and you've a carrier, a lease and a route over that NIC.
There's only systemd-networkd, so there's no problem w/ the configuration.
I removed the Windows drive completely, so fast-boot shouldn't be an issue.
Whether there's a windows drive is irrelevant. The problem is that the hibernating windows leaves the hardware in an undefined state.
You can afterwards remove a random partition or not, it doesn't cure the compromised state.
Disable fast-start, shutdown windows and then you need to figure why and where things are slow (if they still are)
pacman -Qs firmware
ping -c4 _gateway
ping -c4 8.8.8.8
ping -c4 google.com
sudo journalctl -bOffline
Pages: 1