Re: airport wireless problems
On 3 Jul, this message from Jamie Wilkinson echoed through cyberspace:
> This one time, at band camp, Jamie Wilkinson wrote:
>>eth1: Unknown information frame received (type f202).
>
> I'm getting this message about 8 times a minute from all the APs I've
> tried to connect to.
I've not seen that message. I'm using an Airport card on a first-gen
TiBook, with mostly bad results. I need to be litterally next to the
Airport base station in order to make it work; otherwise I get these
messages:
Jul 4 20:51:02 pooh kernel: eth1: New link status: AP In Range (0005)
Jul 4 20:51:04 pooh kernel: eth1: New link status: AP Out of Range (0004)
Jul 4 20:51:04 pooh kernel: eth1: New link status: AP In Range (0005)
Jul 4 20:51:10 pooh kernel: eth1: New link status: AP Out of Range (0004)
Jul 4 20:51:10 pooh kernel: eth1: New link status: AP In Range (0005)
Jul 4 20:51:12 pooh kernel: eth1: New link status: AP Out of Range (0004)
Jul 4 20:51:12 pooh kernel: eth1: New link status: AP In Range (0005)
Jul 4 20:51:14 pooh kernel: eth1: New link status: AP Out of Range (0004)
etc...
This was with the machine completely idle and unattended, so the radio
part should have been in a stable environment (nobody passing between
base and card).
> Please, if anyone is using their builtin airport card using 2.4.21-ben2
> say so, so I have some datapoints to compare to. lspci and dmesg
> output when the module is loaded would be useful too.
Close to the base station, my results are OK. Further away, its
absolutely unuseable. It hasn't always been that way, therefore I
suspect either hardware problem (maybe a lose cable somewhere...) or a
firmware bug. OS X does the same, by the way... doesn't work either.
Here are lspci (why do you need that one?) and dmesg when loading the
module:
pooh:~# lspci
00:0b.0 Host bridge: Apple Computer Inc. UniNorth AGP
00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02)
10:0b.0 Host bridge: Apple Computer Inc. UniNorth PCI
10:17.0 Class ff00: Apple Computer Inc. KeyLargo Mac I/O (rev 03)
10:18.0 USB Controller: Apple Computer Inc. KeyLargo USB
10:19.0 USB Controller: Apple Computer Inc. KeyLargo USB
10:1a.0 CardBus bridge: Texas Instruments PCI1211
24:0b.0 Host bridge: Apple Computer Inc. UniNorth PCI
24:0e.0 Class ffff: Apple Computer Inc. UniNorth FireWire (rev ff)
24:0f.0 Ethernet controller: Apple Computer Inc. UniNorth GMAC (rev 01)
hermes.c: 4 Dec 2002 David Gibson <hermes@gibson.dropbear.id.au>
orinoco.c 0.13b (David Gibson <hermes@gibson.dropbear.id.au> and others)
airport.c 0.13b (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Airport at physical address 80030000
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:12:42:8C
eth1: Station name "HERMES I"
eth1: ready
airport: card registered for interface eth1
eth1: New link status: Connected (0001)
(and shortly after the In Range/Out of Range dance starts...)
I started getting Tx excessive retries messages sometime late last year.
I believe that problem was caused by a buggy firmware. I had a
discussion on this same list about my problems sometime ago:
http://lists.debian.org/debian-powerpc/2003/debian-powerpc-200301/threads.html#00187
Or see this thread:
http://lists.debian.org/debian-powerpc/2003/debian-powerpc-200302/threads.html#00378
Cheers
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
Reply to: