Open johntdavis84 opened 2 weeks ago
@johntdavis84 Any progress on your problem ? your problem is bad install or remove from this driver i915-sriov-dkms Maybe you can remember what you did with this driver?
Maybe this one is your error? driver i915-sriov-dkms
https://forum.proxmox.com/threads/kernel-upgrade-6-5-13-1-failed-to-install.144756/
Consult /var/lib/dkms/i915-sriov-dkms/6.5.13-5/build/make.log
I use WinSCP to login to Proxmox and search the log.
I have a similar problem from a bad remove with a snap install from veeam- dkms/blksnap And for months I use this old and pinned kernel 6.2.16-19-pve without any problems and today after a bare-metal backup I did a apt update && apt dist-upgrade Same problem the new the kernel....
I'd recommend to remove the module, reinstall all your kernels via apt (read the linked post once before starting, especially the "Edit"-part at the end) and install the latest version of this dkms package. It should work fine with all recent pve kernels.
@pasbec thanks for the reply:) but this wash not about my problem but from johntdavis84
And wanted to explain what is best practice to proceed and that is reading and research the problem and make off-side backups.
And yes Today I solved my Proxmox kernel problem after months running on a pinned Kernel. Yeah I am so happy:)< lossing the server wash no option.
After many reading work and research and learning a lot in that process myself.
I made sure my backups were in place made with PBS and a bare-metal backup with Clonezilla. I decided to apt update && apt dist-upgade the server. And after that I saw what happend reading the Consult /var/lib/dkms/blksnap/6.0.3.1221/build/make.log for more information.
This blksnap came from a veeam agent that I installed but the log file showed me that the blksnap didn't remove correctly. I removed veeam many months ago.
Today after I found out what this blksnap wash I uninstalled it and Proxmox did the rest and I removed the pinned old kernel and booted to the new one 6.8.12-1-pve.
https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_proxmox_boot_tool
https://forum.proxmox.com/threads/how-to-pin-unpin-a-specific-kernel.111732/
https://clonezilla.org/clonezilla-live.php
greetings Charlesm
@johntdavis84 Any progress on your problem ? your problem is bad install or remove from this driver i915-sriov-dkms Maybe you can remember what you did with this driver?
Maybe this one is your error? driver i915-sriov-dkms
https://forum.proxmox.com/threads/kernel-upgrade-6-5-13-1-failed-to-install.144756/
Consult /var/lib/dkms/i915-sriov-dkms/6.5.13-5/build/make.log
I use WinSCP to login to Proxmox and search the log.
I have a similar problem from a bad remove with a snap install from veeam- dkms/blksnap And for months I use this old and pinned kernel 6.2.16-19-pve without any problems and today after a bare-metal backup I did a apt update && apt dist-upgrade Same problem the new the kernel....
Thanks for this. :)
I completely removed the previous SR-IOV DKMS install, which was quite outdated anyway, reinstalled the kernels I wanted, and then installed the latest version of the DKMS driver. It's working great. :)
I also updated the DKMS driver inside the Lubuntu VM I had using it. No issues there.
Previously, I had the 6.5.13-5 kernel pinned in the PVE host. It's nice to be on the latest 6.8.x. Should I pin the latest 6.8 kernel? What's the safest way to keep the SR-IOV support working and update the kernel at the same time? I think I just need to update to the latest kernel, reboot the PVE host, and then uninstall and reinstall the DKMS driver. Is there more to it than that?
Hello,
I just updated my Proxmox system, and saw this output on the CLI.
I'm not sure why it's trying to build the dkms module against 6.8.x, as I haven't configured it to do that (I installed it against 6.5.13-5). I'm concerned, however, that it's reporting that it couldn't configure the 6.8.8 kernels, though. At some point, I'm going to want to unpin 6.5.13-5 and switch over to the 6.8 series.
Are my 6.8.x kernels damaged at this point? Do I need to do anything to fix this?
Thanks!