[ath9k-devel] Constant AP dropout

[ath9k-devel] Constant AP dropout

[Tyler W. Mills]

wlan0: associate with AP 00:1f:41:a8:bc:59
wlan0: RX ReassocResp from 00:1f:41:a8:bc:59 (capab=0x31 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)
wlan0: deauthenticated
wlan0: authenticate with AP 00:1f:41:a8:bc:59
wlan0: authenticated
wlan0: associate with AP 00:1f:41:a8:bc:59
wlan0: RX ReassocResp from 00:1f:41:a8:bc:59 (capab=0x31 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)

I get this every few minutes while associated with my AP.

WPA2/TKIP encryption, this has only started happening with the latest
kernel in F10.

[tyler at parabola ~]$ uname -a
Linux parabola 2.6.27.5-113.fc10.x86_64 #1 SMP Mon Nov 17 04:03:45 EST
2008 x86_64 x86_64 x86_64 GNU/Linux

Reloading ath9k has no effect, still getting constant dropouts.

Should I try building the latest driver from source?

Thanks

-- 
':wq' - The right way to close a file

[ath9k-devel] Constant AP dropout

[Jouni Malinen]

On Wed, 2008-11-19 at 09:41 -0800, Tyler W. Mills wrote:
> wlan0: associated
> wlan0: disassociating by local choice (reason=3)

> I get this every few minutes while associated with my AP.
> 
> WPA2/TKIP encryption, this has only started happening with the latest
> kernel in F10.

Are you using wpa_supplicant as the supplicant? Do you start it
manually? Do you have NetworkManager running? If yes to all these, try
stopping NetworkManager.. It seems to really like to keep the connection
down if the connection was not initiated by it.

- Jouni

[ath9k-devel] Constant AP dropout

[Tyler W. Mills]

I'm only using NetworkManager, to initiate and reconnect after it drops
out.

Thanks

On Wed, Nov 19, 2008 at 11:54:58AM -0600, Jouni Malinen wrote:
> On Wed, 2008-11-19 at 09:41 -0800, Tyler W. Mills wrote:
> > wlan0: associated
> > wlan0: disassociating by local choice (reason=3)
> 
> > I get this every few minutes while associated with my AP.
> > 
> > WPA2/TKIP encryption, this has only started happening with the latest
> > kernel in F10.
> 
> Are you using wpa_supplicant as the supplicant? Do you start it
> manually? Do you have NetworkManager running? If yes to all these, try
> stopping NetworkManager.. It seems to really like to keep the connection
> down if the connection was not initiated by it.
> 
> - Jouni
> 
> 

-- 
':wq' - The right way to close a file

[ath9k-devel] Constant AP dropout

[Tyler W. Mills]

There was a kernel update for Fedora 10, and with it, ath9k was no
longer working.  I built my own from the latest available download, and
now get this error when trying to associate via NetworkManager:

ath9k_bss_assoc_info: Unable to set channel
wlan0: No ProbeResp from current AP 00:1f:41:a4:3b:19 - assume out of
range
wlan0: authenticate with AP 00:1f:41:96:42:79
wlan0: authenticated
wlan0: associate with AP 00:1f:41:96:42:79
wlan0: RX ReassocResp from 00:1f:41:96:42:79 (capab=0x431 status=0
aid=1)
wlan0: associated
ath_set_channel: unable to reset channel 1 (2412Mhz) flags 0x300e0 hal
status 4294967274
ath9k_bss_assoc_info: Unable to set channel
wlan0: No ProbeResp from current AP 00:1f:41:96:42:79 - assume out of
range
wlan0: authenticate with AP 00:1f:41:96:42:79
wlan0: authenticate with AP 00:1f:41:96:42:79
wlan0: deauthenticated (Reason: 2)
wlan0: direct probe to AP 00:1f:41:96:42:79 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:1f:41:96:42:79
wlan0: authenticate with AP 00:1f:41:96:42:79
wlan0: authentication with AP 00:1f:41:96:42:79 timed out

I am able to connect to unsecured networks with ease however.  The AP in
question is in the same room I am in as well, with about 77/100 signal
quality.

On Wed, Nov 19, 2008 at 11:58:18AM -0600, Tyler W. Mills wrote:
> I'm only using NetworkManager, to initiate and reconnect after it drops
> out.
> 
> Thanks
> 
> On Wed, Nov 19, 2008 at 11:54:58AM -0600, Jouni Malinen wrote:
> > On Wed, 2008-11-19 at 09:41 -0800, Tyler W. Mills wrote:
> > > wlan0: associated
> > > wlan0: disassociating by local choice (reason=3)
> > 
> > > I get this every few minutes while associated with my AP.
> > > 
> > > WPA2/TKIP encryption, this has only started happening with the latest
> > > kernel in F10.
> > 
> > Are you using wpa_supplicant as the supplicant? Do you start it
> > manually? Do you have NetworkManager running? If yes to all these, try
> > stopping NetworkManager.. It seems to really like to keep the connection
> > down if the connection was not initiated by it.
> > 
> > - Jouni
> > 
> > 
> 
> -- 
> ':wq' - The right way to close a file
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

-- 
':wq' - The right way to close a file

[ath9k-devel] Constant AP dropout -LINKS

[Brian]

Tyler,
1)
During an email conversation with Luis he provided me with a whole
series of links to good stuff, see below
One of which applies to Networkmanager

2) on 4/11/08 Luis posted a patch to this list which may be applicable.
I used it and it worked.

3) During my testing I found that using WPA_GUI helped.
This may not apply to all but I found that my link would keep dropping
out, because it got a deathentication request. This turned out to be a
wrong PSK key. I hasten to add that my key was not put in wrong, it just
was not accepted. The way I got out of it was to use wpa_gui to re-input
the key.

4) All the above is now on a Suse 11.0 with the git wireless kernel
 2.6.28-rc5-wl #10 SMP
Again this may only apply to SUSE but the new kernel seems to use a
different .conf file. It no longer uses the the one in
/etc/wpa_supplicant but builds its own in /etc.
In my case it creates /etc/wpa_supplicant.conf

I have not tracked down yet exactly how it does this or where it gets
its info from to build the file. Working on it:)

HTH
Brian


See this to find out how to disable NetworkManager and wpa_supplicant
(which NM runs):

http://wireless.kernel.org/en/users/Documentation/Reporting_bugs

http://wireless.kernel.org/en/developers/Documentation/git-guide
http://wireless.kernel.org/en/developers/Documentation


Just a note you should install CRDA now that you are on 2.6.28

http://wireless.kernel.org/en/developers/Regulatory/CRDA

Also get iw:

http://wireless.kernel.org/en/users/Documentation/iw


You may want to subscribe to the entire wiki, I just updated the git
guide yesterday with new found fun stuff. You can subscribe to all pages
by going to:

http://wireless.kernel.org/welcome?action=userprefs&sub=notification












Tyler W. Mills wrote:
> I'm only using NetworkManager, to initiate and reconnect after it drops
> out.
> 
> Thanks
> 
> On Wed, Nov 19, 2008 at 11:54:58AM -0600, Jouni Malinen wrote:
>> On Wed, 2008-11-19 at 09:41 -0800, Tyler W. Mills wrote:
>>> wlan0: associated
>>> wlan0: disassociating by local choice (reason=3)
>>> I get this every few minutes while associated with my AP.
>>>
>>> WPA2/TKIP encryption, this has only started happening with the latest
>>> kernel in F10.
>> Are you using wpa_supplicant as the supplicant? Do you start it
>> manually? Do you have NetworkManager running? If yes to all these, try
>> stopping NetworkManager.. It seems to really like to keep the connection
>> down if the connection was not initiated by it.
>>
>> - Jouni
>>
>>
> 

[ath9k-devel] Constant AP dropout -LINKS

[Luis R. Rodriguez]

On Wed, Nov 19, 2008 at 02:34:56PM -0800, Brian wrote:
> Tyler,
> 1)
> During an email conversation with Luis he provided me with a whole
> series of links to good stuff, see below
> One of which applies to Networkmanager
> 
> 2) on 4/11/08 Luis posted a patch to this list which may be applicable.
> I used it and it worked.
> 
> 3) During my testing I found that using WPA_GUI helped.
> This may not apply to all but I found that my link would keep dropping
> out, because it got a deathentication request. This turned out to be a
> wrong PSK key. I hasten to add that my key was not put in wrong, it just
> was not accepted. The way I got out of it was to use wpa_gui to re-input
> the key.
> 
> 4) All the above is now on a Suse 11.0 with the git wireless kernel
>  2.6.28-rc5-wl #10 SMP
> Again this may only apply to SUSE but the new kernel seems to use a
> different .conf file. It no longer uses the the one in
> /etc/wpa_supplicant but builds its own in /etc.
> In my case it creates /etc/wpa_supplicant.conf
> 
> I have not tracked down yet exactly how it does this or where it gets
> its info from to build the file. Working on it:)
> 
> HTH
> Brian
> 
> 
> See this to find out how to disable NetworkManager and wpa_supplicant
> (which NM runs):
> 
> http://wireless.kernel.org/en/users/Documentation/Reporting_bugs
> 
> http://wireless.kernel.org/en/developers/Documentation/git-guide
> http://wireless.kernel.org/en/developers/Documentation
> 
> 
> Just a note you should install CRDA now that you are on 2.6.28
> 
> http://wireless.kernel.org/en/developers/Regulatory/CRDA
> 
> Also get iw:
> 
> http://wireless.kernel.org/en/users/Documentation/iw
> 
> 
> You may want to subscribe to the entire wiki, I just updated the git
> guide yesterday with new found fun stuff. You can subscribe to all pages
> by going to:
> 
> http://wireless.kernel.org/welcome?action=userprefs&sub=notification
> 
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

So we had over 40 patches pending which John just merged today. You
can do a git pull or wait for compat-wireless to get updated.

  Luis

[ath9k-devel] It Works!

[Brian]

Luis,

> So we had over 40 patches pending which John just merged today. You
> can do a git pull or wait for compat-wireless to get updated.
Took your suggestion and did a git-pull.

Did a recompile after carefully checking menuconfig again.
The only major thing I have done is to remove any reference to IPV6.

Rebooted and everything came up and WORKED!:)
Not sure what you changed but it has done the trick.

I have been up for about 30mins with no issues.
2.6.28-rc5-wl-W #11 SMP

With this result
Mode		Rate (Mbps)	Signal (%)
802.11n (2.4GHz)	78	100


So while I am happy the 11n is now working the rate does not seem to be
as expected.

ISSUES so far

1) When I do a ping there is about a 10-15sec delay before the responses
start coming back.

2) I cannot start WPA_GUI or WPA_CLI it comes back with
Selected interface 'wlan0.pid'
Trying to connect to '/var/run/wpa_supplicant/wlan0.pid'
Failed to open control connection to wpa_supplicant.
PING failed - trying to reconnect

The pid is correct.


So many thanks to the atheros team for getting ath9k going.

Brian

[ath9k-devel] It Works!

[Sujith]

Brian wrote:
> Did a recompile after carefully checking menuconfig again.
> The only major thing I have done is to remove any reference to IPV6.
> 
> Rebooted and everything came up and WORKED!:)
> Not sure what you changed but it has done the trick.
> 
> I have been up for about 30mins with no issues.
> 2.6.28-rc5-wl-W #11 SMP
> 
> With this result
> Mode		Rate (Mbps)	Signal (%)
> 802.11n (2.4GHz)	78	100
> 
> 
> So while I am happy the 11n is now working the rate does not seem to be
> as expected.
> 

I am assuming you are using HT20 ?

> ISSUES so far
> 
> 1) When I do a ping there is about a 10-15sec delay before the responses
> start coming back.
> 

This is an issue, and we are looking into this.

> 2) I cannot start WPA_GUI or WPA_CLI it comes back with
> Selected interface 'wlan0.pid'
> Trying to connect to '/var/run/wpa_supplicant/wlan0.pid'
> Failed to open control connection to wpa_supplicant.
> PING failed - trying to reconnect

Can you show your wpa_supplicant config ?

Sujith
-- 
http://sujith-m.blogspot.com

[ath9k-devel] Issues

[Brian]

Sujith,
> 
> I am assuming you are using HT20 ?
> 
Sorry, what is that? I did a git-pull about 18hours ago.

>> ISSUES so far
>>
>> 1) When I do a ping there is about a 10-15sec delay before the responses
>> start coming back.
>>
> 
> This is an issue, and we are looking into this.
> 
Ok, This could be generic. By that I mean I get a similar delay when I
log into my router. Subjective of course.



>> 2) I cannot start WPA_GUI or WPA_CLI it comes back with
>> Selected interface 'wlan0.pid'
>> Trying to connect to '/var/run/wpa_supplicant/wlan0.pid'
>> Failed to open control connection to wpa_supplicant.
>> PING failed - trying to reconnect
> 
> Can you show your wpa_supplicant config ?
Is their a show command?
In /var/run/wpa_supplicant-wlan0.conf

I have
ctrl_interface=/var/run/wpa_supplicant
network={
  scan_ssid=1
  ssid="dlink"
  key_mgmt=WPA-PSK
  psk="secret"
}

Brian

[ath9k-devel] Issues

[Sujith]

Brian wrote:
> Sorry, what is that? I did a git-pull about 18hours ago.

I meant the mode in which you have connected to the AP ( HT20/HT40 ).
Since you are operating in 2.4 Ghz, it probably is HT20, in which case
the numbers are not too bad.

But if your AP is dual-band, you can configure it to use HT40 in 5Ghz
and get improved throughput.

> >> 2) I cannot start WPA_GUI or WPA_CLI it comes back with
> >> Selected interface 'wlan0.pid'
> >> Trying to connect to '/var/run/wpa_supplicant/wlan0.pid'
> >> Failed to open control connection to wpa_supplicant.
> >> PING failed - trying to reconnect
> >
> > Can you show your wpa_supplicant config ?
> Is their a show command?
> In /var/run/wpa_supplicant-wlan0.conf
> 
> I have
> ctrl_interface=/var/run/wpa_supplicant
> network={
>   scan_ssid=1
>   ssid="dlink"
>   key_mgmt=WPA-PSK
>   psk="secret"
> }
> 

Does running wpa_supplicant manually connect to the network ?

Sujith

[ath9k-devel] Issues

[Brian]

Sujith,
> I meant the mode in which you have connected to the AP ( HT20/HT40 ).
> Since you are operating in 2.4 Ghz, it probably is HT20, in which case
> the numbers are not too bad.
> 
> But if your AP is dual-band, you can configure it to use HT40 in 5Ghz
> and get improved throughput.
> 
As mentioned that was a really good tip. However, just to be clear I am
currently running with the 40Mhz bandwidth(HT40?) at 2.5Ghz.
As far as I can see my router does not do 5Ghz.


>>>> 2) I cannot start WPA_GUI or WPA_CLI 
> Does running wpa_supplicant manually connect to the network ?
> 
Had another go at this  and started wpa_cli and got back

Selected interface 'wlan0.pid'
Could not connect to wpa_supplicant - re-trying

and it sits there and does nothing.

Are you supposed to be able to run the wpa_gui/cli if you have the
supplicant running in background?
Now that I have the system working, this is not a high priority but it
would be 'nice to have'.


3) A while back I reported that I was having problems getting certain
things to run in my SUSE 11 system. It turns out the problem was that
the .config file supplied with wireless testing has a lot of modules
turned off. I did a merge of my old config with the wireless-testing one
and now I have a full working system, but with the wireless kernel.

and this is the best result so far
Mode			Rate (Mbps)	Signal (%)
802.11n (2.4GHz)	216		94

Again many thanks to all for a great result,

Brian

[ath9k-devel] 2.6.28-rc6-wl

[Brian]

All,
Just installed this.

1) I had a few lockups with RC5. I worked out that it was mainly when I
tried to use Java in FF. probably not relevant to the driver.

2) Just tried a ping to my router and the responses come back straight
away. Also tried a ping to my ISP and that still appeared to take some
time, just checked again using the ip address and it was fine.
So it looks like this is fixed. Only the DNS is slow.

3) The rate is now 135Mbs. While this is slower than before it seems
more consistent. Only been up for an hour so a bit early to tell on
reliability.

4) I am still running without IPV6.

Is there any other tests I can run?

Brian

[ath9k-devel] Link drops out

[Brian]

All,
This has happened twice now and I am not sure what to collect to get
more info for you.

1) I fire up a wireless link from this machine to the router.
This is running 2.6.28.rc6.

Nov 29 10:08:41 L2 SuSEfirewall2: Error: iptables-batch failed,
re-running using iptables
Nov 29 10:08:41 L2 SuSEfirewall2: Firewall rules successfully set
Nov 29 10:08:46 L2 kernel: [   66.931665] TKIP decrypt: data(len=56) 00
20 01 a0 00 00 00 00 aa aa 03 00 00 00 08 06 00 01 08 00 06 04 00 01 00
1b 11 e9 b1 88 c0 a8 01 05 00 00 00 00 00 00 c0 a8 01 01 82 c8 9c 22 09
19 a8 11 df a5 57 23


2) When I first fire it up the link is extremely quick but then seems to
get progressively slower.

3) It takes a few hours but eventually the link drops.
This is what dmesg says.
00 00 00 00 c0 a8 01 01 90 58 70 ed e9 e1 db a1 af bb 19 5a
Nov 29 19:08:38 L2 kernel: [32458.714789] TKIP decrypt: iv16=0002
iv32=00000000
Nov 29 19:08:39 L2 kernel: [32459.714665] TKIP decrypt: data(len=56) 00
20 03 60 00 00 00 00 aa aa 03 00 00 00 08 06 00 01 08 00 06 04 00 01 00
1b 11 e9 b1 88 c0 a8 01 05 00 00 00 00 00 00 c0 a8 01 01 90 58 70 ed e9
e1 db a1 af bb 19 5a
Nov 29 19:08:39 L2 kernel: [32459.714741] TKIP decrypt: iv16=0003
iv32=00000000
Nov 29 19:08:42 L2 kernel: [32462.130305] wlan0: deauthenticated (Reason: 9)
Nov 29 19:08:43 L2 kernel: [32463.130065] wlan0: direct probe to AP
00:1c:f0:fb:6d:92 try 1
Nov 29 19:08:43 L2 kernel: [32463.134532] wlan0 direct probe responded
Nov 29 19:08:43 L2 kernel: [32463.134543] wlan0: authenticate with AP
00:1c:f0:fb:6d:92
Nov 29 19:08:43 L2 kernel: [32463.136485] wlan0: authenticated
Nov 29 19:08:43 L2 kernel: [32463.136496] wlan0: associate with AP
00:1c:f0:fb:6d:92
Nov 29 19:08:43 L2 kernel: [32463.139944] wlan0: RX ReassocResp from
00:1c:f0:fb:6d:92 (capab=0x431 status=0 aid=2)
Nov 29 19:08:43 L2 kernel: [32463.139954] wlan0: associated
[32459.714665] TKIP decrypt: data(len=56) 00 20 03 60 00 00 00 00 aa aa
03 00 00 00 08 06 00 01 08 00 06 04 00 01 00 1b 11 e9 b1 88 c0 a8 01 05
00 00 00 00 00 00 c0 a8 01 01 90 58 70 ed e9 e1 db a1 af bb 19 5a


So the link stayed up almost exactly 9 hours.


4) Both times is has happened after I have started another machine with
a wireless connection. Not sure this is relevant though.


5) I have tried restarting wlan0, wpa_suppicant, network restart, but
the only way I can get going again is to reboot.

6) I have the -dd flags turned on when wpa_supplicant starts and it goes
to a file. This shows(see below) that the problem appears to be the fact
that the ssid field is blank. Eventually both my APs get added to a
black list, then taken out and the cycle starts again.
I do not understand why the ssid comes up blank.
Where do you look for the contents of the blacklist?

Thanks,
Brian

Wireless event: cmd=0x8b19 len=8
Received 438 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
Try to find non-WPA AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
No APs found - clear blacklist and try again
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Removed BSSID 00:1c:f0:fb:6d:92 from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
Try to find non-WPA AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=8
Received 438 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
Try to find non-WPA AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Control interface directory not empty - leaving it behind
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6

[ath9k-devel] 2.6.28-rc6-wl update

[Brian]

All,
I have baked out to another suse 11.0 that uses everything the same but
not the wireless-testing kernel.
i.e I am still using the ath9k driver.

> 2) Just tried a ping to my router and the responses come back straight
> away. Also tried a ping to my ISP and that still appeared to take some
> time, just checked again using the ip address and it was fine.
> So it looks like this is fixed. Only the DNS is slow.
With this kernel all pings have  normal response.
With the wireless-testing kernel everything seemed to have a delay.
Pings, getting pages from the web sending mail.
All appears normal now.

> 
> 3) The rate is now 135Mbs. While this is slower than before it seems
> more consistent. Only been up for an hour so a bit early to tell on
> reliability.

I now have two wireless connections into the router and both appear
good, while they are operating.
I have had the link stop responding. i.e the network was up and appeared
ok but pings did not get a response.
This time though a /etc/init.d/network restart fixed the problem.

One thing I have noticed was that under the wireless-testing kernel I
was using the swap file. I never have used it in the past. Looks like
there may be a leak there. Can I check this somehow?

Thanks,
Brian

[ath9k-devel] 2.6.28-rc6-wl update2

[Brian]

All,
Had some problems with previous version so decide to upgrade.

Upgraded to, the git-pull gave me, bb42ffe..3b329bc  master-2008-11-24
Just did this in the last hour.

Congrats the first ping test confirmed the delay is GONE:)
Even when I did a ping to a name, the response was instantaneous.

I have even hit the magic 300 for the first time:)
SSID	MAC Address  IP Address	Mode		Rate(Mbps) Signal (%)
dlink	000FB5888888 0.0.0.0	802.11g		  54		66
dlink	001B11E99999 0.0.0.0	802.11n (2.4GHz)  300		96

I hope to get SUSE 11.1 soon, when I do I will try IW etc.

Please advise if there is something that needs testing/checking.

Just read that LED is supposed to be supported.
The leds on my cardbus are on (both constant) but that does not look right.
Do I have to include something in the config?

Thanks,
Brian