Upgrade problem to 8.2 (6.8 kernel - r8168 )

K

kwenosaure

New Member
Apr 4, 2024
7
3
3
Hi evryone,


I'm having some trouble since yesterday to update Proxmox. Is there a way to solve that?

Code: 
apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
proxmox-kernel-6.5.13-3-pve-signed
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-kernel-6.8.4-2-pve-signed (6.8.4-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.4-2-pve /boot/vmlinuz-6.8.4-2-pve
dkms: running auto installation service for kernel 6.8.4-2-pve.
Sign command: /lib/modules/6.8.4-2-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub


Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.8.4-2-pve -C /lib/modules/6.8.4-2-pve/build M=/var/lib/dkms/r8168/8.052.01-1/build........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.4-2-pve (x86_64)
Consult /var/lib/dkms/r8168/8.052.01-1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.4-2-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.4-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.4-2-pve-signed (--configure):
installed proxmox-kernel-6.8.4-2-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
proxmox-kernel-6.8 depends on proxmox-kernel-6.8.4-2-pve-signed | proxmox-kernel-6.8.4-2-pve; however:
Package proxmox-kernel-6.8.4-2-pve-signed is not configured yet.
Package proxmox-kernel-6.8.4-2-pve is not installed.
Package proxmox-kernel-6.8.4-2-pve-signed which provides proxmox-kernel-6.8.4-2-pve is not configured yet.


dpkg: error processing package proxmox-kernel-6.8 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
proxmox-default-kernel depends on proxmox-kernel-6.8; however:
Package proxmox-kernel-6.8 is not configured yet.


dpkg: error processing package proxmox-default-kernel (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on proxmox-default-kernel; however:
Package proxmox-default-kernel is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
proxmox-kernel-6.8.4-2-pve-signed
proxmox-kernel-6.8
proxmox-default-kernel
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

and the var/lib/dkms/r8168/8.052.01-1/build/make.log content :

Code: 
DKMS make.log for r8168-8.052.01-1 for kernel 6.8.4-2-pve (x86_64)
Fri Apr 26 06:54:34 CEST 2024
make: Entering directory '/usr/src/linux-headers-6.8.4-2-pve'
  CC [M]  /var/lib/dkms/r8168/8.052.01-1/build/r8168_n.o
  CC [M]  /var/lib/dkms/r8168/8.052.01-1/build/r8168_asf.o
  CC [M]  /var/lib/dkms/r8168/8.052.01-1/build/rtl_eeprom.o
  CC [M]  /var/lib/dkms/r8168/8.052.01-1/build/rtltool.o
/var/lib/dkms/r8168/8.052.01-1/build/rtl_eeprom.c:96:5: warning: no previous prototype for ‘rtl8168_eeprom_cmd_done’ [-Wmissing-prototypes]
   96 | int rtl8168_eeprom_cmd_done(struct rtl8168_private *tp)
      |     ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:1624:6: warning: no previous prototype for ‘_proc_dump_tx_desc’ [-Wmissing-prototypes]
 1624 | void _proc_dump_tx_desc(struct seq_file *m, struct TxDesc *desc_base,
      |      ^~~~~~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:2949:5: warning: no previous prototype for ‘mdio_real_read’ [-Wmissing-prototypes]
 2949 | u32 mdio_real_read(struct rtl8168_private *tp,
      |     ^~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:5726:1: warning: no previous prototype for ‘rtl8168_set_rx_vlan_filter’ [-Wmissing-prototypes]
 5726 | rtl8168_set_rx_vlan_filter(struct rtl8168_private *tp)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c: In function ‘rtl8168_get_drvinfo’:
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:6296:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration]
 6296 |                 strlcpy(info->fw_version, rtl_fw->version,
      |                 ^~~~~~~
      |                 strscpy
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c: At top level:
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:28087:5: warning: no previous prototype for ‘rtl8168_enable_msix’ [-Wmissing-prototypes]
28087 | int rtl8168_enable_msix(struct rtl8168_private *tp)
      |     ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:243: /var/lib/dkms/r8168/8.052.01-1/build/r8168_n.o] Error 1
make[1]: *** [/usr/src/linux-headers-6.8.4-2-pve/Makefile:1926: /var/lib/dkms/r8168/8.052.01-1/build] Error 2
make: *** [Makefile:240: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.8.4-2-pve'

Have someone an idea?

Thanks in advance for your answer.

Kwenosaure
 
Last edited:
for this particular dkms-package we ship a version which contains a fix for it to work with the 6.8 kernel - try installing:
r8168-dkms from the proxmox repositories.

I hope this helps!
 
Thank you very much for your answer.

I try to install r8168-dkms , but I have always the same problem :-'( .

Here is the complete prompt

Code: 
apt install r8168-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
r8168-dkms is already the newest version (8.052.01-1-bpo12).
The following package was automatically installed and is no longer required:
proxmox-kernel-6.5.13-3-pve-signed
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up proxmox-kernel-6.8.4-2-pve-signed (6.8.4-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.4-2-pve /boot/vmlinuz-6.8.4-2-pve
dkms: running auto installation service for kernel 6.8.4-2-pve.
Sign command: /lib/modules/6.8.4-2-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub


Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.8.4-2-pve -C /lib/modules/6.8.4-2-pve/build M=/var/lib/dkms/r8168/8.052.01-1/build........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.4-2-pve (x86_64)
Consult /var/lib/dkms/r8168/8.052.01-1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.4-2-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.4-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.4-2-pve-signed (--configure):
installed proxmox-kernel-6.8.4-2-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
proxmox-kernel-6.8 depends on proxmox-kernel-6.8.4-2-pve-signed | proxmox-kernel-6.8.4-2-pve; however:
Package proxmox-kernel-6.8.4-2-pve-signed is not configured yet.
Package proxmox-kernel-6.8.4-2-pve is not installed.
Package proxmox-kernel-6.8.4-2-pve-signed which provides proxmox-kernel-6.8.4-2-pve is not configured yet.


dpkg: error processing package proxmox-kernel-6.8 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
proxmox-default-kernel depends on proxmox-kernel-6.8; however:
Package proxmox-kernel-6.8 is not configured yet.


dpkg: error processing package proxmox-default-kernel (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on proxmox-default-kernel; however:
Package proxmox-default-kernel is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
proxmox-kernel-6.8.4-2-pve-signed
proxmox-kernel-6.8
proxmox-default-kernel
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)


and the var/lib/dkms/r8168/8.052.01-1/build/make.log content :

Code: 
DKMS make.log for r8168-8.052.01-1 for kernel 6.8.4-2-pve (x86_64)
Fri Apr 26 01:19:53 PM CEST 2024
make: Entering directory '/usr/src/linux-headers-6.8.4-2-pve'
CC [M] /var/lib/dkms/r8168/8.052.01-1/build/r8168_n.o
CC [M] /var/lib/dkms/r8168/8.052.01-1/build/r8168_asf.o
CC [M] /var/lib/dkms/r8168/8.052.01-1/build/rtl_eeprom.o
CC [M] /var/lib/dkms/r8168/8.052.01-1/build/rtltool.o
/var/lib/dkms/r8168/8.052.01-1/build/rtl_eeprom.c:96:5: warning: no previous prototype for ‘rtl8168_eeprom_cmd_done’ [-Wmissing-prototypes]
96 | int rtl8168_eeprom_cmd_done(struct rtl8168_private *tp)
| ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:1624:6: warning: no previous prototype for ‘_proc_dump_tx_desc’ [-Wmissing-prototypes]
1624 | void _proc_dump_tx_desc(struct seq_file *m, struct TxDesc *desc_base,
| ^~~~~~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:2949:5: warning: no previous prototype for ‘mdio_real_read’ [-Wmissing-prototypes]
2949 | u32 mdio_real_read(struct rtl8168_private *tp,
| ^~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:5726:1: warning: no previous prototype for ‘rtl8168_set_rx_vlan_filter’ [-Wmissing-prototypes]
5726 | rtl8168_set_rx_vlan_filter(struct rtl8168_private *tp)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c: In function ‘rtl8168_get_drvinfo’:
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:6296:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration]
6296 | strlcpy(info->fw_version, rtl_fw->version,
| ^~~~~~~
| strscpy
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c: At top level:
/var/lib/dkms/r8168/8.052.01-1/build/r8168_n.c:28087:5: warning: no previous prototype for ‘rtl8168_enable_msix’ [-Wmissing-prototypes]
28087 | int rtl8168_enable_msix(struct rtl8168_private *tp)
| ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:243: /var/lib/dkms/r8168/8.052.01-1/build/r8168_n.o] Error 1
make[1]: *** [/usr/src/linux-headers-6.8.4-2-pve/Makefile:1926: /var/lib/dkms/r8168/8.052.01-1/build] Error 2
make: *** [Makefile:240: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.8.4-2-pve'

Can I restart my Proxmox server or is this a risk?

Thanks in advance for your answer.

Kwenosaure
 
try removing the current dkms package - wipe it ... install the new one.

kwenosaure said:
Can I restart my Proxmox server or is this a risk?
Click to expand...
I would only do this if you have access to the server physically - or if the r8168 module is not needed for access (meaning if you can reach the server on a NIC, which does not need the out of tree realtek driver...)
 
  • Like
Reactions: UnLock and kwenosaure
Just to be sure, i have to removing dkms package :
Code: 
apt remove r8168-dkms

Wipe it :
Code: 
apt purge r8168-dkms

Install the new one :
Code: 
apt install r8168-dkms

Is that right?

Thanks for your answer,

Kwenosaure
 
Last edited:
  • Like
Reactions: Kingneutron, Ramalama and kwenosaure
Thanks for your answer.

So I apt remove r8168-dkms, and try to install r8169-dkms but I have this message
Code: 
E: Unable to locate package r8169-dkms

The r8169 is installed by default normaly? Or shoud I do something?

Thanks in advance for your answer

Kwenosaure
 
kwenosaure said:
So I apt remove r8168-dkms, and try to install r8169-dkms but I have this message
Click to expand...
the r8169 driver is in-tree - this means it is part of the linux kernel and thus shipped with our kernel package.
no need for a dkms package

I hope this explains it!
 
You're welcome - glad it worked out so well!

Have a nice weekend as well!
 
I found this thread because I have the same issue - the 6.8 kernel upgrade didn't complete.

I had this same problem previously when Proxmox went to kernel 6.5. Luckily at the time a new Realtek r8168 driver (version 8.052.01) fixed that problem. This time though there isn't a new Realtek driver as far as I can tell - they're here

So I'm now at a bit of a loss. Unfortunately I know that my particular hardware does not work reliably with the in-tree r8169 driver - it runs for a few hours then has all sorts of issues and fails rendering the server (let's be clear it's not a server it's a mini PC) unreachable.

I appreciate that this isn't a Proxmox issue per se, but it does leave me now in a quandry. I guess I'll have to stay on 6.5 for that node.

Anyway, just thought I'd let others know if they're in the same situation. And also that using the in-tree r8169 driver on r8168 hardware isn't always a reliable fix.
 
The logs from the first post show, the kernel installation is trying to use drivers version 8.052.01 (which work with kernel max 6.5), Realtek has released new drivers version 8.053.00 which work with kernel 6.8: https://www.realtek.com/Download/List?cate_id=584
I had similar issue with my Wyse 5070, I managed to update the system as follows.
Downloaded new driver, copied the contents of the "src" directory to /usr/src/r8168-8.053.00/ and issued the following commands:
Code: 
echo PACKAGE_NAME="r8168" > /usr/src/r8168-8.053.00/dkms.conf
echo PACKAGE_VERSION="8.053.00" >> /usr/src/r8168-8.053.00/dkms.conf
echo BUILT_MODULE_NAME[0]="$PACKAGE_NAME" >> /usr/src/r8168-8.053.00/dkms.conf
echo DEST_MODULE_LOCATION[0]="/updates/dkms" >> /usr/src/r8168-8.053.00/dkms.conf
echo AUTOINSTALL="YES" >> /usr/src/r8168-8.053.00/dkms.conf
echo REMAKE_INITRD="YES" >> /usr/src/r8168-8.053.00/dkms.conf
Next:
Code: 
dkms add -m r8168 -v 8.053.00
In my case, dkms status returned 3 kernel versions working with the 8.052.01 driver, some of them were no longer used, but at this point I didn't want to complicate things and did the following for all kernels (xxx):
Code: 
dkms build -m r8168 -v 8.053.00 -k 6.5.13-xxx-pve
dkms install -m r8168 -v 8.053.00 -k 6.5.13-xxx-pve
and additionally:
Code: 
dkms build -m r8168 -v 8.053.00 -k 6.8.4-2-pve
dkms install -m r8168 -v 8.053.00 -k 6.8.4-2-pve
I removed the old version of the driver:
Code: 
dkms remove r8168/8.052.01 --all
after the above 'dkms status' showed only modules based on the new driver version, then I performed
Code: 
apt install pve-kernel-6.8.4-2-pve
Everything went without any error and after reboot the system works with the new kernel and the appropriate driver.


To be clear, I haven't tried the r8168-dkms reinstallation solution. I installed the current server with ISO 8.1 and from the very beginning I had a problem with the network card driver, only manual installation of the driver version 8.052.01 solved the problem (from what I remember, installing 'r8168-dkms' still caused the system to use the r8169 driver) .
 
  • Like
Reactions: pringlestuffs
I face the same issue. Since upgrading to 8.2, the r8168-dkms module does not work anymore.
After some research, I saw that a patch has been merged in the Linux Kernel upstream, which should fix the issue, at least for my specific network card: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=39f59c72ad3a

According to https://lore.kernel.org/all/8bacfc9f-7194-4376-acf7-38a935d735be@gmail.com/T/, this patch will be included starting from kernel 6.10. It will take quite some time until kernel 6.10 is released, let alone integrated into PVE. So, how can I already use this patch now? I guess the only way is to manually patch the kernel?
 
tziarko said:
The logs from the first post show, the kernel installation is trying to use drivers version 8.052.01 (which work with kernel max 6.5), Realtek has released new drivers version 8.053.00 which work with kernel 6.8: https://www.realtek.com/Download/List?cate_id=584
I had similar issue with my Wyse 5070, I managed to update the system as follows.
Downloaded new driver, copied the contents of the "src" directory to /usr/src/r8168-8.053.00/ and issued the following commands:
Code: 
echo PACKAGE_NAME="r8168" > /usr/src/r8168-8.053.00/dkms.conf
echo PACKAGE_VERSION="8.053.00" >> /usr/src/r8168-8.053.00/dkms.conf
echo BUILT_MODULE_NAME[0]="$PACKAGE_NAME" >> /usr/src/r8168-8.053.00/dkms.conf
echo DEST_MODULE_LOCATION[0]="/updates/dkms" >> /usr/src/r8168-8.053.00/dkms.conf
echo AUTOINSTALL="YES" >> /usr/src/r8168-8.053.00/dkms.conf
echo REMAKE_INITRD="YES" >> /usr/src/r8168-8.053.00/dkms.conf
Next:
Code: 
dkms add -m r8168 -v 8.053.00
In my case, dkms status returned 3 kernel versions working with the 8.052.01 driver, some of them were no longer used, but at this point I didn't want to complicate things and did the following for all kernels (xxx):
Code: 
dkms build -m r8168 -v 8.053.00 -k 6.5.13-xxx-pve
dkms install -m r8168 -v 8.053.00 -k 6.5.13-xxx-pve
Click to expand...

I got to this step and build failed:

Code: 
# dkms build -m r8168 -v 8.053.00 -k 6.5.13-5-pve
Sign command: /lib/modules/6.5.13-5-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/r8168/8.053.00/source/dkms.conf)

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.5.13-5-pve -C /lib/modules/6.5.13-5-pve/build M=/var/lib/dkms/r8168/8.053.00/build...
Error!  Build of r8168.ko failed for: 6.5.13-5-pve (x86_64)
Make sure the name of the generated module is correct and at the root of the
build directory, or consult make.log in the build directory
/var/lib/dkms/r8168/8.053.00/build for more information.

The log file contains only

Code: 
DKMS make.log for r8168-8.053.00 for kernel 6.5.13-5-pve (x86_64)
Sat May  4 02:21:08 PM EDT 2024
make: Entering directory '/usr/src/linux-headers-6.5.13-5-pve'
  MODPOST /var/lib/dkms/r8168/8.053.00/build/Module.symvers
make: Leaving directory '/usr/src/linux-headers-6.5.13-5-pve'
 
@pringlestuffs you should only copy the contents of the src directory of Realtek driver to: /usr/src/r8168-8.053.00

Bash: 
root@proxmox:/usr/src/r8168-8.053.00# ls -al /usr/src/r8168-8.053.00
total 1504
drwxr-xr-x  2 root root    4096 Jun  1 09:39 .
drwxr-xr-x 20 root root    4096 Jun  1 08:58 ..
-rw-r--r--  1 root root     179 Jun  1 09:07 dkms.conf
-rw-r--r--  1 root root    5897 Mar 13 15:41 Makefile
-rw-r--r--  1 root root    2400 Mar 13 15:41 Makefile_linux24x
-rw-r--r--  1 root root   16692 Mar 13 15:38 r8168_asf.c
-rw-r--r--  1 root root    9084 Mar 13 15:38 r8168_asf.h
-rw-r--r--  1 root root    7683 Mar 13 15:38 r8168_dash.h
-rw-r--r--  1 root root    2900 Mar 13 15:38 r8168_fiber.h
-rw-r--r--  1 root root    8747 Mar 13 15:38 r8168_firmware.c
-rw-r--r--  1 root root    2476 Mar 13 15:38 r8168_firmware.h
-rw-r--r--  1 root root   76946 Mar 13 15:38 r8168.h
-rw-r--r--  1 root root 1320252 Mar 13 15:38 r8168_n.c
-rw-r--r--  1 root root    3641 Mar 13 15:38 r8168_realwow.h
-rw-r--r--  1 root root   15165 Mar 13 15:38 r8168_rss.c
-rw-r--r--  1 root root    3067 Mar 13 15:38 r8168_rss.h
-rw-r--r--  1 root root    7965 Mar 13 15:38 rtl_eeprom.c
-rw-r--r--  1 root root    2322 Mar 13 15:38 rtl_eeprom.h
-rw-r--r--  1 root root    9096 Mar 13 15:38 rtltool.c
-rw-r--r--  1 root root    2471 Mar 13 15:38 rtltool.h
 
is this also because of r8168? I suppose it is not.


Code: 
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  proxmox-headers-6.8.4-3-pve
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-kernel-6.8.4-3-pve-signed (6.8.4-3) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.4-3-pve /boot/vmlinuz-6.8.4-3-pve
dkms: running auto installation service for kernel 6.8.4-3-pve.
Sign command: /lib/modules/6.8.4-3-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub


Building module:
Cleaning build area...
make -j24 KERNELRELEASE=6.8.4-3-pve KDIR=/lib/modules/6.8.4-3-pve/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.4-3-pve (x86_64)
Consult /var/lib/dkms/vendor-reset/0.1.1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.4-3-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.4-3-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.4-3-pve-signed (--configure):
 installed proxmox-kernel-6.8.4-3-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.8.8-1-pve-signed (6.8.8-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.8-1-pve /boot/vmlinuz-6.8.8-1-pve
dkms: running auto installation service for kernel 6.8.8-1-pve.
Sign command: /lib/modules/6.8.8-1-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub


Building module:
Cleaning build area...
make -j24 KERNELRELEASE=6.8.8-1-pve KDIR=/lib/modules/6.8.8-1-pve/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.8-1-pve (x86_64)
Consult /var/lib/dkms/vendor-reset/0.1.1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.8-1-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.8-1-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.8-1-pve-signed (--configure):
 installed proxmox-kernel-6.8.8-1-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
 proxmox-kernel-6.8 depends on proxmox-kernel-6.8.8-1-pve-signed | proxmox-kernel-6.8.8-1-pve; however:
  Package proxmox-kernel-6.8.8-1-pve-signed is not configured yet.
  Package proxmox-kernel-6.8.8-1-pve is not installed.
  Package proxmox-kernel-6.8.8-1-pve-signed which provides proxmox-kernel-6.8.8-1-pve is not configured yet.


dpkg: error processing package proxmox-kernel-6.8 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.8; however:
  Package proxmox-kernel-6.8 is not configured yet.


dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.8.4-3-pve-signed
 proxmox-kernel-6.8.8-1-pve-signed
 proxmox-kernel-6.8
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: 
DKMS make.log for vendor-reset-0.1.1 for kernel 6.8.8-1-pve (x86_64)
Mon Jun 24 01:27:22 AM MSK 2024
make -C /lib/modules/6.8.8-1-pve/build M=/var/lib/dkms/vendor-reset/0.1.1/build modules
make[1]: Entering directory '/usr/src/linux-headers-6.8.8-1-pve'
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/module.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/vendor-reset-dev.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/ioctl.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/ftrace.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/hook.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/common.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/compat.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/firmware.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/navi10.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/polaris10.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/vega10.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/vega20.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_device.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_discovery.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_bios.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_atomfirmware.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/common_baco.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/navi10_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/navi12_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/navi14_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/polaris_baco.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/smu7_baco.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega10_reg_init.o
  CC [M]  /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega20_reg_init.o
/var/lib/dkms/vendor-reset/0.1.1/build/src/ioctl.c:91:5: warning: no previous prototype for ‘vendor_reset_ioctl_init’ [-Wmissing-prototypes]
   91 | int vendor_reset_ioctl_init(void)
      |     ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/ioctl.c:96:6: warning: no previous prototype for ‘vendor_reset_ioctl_exit’ [-Wmissing-prototypes]
   96 | void vendor_reset_ioctl_exit(void)
      |      ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/ftrace.c:66:5: warning: no previous prototype for ‘fh_install_hook’ [-Wmissing-prototypes]
   66 | int fh_install_hook(struct ftrace_hook *hook)
      |     ^~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/ftrace.c:96:6: warning: no previous prototype for ‘fh_remove_hook’ [-Wmissing-prototypes]
   96 | void fh_remove_hook(struct ftrace_hook *hook)
      |      ^~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/firmware.c:40:5: warning: no previous prototype for ‘amdgpu_io_rreg’ [-Wmissing-prototypes]
   40 | u32 amdgpu_io_rreg(struct amd_fake_dev *adev, u32 reg)
      |     ^~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/firmware.c:60:6: warning: no previous prototype for ‘amdgpu_io_wreg’ [-Wmissing-prototypes]
   60 | void amdgpu_io_wreg(struct amd_fake_dev *adev, u32 reg, u32 v)
      |      ^~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_device.c:47:6: warning: no previous prototype for ‘amdgpu_device_vram_access’ [-Wmissing-prototypes]
   47 | void amdgpu_device_vram_access(struct amd_fake_dev *adev, loff_t pos,
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.c: In function ‘amdgpu_atom_parse’:
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.c:1427:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration]
 1427 |                 strlcpy(ctx->vbios_version, str, sizeof(ctx->vbios_version));
      |                 ^~~~~~~
      |                 strscpy
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega10_reg_init.c:29:5: warning: no previous prototype for ‘vega10_reg_base_init’ [-Wmissing-prototypes]
   29 | int vega10_reg_base_init(struct amd_fake_dev *adev)
      |     ^~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_bios.c:91:6: warning: no previous prototype for ‘amdgpu_read_bios’ [-Wmissing-prototypes]
   91 | bool amdgpu_read_bios(struct amd_fake_dev *adev)
      |      ^~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/amdgpu_bios.c:156:6: warning: no previous prototype for ‘amdgpu_get_bios’ [-Wmissing-prototypes]
  156 | bool amdgpu_get_bios(struct amd_fake_dev *adev)
      |      ^~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/vega20_reg_init.c:29:5: warning: no previous prototype for ‘vega20_reg_base_init’ [-Wmissing-prototypes]
   29 | int vega20_reg_base_init(struct amd_fake_dev *adev)
      |     ^~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vendor-reset/0.1.1/build/src/amd/vega10.c:96:5: warning: no previous prototype for ‘vega10_baco_set_state’ [-Wmissing-prototypes]
   96 | int vega10_baco_set_state(struct amd_fake_dev *adev, enum BACO_STATE state)
      |     ^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:243: /var/lib/dkms/vendor-reset/0.1.1/build/src/amd/amdgpu/atom.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.8.8-1-pve/Makefile:1926: /var/lib/dkms/vendor-reset/0.1.1/build] Error 2
make[1]: *** [Makefile:240: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.8.8-1-pve'
make: *** [Makefile:8: build] Error 2
 
tziarko said:
The logs from the first post show, the kernel installation is trying to use drivers version 8.052.01 (which work with kernel max 6.5), Realtek has released new drivers version 8.053.00 which work with kernel 6.8: https://www.realtek.com/Download/List?cate_id=584
I had similar issue with my Wyse 5070, I managed to update the system as follows.
Downloaded new driver, copied the contents of the "src" directory to /usr/src/r8168-8.053.00/ and issued the following commands:
Code: 
echo PACKAGE_NAME="r8168" > /usr/src/r8168-8.053.00/dkms.conf
echo PACKAGE_VERSION="8.053.00" >> /usr/src/r8168-8.053.00/dkms.conf
echo BUILT_MODULE_NAME[0]="$PACKAGE_NAME" >> /usr/src/r8168-8.053.00/dkms.conf
echo DEST_MODULE_LOCATION[0]="/updates/dkms" >> /usr/src/r8168-8.053.00/dkms.conf
echo AUTOINSTALL="YES" >> /usr/src/r8168-8.053.00/dkms.conf
echo REMAKE_INITRD="YES" >> /usr/src/r8168-8.053.00/dkms.conf
Next:
Code: 
dkms add -m r8168 -v 8.053.00
In my case, dkms status returned 3 kernel versions working with the 8.052.01 driver, some of them were no longer used, but at this point I didn't want to complicate things and did the following for all kernels (xxx):
Code: 
dkms build -m r8168 -v 8.053.00 -k 6.5.13-xxx-pve
dkms install -m r8168 -v 8.053.00 -k 6.5.13-xxx-pve
and additionally:
Code: 
dkms build -m r8168 -v 8.053.00 -k 6.8.4-2-pve
dkms install -m r8168 -v 8.053.00 -k 6.8.4-2-pve
I removed the old version of the driver:
Code: 
dkms remove r8168/8.052.01 --all
after the above 'dkms status' showed only modules based on the new driver version, then I performed
Code: 
apt install pve-kernel-6.8.4-2-pve
Everything went without any error and after reboot the system works with the new kernel and the appropriate driver.


To be clear, I haven't tried the r8168-dkms reinstallation solution. I installed the current server with ISO 8.1 and from the very beginning I had a problem with the network card driver, only manual installation of the driver version 8.052.01 solved the problem (from what I remember, installing 'r8168-dkms' still caused the system to use the r8169 driver) .
Click to expand...
Sorry for the newbie question, how do you copy the files from src to the /usr/src/r8168-8.053.00/? USB? I did a new install and my ethernet card doesn't even show up. I need some manual way to fix this.
 
kwenosaure said:
Thanks a lot for your answer, all the explanation and your time!

I remove it, reboot and it works like a charm!

Thanks a lot, you save my day :-D .

Have a nice week-end!
Click to expand...
HI, What commands did you use to remove and add the r8169? Can you please share your method. Thank s in advance. I only have access to the command line connected via hdmi to a screen.
 
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