Sorry, they were down, when wlan0 is up:
wlan0 IEEE 802.11abg Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
wlan0 Link encap:Ethernet HWaddr 00:80:48:47:52:DC
inet addr:10.2.0.10 Bcast:10.2.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Is there a way to verify that rfkill really is disabled? I've compiled the
linux kernel
with "CONFIG_RFKILL is not set" is that enough?
However, the radios aren't totally dead. With calibration debug turned on, I
can see the
noise floor changing when I attach/remove the antenna. So the radio doesn't
seem to be
completely dead, just almost.
If it's to any help, the system is a small embedded platform (ARM big-endian)
running a
openEmbedded linux dist. That might mean that I'm missing some vital support
software,
hotplug, udev etc, but could something like that really stop the communication
completely?
Regards,
Mattias
-----Original Message-----
From: bcopel...@gmail.com on behalf of Bob Copeland
Sent: Thu 9/24/2009 4:45 PM
To: Mattias Guhl
Cc: ath5k-devel@lists.ath5k.org
Subject: Re: [ath5k-devel] ath5k: No communication
On Wed, Sep 23, 2009 at 10:56 AM, Mattias Guhl
<mattias.g...@crlsweden.com> wrote:
> iwconfig:
> wlan0 IEEE 802.11abg Mode:Managed Access Point: Not-Associated
> Tx-Power=0 dBm
> communication. It's like the radios are totally disabled.
That may be the case - can you make sure rfkill is disabled?
Also txpower is 0 above, is that with the interface up?
--
Bob Copeland %% www.bobcopeland.com
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
