Problems with Airport (classic) card
Hello there,
In some of my last posts I was just spreading the love about Pismo
Powerbook and wrote something about how perfectly the airport works with
Linux ;)
Well, today I finally got my empty airport slot filled with an Airport
card, and I have some problems with it.
I have a rtl8180-based wifi PCI card in my desktop PC, the card supports
AP mode.
Dmesg shows that my Airport card has the 8.70 firmware installed, so
it's fairly new if not the latest.
The card I've been using before the Airport is Cisco Aironet 340 series,
it worked ok in Linux with the Realtek both in ad-hoc and AP modes.
When the desktop was running windows, I could only use the ad-hoc mode,
and got used to that.
First thing - when the airport is in ad-hoc mode I cannot read the
signal levels, even when the connection is up and working.
The ad-hoc mode on Airport works okay.
When I set the rtl8180 to AP mode, there is no way I can establish a
connection with the airport. When I bring the airport's interface (eth1
in my case) up, it's up for a few seconds and then dies. In dmesg it
looks like this:
Oct 20 14:10:56 opium kernel: eth1: New link status: Connected (0001)
Oct 20 14:10:58 opium kernel: eth1: New link status: Disconnected (0002)
As you see, it dies after like about 2 seconds.
Also, during these 2 seconds there is a strange signal level shown which
seems to be above 100%.
I couldn't use my card with a dedicated AP also.
I've tried the drivers that come with the kernel, and the standalone
ones from orinoco.nongnu.org
I've tried both monitor-mode patched versions and clean ones, I still
get the same thing. No way to connect to an access point.
Can anyone point me any direction? Any special values I should set via
iwpriv/iwconfig?
Kismet works nice with my card, ad-hoc mode works great too, both with
and without WEP, but no way to work in managed mode.
In managed mode, iIwconfig shows me a correct AP address for about a
second, then it changes to 44:44:44:44:44:44 (the default one?), for
about 4 seconds, then it sees the correct AP for one second, etc, etc...
Is it a matter of firmware?
I guess Benh has quite a big knowledge about that card :)
thanks in advance for any info,
owczi
--
[x]--Wojciech---owczi---Owczarek--WO111-RIPE--[_][+]
|--------- mailto: owczi|at|owczi|dot|net -------|
+-------------------- gg: #4245064 --------------+
Reply to: