Package: r8168-dkms
Version: 8.037.00-1
I have a desktop machine to which I just added a second NIC. One
(correctly) uses the r8169 driver, while the new one (StarTech miniPCI-E
adapter) is an r8168 that doesn't work correctly with the r8169 driver.
I'll be filing the requests/bugs on the device, but it doesn't appear
that anything is happening quickly on the upstream resolution of this
issue.
First, thanks for the DKMS package. Second, instead of outright
blacklisting the r8169 module altogether in
/etc/modprobe.d/r8168-dkms.conf, I'd suggest simply overriding the
specific aliases that r8168 provides. The modinfo on the build r8168
module only lists two pci hardware alias ids. In my testing locally,
that results in r8168 being properly bound to the 8168 device, while
still allowing r8169 to coexist and be bound to other ids.
# Just map the specific PCI id instead of blacklisting the whole module
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
Joel
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
