Red Hat Bugzilla – Bug 999571
2nd network card no longer accessible/usable
Last modified: 2014-04-30 08:51:21 EDT
Description of problem:
This machine has 2 network cards. pcie card: D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter (rev 13) [works fine] and on the MB Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03) [it may have stopped working with the 3.10.* kernels] Immediately after the install, both worked fine. After the first kernel update, the realtek card stopped working altogether. I have tried allowing NetworkManager to control the card and not doing so (both ways work under fc 17).
To check that the card is working, I put the old root (drive) file system from fedora 17 back in place, and when I booted, both cards came up and worked as expected - and did so for about 6 hours before I swapped the drives back and went back to fedora 19.
I'm not sure whether this is a NetworkManager problem, a kernel problem, a library problem or some other network-specific problem. So the NetworkManager "component selection" above is a best-guess approximation.
manually setting the routing for the card does not help at all (or appear to work). The D-link card controls the external interfaces (ISP, other non-local systems) and the Realtek card is on the local (192.168.1.0) network.
Version-Release number of selected component (if applicable):
Not sure it's relevent but:
kernel-3.10.7-200.fc19.x86_64 (same as with all other 3.10.* x86_64 kernels)
Happens every time
Steps to Reproduce:
1.Reboot the machine (or restart network and NetworkManager)
D-Link (sky) card works as expected
Realtek card cannot contact anything on its network.
Both cards should work as expected
Immediately after the initial install, both cards worked perfectly. But after running yum update, the problem appeared. Since there were > 400 updates in that first batch I don't have a clue which of them triggered the problem.
*** Bug 999572 has been marked as a duplicate of this bug. ***
*** Bug 999573 has been marked as a duplicate of this bug. ***
Could you please get the following data?
$ lspci -vvnn | grep Network
$ ip link
$ NetworkManager log messages showing NM startup (/var/log/messages)
As the problem went away when I went from FC19 to FC20 I'm going to say that it was apparently fixed at some point (either intentionally or otherwise).
As I can no longer reproduce the bug, I recommend that this bug be closed.
Closing per comment #4.