There are two possibilities either:
a. im gravely unfamiliar with package name conversions of OM
b. your naming conventions are lets say very unorthodox
If you have those two versions of an iso installer OMLx 5.0 Plasma x86_64
[OMLx 5.0 Plasma AMD CPU (newer than 2017)]
Some user may assume that the kernels and kernels-headers for those two will be present somewhere on repo.
Every package in repo is equipped with some kind of decryption to easy identify the package we need in human readable format.
Any sane user that assumed he or she needs specific kernel will search for specific string of text from a description using grep.
If we have info like this AMD CPU (newer than 2017) in a name of an iso and iso it self have znver1 in its name user most likely will search against.
dnf search linux
dnf search kernel
dnf search linux-image
dnf search kernel-image
Just to establish the name conventions for kernel rpm itself
then he will go with grep for narrowing search to specyfic package piping thru grep with amd or znver1.
I’ve done that and im more clueless then on the beginning
Ok forgetting of * wildcard makes me stupid dipstick , but does not change fact it is hard to find which kernel from the list is for zen architecture .
Let me ask this way
What is the actual difference between znver iso and regular iso if not the kernels?
i have not used debian or fedora based distros for my day-driver in a long time (brave didn’t exist last time i used one of them, use debian on my servers but those are cli only anyway) and in arch aur its brave-bin another distro i did play with had it just as brave.
Package naming isn’t a standardized thing. Ideally package maintainers would just use whatever name the source uses. I have been using Arch for about two years and openSUSE for about a year, and there are a lot of different names for the same package, especially on openSUSE’s OBS community repos.
, but does not change fact it is hard to find which kernel from the list is for zen architecture .