ublue-os/akmods

F41 akmods Tracker

Closed this issue · 10 comments

Tracking Status of akmods for F41 Release:

  • akmods (common)
    • xpadneo
      • Not yet available for F41. Fixed in #260
      • Workaround: build disabled, but should auto-enable when required package shows up in negativo17's repo.
  • akmods-extra
  • akmods-nvidia
    • nvidia
      • nvidia was failing due to rpmrebuild issues.
      • Workaround: @m2Giles has resolved. Building fine

For rpmrebuild it's gonna be something we need to add from now on it seems like. The issue is caused by rpmbuild running prep commands that can nuke the build root.

Additionally, the rpmrebuild command is used with all kmods and kernel-cache. It just showed up first with Nvidia since it only builds the one set of kmods

For akmods-extra 41. Ayn-platform rpm needs a copr rebuild. The 41 package is not the latest tarball.

For akmods-extra 41. Ayn-platform rpm needs a copr rebuild. The 41 package is not the latest tarball.

I rebuilt ayn-platform in COPR and kicked off a rebuild here: https://github.com/ublue-os/akmods/actions/runs/11227926052/job/31266324881

It seems that the xpadneo and evdi rpms are now present in negativo17's repo.

p5 commented

It seems that the xpadneo and evdi rpms are now present in negativo17's repo.

Awesome! Have created a PR so we can get these building!

Created issue upstream with Negativo: negativo17/evdi-kmod#2

Just stumbled on this bug due to the fact that I missed building displaylink for Fedora 41 as I don't have a DisplayLink docking station anymore. Feel free to ping me in this sort of tracking issues.

Thanks.

I usually try to have everything available for new distribution releases ~1 month before the actual relase date, this time I was a bit under pressure at work and could not dedicate so much time to it as I wanted.

@scaronni No worries! I really appreciate you being able to get this fixed so quickly! I will try running a build now.