LinuxQuestions.org - [SOLVED] Slackware64-14.2 gets confused when I plug in a second Ethernet card

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware64-14.2 gets confused when I plug in a second Ethernet card (https://www.linuxquestions.org/questions/slackware-14/slackware64-14-2-gets-confused-when-i-plug-in-a-second-ethernet-card-4175618177/)

@FlinchX
Thanks for the clarifications, it looks like the r8169 driver is not really functional in this 2 cards scenario and the r8168 should be used instead ATM. Your English is good, don't worry about it, I'm also not a native speaker. Regarding your privacy concerns, you're not the only one and paranoia is just heightened awareness, remember that ;)

I was suggesting to get in touch with the developers yourself just because they might ask some HW details that I couldn't provide as I don't own any r816x NICs. Anyways, I just sent an E-mail to the two developers (originators) found in the header of the source file and asked them politely to take a look at this thread and the other one related that I referenced above.
https://github.com/torvalds/linux/bl...ealtek/r8169.c

@bassmadrigal
EDIT>
The r8168 driver you referred to looks to be maintained by a single contributor that takes it from Realtek. I was under the impression that Realtek stopped the development on it and that the r8169 took it's place:
https://git.slackbuilds.org/slackbui...b2110e283e9d4a
https://github.com/mtorromeo/r8168/

Related to the r8169 kernel supported driver, it is actively maintained but it's a little difficult to go through all the changes and try to relate them with the issues observed.
https://github.com/torvalds/linux/co...ealtek/r8169.c
I'm concerned about this driver because it looks like the Realtek chips that require this driver are getting used more often in Motherboards / NICs.

Quote:

Originally Posted by abga (Post 5784360)

@bassmadrigal
EDIT>
The r8168 driver you referred to looks to be maintained by a single contributor that takes it from Realtek. I was under the impression that Realtek stopped the development on it and that the r8169 took it's place:
https://git.slackbuilds.org/slackbui...b2110e283e9d4a
https://github.com/mtorromeo/r8168/

It looks like mtorromeo is just mirroring the source from Realtek onto github. Based on one of his other repos, he might be an Arch user and was just looking for a better way to host the source for an AUR package.

Quote:

Originally Posted by abga (Post 5784360)

Related to the r8169 kernel supported driver, it is actively maintained but it's a little difficult to go through all the changes and try to relate them with the issues observed.
https://github.com/torvalds/linux/co...ealtek/r8169.c
I'm concerned about this driver because it looks like the Realtek chips that require this driver are getting used more often in Motherboards / NICs.

It'd certainly be interesting if that issue is still happening with a newer kernel.

Posting here for further reference. Earlier today I have noticed the kernel update in Slackware64-14.2. I got myself a local copy of buildscript and source code for r8168 from SBo. The kernel update to version 4.4.111 killed my network again, so the problem persists for this kernel version too. I had to manually rebuild the package for r8168 against the new kernel, install it, then I got my network interfaces back.

Quote:

Originally Posted by FlinchX

... After the boot process is completed and I log in, here is the output of 'ifconfig -a'

Code:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.137.22  netmask 255.255.255.0  broadcast 192.168.137.255

        inet6 fe80::7285:c2ff:fe28:87ab  prefixlen 64  scopeid 0x20<link>

        ether xx:xx:xx:xx:xx:xx txqueuelen 1000  (Ethernet)

...

...

Code:

Link-local:    fe80::7285:c2ff:fe28:87ab

Mac:          70:85:C2:28:87:AB

@MadMaverick9 full disclosure hurts egos :)