GTVincent Tux's lil' helper
![Tux's lil' helper Tux's lil' helper](/images/ranks/rank_rect_1.gif)
Joined: 26 Oct 2002 Posts: 91 Location: Las Vegas, NV
|
Posted: Mon Jan 16, 2006 4:51 am Post subject: ifconfig reports an enormous amount of errors |
|
|
I'm noticing an enormous amount of RX errors when requesting the network status using ifconfig:
ath0 Link encap:Ethernet HWaddr 00:11:95:91:C1:6C
inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20550 errors:221326 dropped:0 overruns:0 frame:221326
TX packets:15040 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:24175654 (23.0 Mb) TX bytes:2213100 (2.1 Mb)
Interrupt:217 Memory:ffffc200100a0000-ffffc200100b0000
The amount of errors goes up with 5 per second or so. The network adapter is a D-Link using an Atheros chip:
01:07.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01)
Subsystem: D-Link System Inc D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.B)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 217
Region 0: Memory at ea000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
I used to have this card in a 32 bit AMD machine using ndiswrapper, where it just got unmanagable because ndiswrapper would report the resetting of eth0 all the time, so I bought a new card for that machine. Now it's in an amd64 machine, using the madwifi drivers since ndiswrapper won't be able to use the 32 bit windows drivers that came with the card.
Question is: what causes all these errors? Is this card (about to be) broken? Or is there something in the madwifi drivers that could fix the errors? |
|