[TUTORIAL] Custom Proxmox 6.19.0 Kernel. 6.18.0 is also available for Testing.

J

jaminmc

Member
Aug 1, 2022
89
76
23
DISCLAIMER: This is not Official Proxmox. I use the source code and applied it to the latest available kernels that Ubuntu has in the same way Proxmox does. Except they have a team, and a bunch of test benches, and procedures to make sure things are stable before releasing. I have only 3 Proxmox systems that I can test on.

I managed to make my own 6.19.0-jaminmc-pve kernel based on Ubuntu-6.19.0-3.3, which itself is based on Linux 6.19-rc6. With Proxmox Patches and Configuration, I was also able to get OpenZFS 2.4.0 to work with 6.19 with my own patches. So far, it’s been stable, and GPU passthrough is working well (Vega 64).

Both 6.18.0 and 6.19.0 are available here:
https://github.com/jaminmc/pve-kernel/releases/

EDIT: 6.18 is not going to have any more versions than this.

There are multiple versions on Release page.

Download and install the Kernel.:
Code: 
# Download Kernel & Headers
wget https://github.com/jaminmc/pve-kernel/releases/download/v6.19.5-2/proxmox-{kernel,headers}-6.19.5-2-pve_6.19.5-2.jaminmc1_amd64.deb

# Download Firmware
wget https://github.com/jaminmc/pve-kernel/releases/download/v6.19.5-2/pve-firmware_3.19-4-jaminmc_all.deb

# Install Them
apt install ./proxmox-{kernel,headers}-6.19.5-2-pve_6.19.5-2.jaminmc1_amd64.deb ./pve-firmware_3.19-4-jaminmc_all.deb

# Unpin your current kernel. Since it is the Newest and highest PVE kernel, it should be the default.
proxmox-boot-tool kernel unpin
 
Last edited:
  • Like
Reactions: bberger
just wanted to say thanks. I did install the latest 6.19.1 on my proxmox runnnig amd strix halo (framework desktop), and that kernel actually fixed the problem in my immich lxc container running onnx models. Before i was running 6.17 from proxmox and there are missing amd patches which seem to prevent being able to run this new migraph onnx inference engine.

PBS also worked for me

anyway long story short... i'm super happy, this was my first time running a (not self) custom compiled kernel but it did work.
 
Last edited:
  • Like
Reactions: jaminmc
I'm glad I could help! Every few days, I check for a newer kernel at the Ubuntu kernel repository on Launchpad, then pull and compile it with the Proxmox magic. If it works, I update my GitHub.

It looks like you have the latest version — so far, 6.19 has been stable on my systems, and I only needed to apply one patch to get it working. The patch was originally written for 6.18, and I haven't tested 6.19 without it. Without the patch, LXC containers fail to obtain an IPv4 address via DHCP.

EDIT:
If you're seeking an official Proxmox kernel, enabling the test repository grants access to pve-firmware version 3.18-1 (based on firmware-linux 20260110) and the newer proxmox-kernel-6.17.13-1-pve, which may suit your requirements. My 6.19 kernel uses the same firmware bundle, so if firmware compatibility is the issue, the older 6.17.13 kernel should also work.
 
Last edited:
I have 2 new releases. One is proxmox-kernel 6.19.2 (unofficial) — Linux 6.19.2 + OpenZFS 2.4.1, which is based on Ubuntu 6.19.0-6.6. I made it an official release, as The Resolute Raccoon has it as a stable release. I have updated it to have OpenZFS 2.4.1.

The other is proxmox-kernel 6.19.5 — AMD NPU fix, which is based on Ubuntu-6.19.0-9.9, which they just posted yesterday. I did have a user that had an issue with the AMD NPU. Turns out the firmware in the latest linux-firmware 20260221, where I updated the pve-firmware package from had too new firmware for the firmware. So I updated my Firmware package. Added This patch to fix it. That Kernel has other new fixes since the release of the other kernel. They both run great on my Ryzen 7 9700X., and my i3-4030U minipc.
 
  • Like
Reactions: bberger
jaminmc said:
I have 2 new releases. One is proxmox-kernel 6.19.2 (unofficial) — Linux 6.19.2 + OpenZFS 2.4.1, which is based on Ubuntu 6.19.0-6.6. I made it an official release, as The Resolute Raccoon has it as a stable release. I have updated it to have OpenZFS 2.4.1.

The other is proxmox-kernel 6.19.5 — AMD NPU fix, which is based on Ubuntu-6.19.0-9.9, which they just posted yesterday. I did have a user that had an issue with the AMD NPU. Turns out the firmware in the latest linux-firmware 20260221, where I updated the pve-firmware package from had too new firmware for the firmware. So I updated my Firmware package. Added This patch to fix it. That Kernel has other new fixes since the release of the other kernel. They both run great on my Ryzen 7 9700X., and my i3-4030U minipc.
Click to expand...
I appreciate the updated Kernels as it fixed some issues on my Minisforum N5 Air NAS.

Unfortunately all your links seem to be down (404) now :-/
 
bberger said:
I appreciate the updated Kernels as it fixed some issues on my Minisforum N5 Air NAS.

Unfortunately all your links seem to be down (404) now :-/
Click to expand...
I have no idea what happened. Last night, I received an email from GitHub stating:
Code: 
We recently noticed that your GitHub account had a suspicious login. Out of an abundance of caution, we made the decision to force a password reset for the account associated with this email address.

We have no reason to believe that this was the result of a GitHub vulnerability. While we can’t speak to your particular case, in other similar account takeovers our users have told us that infostealer malware was discovered on their system.
I use two-factor authentication, so I have no idea what that was. I looked through the account history, and didn't see anything suspicious either.

I have done an account reinstatement request, but it says "Due to high support volume, it may take up to seven business days to hear back from our Support Engineers."
 
Is there any chance you have a different option to share the kernel package in the meantime? Today I received my Optane M10 drives from Ali, wiped and returned my noname China SSD to Amazon and now need a patched Kernel to get my N5 Air Proxmox host working again^^
 
You must log in or register to reply here.
Top Bottom
Back