pcnet32 AMD PCnet no activity LED/FDX LED

Asked by Dan Cooper

Hello,
I have the following NIC:
06:01.0 Ethernet controller [0200]: Trident Microsystems 4DWave DX [1023:2000] (rev 26)
        Kernel driver in use: pcnet32
        Kernel modules: pcnet32
I know, this is rather strange, but it seems to be a real id of this card

It works fine, but only the 100 LED (indicating link speed of 100 MBit/s) works. There are 2 other LEDs: FDX (Full Duplex) and an activity LED.
Both of the LEDs work fine when I test them via ethtool: sudo ethtool -p enp6s1 120

This also happens on a fresh installation of Ubuntu
Is this a bug and where should I file it?
Kind regards

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What are you connecting the NIC to please?

Revision history for this message
Dan Cooper (pcfan1234) said :
#2

To the Full Duplex Fast Ethernet Port of my Cisco Router through my inhouse cabling.
It negotiates with Full Duplex Fast Ethernet, ethtool and Cisco IOS report this

mm@mm:~$ sudo ethtool enp6s1
[sudo] Passwort für mm:
Settings for enp6s1:
        Supported ports: [ TP MII ]
        Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
mm@mm:~$

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Sounds like the route is only advertising 100Mbps. Check the Cisco configuration and make sure that you have the latest firmware in the kit. What model Cisco device do you have please?

Revision history for this message
Dan Cooper (pcfan1234) said :
#4

Cisco IOS Software, C800 Software (C800-UNIVERSALK9-M), Version 15.9(3)M3, RELEASE SOFTWARE (fc1)
Cisco C886VA-K9 (revision 1.0)
It is the latest FW.

I don't know why it only offers 100 MBit/s, but I haven't set the speed option in the interface in IOS, but I could set it to 10 to try it out.

But I don't think this has something to do with the Activity LED of the NIC.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#6

So... No bug. It's running as expected

Revision history for this message
Dan Cooper (pcfan1234) said :
#7

I think you misunderstood me.
It is about that the Activity and FDX (Full Duplex) LED on the NIC in my PC do not light up as I expect them to.
The LEDs itself are ok, ethtool -p makes them flash.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#8

Your ethtool output shows the interface is 100/full

I don't know what else to advise. Sounds like an LED is weird. Are you seeing full duplex traffic?

Revision history for this message
Dan Cooper (pcfan1234) said :
#9

That's what I'm asking for. The LED is electrically working, I can use ethtool -p ifname to make FDX (indicating Full Duplex) and ACT (Activity) flashing, but both are dark in normal operation, but they should light up.

I thought this might by a driver (kernel module) issue.
I might also boot another OS and try it there.

Revision history for this message
Launchpad Janitor (janitor) said :
#10

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.