Unable to rebase back to fedora 41.
I use the rebase command:
brh rebase stable-41.20250409.1
It seems to correctly stage the rebased image and asks me to reboot, but when it does, it boots into 42 and says there was an error deploying it
Any suggestions?13 Replies
The relevant logs:
unfortunately there is a bug preventing rebase between 41 and 42, why do you need f41?
ah, that's unfortunate. I need ROCM to work, and as I understand it, the kernel in 42 does not current support it
someone made bazzite with older kernel
https://github.com/btekv4/bazzite-gnome-rocm
you can use it probably
GitHub
GitHub - BTekV4/bazzite-gnome-rocm: Template for making your own OS...
Template for making your own OS image using BlueBuild - BTekV4/bazzite-gnome-rocm
oh they are hardcoding the kernel š
hah that's one way to do it. I'll give it a shot. Thanks!
if you do decide to make your own image, i suggest to follow the akmod docs
https://github.com/ublue-os/akmods#usage
GitHub
GitHub - ublue-os/akmods: A caching layer for pre-built Fedora akmo...
A caching layer for pre-built Fedora akmod RPMs. Contribute to ublue-os/akmods development by creating an account on GitHub.
you can replicate it inside bluebuild too
Unfortunately I have not found any other way
you can do something like this
for the kernel version you can manually update it or use a little hacking in the gh action
This is how the modules should also work, right? I try
yes
also just remembered you dont need to use the gh action stuff
you are pinning kernel version anyway lol
the action is used if you want sync kernel version to upstream
thanks, I had a chance to try that build and it seems to work. I'll keep that deployment pinned so I can jump to it when needed for now while I wait for ROCm to support our current kernel