Linux wireless drivers development
 help / color / mirror / Atom feed
* Re: Ath9k, single antenna on ar9280
From: Adrian Chadd @ 2011-10-15  9:48 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzd+8wq4Mw3Ww8jTOYNk-Q2EYOvtdgHPi=RMQqbJvJRZtdw@mail.gmail.com>

You'll have to ask Felix and others, but I think they're more generic
APIs to support things like AR9285 (and the relevant AR9300/AR9400
series NICs) which implement 1x1 but have "classic" style antenna
diversity.

Also, as I've discovered, you _can_ glue an antenna switch onto the
side of a MIMO NIC. Eg, I have an AR9220 based NIC (2x2:2) which has
three antennas, both the second and third are connected to chain 1 via
an antenna switch.



Adrian

^ permalink raw reply

* Re: ath9k: irq storm after suspend/resume
From: Adrian Chadd @ 2011-10-15 10:01 UTC (permalink / raw)
  To: Clemens Buchacher; +Cc: Mohammed Shafi, linux-wireless
In-Reply-To: <20111015093902.GA23520@ecki>

I've found some perhaps relevant bits of code here which force the
chip into and out of reset/sleep states.

It's possible that your BIOS doesn't fully reset the NIC upon startup.
It's also possible there are issues with the ath9k power save/resume
code. It's also possible they're all compounding to make things worse.
Are you able to completely and utterly disable any/all power saving on
ath9k, including APSM if you have it enabled?

Unfortunately the information I have is a bit sketchy. I'll do some
further digging (and hope I don't bug Atheros people too much :) to
see if I can extract out some more information about what's going on.

Thanks,


Adrian

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 10:02 UTC (permalink / raw)
  To: Adrian Chadd; +Cc: linux-wireless
In-Reply-To: <CAJ-VmonaBUTEKLghg8DJsqUpp6iR-R=pPuejUWwq=ukxt+utzg@mail.gmail.com>

Thanks. I'll ask him.

>>both the second and third are connected to chain 1 via
an antenna switch.

That's interesting. Could you give me a clue how to implement this?
Also after doing that, will it be enough to use only one physical
antenna connector?

2011/10/15 Adrian Chadd <adrian@freebsd.org>:
> You'll have to ask Felix and others, but I think they're more generic
> APIs to support things like AR9285 (and the relevant AR9300/AR9400
> series NICs) which implement 1x1 but have "classic" style antenna
> diversity.
>
> Also, as I've discovered, you _can_ glue an antenna switch onto the
> side of a MIMO NIC. Eg, I have an AR9220 based NIC (2x2:2) which has
> three antennas, both the second and third are connected to chain 1 via
> an antenna switch.
>
>
>
> Adrian
>

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Adrian Chadd @ 2011-10-15 11:29 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzdJiBp742nrgb4eGwRDQO_nBgKNU1v405D_4SwBYPJ3S=A@mail.gmail.com>

On 15 October 2011 18:02, Stanislav Demakov <s.demakov@gmail.com> wrote:
> Thanks. I'll ask him.
>
>>>both the second and third are connected to chain 1 via
> an antenna switch.
>
> That's interesting. Could you give me a clue how to implement this?
> Also after doing that, will it be enough to use only one physical
> antenna connector?

It depends on how it's all wired up. And yes, once you know how it's
wired up and which antenna configuration words to program in, you can
run just one of three antennas.



adrian

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 11:33 UTC (permalink / raw)
  To: Adrian Chadd; +Cc: linux-wireless
In-Reply-To: <CAJ-Vmo=PFEzagWG9ddR5dYoDej7yJyHCXCVTX_67W4QNYaqihg@mail.gmail.com>

If you tell me how exactly you did it on the AR9220 in your case, this
will be a good example at least.

2011/10/15 Adrian Chadd <adrian@freebsd.org>:
> On 15 October 2011 18:02, Stanislav Demakov <s.demakov@gmail.com> wrote:
>> Thanks. I'll ask him.
>>
>>>>both the second and third are connected to chain 1 via
>> an antenna switch.
>>
>> That's interesting. Could you give me a clue how to implement this?
>> Also after doing that, will it be enough to use only one physical
>> antenna connector?
>
> It depends on how it's all wired up. And yes, once you know how it's
> wired up and which antenna configuration words to program in, you can
> run just one of three antennas.
>
>
>
> adrian
>

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Felix Fietkau @ 2011-10-15 11:38 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzd+TcY+n90RBMU+Cpp0Bt9d_eAGgY4yffO+PSStWSzbf-Q@mail.gmail.com>

On 2011-10-14 5:46 PM, Stanislav Demakov wrote:
> I've noticed that set_antenna and get_antenna functionality was added
> to the ath9k driver. But iw phy set antenna command still isn't
> working.
Did you try bringing down all active wlanX interfaces belonging to that 
phy before running that command?

- Felix

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 11:45 UTC (permalink / raw)
  To: Felix Fietkau; +Cc: linux-wireless
In-Reply-To: <4E9970A6.10305@openwrt.org>

Ok, just have tried:

ifconfig wlan0 down

and then tested it:

iw phy phy0 set antenna all all

but it's only showing iw help as before.
I'm using the latest compiled compat-wireless.

2011/10/15 Felix Fietkau <nbd@openwrt.org>:
> On 2011-10-14 5:46 PM, Stanislav Demakov wrote:
>>
>> I've noticed that set_antenna and get_antenna functionality was added
>> to the ath9k driver. But iw phy set antenna command still isn't
>> working.
>
> Did you try bringing down all active wlanX interfaces belonging to that phy
> before running that command?
>
> - Felix
>

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Adrian Chadd @ 2011-10-15 11:49 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzd+Lzj5CD7iUShDBg1HxRYiGyxCpWHeC-T6MM7NRLFT=qg@mail.gmail.com>

On 15 October 2011 19:33, Stanislav Demakov <s.demakov@gmail.com> wrote:
> If you tell me how exactly you did it on the AR9220 in your case, this
> will be a good example at least.

I haven't yet written to code for FreeBSD/ath9k. Sorry.



Adrian

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Felix Fietkau @ 2011-10-15 11:52 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzd+ou1DXL_d_W0dvTcYrNMfH9NjSoFUa=07fE4BYJ+N7bQ@mail.gmail.com>

On 2011-10-15 1:45 PM, Stanislav Demakov wrote:
> Ok, just have tried:
>
> ifconfig wlan0 down
>
> and then tested it:
>
> iw phy phy0 set antenna all all
>
> but it's only showing iw help as before.
> I'm using the latest compiled compat-wireless.
Try using "1 1" instead of "all all".
Are you using the latest iw version?

- Felix

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 12:13 UTC (permalink / raw)
  To: Felix Fietkau; +Cc: linux-wireless
In-Reply-To: <4E997413.8010008@openwrt.org>

Ok, I've compiled and installed iw from git. Now I have this (wlan0 is down):

sudo iw phy phy0 set antenna 1 1

command failed: Operation not supported (-95)


2011/10/15 Felix Fietkau <nbd@openwrt.org>:
> On 2011-10-15 1:45 PM, Stanislav Demakov wrote:
>>
>> Ok, just have tried:
>>
>> ifconfig wlan0 down
>>
>> and then tested it:
>>
>> iw phy phy0 set antenna all all
>>
>> but it's only showing iw help as before.
>> I'm using the latest compiled compat-wireless.
>
> Try using "1 1" instead of "all all".
> Are you using the latest iw version?
>
> - Felix
>

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Felix Fietkau @ 2011-10-15 12:19 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzd+R42SArWR+gEgqvJ7h1_6ZnB61xyKzOo8FqNxkRhxqrQ@mail.gmail.com>

On 2011-10-15 2:13 PM, Stanislav Demakov wrote:
> Ok, I've compiled and installed iw from git. Now I have this (wlan0 is down):
>
> sudo iw phy phy0 set antenna 1 1
>
> command failed: Operation not supported (-95)
No idea then. It works on all of my systems.

- Felix

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 12:24 UTC (permalink / raw)
  To: Felix Fietkau; +Cc: linux-wireless
In-Reply-To: <4E997A54.2080004@openwrt.org>

I'm running Ubuntu Server 11.10 - (kernel:  Linux server
3.0.0-12-generic x86_64)

