System hanging after upgrade...NIC driver?

Thank you for this thread, this seems to have fixed my issue on my OptiPlex 3080

I'm a complete n00b to this and have no idea what I've actually done, do I need to amend any of this in the future, presuming there will be a release that fixes this in the future?
 
Chris said:
If you remove the repo component again, than you will not get updates for the dkms package if available. No harm in keeping it.
Click to expand...
The above was posted in response to the question: "I followed your small guide and ask myself if i should go back to original sources.list, afterwards?"

Does this mean to keep the file as modified or restore it to the pre-modified state?
 
Thank you from another Wyse 5070 owner who has only started his proxmox journey this week. I was sure my problem were related to my Frigate+coral configuration woes today, only to spot the network loop issue when I connected a screen, leading me to this thread. Issue now resolved. Thank you
 
  • Like
Reactions: andlil
Kernel starting from 6.2.16-16-pve includes the fix for the r8169 hangup from the Ubuntu-6.2.0-36.36 kernel (commit f73a8359f2746). The kernel is available in the pvetest repository. I'm currently running 6.2.16-18-pve for 30+ hours with no issues.
 
  • Like
Reactions: majes, PaperLawyer and andlil
MT5 said:
This is how I resolved the network driver issue after upgrading from Proxmox 7 to 8 on a Dell Optiplex 3090. Rolling back to r8168-dkms as others suggested didn't work for me.

Code: 
nano /etc/apt/sources.list

2. Add line
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

Code: 
apt update

apt install pve-kernel-5.15.108-1-pve

proxmox-boot-tool kernel pin 5.15.108-1-pve

reboot

Finally, remove line from step 2 as you don't need it for Proxmox 8.
Click to expand...
This was very helpful, thank you.

Noting that the latest kernel within the pve-test repository resolves the issue (https://forum.proxmox.com/threads/system-hanging-after-upgrade-nic-driver.129366/post-596604), to unpin kernel 5.15.108-1-pve, replace with the latest kernel within the test repository and take advantage of future kernel upgrades, are these steps correct?

1. Edit sources.list to add the test repository: deb http://download.proxmox.com/debian/pve bookworm pvetest

2. apt update

3. apt install proxmox-kernel-6.2.16-18-pve [EDIT: Correction by proxywyse]

4. apt install proxmox-headers-6.2.16-18-pve [EDIT: Correction by proxywyse]

5. proxmox-boot-tool kernel unpin (https://forum.proxmox.com/threads/how-to-pin-unpin-a-specific-kernel.111732/post-481893)

6. reboot

7. Remove the test repository added in step 1.

Does the above make sense?
 
Last edited:
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...
This might be a stupid question but do I have to uninstall old driver after this?

Code: 
root@pve01:~# lsmod | grep 816
r8169                 114688  0
r8168                 655360  0

I see faulty one and the good one together.
 
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...

Thanks for this. Hopefully, I don't get the issue again.
Just wondering, if there is any harm in keeping the repo still there and has a bugfix been introduced yet?
 
Last edited:
proxywyse said:
Kernel starting from 6.2.16-16-pve includes the fix for the r8169 hangup from the Ubuntu-6.2.0-36.36 kernel (commit f73a8359f2746). The kernel is available in the pvetest repository. I'm currently running 6.2.16-18-pve for 30+ hours with no issues.
Click to expand...
Do you happen to know how long it takes until a kernel from pvetest is published on the regular pve repositories (e.g. pve-no-subscription)?
 
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...
Hello,
Tried this solution, after reboot the web client is no longer online.
Is there any way to fix this locally without internet?
 
cubo said:
Hello,
Tried this solution, after reboot the web client is no longer online.
Is there any way to fix this locally without internet?
Click to expand...
I've had the same thing happen to me, what can I do?
Have you come up with any solution?
 
majes said:
Do you happen to know how long it takes until a kernel from pvetest is published on the regular pve repositories (e.g. pve-no-subscription)?
Click to expand...
Just upgraded a test-server with standard no-subscription repo enabled to Kernel 6.2.16-19 . Let's see if it's stable.
 
Hi all

I'm having same issue on a Beelink U59 and Proxmox 7.4-17

This is the log
Code: 
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).

This is my network card

Code: 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 15


This is my Proxmox version

Code: 
root@pve:/etc# pveversion
pve-manager/7.4-17/513c62be (running kernel: 6.2.16-11-bpo11-pve)


My /etc/apt/sources.list is like this now


Code: 
deb http://ftp.debian.org/debian bullseye main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bullseye-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bullseye-security main contrib non-free non-free-firmware
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

#deb http://ftp.debian.org/debian bullseye main contrib
#deb http://ftp.debian.org/debian bullseye-updates main contrib
#deb http://security.debian.org/debian-security bullseye-security main contrib

but I get these warnings

Code: 
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://security.debian.org/debian-security bullseye-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://security.debian.org/debian-security bullseye-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_US' as repository 'http://security.debian.org/debian-security bullseye-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://ftp.debian.org/debian bullseye InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_US' as repository 'http://ftp.debian.org/debian bullseye InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://ftp.debian.org/debian bullseye InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://ftp.debian.org/debian bullseye-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_US' as repository 'http://ftp.debian.org/debian bullseye-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://ftp.debian.org/debian bullseye-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)


I sees that previous messages uses bookworm instead of bullseye, which one should I use, since I am on Proxmox 7.4 ?


Then, doing an apt list, searching for r8168, I see this:

Code: 
r8168-dkms/oldstable 8.048.03-3 all

and nothing searching for r8169


Should I do then this to update realtek drivers?

Code: 
apt update

#Install the headers:
apt install pve-headers

#Install the r8168-dkms driver
apt install r8168-dkms


Thanks
 
Last edited:
Vittorio said:
Hi all

I'm having same issue on a Beelink U59 and Proxmox 7.4-17

This is the log
Code: 
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).

This is my network card

Code: 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 15


This is my Proxmox version

Code: 
root@pve:/etc# pveversion
pve-manager/7.4-17/513c62be (running kernel: 6.2.16-11-bpo11-pve)


My /etc/apt/sources.list is like this now


Code: 
deb http://ftp.debian.org/debian bullseye main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bullseye-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bullseye-security main contrib non-free non-free-firmware
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

#deb http://ftp.debian.org/debian bullseye main contrib
#deb http://ftp.debian.org/debian bullseye-updates main contrib
#deb http://security.debian.org/debian-security bullseye-security main contrib

but I get these warnings

Code: 
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://security.debian.org/debian-security bullseye-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://security.debian.org/debian-security bullseye-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_US' as repository 'http://security.debian.org/debian-security bullseye-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://ftp.debian.org/debian bullseye InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_US' as repository 'http://ftp.debian.org/debian bullseye InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://ftp.debian.org/debian bullseye InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://ftp.debian.org/debian bullseye-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_US' as repository 'http://ftp.debian.org/debian bullseye-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://ftp.debian.org/debian bullseye-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)


I sees that previous messages uses bookworm instead of bullseye, which one should I use, since I am on Proxmox 7.4 ?


Then, doing an apt list, searching for r8168, I see this:

Code: 
r8168-dkms/oldstable 8.048.03-3 all

and nothing searching for r8169


Should I do then this to update realtek drivers?

Code: 
apt update

#Install the headers:
apt install pve-headers

#Install the r8168-dkms driver
apt install r8168-dkms


Thanks
Click to expand...

Regarding the update, i suggest you follow this guide:
https://gist.github.com/SQLJames/fe6fcd5e819d864986ce2eff6ad350da
 
Last edited:
  • Like
Reactions: Vittorio
robocon said:
Hello everyone, does it have a new kernel version that fixes this nic issue yet?
Click to expand...
It is possible to keep your sistem updated without updating the ethernet drivers. Somewhere in this thread is a tutorial on how to exclude the drivers from being updated.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom