Skip to content
Discussion options

You must be logged in to vote

this isn’t a bad wl recipe - it’s a kernel skew between your base image and the akmods RPMs the module tries to install.

from your log:

  • base (@System) is still on kernel-*-7.1.13-200.fc44
  • kmod-wl-...fc44 from akmods wants kernel-uname-r = 7.2.5-200.fc44
  • dnf then refuses to pull the newer kernel-core / kernel-modules-core alongside the older ones already in the image → conflicting requests

that’s why it “fails frequently” with image-version: latest on ghcr.io/ublue-os/bluefin-dx: when Universal Blue’s published base lags (or leads) the akmods build for a bit, every blue-build run that installs wl can trip this. Blue-Build documents the same depsolve pattern under Outdated akmods compared…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@tomm1990
Comment options

@white-gecko
Comment options

Answer selected by white-gecko
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants