Not connecting to network- r8169 [\_SB.UBTC.RUCC], AE_NOT_FOUND

[hallalec]

My new install of Proxmox-ve loses the network connection immediately or within 5 minutes of first install. After this time I have no web interface access (port 8006) and the device can no longer be ping-ed on the lan or ping others.

I have tried quite a few solutions on this forum but can't find a solution that works for me. I have read and checked the documentation https://pve.proxmox.com/pve-docs/pve-admin-guide.htm but happy if someone can find something I missed.

I am installing Proxmox VE 8.0 ISO Installer on usb from proxmox.com. I have checked hardware, cables and lan network, and the PVE network settings.

I think the real error is in the beginning of the install process. Hopefully there is enough information in the samples of output below to pinpoint the problem, but happy to provide the original photos of the screens if needed.

Starting the install from the very first graphic screen with prompt how to install Proxmo VE, then:

loading Proxmox VE Installer ...
Loading initial ramdisk ...

Screens clears, below is a sample of the errors that come up in the couple of screens length of output:

2C2.-_INI1, AE_ALREADY EXISTS (20221020,dswload2-326)
[ 0.212395] ACPI Error: AE_ALREADY EXISTS, During name lookup catalog (202210
20/psobject-220)
[ 0.382225] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCCI,
AE_NOT_FOUND (20221020/psargs-330)
[ 0.382242] ACPI Error: Aborting method \_SB.PCOO.XHCI.RHUB.HS04._ PLD due to
previous error (AE_NOT_FOUND) (20221020/psparse-529)

... and later on:

[ 2.601541] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT.
[2.601583] ACPI Error: Aborting method \_SB.PCO®.XHCI.RHUB.HS@4. PLD due to previous e
2.6016481 ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND

Screen reduces the text size and then boots into the welcome message and login comand prompt.
Also get erros here I think at around the time of losing the network connection:

Pve login: [
67.944602] r8169 0000:02:00.0 enp2s: rt1_chipemd_cond == 1 (loop: 100, delay: 100)
67.947311] r8169 0000:02:00.0 enp2s: rt1_ephyar_cond == 1 (loop: 100, delay: 10)
67.949982] r8169 0000:02:00.0 enp2s: rt1_ephyar_cond == 1 (loop: 100, delay: 10).
67.952678] r8169 0000:02:00.0 enp2s: rt1_ephyar_cond == 1 (loop: 100, delay: 10).
67.955368] r8169 0000:02:00.0 enp2s: rtl_ephyar_cond== 1 (loop: 100, delay: 10).
67.958037] r8169 0000:02:00.0 enp2s: rt1_ephyar_cond == 1 (loop: 100, delay: 10).
67.960743] r8169 0000:02:00.0 enp2s: rtl_ephyar_cond==1 (loop: 100, delay: 10).
67.986414) r8169 0000:02:00.0 enp2so: rtlerlar_cond== 1 (loop: 100, delay: 100).
68.012264] r8169 0000:02:00.0 enp2s: rt1_eriar_cond == 1 (loop: 100, delay: 100).
68.038102] r8169 0000:02:00.0 enp2so: rtl_eriar_cond == 1 (loop: 100, delay: 100)

Running dmesg comes up with again the aload of the [\_SB.UBTC.RUCC], AE_NOT_FOUND errors, and at the beinging a few [mem 0xfed20000-0xfed7ffff] could not be reserved lines.

dmesg -h -e
Oct 14 14:16:23 pve kernel: system 00:04: [mem 0xfed20000-0xfed7ffff] could not be reserved
Oct 14 14:16:23 pve kernel: system 00:04: [mem 0xfed90000-0xfed93fff] could not be reserved
Oct 14 14:16:23 pve kernel: system 00:04: [mem 0xfed45000-0xfed8ffff] could not be reserved
Oct 14 14:16:23 pve kernel: system 00:04: [mem 0xfee00000-0xfeefffff] could not be reserved

Oct 14 14:16:23 pve kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20221020/psargs-330)
Oct 14 14:16:23 pve kernel:
Oct 14 14:16:23 pve kernel: No Local Variables are initialized for Method [_PLD]
Oct 14 14:16:23 pve kernel:
Oct 14 14:16:23 pve kernel: No Arguments are initialized for method [_PLD]
Oct 14 14:16:23 pve kernel:
Oct 14 14:16:23 pve kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20221020/psparse-529)
Oct 14 14:16:23 pve kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20221020/psargs-330)

ip address:

root@pve:~# ip address
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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 38:f7:cd:c5:2a:09 brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 14:f5:f9:14:cb:34 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 38:f7:cd:c5:2a:09 brd ff:ff:ff:ff:ff:ff
inet 192.168.33.10/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::3af7:cdff:fec5:2a09/64 scope link
valid_lft forever preferred_lft forever

tried a few things with the etc/network/interfaces, including being vlan aware.
/etc/network/interfaces:

auto lo
iface lo inet loopback
iface enp2s0 inet manual
auto vmbr0
iface vmbr0 inet static
    address 192.168.33.10/24
     gateway 192.168.33.1
     bridge-ports enp2s0
     bridge-stp off
     bridge-fd 0
iface wlp1s0 inet manual

Hope this is enough to information. Many thanks.

 

[leesteken]

There have been many reports of problems with r8169 and PVE 8 (kernel 6.2). I did not read them to find out if there has been a common work-around yet, since I don't have an r8169.

 

[hallalec]

Leesteken Thank you. I have had a look at few but didn't find one that worked for me or they don't clearly say what the solution was or how, in easy steps, to aply the solution. And without knowing if my issue is the same as the others don't known how best to move forward.