[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Problem with TP-Link network card



Hi all!

Yesterday I had a power outage in my workplace and when the power was
restored, I noticed I did not have Internet access.

In reviewing the DSL router, I saw the "Ethernet" LED representing the
connection to the computer behind it, a PC firewall with Debian Jessie,
was turned off.

Apparently, the interface on Jessie side had no link. The network
interface is given by a PCI card with Realtek chipset RTL8139D that I'm
using since June 2008 without problems on this computer. It went through
several Debian versions and it was running smoothly with Jessie before
this incident. In fact, in the last update of the kernel that I have
applied (the one published by Salvatore Bonaccorso on December 17), I
restarted the operating system without downside.

I was looking at the syslog and it seems that the link comes and goes:

------------------------------------------------------------------------
(...)
Jan 15 21:47:24 alderamin kernel: [  249.092973] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:47:24 alderamin kernel: [  249.114731] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:10 alderamin kernel: [  295.226378] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:10 alderamin kernel: [  295.245295] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:14 alderamin kernel: [  299.105773] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:14 alderamin kernel: [  299.117529] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:23 alderamin kernel: [  307.755787] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:23 alderamin kernel: [  307.759521] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:29 alderamin kernel: [  314.046708] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:29 alderamin kernel: [  314.055246] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:49:01 alderamin kernel: [  346.182821] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:49:01 alderamin kernel: [  346.184420] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:49:36 alderamin kernel: [  380.625602] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:49:36 alderamin kernel: [  380.628902] 8139too 0000:00:09.0
eth1: link down
(...)
------------------------------------------------------------------------

To rule out a problem in the DSL router or the network cable, I
unplugged the end connected to the Jessie firewall and plugged it into
my notebook (which also uses Debian Jessie). In this case it is an Intel
network interface:

------------------------------------------------------------------------
$ lspci | grep -i ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
------------------------------------------------------------------------

Here everything runs smoothly. So this leads me to think it's something
on the side of the Jessie firewall.

The strange part is that if I set the card into 10Mbps, the link becomes up:

# mii-tool eth0 -F 10baseT-FD
# rmmod 8139too
# modprobe 8139too

------------------------------------------------------------------------
# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 10Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
------------------------------------------------------------------------
# ethtool -s eth1 speed 100
------------------------------------------------------------------------
# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no
------------------------------------------------------------------------
# ethtool -s eth1 speed 10
------------------------------------------------------------------------
# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 10Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
------------------------------------------------------------------------

In fact, I tested it with a new TP-Link card with the same Realtek
chipset and I have observed the same behavior.

Any idea what could be the problem?


Thank you in advance for your reply

Best regards,
Daniel

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: