Routine Proxmox update throwing errors

B

bawjaws

New Member
Apr 27, 2023
19
0
1
I've done the routine check for updates today and saw there were a bunch of updates, so went ahead and installed. I seem to get continuous errors around upgrading the kernel:

Code: 
Starting system upgrade: apt-get dist-upgrade
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:
  proxmox-headers-6.5.13-1-pve proxmox-headers-6.5.13-3-pve
  proxmox-kernel-6.5.13-1-pve-signed
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  pve-qemu-kvm
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 28.4 MB of archives.
After this operation, 31.7 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-qemu-kvm amd64 8.1.5-5 [28.4 MB]
Fetched 28.4 MB in 2s (16.6 MB/s)       
Reading changelogs... Done
(Reading database ... 162561 files and directories currently installed.)
Preparing to unpack .../pve-qemu-kvm_8.1.5-5_amd64.deb ...
Unpacking pve-qemu-kvm (8.1.5-5) over (8.1.5-4) ...
Setting up proxmox-kernel-6.5.13-5-pve-signed (6.5.13-5) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.13-5-pve /boot/vmlinuz-6.5.13-5-pve
dkms: running auto installation service for kernel 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


Building module:
Cleaning build area...
make -j20 KERNELRELEASE=6.5.13-5-pve -C /lib/modules/6.5.13-5-pve/build M=/var/lib/dkms/i915-sriov-dkms/6.5.13-1/build KVER=6.5.13-5-pve........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.13-5-pve (x86_64)
Consult /var/lib/dkms/i915-sriov-dkms/6.5.13-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.5.13-5-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.5.13-5-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.13-5-pve-signed (--configure):
 installed proxmox-kernel-6.5.13-5-pve-signed package post-installation script subprocess returned error exit status 2
Setting up pve-qemu-kvm (8.1.5-5) ...
dpkg: dependency problems prevent configuration of proxmox-kernel-6.5:
 proxmox-kernel-6.5 depends on proxmox-kernel-6.5.13-5-pve-signed | proxmox-kernel-6.5.13-5-pve; however:
  Package proxmox-kernel-6.5.13-5-pve-signed is not configured yet.
  Package proxmox-kernel-6.5.13-5-pve is not installed.
  Package proxmox-kernel-6.5.13-5-pve-signed which provides proxmox-kernel-6.5.13-5-pve is not configured yet.


dpkg: error processing package proxmox-kernel-6.5 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
 proxmox-kernel-6.5.13-5-pve-signed
 proxmox-kernel-6.5
E: Sub-process /usr/bin/dpkg returned an error code (1)


Your System is up-to-date


starting shell
root@pve:/#

But when I check which kernel version is running I get:
Code: 
pve-manager/8.1.10/4b06efb5db453f29 (running kernel: 6.5.13-3-pve)

Is there anything I should be doing to fix this?
 
Seems like you have a custom kernel module (sriov drivers for i915), it seems like that one isn't compatible with 6.5.13, which is why upgrading the kernel fails. Either get a new version of that module that is compatible with 6.5.13, remove the custom module, or stick with the current kernel until a compatible version has been release by the vendor.
 
  • Like
Reactions: Kingneutron
D'oh! A previous attempt to get Intel 13th Gen iGPUs passed through to VMs. Now removed and now working. Thanks for the superquick response
 
hello, I have the exact same error due to the same reason. Could you guide me on what command I need to remove the dkms stuff with the custom module ? I did some try before to passthrough stuff with a 13th gen Intel as well.
 
Hey! I think this was the command I ran:

dkms uninstall -m i915-sriov-dkms/6.5.13-1 --all

(I take it you never got the virtualised GPU thing to work either?)
 
Thanks for the answer. No, it never really worked... i am now using an lxc which somehow is easier for a igpu "passthrough".
I just ran a command after googling in the meantime:
dkms remove i915-sriov-dkms/6.5.13-1 --all

Do you think it has the same effect ?
 
You must log in or register to reply here.
Top Bottom