[elrepo] serious design flaw in network kmod rpms

[Tuan Hoang]

 Hi Levente,
As noted in the bug tracker, we have pushed out a new kmod-r8125 that removes the blacklist file.https://elrepo.org/bugs/view.php?id=1572
Note: That the kmod-r8168 will still retain the blacklist-r8169.conf.
Tuan

    On Tuesday, December 2, 2025 at 01:28:28 PM EST, Akemi Yagi <amyagi at gmail.com> wrote:  
 
 On Tue, Dec 2, 2025 at 2:14 AM Farkas Levente <lfarkas at lfarkas.org> wrote:
>
> hi,
> I wrote an issue about it:
> https://elrepo.org/bugs/view.php?id=1572
> and for me it was very clear it's a serious bug, but it seems I've to
> explain it more details.
>
> The problem:
> kmod-r8125 blacklist r8169 kmod.
>
> The bigger problem:
> It was not doing it on el 9.6 but do it on 9.7! Which cause if someone
> install kmod-r8125 on a system which has any other realtek network
> device it's stop working and no longer be able to access to the system
> remotely.
> So it's a serious regression!
> What's more can be solved only in place!
>
> Why it's so big problem? eg we've got a few thousands of server in a few
> dozens of country...and wouldn't like to travel...
> we keep the installed package list identical on all of our server, but
> of course the hardware is not exactly the same.
>
> of course i can solve this simple rebuild the buggy rpm, but imho it's a
> much larger problem.
>
> blacklist is for module for identical hardware eg nvidia and nouveau,
> but in this case kmod-r8125 blacklist r8169 which is a much larger set
> of hardware list. and the suggestion to install kmod-r8168 is not a
> solution or have to install to all kmod-r*.
> in case of i install ANY of the elrepo kmod the system still have to be
> usable and working (what's more should have to be better). this is not
> the case with kmod-r8125.
>
> So IMHO this move is very serious regression what's more these changes
> have to revert in all similar places.
>
> regards.
>
> --
> Levente                              "Si vis pacem para bellum!"

Hi Levente ,

Thanks for the note. I suppose there is no "one-size-fit-all" solution
to the issue. The original reason why r8169 was blacklisted was that,
with the kmod-r8125 in RHEL 10, it still used the r8169 driver. Of
course, when you have 2 NICs, the situation is not as simple as
disabling one driver or the other.

We'd like to get a good and reasonable solution but in the mean time,
we could revert the change if that works as a temporary fix.


Akemi
_______________________________________________
elrepo mailing list
elrepo at lists.elrepo.org
http://lists.elrepo.org/mailman/listinfo/elrepo
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20251203/002af803/attachment.html>