brunokc / pve-kernel-builder Goto Github PK

Does a support of aarch64 is achievable (even if not officially supported) ?

https://github.com/jiangcuo/Proxmox-Port?tab=readme-ov-file#interesting-thing states:

related to https://forum.proxmox.com/threads/proxmox-on-aarch64-arm64.121925/
which points to https://github.com/pimox/pimox7 and https://github.com/jiangcuo/Proxmox-Arm64

are you interssted in bringing this to a more recent version?

proxmox 8.2.2 with 6.8.4-x-pve has some issues / crashes

I would love to bringe back the pve-edge kernel support but I need some help

Hi,

just noticed that ne release build for 7.4 5.15.108-1-pve is not named "relaxablermrr". Does it contain the patch?

howdy!

this project saved my butt, so im here tryna help

i was wondering if youve heard of DKMS?

• https://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support
• https://github.com/dell/dkms
• https://www.kernel.org/doc/ols/2004/ols2004v1-pages-187-202.pdf
• https://wiki.debian.org/KernelDKMS
• https://wiki.archlinux.org/title/Dynamic_Kernel_Module_Support
• https://wiki.archlinux.org/title/DKMS_package_guidelines

i originally heard about it a few years ago when i had an old imac that needed a broadcom driver for the wifi card
everytime i got a kernel update, i lost wifi, it was the worst,
had to lug the computer upstairs, hard wire it to patch it for the update,
i literally didnt even understand why it was breaking for 6 months probably
when i found the dkms patch, it solved my issue: no more rebuilding, it just auto applied this patch
i cant believe it just wasnt that easy

i currently use it with my proxmox build to get the nvidia drivers

you, me, and many others have this exact same problem
i feel like the DKMS path might solve this problem with less labor, while benefitting a wider community
i dont need to tell you anything beats rebuilding the kernel over and over
if done right, i think it can be used across the distros: debian arch fedora

all that being said, ive only used it, ive never built for it
but from my experience, this was the first thing i looked for,
i was slightly surprised there already wasnt a fix

i see the amount of work youre putting in and i can afford to pick up a shovel myself right now
might as well get as close to solving it for everyone as possible
i appreciate all your hard work 🙏
lmk if theres anything i can do!

ps:
i know this is alpha software, but im not the most familiar with docker nor github actions
for the life of me, i cant figure out what commands youre using to run what
at very least the docs will improve!

Not really an issue, just wanted to highlight that https://github.com/Aterfax/relax-intel-rmrr exists which I am (relatively) actively maintaining. Nice to see its not just me plugging this gap!

i installed docker on a fresh pve install via the debian convenience script

then i cloned the repo and tried to build it via the build script

git clone https://github.com/brunokc/pve-kernel-builder.git 
cd pve-kernel-builder
./build.sh

Preparing container...
[+] Building 0.2s (2/2) FINISHED
 => [internal] load .dockerignore                                                         0.1s
 => => transferring context: 2B                                                           0.0s
 => [internal] load build definition from Dockerfile                                      0.0s
 => => transferring dockerfile: 2.10kB                                                    0.0s
Dockerfile:5
--------------------
   3 |     #
   4 |     ARG DEBIAN_RELEASE=bullseye
   5 | >>> FROM debian:${DEBIAN_RELEASE}-slim
   6 |
   7 |     ARG DEBIAN_RELEASE
--------------------
ERROR: failed to solve: failed to parse stage name "debian:-slim": invalid reference format
Building PVE kernel...

i havent noticed any issues, just a little confused on semver

also are your shutdown downs and reboots slow?
they were slow before the bump, after the patched 6.2.16-4