Tx Error

Nigel Jones jonesn at hursley.ibm.com
Fri Jan 11 20:21:26 EST 2002


Hi,
 I'm using the orinoco driver 0.9a under RH 7.2 with pcmcia-cs-3.1.29,
kernel 2.4.12 & a D-Link DWL-650 pccard at 8c3 firmware level (prism 2
chipset).

Configuration is using 802.11b ad-hoc with 128bit WEP.

Only 2 machines in net. Peer runs latest intersil w2k drivers for the same
card (from SMC at the time)

In my linux messages log I get errors like:

Jan 11 07:59:39 localhost kernel: eth0: Tx error (FID=041A)!
Jan 11 07:59:50 localhost kernel: eth0: Tx error (FID=05F1)!
Jan 11 07:59:50 localhost kernel: eth0: Tx error (FID=0207)!
Jan 11 07:59:55 localhost kernel: eth0: Tx error (FID=0536)!
...
Jan 11 08:06:24 localhost kernel: eth0: Tx error (FID=01B1)!
Jan 11 08:06:25 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan 11 08:06:25 localhost kernel: eth0: Tx timeout! Resetting card.
Jan 11 08:06:25 localhost kernel: About to write key 0, keylen=13
Jan 11 08:06:25 localhost kernel: About to write key 1, keylen=13
Jan 11 08:06:25 localhost kernel: About to write key 2, keylen=13
Jan 11 08:06:25 localhost kernel: About to write key 3, keylen=13
Jan 11 08:06:25 localhost kernel: eth0: Error -110 writing packet header to
BAP
Jan 11 08:06:25 localhost last message repeated 3 times
Jan 11 08:06:25 localhost kernel: eth0: Tx error (FID=010F)!
Jan 11 08:06:25 localhost kernel: eth0: Tx error (FID=0136)!
....
Jan 11 08:06:44 localhost kernel: eth0: Tx error (FID=0186)!
Jan 11 08:06:45 localhost kernel: eth0: Tx error (FID=01F3)!
Jan 11 08:06:46 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan 11 08:06:46 localhost kernel: eth0: Tx timeout! Resetting card.
Jan 11 08:06:46 localhost kernel: About to write key 0, keylen=13
Jan 11 08:06:46 localhost kernel: About to write key 1, keylen=13
Jan 11 08:06:46 localhost kernel: About to write key 2, keylen=13

and this pretty much continues.the Tx errors occuring every few seconds

The card isn't always reset
I *think* this may have started when I enabled 128 bit WEP. I'll have to
disable to see.
-- Just did this. No difference!

Here's my config:
eth0      IEEE 802.11-DS  ESSID:"????"  Nickname:"???"
          Mode:Ad-Hoc  Frequency:2.452GHz  Cell: 52:CA:65:??:??:??
Bit Rate:11Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:????-????-????-????-????-????-?? Encryption
mode:rest
ricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  invalid crypt:1933  invalid misc:0

??? are my entries

The invalid crypt remains fairly constant - much of the churn was when I was
fiddling with the config

On WIndows I have
adhoc demo: off
authentication algorithm: open system
Channel: 9
driver ibss: enabled
driver polling: disabled
fragmentation: 2432
listen interval: 3
network: 802.11b adhoc
powersave: disabled
preamble: auto
rts: 2432
ssid: ???
transmit: auto
wep: 128 bit
wep passphrase any (don't think this is used - I've entered my own key!)




Thanks,

--
Nigel Jones
jonesn at hursley.ibm.com






More information about the wireless mailing list