dnf5 build nearly working for bazzite
close, fails due to multiple kernels being found in rechunker step
14 Replies
@M2 I was helping on bazzite again tonight and we hit this issue where rechunker says there are muliple kernels in /usr/lib/modules
I'm almost certain we ran into the same thing in bluefin, no?
Was the fix just a matter of getting the proper commands for removing the existing kernel before installing the new one?
https://github.com/ublue-os/bazzite/actions/runs/12742032515/job/35509533326#step:26:156
This usually means akmods and Bazzite are out of sync. Try rebuilding akmods to get the drivers built for the newer kernels.
The akmods requires one kernel version and Bazzite has another. So when the akmods are installed, additional kernels are pulled in.
(I'm saying this without looking through the build logs since you can't search on mobile for some reason)
its not rechunker, its ostree complaining
Creating repo with ref master starts committing to ostreeAre you explicitly deleting the previous kernels with rpm or relying on dnf to remove the old kernel?
rpm, exactly what bluefin does
GitHub
bazzite/build_files/install-kernel-akmods at unstable · ublue-os/ba...
Bazzite is a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - ublue-os/bazzite
I might have some tonight to play with this
Is there any desire to fix the local justfile for building?
Sure
do you mean refactor everything to use just for local and CI building? 🙂
FWIW, we have 2 branches building in bazzite right now:
-
unstable is structured the way it always has been but now with dnf5 fixes being worked in
- separate-scripts is my attempt to make minimal changes overall, mostly keep it in sync with unstable, but still split out to only 3 Containerfile RUN statements each building a distinct image with shell scripts instead of massive Containerfile RUNs
@j0rge @M2 @bsherman
OH YEAH.