ath9k from compat-wireless-2011-10-12 and current iw from git compiled
with libnl1.

The wireless chip is AR9280. (2x2 MIMO)

Also
echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask
echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/tx_chainmask
is written at boot.

Is something wrong above?



2011/10/15 Felix Fietkau <nbd@openwrt.org>:
> On 2011-10-15 2:13 PM, Stanislav Demakov wrote:
>>
>> Ok, I've compiled and installed iw from git. Now I have this (wlan0 is
>> down):
>>
>> sudo iw phy phy0 set antenna 1 1
>>
>> command failed: Operation not supported (-95)
>
> No idea then. It works on all of my systems.
>
> - Felix
>

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Felix Fietkau @ 2011-10-15 12:39 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzdLBxCB7U1+ig+ctPJKZMgC3D2V0KHOXXZH8ZVBgi67BQg@mail.gmail.com>

On 2011-10-15 2:24 PM, Stanislav Demakov wrote:
> I'm running Ubuntu Server 11.10 - (kernel:  Linux server
> 3.0.0-12-generic x86_64)
>
> ath9k from compat-wireless-2011-10-12 and current iw from git compiled
> with libnl1.
>
> The wireless chip is AR9280. (2x2 MIMO)
>
> Also
> echo 1>  /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask
> echo 1>  /sys/kernel/debug/ieee80211/phy0/ath9k/tx_chainmask
> is written at boot.
>
> Is something wrong above?
Do not mess with the rx_chainmask/tx_chainmask parameters, that may be 
the reason why it's not working for you.

- Felix

^ permalink raw reply

* Re: [PATCH] ssb: Convert to use crc8 code in kernel library
From: Larry Finger @ 2011-10-15 13:29 UTC (permalink / raw)
  To: Arend van Spriel
  Cc: Pavel Roskin, John W Linville, Michael Buesch, zajec5@gmail.com,
	b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
In-Reply-To: <4E9943D5.1060607@broadcom.com>

On 10/15/2011 03:27 AM, Arend van Spriel wrote:
>
> Feedback on the renaming is indeed valid. Passing the word count is
> better here. For brcmsmac I plan to fill the buffer using 8-bit reads
> from SPROM, verify the crc8, and perform the endianess conversion from
> le16 to cpu when crc is ok (actually under review internally).

That sounds like a good plan. When that is posted, I'll study if that kind of 
change makes sense for ssb.

Larry


^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 13:34 UTC (permalink / raw)
  To: Felix Fietkau; +Cc: linux-wireless
In-Reply-To: <4E997F13.7060602@openwrt.org>

I've found it. Hostapd was the reason. After killing it set antenna works.
Thanks. :)

2011/10/15 Felix Fietkau <nbd@openwrt.org>:
> On 2011-10-15 2:24 PM, Stanislav Demakov wrote:
>>
>> I'm running Ubuntu Server 11.10 - (kernel:  Linux server
>> 3.0.0-12-generic x86_64)
>>
>> ath9k from compat-wireless-2011-10-12 and current iw from git compiled
>> with libnl1.
>>
>> The wireless chip is AR9280. (2x2 MIMO)
>>
>> Also
>> echo 1>  /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask
>> echo 1>  /sys/kernel/debug/ieee80211/phy0/ath9k/tx_chainmask
>> is written at boot.
>>
>> Is something wrong above?
>
> Do not mess with the rx_chainmask/tx_chainmask parameters, that may be the
> reason why it's not working for you.
>
> - Felix
>

^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Stanislav Demakov @ 2011-10-15 13:41 UTC (permalink / raw)
  To: Felix Fietkau; +Cc: linux-wireless
In-Reply-To: <CAN=pzd+8b9cqc6BgvaF8vdq-CywJ7mNTVpeXz92ZvwJwefJOkA@mail.gmail.com>

And the last question...
Can you confirm that after setting antenna configuration to 1x1 I can
safely detach 2nd physical connector from the adapter? I mean is there
a guarantees that device will only use the 1st antenna.

2011/10/15 Stanislav Demakov <s.demakov@gmail.com>:
> I've found it. Hostapd was the reason. After killing it set antenna works.
> Thanks. :)
>
> 2011/10/15 Felix Fietkau <nbd@openwrt.org>:
>> On 2011-10-15 2:24 PM, Stanislav Demakov wrote:
>>>
>>> I'm running Ubuntu Server 11.10 - (kernel:  Linux server
>>> 3.0.0-12-generic x86_64)
>>>
>>> ath9k from compat-wireless-2011-10-12 and current iw from git compiled
>>> with libnl1.
>>>
>>> The wireless chip is AR9280. (2x2 MIMO)
>>>
>>> Also
>>> echo 1>  /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask
>>> echo 1>  /sys/kernel/debug/ieee80211/phy0/ath9k/tx_chainmask
>>> is written at boot.
>>>
>>> Is something wrong above?
>>
>> Do not mess with the rx_chainmask/tx_chainmask parameters, that may be the
>> reason why it's not working for you.
>>
>> - Felix
>>
>

^ permalink raw reply

* Re: [PATCH] ssb: Convert to use crc8 code in kernel library
From: Michael Büsch @ 2011-10-15 13:53 UTC (permalink / raw)
  To: Larry Finger
  Cc: Arend van Spriel, Pavel Roskin, John W Linville, Michael Buesch,
	zajec5@gmail.com, b43-dev@lists.infradead.org,
	linux-wireless@vger.kernel.org
In-Reply-To: <4E998AA1.4080907@lwfinger.net>

On Sat, 15 Oct 2011 08:29:05 -0500
Larry Finger <Larry.Finger@lwfinger.net> wrote:

> > I plan to fill the buffer using 8-bit reads from SPROM,

> That sounds like a good plan. When that is posted, I'll study if that kind of 
> change makes sense for ssb.

If this change is made, it has to be tested on all supported devices, IMO.
I would not be surprised if there are older devices that don't like that.

-- 
Greetings, Michael.

^ permalink raw reply

* Re: [PATCH] ssb: Convert to use crc8 code in kernel library
From: Larry Finger @ 2011-10-15 14:18 UTC (permalink / raw)
  To: Michael Büsch
  Cc: Arend van Spriel, Pavel Roskin, John W Linville, Michael Buesch,
	zajec5@gmail.com, b43-dev@lists.infradead.org,
	linux-wireless@vger.kernel.org
In-Reply-To: <20111015155306.6bd1e695@milhouse>

On 10/15/2011 08:53 AM, Michael Büsch wrote:
> On Sat, 15 Oct 2011 08:29:05 -0500
> Larry Finger<Larry.Finger@lwfinger.net>  wrote:
>
>>> I plan to fill the buffer using 8-bit reads from SPROM,
>
>> That sounds like a good plan. When that is posted, I'll study if that kind of
>> change makes sense for ssb.
>
> If this change is made, it has to be tested on all supported devices, IMO.
> I would not be surprised if there are older devices that don't like that.

Two of my devices are a BCM4303 (14e4:4301), and an early BCM4306. There are not 
likely to be any older than that.

Larry

^ permalink raw reply

* Re: Alfa AWUS036NHR with RTL8188RU chipset
From: v4mp @ 2011-10-15 14:22 UTC (permalink / raw)
  To: linux-wireless
In-Reply-To: <4E91B400.1020305@lwfinger.net>



i've tried also kernel 3.1-rc9 with latest compat wireless 14-10-2011 and still
don't work...it was recognized but no APs can be detected..the led of the alfa
is off..seems that it is power off..

i don't know about firmware, i see that there are .bin on lib/firmware/rtlwifi..
 how can i update them?

thx




^ permalink raw reply

* Re: Ath9k, single antenna on ar9280
From: Felix Fietkau @ 2011-10-15 14:22 UTC (permalink / raw)
  To: Stanislav Demakov; +Cc: linux-wireless
In-Reply-To: <CAN=pzdJgba-mdJHLDC+_LpgSiMwff4vbB-oUp2VDwYsSouedPA@mail.gmail.com>

On 2011-10-15 3:41 PM, Stanislav Demakov wrote:
> And the last question...
> Can you confirm that after setting antenna configuration to 1x1 I can
> safely detach 2nd physical connector from the adapter? I mean is there
> a guarantees that device will only use the 1st antenna.
Changing the antenna configuration will alter the chainmask accordingly, 
so it should be safe to disconnect the second physical connector.

- Felix

^ permalink raw reply

* Re: 3.1-rc9 wifi problem
From: Arend van Spriel @ 2011-10-15 18:38 UTC (permalink / raw)
  To: werner; +Cc: linux-wireless@vger.kernel.org
In-Reply-To: <web-626864831@zbackend1.aha.ru>

On 10/15/2011 08:07 PM, werner wrote:
> A laptop of a friend, which worked always with wifi until 
> 3.0.4 , stopped to work when installing 3.1-rc9 , after 
> re-installing 3.0.4 wifi returned to work.  I think it was 
> a packard-bell laptop.   I can't test this better because 
> he gone with his laptop; perhaps next week he'll visit me 
> again. Since 2.6.38 his laptop worked with my wifi.
> 
> This can be a regression in the wifi drivers, or because 
> of a slightly changed config. Anyway the diff of config is 
> enclosed.
> 
> w.landgraf
> ---
> Professional hosting for everyone - http://www.host.ru

Another thing. As this seems a wireless issue it may be better to send
this thread to the linux-wireless list.

Gr. AvS


^ permalink raw reply

* Compat-wireless release for 2011-10-15 is baked
From: Compat-wireless cronjob account @ 2011-10-15 19:02 UTC (permalink / raw)
  To: linux-wireless


compat-wireless code metrics

    814119 - Total upstream lines of code being pulled
      2431 - backport code changes
      2113 - backport code additions
       318 - backport code deletions
      8588 - backport from compat module
     11019 - total backport code
    1.3535 - % of code consists of backport work

^ permalink raw reply

* Re: 3.1-rc9 wifi problem
From: David Täht @ 2011-10-15 19:21 UTC (permalink / raw)
  To: Arend van Spriel; +Cc: werner, linux-wireless@vger.kernel.org
In-Reply-To: <4E99D30A.1030108@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

On 10/15/2011 08:38 PM, Arend van Spriel wrote:
> On 10/15/2011 08:07 PM, werner wrote:
>> A laptop of a friend, which worked always with wifi until 
>> 3.0.4 , stopped to work when installing 3.1-rc9 , after 
>> re-installing 3.0.4 wifi returned to work.  I think it was 
>> a packard-bell laptop.   I can't test this better because 
>> he gone with his laptop; perhaps next week he'll visit me 
>> again. Since 2.6.38 his laptop worked with my wifi.
>>
>> This can be a regression in the wifi drivers, or because 
>> of a slightly changed config. Anyway the diff of config is 
>> enclosed.
>>
>> w.landgraf
>> ---
>> Professional hosting for everyone - http://www.host.ru
> Another thing. As this seems a wireless issue it may be better to send
> this thread to the linux-wireless list.
>

In my case, with 3.1-rc9, an atheros SR71 card stopped apparently
negotiating N - as it would not connect faster than 54Mbit on the 5ghz
channel either in HT20 or HT40+ mode, according to sampling iwconfig.


> Gr. AvS
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Dave Täht


[-- Attachment #2: dave_taht.vcf --]
[-- Type: text/x-vcard, Size: 214 bytes --]

begin:vcard
fn;quoted-printable:Dave T=C3=A4ht
n;quoted-printable:T=C3=A4ht;Dave
email;internet:dave.taht@gmail.com
tel;home:1-239-829-5608
tel;cell:0638645374
x-mozilla-html:FALSE
version:2.1
end:vcard


^ permalink raw reply

* [PATCH] wl12xx: set scan probe requests rate according to the no_cck flag
From: Guy Eilam @ 2011-10-15 20:23 UTC (permalink / raw)
  To: coelho; +Cc: linux-wireless

Set the TX rate of probe requests during scanning according to the
no_cck flag in the scan request struct.

Signed-off-by: Guy Eilam <guy@wizery.com>
---
 drivers/net/wireless/wl12xx/scan.c |   15 ++++++++++++---
 1 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/drivers/net/wireless/wl12xx/scan.c b/drivers/net/wireless/wl12xx/scan.c
index 5a6ae29..9a6bba4 100644
--- a/drivers/net/wireless/wl12xx/scan.c
+++ b/drivers/net/wireless/wl12xx/scan.c
@@ -184,7 +184,6 @@ static int wl1271_scan_send(struct wl1271 *wl, enum ieee80211_band band,
 
 	cmd->params.tx_rate = cpu_to_le32(basic_rate);
 	cmd->params.n_probe_reqs = wl->conf.scan.num_probe_reqs;
-	cmd->params.tx_rate = cpu_to_le32(basic_rate);
 	cmd->params.tid_trigger = 0;
 	cmd->params.scan_tag = WL1271_SCAN_DEFAULT_TAG;
 
@@ -243,7 +242,12 @@ void wl1271_scan_stm(struct wl1271 *wl)
 
 	case WL1271_SCAN_STATE_2GHZ_ACTIVE:
 		band = IEEE80211_BAND_2GHZ;
-		rate = wl1271_tx_min_rate_get(wl, wl->bitrate_masks[band]);
+		if (wl->scan.req->no_cck)
+			rate = wl1271_tx_min_rate_get(wl,
+						 CONF_TX_RATE_MASK_BASIC_P2P);
+		else
+			rate = wl1271_tx_min_rate_get(wl,
+						 CONF_TX_RATE_MASK_BASIC);
 		ret = wl1271_scan_send(wl, band, false, rate);
 		if (ret == WL1271_NOTHING_TO_SCAN) {
 			wl->scan.state = WL1271_SCAN_STATE_2GHZ_PASSIVE;
@@ -254,7 +258,12 @@ void wl1271_scan_stm(struct wl1271 *wl)
 
 	case WL1271_SCAN_STATE_2GHZ_PASSIVE:
 		band = IEEE80211_BAND_2GHZ;
-		rate = wl1271_tx_min_rate_get(wl, wl->bitrate_masks[band]);
+		if (wl->scan.req->no_cck)
+			rate = wl1271_tx_min_rate_get(wl,
+						 CONF_TX_RATE_MASK_BASIC_P2P);
+		else
+			rate = wl1271_tx_min_rate_get(wl,
+						 CONF_TX_RATE_MASK_BASIC);
 		ret = wl1271_scan_send(wl, band, true, rate);
 		if (ret == WL1271_NOTHING_TO_SCAN) {
 			if (wl->enable_11a)
-- 
1.7.4.1


^ permalink raw reply related

* Re: 3.1.0-rc9+ : wlan stops working w/o any error messages
From: David Rientjes @ 2011-10-15 21:21 UTC (permalink / raw)
  To: Toralf Förster; +Cc: werner, Wey-Yi Guy, ilw, linux-wireless, linux-kernel
In-Reply-To: <201110152119.58509.toralf.foerster@gmx.de>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 960 bytes --]

On Sat, 15 Oct 2011, Toralf Förster wrote:

> With a ThinkPad T400 with "Intel Corporation PRO/Wireless 5100 AGN [Shiloh] 
> Network Connection" I experienced few times in the last week that the suddenly 
> the network stops to work - no messages in /var/log/messages nor any other 
> outout. Only  a restart of the network services helped
> 
> n22 ~ # uname -a
> Linux n22 3.1.0-rc9+ #1 SMP Fri Oct 14 19:21:56 CEST 2011 i686 Intel(R) 
> Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel GNU/Linux
> 
> It is an almost stable Gentoo.
> 
> Anybody else made similar experiences ?
> 

It looks like werner is reporting a similar problem in 
https://lkml.org/lkml/2011/10/15/67 but with a different laptop, 
information is vague in that regression report.

Adding him, Wey-Yi Guy from Intel, and linux-wireless mailing list to the 
cc.

What's the last kernel prior to 3.1-rc9 that worked for you?

What does "iwconfig" show?

What does "dmesg | grep iwlagn" show?

^ permalink raw reply


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox