It's been a while since the release of 3.10 (around June 2013) when one bloke needlessly broke the driver (yeah, damn you!), and all hail the developer who finally fixed it (all hail, all hail!!).
Marking this thread as solved.
]]>Thanks for the update, misc.
]]>I did notice that, since I use network bridging with kvm, the bridge interface registers stats in /proc/net/dev. My guess would be that the bridge module is handling this and not the alx driver. I also don't know how accurate the data is.
I know this doesn't line up with exactly what you want but maybe it might help.
]]>Compare main.c from the kernel commit with alx_main.c as it was in the dkms driver; no more update_hw_stats etc.
edit:Ah, after looking at the mailing list with your bug report I see that he's already aware of the issue.
]]>Edit: At this time, kernel 3.10.5 carries the same problem. I've filed a bug report with the maintainers. Hopefully it won't take too long to fix this.
]]>I'm having the same problem. Before kernel 3.10 I had to compile the driver from source. Networking and the following conkyrc lines worked:
Down ${downspeed enp5s0}/s ${alignr}Up ${upspeed enp5s0}/s
${downspeedgraph enp5s0 25,107} ${alignr}${upspeedgraph enp5s0 25,107}
Total ${totaldown enp5s0} ${alignr}Total ${totalup enp5s0}
The output of ip link command:
[username@hostname ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 90:2b:34:d1:d5:64 brd ff:ff:ff:ff:ff:ff
My conkyrc has the correct interface's name but still not working.
Has anyone progressed on this issue?
Thanks all!
]]>Networking works fine, though.
]]>In the future, please use the 'report' link and leave a note to the moderators asking us to move the thread to another forum.
Thank You.
]]>