Am 09.06.2015 um 22:38 schrieb Dan Book:
That's great, for people who already know what to do. The problem
is for
people who try to install dkms or akmods and then it doesn't work. There
are plenty of people who use dkms or akmods modules but don't compile
anything themselves (and those people are less likely to understand the
kernel-devel issue).
which issue?
you get the most recent kernel-devel and that's it
if you don't reboot to the most recent kernel installed on your system
before biuld dkmos/akmod modules - bad luck - but how is that a Fedora
problem at all - both are helpers in case of wrong hardware decisions
and so you need in the worst case to ivent 10 minutes of our time you
saved by bouy random broken hardware
that *is not* a Fedora problem at all - period
On Tue, Jun 9, 2015 at 4:24 PM, Reindl Harald
<h.reindl(a)thelounge.net
<mailto:h.reindl@thelounge.net>> wrote:
Am 09.06.2015 um 22:01 schrieb Dan Book:
This has also been a problem for several releases with the
akmods from
rpmfusion. I think the more "correct" solution (read to the end)
would
be to somehow prioritize the kernel-devel package (possibly
multiple)
that matches the installed kernel(s). kernel-debug-devel is
never the
"correct" choice when only standard kernels are installed, but
it gets
installed because of alphabetical order; this ordering is one
way to get
something useful installed instead. This of course is
pie-in-the-sky and
doesn't match with how dependencies can currently be declared and
resolved, AFAIK
honestly that is a *non* problem at all
* if you need to compile modules you need kernel-devel
* if you *once* had it installed yum7dnf will keep it up-to-date