Realtek NIC RTL8125BG driver issues

J

jbobf

Member
Jan 24, 2022
7
2
8
30
Hi, despite following steps from lots of other threads here and on github I can't seem to get my NIC working. I have tried installing using the autorun.sh script directly from Realteks download site "2.5G Ethernet LINUX driver r8125 for kernel up to 6.8" [1] and following the steps in linked comment on awesometic github using dkms [2].

None of the methods have gotten my card working for me, I just get no connection from any port and error messages like the ones below is constantly being printed at the host screen.

[ 108.426301] r8125 0000:04:00.0 enp4s0: NETDEV WATCHDOG: CPU 13: transmit queue 0 timed out 6215 ms
[ 129.417799] r8125 0000:04:00.0 enp4s0: NETDEV WATCHDOG: CPU 8: transmit queue 0 timed out 6252 ms

I also got an error installing with the autorun.sh script saying: Warning: modules_install: missing 'System.map' file. Skipping depmod.
Not sure what this means, searched a little for it, someone had issues with secure boot not being set to other OS but mine already was.

root@server:/media/realtekdriver/r8125-9.013.02# bash autorun.sh

Check old driver and unload it.
rmmod r8125
Build the module and install
Skipping BTF generation for /media/realtekdriver/r8125-9.013.02/src/r8125.ko due to unavailability of vmlinux
Warning: modules_install: missing 'System.map' file. Skipping depmod.
DEPMOD 6.8.8-3-pve
load module r8125
Updating initramfs. Please wait.
update-initramfs: Generating /boot/initrd.img-6.8.8-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Completed.


I'll put some network configs below, let me know if I can provide any other outputs for troubleshooting. I'm at my wits end here, most people in threads report success after following the steps I have but I can't get it working.

Grateful for any help.


lspci -nnk | grep -A2 Ethernet​


00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I218-LM [8086:15a0] (rev 05)
DeviceName: Onboard LAN
Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I218-LM [1043:862a]
Kernel driver in use: e1000e
Kernel modules: e1000e
--
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
Kernel driver in use: r8125
--
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
Kernel driver in use: r8125
--
06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
Kernel driver in use: r8125
--
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
Kernel driver in use: r8125
--
0a:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)
Subsystem: ASUSTeK Computer Inc. I210 Gigabit Network Connection [1043:8557]
Kernel driver in use: igb

etc/network/interfaces​


auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto enp4s0
iface enp4s0 inet manual

auto enp10s0
iface enp10s0 inet manual

auto enp5s0
iface enp5s0 inet manual

auto enp6s0
iface enp6s0 inet manual

auto enp7s0
iface enp7s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.119/24
gateway 192.168.1.1
bridge-ports eno1 enp4s0 enp5s0 enp6s0 enp7s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#LAN/mgmtPort

auto vmbr1
iface vmbr1 inet manual
bridge-ports enp10s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#WAN



[1] https://www.realtek.com/Download/List?cate_id=584
[2] https://github.com/awesometic/realtek-r8125-dkms/issues/55#issuecomment-2184079948
 
hello,
Try that :

To check which partition is /boot with vfat format:
\~# lsblk -o +FSTYPE

To initialize ESP sync first unmount boot partition:
:\~# umount /boot/efi

Then link the vfat partiton with proxmox-boot-tool:
:\~# proxmox-boot-tool init /dev/XXXXXXXX => where XXXXXXXX is the name of vfat partiton from lsblk +FSYSTEM

Then:
:\~# mount -a

Then to update modules:
:\~# update-initramfs -u -k all

If you retry autorun.sh, it's ok ?
 
lolvince said:
hello,
Try that :

To check which partition is /boot with vfat format:
\~# lsblk -o +FSTYPE

To initialize ESP sync first unmount boot partition:
:\~# umount /boot/efi

Then link the vfat partiton with proxmox-boot-tool:
:\~# proxmox-boot-tool init /dev/XXXXXXXX => where XXXXXXXX is the name of vfat partiton from lsblk +FSYSTEM

Then:
:\~# mount -a

Then to update modules:
:\~# update-initramfs -u -k all

If you retry autorun.sh, it's ok ?
Click to expand...

Hi thanks for your answer, unfortunately it did not remove the warning although the autorun.sh output changed a bit.
Connecting anything to the NIC still gives out NETDEV WATCHDOG errors.
This is what the script output:
root@server:/media/realtekdriver/r8125-9.013.02# bash autorun.sh

Check old driver and unload it.
rmmod r8125
Build the module and install
Skipping BTF generation for /media/realtekdriver/r8125-9.013.02/src/r8125.ko due to unavailability of vmlinux
Warning: modules_install: missing 'System.map' file. Skipping depmod.
DEPMOD 6.8.8-3-pve
load module r8125
Updating initramfs. Please wait.
update-initramfs: Generating /boot/initrd.img-6.8.8-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
Completed.
 
lolvince said:
hello,
Try that :

To check which partition is /boot with vfat format:
\~# lsblk -o +FSTYPE

To initialize ESP sync first unmount boot partition:
:\~# umount /boot/efi

Then link the vfat partiton with proxmox-boot-tool:
:\~# proxmox-boot-tool init /dev/XXXXXXXX => where XXXXXXXX is the name of vfat partiton from lsblk +FSYSTEM

Then:
:\~# mount -a

Then to update modules:
:\~# update-initramfs -u -k all

If you retry autorun.sh, it's ok ?
Click to expand...

The commands you listed output this:



root@server:~# lsblk -o +FSTYPE​

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE
sda 8:0 0 3.6T 0 disk
├─sda1 8:1 0 3.6T 0 part zfs_member
└─sda9 8:9 0 8M 0 part
sdb 8:16 0 3.6T 0 disk
├─sdb1 8:17 0 3.6T 0 part zfs_member
└─sdb9 8:25 0 8M 0 part
sdc 8:32 0 111.8G 0 disk
├─sdc1 8:33 0 1007K 0 part
├─sdc2 8:34 0 512M 0 part /boot/efi vfat
└─sdc3 8:35 0 111.3G 0 part LVM2_membe
├─pve-swap 252:0 0 8G 0 lvm [SWAP] swap
└─pve-root 252:1 0 103.3G 0 lvm / ext4
sdd 8:48 0 111.8G 0 disk
└─sdd1 8:49 0 111.8G 0 part /mnt/pve/backups ext4
zd0 230:0 0 3.4T 0 disk
└─zd0p1 230:1 0 3.4T 0 part ext4
zd16 230:16 0 60G 0 disk
├─zd16p1 230:17 0 58G 0 part ext4
└─zd16p2 230:18 0 1G 0 part swap
zd32 230:32 0 32G 0 disk
├─zd32p1 230:33 0 32M 0 part vfat
├─zd32p2 230:34 0 24M 0 part squashfs
├─zd32p3 230:35 0 256M 0 part squashfs
├─zd32p4 230:36 0 24M 0 part squashfs
├─zd32p5 230:37 0 256M 0 part squashfs
├─zd32p6 230:38 0 8M 0 part
├─zd32p7 230:39 0 96M 0 part ext4
└─zd32p8 230:40 0 31.3G 0 part ext4
zd48 230:48 0 48G 0 disk
└─zd48p1 230:49 0 46.6G 0 part ext4
zd64 230:64 0 25G 0 disk
├─zd64p1 230:65 0 24G 0 part ext4
├─zd64p2 230:66 0 1K 0 part
└─zd64p5 230:69 0 975M 0 part swap
zd80 230:80 0 10G 0 disk
├─zd80p1 230:81 0 512K 0 part
├─zd80p2 230:82 0 2G 0 part
└─zd80p3 230:83 0 8G 0 part zfs_member
zd96 230:96 0 1M 0 disk
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:2 0 238.5G 0 part zfs_member
└─nvme0n1p9 259:3 0 8M 0 part
nvme1n1 259:1 0 238.5G 0 disk
├─nvme1n1p1 259:4 0 238.5G 0 part zfs_member
└─nvme1n1p9 259:5 0 8M 0 part


root@server:~# umount /boot/efi​

root@server:~# proxmox-boot-tool init /dev/sdc2​

Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
UUID="40B4-CF23" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="sdc" MOUNTPOINT=""
Mounting '/dev/sdc2' on '/var/tmp/espmounts/40B4-CF23'.
Installing grub x86_64 target..
Installing for x86_64-efi platform.
Installation finished. No error reported.
Installing grub x86_64 target (removable)..
Installing for x86_64-efi platform.
Installation finished. No error reported.
Unmounting '/dev/sdc2'.
Adding '/dev/sdc2' to list of synced ESPs..
Refreshing kernels and initrds..
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done



root@server:~# mount -a​

root@server:~# update-initramfs -u -k all​

update-initramfs: Generating /boot/initrd.img-6.8.8-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.158-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.152-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.149-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.131-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.108-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.102-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.15.60-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.13.19-6-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.13.19-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
update-initramfs: Generating /boot/initrd.img-5.13.19-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
 
Update on my issue, NIC still getting timeout errors and won't produce a connection but I managed to fix the warning from the autorun.sh script.
Tried this script from another dkms github for r8125 drivers (https://github.com/fibreyu/pve_realtek_r8125_dkms).

root@server:~# cert_path="/lib/modules/$(uname -r)/build/certs/"
root@server:~# tee "${cert_path}x509.genkey" > /dev/null << 'EOF'
[ req ]
default_bits = 4096
distinguished_name = req_distinguished_name
prompt = no
string_mask = utf8only
x509_extensions = myexts
[ req_distinguished_name ]
CN = Modules
[ myexts ]
basicConstraints=critical,CA:FALSE
keyUsage=digitalSignature
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid
EOF
openssl req -new -nodes -utf8 -sha512 -days 36500 -batch -x509 -config "${cert_path}x509.genkey" -outform DER -out "${cert_path}signing_key.x509" -keyout "${cert_path}signing_key.pem"
.......+......+........+.+.....+.+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*........+......+....+..............+......+.............+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*.........+.+...........+...+.+............+..+...............+............+.+.....+....+......+.....+...+....+..................+...+...........+....+.........+.....+.+.....................+.....+......+...............+.......+...+.....+............+.+..+.........+.............+...+.........+......+..............+....+.....+............+...+....+...+.....+...+.........+..........+........+...+..........+......+........+......+.+.....+....+.........+...+.....+.........+......+.............+.................+.......+...+........+......+..................+.+.........+..+...+.......+.....................+...+..+.........+.............+...+.....+.........+...+...............+.............+............+........+.........+.+..+............+...+.......+...........+....+........+.......+.....+...............+...................+...........+.............+.....+.......+...+.....+......+.......+...+......+.........+..............+..........+..+....+..+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
........+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*..+...+....+...+...+...+.........+............+...+..+....+..............+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*...+.+......+............+..............................+...+...+..............+...+.......+.....+............+...............+.............+..+.+........+...................+..+.+.........+.........+....................+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----
root@server:~# for i in /boot/System.map*
do
# echo ${i#*map-}
ln -sf $i "/lib/modules/${i#*map-}/build/System.map"
> done
ln: failed to create symbolic link '/lib/modules/5.13.19-2-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.13.19-3-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.13.19-6-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.102-1-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.108-1-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.131-2-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.149-1-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.152-1-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.158-1-pve/build/System.map': No such file or directory
ln: failed to create symbolic link '/lib/modules/5.15.60-1-pve/build/System.map': No such file or directory


Although autorun did not get the warning my NIC still won't work, anyone have suggestions for further troubleshooting?

root@server:/media/realtekdriver/r8125-9.013.02# bash autorun.sh

Check old driver and unload it.
rmmod r8125
Build the module and install
Skipping BTF generation for /media/realtekdriver/r8125-9.013.02/src/r8125.ko due to unavailability of vmlinux
DEPMOD 6.8.8-3-pve
load module r8125
Updating initramfs. Please wait.
update-initramfs: Generating /boot/initrd.img-6.8.8-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/40B4-CF23
Copying kernel 5.15.158-1-pve
Copying kernel 6.8.8-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-3-pve
Found initrd image: /boot/initrd.img-6.8.8-3-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
Completed.
 
did you ever solve this problem i got the exact same issue. its super frustrating as ive put these cards in all my servers and i dont want to replace them all again when they work fine in my current windows server environment :(
 
No sorry to say I didn't find a fix for this problem. Even tried backing up all my VMs and performing a clean install, trying to install the driver in debug mode during installation like people did in this thread.

I had no success and ended up buying a Intel NIC with 1/4 the ports for the same price. And yeah it's frustrating and very much a driver issue on some level, my Realtek NIC worked instantly when I tried it in my Windows PC.
 
I had a different problem with another OS but a similar NIC ( only one port ).
Anyway i solved my problem with:

ethtool -K eth0 tx off sg off tso off
where eth0 it's the address of your hardware NIC ( not the virtual bridge ).
Trying cost nothing ;) Hope it fixes it for you
 
Same issue here. The only solution i found is rollback to kernel 6.5. I wrote more information in this link :https://github.com/awesometic/realtek-r8125-dkms/issues/55

PVE may change something in linux kernel 6.8 because there is no same issue in Debian 12 with 6.8. And I can ensure that only 8125[BG] ver get this problem.

And I find this in changelog of PVE 8.2
Proxmox repackaged the r8125-dkms driver needed for 2.5G RealTek NICs, as the driver is not merged in the upstream kernel, in order to add compatibility with the new 6.8 kernel series.
Click to expand...
Maybe some official guys can find out something and roll it back when they release 8.3
 
  • Like
Reactions: robbo54
This is a shot in the dark. I am not a Proxmox user but I would like to be. I am hoping what I am about to say may be helpful for someone else to troubleshoot this problem in Proxmox so that I know it can be solved. I had a similar problem with the Realtek 2.5G NIC (rev 0c) in my new MOBO where I installed Arch Linux (with Kernel 6.12.10-arch1-1). There is an r8125 DKMS package designed for Arch as well (https://aur.archlinux.org/packages/r8125-dkms) but even with it installed, the r8169 kernel module kept overriding it. And so the solution in Arch was to black list the r8169. For example (again this is in Arch, I don't know if in a Debian based system like Proxmox it is the same procedure or not).

Code: 
sudo nano /etc/modprobe.d/r8169.conf

Then type this into the file

Code: 
blacklist r8169

Save and exit.

Then in Arch I installed linux-headers, dkms, and the r8125-dkms AUR package listed above, rebooted and it worked. And so maybe in Proxmox you also need to black list the r8169 to get the r8125 to work.
 
  • Like
Reactions: cave
Joelk said:
This is a shot in the dark. I am not a Proxmox user but I would like to be. I am hoping what I am about to say may be helpful for someone else to troubleshoot this problem in Proxmox so that I know it can be solved. I had a similar problem with the Realtek 2.5G NIC (rev 0c) in my new MOBO where I installed Arch Linux (with Kernel 6.12.10-arch1-1). There is an r8125 DKMS package designed for Arch as well (https://aur.archlinux.org/packages/r8125-dkms) but even with it installed, the r8169 kernel module kept overriding it. And so the solution in Arch was to black list the r8169. For example (again this is in Arch, I don't know if in a Debian based system like Proxmox it is the same procedure or not).

Code: 
sudo nano /etc/modprobe.d/r8169.conf

Then type this into the file

Code: 
blacklist r8169

Save and exit.

Then in Arch I installed linux-headers, dkms, and the r8125-dkms AUR package listed above, rebooted and it worked. And so maybe in Proxmox you also need to black list the r8169 to get the r8125 to work.
Click to expand...

I tried this method when I first meet this problem, but it didn't work. We can confirm that the network card is working under the r8125 driver using lspci -a.
 
  • Like
Reactions: cave
I am not sure what the difference is between the RTL8125BG and RTL8125B chip set/driver, but I didn't have to do anything to get my RTL8125B based Wavelink USB NIC to work in Proxmox. It just worked, right out of the box. I did have to edit my /etc/network/interfaces file to replace my existing 1 gb NIC on my vmbr0, but that was it.
 
For anyone running into this issue, I just installed the latest drivers from RealTek and blacklisted the default kernal drivers. Worked just fine.
Driver Link
Code: 
apt update
apt install build-essential pve-headers-$(uname -r)
tar xjf driver_file.tar.bz2
cd extracted_driver_folder
sudo ./autorun.sh
echo "blacklist r8169" | sudo tee /etc/modprobe.d/blacklist-realtek.conf
sudo update-initramfs -u
sudo modprobe r8125
lsmod | grep r8125
sudo reboot

Should be ready to config in Proxmox now.
 
Last edited:
  • Like
Reactions: Truckguy
ironman1337 said:
For anyone running into this issue, I just installed the latest drivers from RealTek and blacklisted the default kernal drivers. Worked just fine.
Driver Link
Code: 
apt update
apt install build-essential pve-headers-$(uname -r)
tar xjf driver_file.tar.bz2
cd extracted_driver_folder
./autorun.sh
echo "blacklist r8169" | sudo tee /etc/modprobe.d/blacklist-realtek.conf
sudo update-initramfs -u
sudo modprobe r8125
lsmod | grep r8125
sudo reboot

Should be ready to config in Proxmox now.
Click to expand...
Could you explain to me, whats the best way to get the current driver from realtek on to my proxmox machine?
Did you download the file "r8125-9.015.00.tar.bz2" from realtek?

I'm very much new to all things linux and quite overwhelmed. ;-*
 
vghgvbh said:
Could you explain to me, whats the best way to get the current driver from realtek on to my proxmox machine?
Did you download the file "r8125-9.015.00.tar.bz2" from realtek?

I'm very much new to all things linux and quite overwhelmed. ;-*
Click to expand...
No worries, I've been working on computers for 30+ years, and I still ask for help. Honestly I find AI tools like Gemini to be really helpful.

To copy files from your Windows PC, you need an SFTP tool. Personally I use MobaXterm, which does SSH command line interface, as well as SFTP. With it, when you SSH into a terminal, there will be a file menu on the left hand side. You can download files from your server, or drag and drop files to upload to it. Just make sure you have permission to upload to whatever directory you are in.

You can also use FileZilla, which just does SFTP/FTP. Just use your normal SSH login to connect to your server.
 
ironman1337 said:
No worries, I've been working on computers for 30+ years, and I still ask for help. Honestly I find AI tools like Gemini to be really helpful.

To copy files from your Windows PC, you need an SFTP tool. Personally I use MobaXterm, which does SSH command line interface, as well as SFTP. With it, when you SSH into a terminal, there will be a file menu on the left hand side. You can download files from your server, or drag and drop files to upload to it. Just make sure you have permission to upload to whatever directory you are in.

You can also use FileZilla, which just does SFTP/FTP. Just use your normal SSH login to connect to your server.
Click to expand...
Many thanks ill try this out
 
I'm having similar issues, tried the steps to downgrade driver to r8125 but same symptom as when I was on r8169.

In Proxmox network tab the NIC is shown, and if I assign an IP I can connect via ssh and web UI but when I check the driver and NIC status in the terminal it shows as state down and driver not in use.

Also no lights on the NIC or switch port.
So close to just returning the NIC while I still can. Any ideas?
 
I have an Asrock Deskmini B760 with this Realtek chip. I did exactly what vghgvbh said and it worked great ! The NIC lights came on instantly afterwards.

In order to restore the network connectivity, I had to modify the vmbr0 bridge /etc/network/interfaces to add the NIC because its name had changed. After that, it was all good.

​

 
You must log in or register to reply here.
Top Bottom