[elrepo] More 7.4 incompatible drivers

[Nick Howitt]

On 07/10/2017 12:35, Phil Perry wrote:
>
> On 06/10/17 13:45, Nick Howitt wrote:
>> Hi Phil,
>>
>> One thing I noticed in the summer last year but did not isolate at 
>> all was that when I was running both the r8168 and r8169 drivers in a 
>> box which had both cards, the 8169 NIC would not come up on boot and 
>> had to be modprobed after boot. I got round it by:
>>
>
> That may be because our kmod-r8168 blacklists the r8169 driver from 
> loading and binding the device (see below).
>
Hmm. That sounds dangerous and messes things up when you have both 
cards, or, in my case a motherboard with an r8168 on-board NIC and a PCI 
r8169 NIC. I did not realise you blacklisted the r8169. I have a 
suggestion. The kmod-r8169 driver comes with PCI-IDs removed for the 
r8168 so it will never load against the r8168. If you remove the 
blacklisting of the r8169 from the r8168 package, but instead put a 
dependency on the kmod-r8169 driver, then you have utopia. If you 
install the r8169 it will force the installation of the r8169 as well 
and in an environment with both NICs, both drivers will load against the 
correct NIC.
>> echo "modprobe r8169" > /etc/sysconfig/modules/r8169.modules
>> chmod +x /etc/sysconfig/modules/r8169.modules
>>  > This got the driver to load much earlier in the boot sequence.
>>
>> The person who tested the via-rhine driver found the same here: 
>> https://www.clearos.com/clearfoundation/social/community/clearos-7-4-beta#reply-190651 
>> (and the following post) with drivers compiled for 7.4.
>>
>
> What does lsinitrd say for the kernel in question? Are the appropriate 
> drivers present in the initramfs?
I'm about to rebuild my old box so I'll have a look. I've never used the 
command before
>
> IIRC, the issue with r8168/9 is complicated by the fact that the 
> distro kernel r8169 driver is a unified driver that supports some 
> hardware also supported by the kmod-r8168 driver, so the two are not 
> designed to be used together as they may compete to bind the same 
> device on boot.
Yes, the stock r8169 driver has the PCI IDs for the r8168. I *think* if 
you install the kmod-r8169 it takes precedence over the stock. Certainly 
a modinfo only returns results for the kmod driver
>
> My network config/admin skills are not great. Maybe there is a way to 
> designate/bind a specific driver to a device to ensure you get the 
> expected behaviour?
>
I don't have the knowledge either, but I think what I proposed would work
> _______________________________________________
> elrepo mailing list
> elrepo at lists.elrepo.org
> http://lists.elrepo.org/mailman/listinfo/elrepo