[Proxmox VE 8.0 upgrade] Error while building linux-headers-6.1.0-10-amd64

G

GarcaMan

New Member
Jul 15, 2023
3
0
1
Hello everyone,

Having some issues trying to upgrade from 7.4 to 8. Ran the full pve7to8 --full with no problems. However:
Running apt dist-upgrade, I get this error:

Code: 
Setting up linux-headers-6.1.0-10-amd64 (6.1.37-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-10-amd64.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/aufs/4.19+20190211/6.1.0-10-amd64/x86_64/dkms.conf for module aufs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-10-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-10-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.1.0-10-amd64 (--configure):
 installed linux-headers-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
 linux-headers-amd64 depends on linux-headers-6.1.0-10-amd64 (= 6.1.37-1); however:
  Package linux-headers-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up pve-kernel-6.2.16-4-pve (6.2.16-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.2.16-4-pve /boot/vmlinuz-6.2.16-4-pve
dkms: running auto installation service for kernel 6.2.16-4-pve.
Sign command: /lib/modules/6.2.16-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/aufs/4.19+20190211/6.2.16-4-pve/x86_64/dkms.conf for module aufs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Sign command: /lib/modules/6.2.16-4-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' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.16-4-pve modules...........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.16-4-pve (x86_64)
Consult /var/lib/dkms/nvidia/525.60.11/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.2.16-4-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/pve-kernel-6.2.16-4-pve.postinst line 20.
dpkg: error processing package pve-kernel-6.2.16-4-pve (--configure):
 installed pve-kernel-6.2.16-4-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of pve-kernel-6.2:
 pve-kernel-6.2 depends on pve-kernel-6.2.16-4-pve; however:
  Package pve-kernel-6.2.16-4-pve is not configured yet.

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

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-6.1.0-10-amd64
 linux-headers-amd64
 pve-kernel-6.2.16-4-pve
 pve-kernel-6.2
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

This may be related to my nvidia drivers but I'm not 100% on that. I have a ThinkStation Nvidia P400 HP that I passthrough to my Plex LXC; followed this guide: https://gist.github.com/egg82/90164a31db6b71d36fa4f4056bbee2eb

This is my dkms status:
Code: 
dkms status
aufs/4.19+20190211, 4.19.0-10-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-11-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-12-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-13-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-14-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-16-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-17-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-6-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-8-amd64, x86_64: installed
aufs/4.19+20190211, 4.19.0-9-amd64, x86_64: installed
nvidia/525.60.11, 5.10.0-20-amd64, x86_64: installed
nvidia/525.60.11, 5.10.0-21-amd64, x86_64: installed
nvidia/525.60.11, 5.10.0-22-amd64, x86_64: installed
nvidia/525.60.11, 5.10.0-23-amd64, x86_64: installed
nvidia/525.60.11, 5.15.107-2-pve, x86_64: installed
nvidia/525.60.11, 5.15.108-1-pve, x86_64: installed
nvidia/525.60.11, 6.1.0-10-amd64, x86_64: installed

Thank you for the answer.
 
Just ran into the exact same error!

Code: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  dctrl-tools dkms g++-10 libcuda1 libegl-mesa0 libegl-nvidia0 libegl1 libfontenc1 libgl1-nvidia-glvnd-glx libgles-nvidia1 libgles-nvidia2
  libgles1 libgles2 libice6 libllvm11 libntfs-3g883 libnvcuvid1 libnvidia-cfg1 libnvidia-egl-wayland1 libnvidia-encode1 libnvidia-ml1
  libnvidia-ptxjitcompiler1 libopengl0 libsm6 libstdc++-10-dev libtiff5 libvdpau1 libwebp6 libxaw7 libxcvt0 libxdamage1 libxfont2
  libxkbfile1 libxmu6 libxrandr2 libxt6 nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd nvidia-kernel-common
  nvidia-kernel-dkms nvidia-kernel-support nvidia-modprobe nvidia-persistenced nvidia-smi nvidia-support nvidia-vdpau-driver
  pve-headers-5.13 pve-headers-5.13.19-6-pve pve-headers-5.15 pve-headers-5.15.108-1-pve ruby2.7 ruby2.7-dev ruby2.7-doc sudo telnet
  x11-common x11-xkb-utils xcvt xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 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 pve-kernel-6.2.16-4-pve (6.2.16-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.2.16-4-pve /boot/vmlinuz-6.2.16-4-pve
dkms: running auto installation service for kernel 6.2.16-4-pve.
Sign command: /lib/modules/6.2.16-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
applying patch kernel-5.7.0-set-memory-array.patch...patching file conftest.sh

applying patch linux-2.6.34-dev_pm_info-runtime_auto.patch...patching file conftest.sh

applying patch bashisms.patch...patching file conftest.sh

applying patch use-kbuild-compiler.patch...patching file Makefile

applying patch use-kbuild-flags.patch...patching file Kbuild
patching file nvidia/nvidia.Kbuild
patching file Makefile
patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch use-kbuild-gcc-plugins.patch...patching file Kbuild

applying patch conftest-verbose.patch...patching file Kbuild

applying patch cc_version_check-gcc5.patch...patching file conftest.sh

applying patch nvidia-use-ARCH.o_binary.patch...patching file nvidia/nvidia.Kbuild

applying patch nvidia-modeset-use-ARCH.o_binary.patch...patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch conftest-prefer-arch-headers.patch...patching file conftest.sh


Building module:
Cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j32 modules KERNEL_UNAME=6.2.16-4-pve....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.16-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-current/470.103.01/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.2.16-4-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/pve-kernel-6.2.16-4-pve.postinst line 20.
dpkg: error processing package pve-kernel-6.2.16-4-pve (--configure):
 installed pve-kernel-6.2.16-4-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of pve-kernel-6.2:
 pve-kernel-6.2 depends on pve-kernel-6.2.16-4-pve; however:
  Package pve-kernel-6.2.16-4-pve is not configured yet.

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

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-kernel-6.2.16-4-pve
 pve-kernel-6.2
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Would really appreciate the help!
 
Possible solution:
I did apt autoremove and then did apt update and apt upgrade followed by a reboot and that seems to have worked?

pveversion shows

Code: 
pve-manager/8.0.3/bbf3993334bfa916 (running kernel: 6.2.16-4-pve)

again, not sure why that worked but will update if there are any issues
 
I have the same error.
I have a problem with mi realtek nic and i have to install r8168
Code: 
sudo apt install r8168-dkms
. I tried to upgrade dist (if availlable) i'm running Proxmox 8.03 with the latest kernel :
root@esx1:~#
Code: 
pveversion
pve-manager/8.0.3/bbf3993334bfa916 (running kernel: 6.2.16-4-pve)

This is the output of dist update:

root@esx1:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 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 linux-headers-6.1.0-10-amd64 (6.1.37-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-10-amd64.
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/realtek-r8125/9.003.05/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
Sign command: /usr/lib/linux-kbuild-6.1/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/realtek-r8125/9.003.05/source/dkms.conf)

Building module:
Cleaning build area...(bad exit status: 2)
'make' -j12 KVER=6.1.0-10-amd64 BSRC=/lib/modules/6.1.0-10-amd64 all...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-10-amd64 (x86_64)
Consult /var/lib/dkms/realtek-r8125/9.003.05/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.1.0-10-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-10-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.1.0-10-amd64 (--configure):
installed linux-headers-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
linux-headers-amd64 depends on linux-headers-6.1.0-10-amd64 (= 6.1.37-1); however:
Package linux-headers-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-headers-6.1.0-10-amd64
linux-headers-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


I really don't know what to do, i really would like to reinstall proxmox (7.4 and not 8.0.3 that gives me so much problem with realtek card on latest kernel.
 
May i ask why you use linux-headers 6.1 instead of pve-headers-6.2.16-4-pve ?
Or better said "pve-headers" meta package?

I would remove linux-headers at all, since they don't match your 6.2.16 kernel anyway.
 
Ramalama said:
May i ask why you use linux-headers 6.1 instead of pve-headers-6.2.16-4-pve ?
Or better said "pve-headers" meta package?

I would remove linux-headers at all, since they don't match your 6.2.16 kernel anyway.
Click to expand...
You are right by uninstalling both packages and using only pve headers I was able to install r8168. Now I am only left with the problem of not being able to set the drivers as main instead of r8169.
 
Hi @GarcaMan you need to run these commands:
#Remove Linux Header (you don't need them because you are gonna use pve-heaadders):
Code: 
sudo apt purge linux-headers-* linux-headers-*
If the * won't work just tab and check the correct version to purge.
#Install pve-headers
Code: 
apt install pve-headers

After that you should be able to upgrade dist :)
 
leonardo_benetti said:
You are right by uninstalling both packages and using only pve headers I was able to install r8168. Now I am only left with the problem of not being able to set the drivers as main instead of r8169.
Click to expand...

Just for the sake of completeness:
i use "23:00.1" just as example bus-id, you have to change it to your own!

1. lspci -k | grep Ethernet -A 3
- "Kernel driver in use" will show you what driver its currently using

2. echo "0000:23:00.1" > "/sys/bus/pci/devices/0000:23:00.1/driver/unbind"
- That will unbind the current driver from your adapter.
- But i wouldn't do it over ssh, if youre on that connection connected xD

3. echo "10ec 8168" > "/sys/bus/pci/drivers/r8168/new_id"
- That will bind the new driver to your interface.
- But check before what directory exists, means which driver, as i have no clue of the r8168 driver and don't have any realtek related hardware. Means if /sys/bus/pci/drivers/r8168 exists, or if its /sys/bus/pci/drivers/r8168-dkms ....

4. If thats what you wanted, there are 2 ways to do it on boot:
- 1: Blacklist your default r8169 driver:
- echo "blacklist r8169" > /etc/modprobe.d/nic-blacklist.conf
- update-initramfs -u -k all
- proxmox-boot-tool refresh or update-grub (depends what you use)
- reboot your pve host and the new driver should be assigned automatically.

-2: make a script: /usr/bin/nic-blacklist.sh
Code: 
#!/usr/bin/sh

/usr/bin/echo "0000:23:00.1" > "/sys/bus/pci/devices/0000:23:00.1/driver/unbind"
sleep 0.1
/usr/bin/echo "10ec 8168" > "/sys/bus/pci/drivers/r8168/new_id"
- make a Service: /etc/systemd/system/nic-Blacklist.service
Code: 
[Unit]
Description=Script to Blacklist one Realtek Port on boot
Before=network-pre.target
After=sysinit.target local-fs.target

[Service]
Type=oneshot
ExecStart=/usr/bin/nic-blacklist.sh

[Install]
WantedBy=multi-user.target
- systemctl daemon-reload
- systemctl enable nic-Blacklist.service
Reboot your System...

Only use the one or the other, not both together!
Change your Pci device bus, i made just an example, check how your new driver is called, just to be sure... As i don't own any realtek devices.
- The blacklist approach is actually the proper way, so the driver doesn't get loaded already at the boot stage.
- The Service approach unbinds and rebinds your device to another driver at an very early booting stage, but has the benefit of beeing able to use differenct drivers for different ports/devices. Basically its only usefull if you need to bind the vfio-pci driver to only one Nic Port, if you want to passthrough only one Nic Port to an VM, while using the other Nic Port for Proxmox itself.

EDIT: i would suggest that you just blacklist the one you don't want, means r8169 in your case? And thats it.
Cheers
 
Last edited:
Okay, after removing linux-headers packages, I got way less errors while upgrading:

Code: 
Setting up pve-kernel-6.2.16-4-pve (6.2.16-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.2.16-4-pve /boot/vmlinuz-6.2.16-4-pve
dkms: running auto installation service for kernel 6.2.16-4-pve.
Sign command: /lib/modules/6.2.16-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/aufs/4.19+20190211/6.2.16-4-pve/x86_64/dkms.conf for module aufs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Sign command: /lib/modules/6.2.16-4-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' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.16-4-pve modules...........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.16-4-pve (x86_64)
Consult /var/lib/dkms/nvidia/525.60.11/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.2.16-4-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/pve-kernel-6.2.16-4-pve.postinst line 20.
dpkg: error processing package pve-kernel-6.2.16-4-pve (--configure):
 installed pve-kernel-6.2.16-4-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of pve-kernel-6.2:
 pve-kernel-6.2 depends on pve-kernel-6.2.16-4-pve; however:
  Package pve-kernel-6.2.16-4-pve is not configured yet.

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

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-kernel-6.2.16-4-pve
 pve-kernel-6.2
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Here is part of make,log:
Code: 
[...]
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_init_mode_config’:
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-drv.c:262:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’
  262 |     dev->mode_config.fb_base = 0;
      |                     ^
make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-drv.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-crtc.c: In function ‘__nv_drm_plane_atomic_destroy_state’:
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-crtc.c:678:5: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
  678 |     struct nv_drm_plane_state *nv_drm_plane_state =
      |     ^~~~~~
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-connector.c: In function ‘__nv_drm_detect_encoder’:
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-connector.c:101:18: error: ‘struct drm_connector’ has no member named ‘override_edid’
  101 |     if (connector->override_edid) {
      |                  ^~
make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-connector.o] Error 1
make[1]: *** [Makefile:2026: /var/lib/dkms/nvidia/525.60.11/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.2.16-4-pve'
make: *** [Makefile:82: modules] Error 2
Seems that the nvidia drivers are the culprits now. Any idea how to fix this?
 
Last edited:
GarcaMan said:
Okay, after removing linux-headers packages, I got way less errors while upgrading:

Code: 
Setting up pve-kernel-6.2.16-4-pve (6.2.16-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.2.16-4-pve /boot/vmlinuz-6.2.16-4-pve
dkms: running auto installation service for kernel 6.2.16-4-pve.
Sign command: /lib/modules/6.2.16-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/aufs/4.19+20190211/6.2.16-4-pve/x86_64/dkms.conf for module aufs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Sign command: /lib/modules/6.2.16-4-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' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.16-4-pve modules...........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.16-4-pve (x86_64)
Consult /var/lib/dkms/nvidia/525.60.11/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.2.16-4-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/pve-kernel-6.2.16-4-pve.postinst line 20.
dpkg: error processing package pve-kernel-6.2.16-4-pve (--configure):
 installed pve-kernel-6.2.16-4-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of pve-kernel-6.2:
 pve-kernel-6.2 depends on pve-kernel-6.2.16-4-pve; however:
  Package pve-kernel-6.2.16-4-pve is not configured yet.

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

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-kernel-6.2.16-4-pve
 pve-kernel-6.2
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Here is part of make,log:
Code: 
[...]
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_init_mode_config’:
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-drv.c:262:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’
  262 |     dev->mode_config.fb_base = 0;
      |                     ^
make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-drv.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-crtc.c: In function ‘__nv_drm_plane_atomic_destroy_state’:
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-crtc.c:678:5: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
  678 |     struct nv_drm_plane_state *nv_drm_plane_state =
      |     ^~~~~~
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-connector.c: In function ‘__nv_drm_detect_encoder’:
/var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-connector.c:101:18: error: ‘struct drm_connector’ has no member named ‘override_edid’
  101 |     if (connector->override_edid) {
      |                  ^~
make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/525.60.11/build/nvidia-drm/nvidia-drm-connector.o] Error 1
make[1]: *** [Makefile:2026: /var/lib/dkms/nvidia/525.60.11/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.2.16-4-pve'
make: *** [Makefile:82: modules] Error 2
Seems that the nvidia drivers are the culprits now. Any idea how to fix this?
Click to expand...
apt install pve-headers
apt remove kernel-mft-dkms
 
I'm in a similar situation, my host sports a GT540M, and looks like kernels 6.1+ are not compatible at all with the driver 390.157, currently stuck at the same point, 3 packages not fully installed...

In Ubuntu forums they seem to be getting down the rabbit hole
https://askubuntu.com/questions/146...0-be-used-with-kernel-6-2-23-04-lunar-lobster
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869

I wonder if that fix will come to Debian or Proxmox

Until that moment, my question is if I can use proxmox-ve in the meantime, or even at all ... For now, it seems to be working, although apt disagrees since it marks proxmox-ve as not fully installed.
 
Last edited:
titoshadow said:
I'm in a similar situation, my host sports a GT540M, and looks like kernels 6.1+ are not compatible at all with the driver 390.157, currently stuck at the same point, 3 packages not fully installed...

In Ubuntu forums they seem to be getting down the rabbit hole
https://askubuntu.com/questions/146...0-be-used-with-kernel-6-2-23-04-lunar-lobster
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869

I wonder if that fix will come to Debian or Proxmox

Until that moment, my question is if I can use proxmox-ve in the meantime, or even at all ... For now, it seems to be working, although apt disagrees since it marks proxmox-ve as not fully installed.
Click to expand...
Code: 
dpkg --remove --force-remove-reinstreq <BrokenPKG_Name>
apt-get -f install
apt update
apt autoremove --purge

Who needs gpu drivers for Proxmox:-)
You need them only if you want to use the gpu somewhere...
 
Ramalama said:
Code: 
dpkg --remove --force-remove-reinstreq <BrokenPKG_Name>
apt-get -f install
apt update
apt autoremove --purge

Who needs gpu drivers for Proxmox:)
You need them only if you want to use the gpu somewhere...
Click to expand...
Yeah, totally, why would I want to use all my hardware when I can just dont /s

I'll be glad to introduce you to the conspicous world of low load CPU transcoding, by GPU passthrough to a lxc, which powers my home media center :)

btw I already had to use that commands to repair my broken installation until the point I'm stuck now, useful material
 
  • Like
Reactions: Ramalama
Well, in the long-term you should switch to shield+kodi via samba.
Or get another pve hw...

What i mean is, it will get worse and worse waiting for the driver.

Btw, you can still boot into 5.15 on pve8.
It's not beautiful, but you get a working gpu
 
Ramalama said:
Well, in the long-term you should switch to shield+kodi via samba.
Or get another pve hw...

What i mean is, it will get worse and worse waiting for the driver.

Btw, you can still boot into 5.15 on pve8.
It's not beautiful, but you get a working gpu
Click to expand...
Thats my current approach, locked kernel and working with LTS until hw upgrade or driver fix

I can even disable transcoding and handbrake several versions of the same media, but its not optimal, obviusly

Anyway, I faced similar issues when some Realtek ethernet drivers were left behind, and finally I was able to make it work, so lets not lose hope :D
 
  • Like
Reactions: Ramalama
leonardo_benetti said:
I have the same error.
I have a problem with mi realtek nic and i have to install r8168
Code: 
sudo apt install r8168-dkms
. I tried to upgrade dist (if availlable) i'm running Proxmox 8.03 with the latest kernel :
root@esx1:~#
Code: 
pveversion
pve-manager/8.0.3/bbf3993334bfa916 (running kernel: 6.2.16-4-pve)

This is the output of dist update:

root@esx1:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 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 linux-headers-6.1.0-10-amd64 (6.1.37-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-10-amd64.
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/realtek-r8125/9.003.05/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
Sign command: /usr/lib/linux-kbuild-6.1/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/realtek-r8125/9.003.05/source/dkms.conf)

Building module:
Cleaning build area...(bad exit status: 2)
'make' -j12 KVER=6.1.0-10-amd64 BSRC=/lib/modules/6.1.0-10-amd64 all...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-10-amd64 (x86_64)
Consult /var/lib/dkms/realtek-r8125/9.003.05/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.1.0-10-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-10-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.1.0-10-amd64 (--configure):
installed linux-headers-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
linux-headers-amd64 depends on linux-headers-6.1.0-10-amd64 (= 6.1.37-1); however:
Package linux-headers-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-headers-6.1.0-10-amd64
linux-headers-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


I really don't know what to do, i really would like to reinstall proxmox (7.4 and not 8.0.3 that gives me so much problem with realtek card on latest kernel.
Click to expand...
I made it working by removing package `realtek-r8125-dkms`.
This was the package provided by realtek in their github repo since there was none in Debian bullseye repositories.
I guess if you had proxmox 7 with r8125 drivers, you should have this package installed
 
Last edited:
leonardo_benetti said:
Hi @GarcaMan you need to run these commands:
#Remove Linux Header (you don't need them because you are gonna use pve-heaadders):
Code: 
sudo apt purge linux-headers-* linux-headers-*
If the * won't work just tab and check the correct version to purge.
#Install pve-headers
Code: 
apt install pve-headers

After that you should be able to upgrade dist :)
Click to expand...
This worked for me :)
 
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