LinuxQuestions.org - eth0 doesn't show traffic, but Atheros ethernet card works

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

- - eth0 doesn't show traffic, but Atheros ethernet card works (https://www.linuxquestions.org/questions/slackware-14/eth0-doesnt-show-traffic-but-atheros-ethernet-card-works-4175490134/)

eth0 doesn't show traffic, but Atheros ethernet card works

This is a strange issue that I can't understand. I can use the internet, upload and download just fine, but nothing shows up on any ethernet monitor.

Code:

bash-4.2$ /sbin/lspci -v

04:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)

        Subsystem: ASRock Incorporation Device 10a1

        Flags: bus master, fast devsel, latency 0, IRQ 45

        Memory at f0400000 (64-bit, non-prefetchable) [size=256K]

        I/O ports at e000 [size=128]

        Capabilities: <access denied>

        Kernel driver in use: alx

        Kernel modules: alx



bash-4.2$ /sbin/ifconfig

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

        inet 192.168.1.73  netmask 255.255.255.0  broadcast 192.168.1.255

        inet6 fe80::be5f:f4ff:fed2:f958  prefixlen 64  scopeid 0x20<link>

        ether bc:5f:f4:d2:f9:58  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 19  



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 202  bytes 18100 (17.6 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 202  bytes 18100 (17.6 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



bash-4.2$ cat /proc/interrupts

 45:      8451          0          0          0  PCI-MSI-edge      eth0

the RX and TX for eth0 are always 0.

I suspect a driver issue. I am using kernel 3.10.25. I don't remember if it worked with earlier kernels.

Any ideas ?

What networking management tool are you using? Wicd, dhcpcd, or networkmanager?

I'm using network manager ATM. If you think it makes a difference I can turn it off and connect manually using dhcpcd. I'll try it a bit later.

Quote:

Originally Posted by metaschima (Post 5091868)

I suspect a driver issue. I am using kernel 3.10.25. I don't remember if it worked with earlier kernels.

You're right. The alx driver was very recently mainlined (6/2013) by J. Berg based on a very basic driver proposed by Qualcomm/Atheros. Traffic counters have not been added yet.

--mancha

Quote:

Originally Posted by mancha (Post 5091970)

You're right. The alx driver was very recently mainlined (6/2013) by J. Berg based on a very basic driver proposed by Qualcomm/Atheros. Traffic counters have not been added yet.

--mancha

That might be it. I just built this desktop a few months ago, and it is new, so I guess the driver just isn't complete. I might try a newer kernel, but I would like a long-term kernel, so I'll wait a bit.

If you are running NetworkManager check the NM-Applet utility's built-in logs to see what usage has happened.

Quote:

Originally Posted by ReaperX7 (Post 5091987)

If you are running NetworkManager check the NM-Applet utility's built-in logs to see what usage has happened.

I've checked the menus but I don't see any logs.

I will e-mail the developers of the driver to see if this is a bug or not.

Quote:

Originally Posted by metaschima (Post 5091992)

I will e-mail the developers of the driver to see if this is a bug or not.

Not a bug. As that fellow mancha mentioned in post #4, traffic counters are not yet in the driver which is still very basic.

--mancha

Quote:

Originally Posted by mancha (Post 5091999)

Not a bug. As that fellow mancha mentioned in post #4, traffic counters are not yet in the driver which is still very basic.

--mancha

Yes, I saw that, but maybe e-mailing them will get them to look into it. Their git repo hasn't been updated since April 2013, so I don't see why I shouldn't send them an e-mail and see if they respond.

Hi, did you optain any response for this bug? I have the same for a Qualcomm Atheros QCA8172 Fast Ethernet

Nope, so I guess the monitor won't be working for a while. I could try to fix it myself, but I've never worked on drivers.

I just discovered and at least in Ubuntu 14.04 64 bits is a problem with the actual kernel.