Bug 1006820

lspci output:
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M]
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
08:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

When you re-plug the cable, please open a terminal and report the output of the following commands:

sudo ethtool <interface name of your ethernet device>

cat /sys/class/net/<interface name of your ethernet device>/carrier

Many thanks for your reply. Here is the info:

# ifconfig
em1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet6 fe80::baca:3aff:fedf:9185  prefixlen 64  scopeid 0x20<link>
        ether b8:ca:3a:df:91:85  txqueuelen 1000  (Ethernet)
        RX packets 133532  bytes 125905231 (120.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 129194  bytes 80585045 (76.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 545  bytes 22397 (21.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 545  bytes 22397 (21.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp8s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.x  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::62xx:xxxx:fece:c4df  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:c4:df  txqueuelen 1000  (Ethernet)
        RX packets 14720  bytes 11269799 (10.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13523  bytes 6881818 (6.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@tklaptop ~]# ethtool em1
Settings for em1:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available
[root@tklaptop ~]# cat /sys/class/net/em1/carrier 
0

PS: Local IP and ethernet addresses have been changed by me.

Ok, this is a kernel driver problem.  If the kernel driver is working correctly, then after plugging the cable in, /sys/class/net/em1/carrier should be '1' and you should see "RUNNING" in the ifconfig flags.  This indicates the driver does not correctly notify the kernel networking layer of changes in the carrier state.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Thank you!  For the first time it worked correctly. I removed the ethernet cable, NetworkManager detected it.. Re-inserted it, it also detected it.

Thanks for letting us know.