causes all sorts of conflicts and I can’t figure out how to replace/remove the old packages:
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-modules-extra-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-tools-libs-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-devel-matched-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-tools-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-devel-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-modules-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-core-6.9.0-64.fc41.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/kernel/6.9.0/64.fc41/x86_64/kernel-modules-core-6.9.0-64.fc41.x86_64.rpm...done
Inactive base replacements:
kernel-devel-6.9.0-64.fc41.x86_64
kernel-devel-matched-6.9.0-64.fc41.x86_64
kernel-tools-6.9.0-64.fc41.x86_64
kernel-tools-libs-6.9.0-64.fc41.x86_64
Checking out tree d31b7c6... done
[...]
error: Could not depsolve transaction; 4 problems detected:
Problem 1: package kernel-devel-matched-6.8.10-300.fc40.x86_64 from @System requires kernel-core = 6.8.10-300.fc40, but none of the providers can be installed
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from updates
- conflicting requests
Problem 2: package kmod-xpadneo-6.8.10-300.fc40.x86_64-0.9.6-2.20240423git73be2eb.fc40.x86_64 from @System requires kernel-uname-r = 6.8.10-300.fc40.x86_64, but none of the providers can be installed
- package kernel-uki-virt-6.8.10-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.10-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from updates
- cannot install both kernel-modules-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-modules-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-modules-core-6.8.10-300.fc40.x86_64 from updates
- package kernel-modules-6.9.0-64.fc41.x86_64 from @commandline requires kernel-uname-r = 6.9.0-64.fc41.x86_64, but none of the providers can be installed
- conflicting requests
Problem 3: package kernel-uki-virt-6.8.10-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.10-300.fc40.x86_64, but none of the providers can be installed
- package kmod-xpadneo-6.8.10-300.fc40.x86_64-0.9.6-2.20240423git73be2eb.fc40.x86_64 from @System requires kernel-uname-r = 6.8.10-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-modules-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-modules-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-modules-core-6.8.10-300.fc40.x86_64 from updates
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from updates
- package xpadneo-kmod-common-0.9.6-2.20240423git73be2eb.fc40.noarch from @System requires xpadneo-kmod = 0.9.6, but none of the providers can be installed
- package kernel-modules-extra-6.9.0-64.fc41.x86_64 from @commandline requires kernel-modules-core-uname-r = 6.9.0-64.fc41.x86_64, but none of the providers can be installed
- package kernel-modules-extra-6.9.0-64.fc41.x86_64 from @commandline requires kernel-uname-r = 6.9.0-64.fc41.x86_64, but none of the providers can be installed
- conflicting requests
Problem 4: package kernel-uki-virt-6.8.10-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.10-300.fc40.x86_64, but none of the providers can be installed
- package kmod-xone-6.8.10-300.fc40.x86_64-0.0.git.45.5441d09a-1.fc40.x86_64 from @System requires kernel-uname-r = 6.8.10-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-modules-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-modules-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-modules-core-6.8.10-300.fc40.x86_64 from updates
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.9.0-64.fc41.x86_64 from @commandline and kernel-core-6.8.10-300.fc40.x86_64 from updates
- package kernel-6.9.0-64.fc41.x86_64 from @commandline requires kernel-modules-core-uname-r = 6.9.0-64.fc41.x86_64, but none of the providers can be installed
- package kernel-6.9.0-64.fc41.x86_64 from @commandline requires kernel-core-uname-r = 6.9.0-64.fc41.x86_64, but none of the providers can be installed
- conflicting requests
Anyone managed to replace the kernel on Bluefin? Not sure what I’m missing here…already tried many combinations of replace with --remove and --install
Hi there. Just curious, were you ever able to get this to work?
I was trying to install on Aurora a custom kernels I compiled: sudo rpm-ostree override replace ./kernel*
And it returns this mess. Pretty much the same error as you’re having:
error: Could not depsolve transaction; 4 problems detected:
Problem 1: package kmod-xpadneo-6.8.11-300.fc40.x86_64-0.9.6-2.20240423git73be2eb.fc40.x86_64 from @System requires kernel-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- package kernel-uki-virt-6.8.11-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from updates
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from updates
- conflicting requests
Problem 2: package kernel-uki-virt-6.8.11-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- package kmod-xpadneo-6.8.11-300.fc40.x86_64-0.9.6-2.20240423git73be2eb.fc40.x86_64 from @System requires kernel-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from updates
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from updates
- package xpadneo-kmod-common-0.9.6-2.20240423git73be2eb.fc40.noarch from @System requires xpadneo-kmod = 0.9.6, but none of the providers can be installed
- package kernel-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline requires kernel-modules-core-uname-r = 6.8.11-300.vfioamdcompat.fc40.x86_64, but none of the providers can be installed
- package kernel-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline requires kernel-core-uname-r = 6.8.11-300.vfioamdcompat.fc40.x86_64, but none of the providers can be installed
- conflicting requests
Problem 3: package kernel-uki-virt-6.8.11-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- package kmod-xone-6.8.11-300.fc40.x86_64-0.0.git.115.fdbb71f1-1.fc40.x86_64 from @System requires kernel-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from updates
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from updates
- package kernel-modules-extra-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline requires kernel-modules-core-uname-r = 6.8.11-300.vfioamdcompat.fc40.x86_64, but none of the providers can be installed
- package kernel-modules-extra-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline requires kernel-uname-r = 6.8.11-300.vfioamdcompat.fc40.x86_64, but none of the providers can be installed
- conflicting requests
Problem 4: package kernel-uki-virt-6.8.11-300.fc40.x86_64 from updates requires kernel-modules-core-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- package kmod-xone-6.8.11-300.fc40.x86_64-0.0.git.115.fdbb71f1-1.fc40.x86_64 from @System requires kernel-uname-r = 6.8.11-300.fc40.x86_64, but none of the providers can be installed
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-modules-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-modules-core-6.8.11-300.fc40.x86_64 from updates
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from @System
- cannot install both kernel-core-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline and kernel-core-6.8.11-300.fc40.x86_64 from updates
- package xone-kmod-common-0.0.git.115.fdbb71f1-1.fc40.noarch from @System requires xone-kmod = 0.0.git.115.fdbb71f1, but none of the providers can be installed
- package kernel-modules-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline requires kernel-modules-core-uname-r = 6.8.11-300.vfioamdcompat.fc40.x86_64, but none of the providers can be installed
- package kernel-modules-6.8.11-300.vfioamdcompat.fc40.x86_64 from @commandline requires kernel-uname-r = 6.8.11-300.vfioamdcompat.fc40.x86_64, but none of the providers can be installed
- conflicting requests
For anyone else having this issue, I’ve been informed that you’ll just have to create your own custom image. Installing a custom kernel is not supported.
Anyone happen to know if it is now possible to build and install custom kerrnels with bluefin (or bazzite?)?
I’m getting an Asus Flow Z13 (with the new Strix Halo APU in it) tomorrow - largely to get linux working nicely on it. I’m trying to select a distribution right now to do this work with.
From talking with the devs on asus-linux I think it is likely I’ll have to apply a few patches & do some development on the current 6.14 WIP kernel. I can handle that fine, but it is a long time since I last worked with an rpm based distribution. Even with that limitation I was still thinking about trying one of your new cool container targeted forks/layers/unclear-on-the-preferred-term. However, this thread makes me think universal-blue is not yet recommended if I want to just be able to build an image and reboot to try with new kernel/module changes?
I’ve done a fair amount of kernel development, but it was all for semi-closed source hardware products. I’ve never before futzed with this new ‘atomic’ layer fedora is describing. Would it be better for me to use old-school !atomic fedora till I get the kernel solid then afterwards deal with switching to something like bluefin to be my daily driver (with my fixed kernel)?