惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
Google DeepMind News
Google DeepMind News
Microsoft Security Blog
Microsoft Security Blog
Martin Fowler
Martin Fowler
MyScale Blog
MyScale Blog
The GitHub Blog
The GitHub Blog
I
InfoQ
A
About on SuperTechFans
GbyAI
GbyAI
宝玉的分享
宝玉的分享
爱范儿
爱范儿
博客园 - 【当耐特】
博客园 - 司徒正美
博客园 - 聂微东
P
Proofpoint News Feed
WordPress大学
WordPress大学
云风的 BLOG
云风的 BLOG
Last Week in AI
Last Week in AI
阮一峰的网络日志
阮一峰的网络日志
B
Blog RSS Feed
Jina AI
Jina AI
aimingoo的专栏
aimingoo的专栏
J
Java Code Geeks
博客园 - 叶小钗

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
[SOLVED] - Upgrading from PVE 8 to 9 - One node successfu...
invalid@exam · 2026-06-02 · via Proxmox Support Forum

I was trying upgrade both nodes of my 8.4 PVEs to 9.x. One completed successfully, but one failed. I can't figure out how to resolve this particular one. Can someone point me in the correct direction?

root@pve1:~# sudo apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up proxmox-kernel-6.8.12-29-pve-signed (6.8.12-29) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.12-29-pve /boot/vmlinuz-6.8.12-29-pve
dkms: running auto installation service for kernel 6.8.12-29-pve.
Sign command: /lib/modules/6.8.12-29-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/i915-sriov-dkms/6.5.13-3/6.8.12-29-pve/x86_64/dkms.conf for module i915-sriov-dkms 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.8.12-29-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.12-29-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.12-29-pve-signed (--configure):
installed proxmox-kernel-6.8.12-29-pve-signed package post-installation script subprocess returned error exit status 2

Setting up proxmox-kernel-7.0.6-2-pve-signed (7.0.6-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 7.0.6-2-pve /boot/vmlinuz-7.0.6-2-pve
dkms: running auto installation service for kernel 7.0.6-2-pve.
Sign command: /lib/modules/7.0.6-2-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/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf for module i915-sriov-dkms 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: 7.0.6-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-7.0.6-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-7.0.6-2-pve-signed (--configure):
installed proxmox-kernel-7.0.6-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.12-29-pve-signed | proxmox-kernel-6.8.12-29-pve; however:
Package proxmox-kernel-6.8.12-29-pve-signed is not configured yet.
Package proxmox-kernel-6.8.12-29-pve is not installed.
Package proxmox-kernel-6.8.12-29-pve-signed which provides proxmox-kernel-6.8.12-29-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-kernel-7.0:
proxmox-kernel-7.0 depends on proxmox-kernel-7.0.6-2-pve-signed | proxmox-kernel-7.0.6-2-pve; however:
Package proxmox-kernel-7.0.6-2-pve-signed is not configured yet.
Package proxmox-kernel-7.0.6-2-pve is not installed.
Package proxmox-kernel-7.0.6-2-pve-signed which provides proxmox-kernel-7.0.6-2-pve is not configured yet.

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

dpkg: error processing package proxmox-default-kernel (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
proxmox-kernel-6.8.12-29-pve-signed
proxmox-kernel-7.0.6-2-pve-signed
proxmox-kernel-6.8
proxmox-kernel-7.0
proxmox-default-kernel
Removing subscription nag from UI...
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve1:~# nano /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf
root@pve1:~# nano /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf
root@pve1:~# cd /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf
-bash: cd: /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf: No such file or directory
root@pve1:~# cd /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64
-bash: cd: /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64: No such file or directory
root@pve1:~#

Error! The /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf for module i915-sriov-dkms includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
You probably need to get a newer driver version (from wherever you manually got this) that is compatible with the new Linux kernel.

EDIT: Lots of threads on this forum about third-party drivers (mostly NVidia but also AMD and others) that happen to be incompatible with newer Linux kernels as the Linux kernel does not provide a stable interface. Maybe consider switching to a (open-source) driver that comes with the Linux kernel? Or maybe the maintainers of that driver can upstream it to the kernel?

Last edited:

Error! The /var/lib/dkms/i915-sriov-dkms/6.5.13-3/7.0.6-2-pve/x86_64/dkms.conf for module i915-sriov-dkms includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
You probably need to get a newer driver version (from wherever you manually got this) that is compatible with the new Linux kernel.

EDIT: Lots of threads on this forum about third-party drivers (mostly NVidia but also AMD and others) that happen to be incompatible with newer Linux kernels as the Linux kernel does not provide a stable interface. Maybe consider switching to a (open-source) driver that comes with the Linux kernel? Or maybe the maintainers of that driver can upstream it to the kernel?

Thanks for the suggestion. I'll see if I can either update or remove that driver.

That was it. I removed the drivers and it completed the update. Running on 9.2.3 now. Thank you very much!

I removed the drivers and it completed the update.

Sure, but what functionality are you missing? There must have been a reason for you to download and install a third-party driver. If the driver or functionality has been integrated into Linux then that's the best outcome of course. Just wondering..