Re: airport wireless problems
This one time, at band camp, Jamie Wilkinson wrote:
>This one time, at band camp, Jamie Wilkinson wrote:
>>This one time, at band camp, Jamie Wilkinson wrote:
>>>So, still no joy with the wireless yet, which is sad -- in January it was
>>>working brilliantly.
>>
>>Actually, I remember now having done a MacOS X software update in the last
>>month or so which ISTR had an Airport firmware update in it. Perhaps thats
>>the cause of the problem?
>>
>>Ready to provide more information on request...
>
>
>Ben, any chance of the 0.13e orinoco driver getting backported from 2.5 into
>your 2.4 tree?
I copied the wireless code -- i.e. the source code in drivers/net/wireless
-- from 2.5.73 to my local 2.4.21-ben2 tree, and applied the
iw241_we16-6.diff patch for the wireless extensions version 16 code, and
rebuilt. I also turned on the orinoco debug flag.
Here's the output of dmesg after I run ifup eth1, with the correct essid and
enc key set in /etc/network/interfaces:
orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
airport.c 0.13e (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Airport at physical address 80030000
eth1: -> orinoco_init()
eth1: Station identity 001f:0001:0008:0046
eth1: Looks like a Lucent/Agere firmware version 8.70
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:30:65:04:C4:B0
eth1: Station name "HERMES I"
eth1: ready
eth1: <- orinoco_init()
airport: card registered for interface eth1
eth1: -> orinoco_ioctl()
eth1: <- orinoco_ioctl()
eth1: -> orinoco_ioctl()
eth1: -> orinoco_ioctl_getiwrange()
eth1: <- orinoco_ioctl_getiwrange()
eth1: <- orinoco_ioctl()
...
eth1: Unknown information frame received (type f202).
eth1: -> orinoco_xmit()
eth1: <- orinoco_xmit()
eth1: Unknown information frame received (type f202).
eth1: -> orinoco_xmit()
eth1: <- orinoco_xmit()
eth1: Unknown information frame received (type f202).
eth1: -> orinoco_xmit()
eth1: <- orinoco_xmit()
eth1: Unknown information frame received (type f202).
...
and that's followed by a lot of f202 packets and orinoco_xmit()s.
still no sign of a connection to the AP though.
eth1 IEEE 802.11-DS ESSID:"AP" Nickname:"willow"
Mode:Managed Frequency:2.412GHz Access Point: 44:44:44:44:44:44
Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry limit:4 RTS thr:off Fragment thr:off
Encryption key:xxxx
Power Management:off
Link Quality:0/92 Signal level:134/153 Noise level:134/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
--
jaq@debian.org http://people.debian.org/~jaq
Reply to: