brcm80211 not setting correct country code?

brcm80211 not setting correct country code?

[Ben Hutchings]

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

Wenceslao González-Viñas wrote:
[...]
> [  330.205983] brcm80211: module is from the staging directory, the quality is unknown, you have been warned.
> [  330.212186] brcm80211 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [  330.212195] brcm80211 0000:03:00.0: setting latency timer to 64
> [  330.268237] Found chip type AI (0x13814313)
> [  330.271328] Changing max_res_mask to 0xffff
> [  330.271330] Changing min_res_mask to 0x200d
> [  330.277446] Applying 4313 WARs
> [  330.278330] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x51a macaddr: 88:25:2c:4e:9e:34
> [  330.283578] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
> [  330.285363] wl_set_hint: Sending country code US to MAC80211
> [  330.285371] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver (1.82.8.0) (Compiled at 04:19:31 on Apr  7 2011)
> [  330.365121] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> ----------------------
> 
> By the way, before I used 'modprobe cfg80211 ieee80211_regdom=EU' .  
> Perhaps the problem comes from that and line (dmesg) 330.285363 ?  I  
> need channel 13 ...
[...]

I asked where the device was purchased:

> In Spain (PC - City company). It is a Dell Inspiron M101z (service tag  
> CHL0SM1) . BTW, in Windows 7, it worked perfectly. But I removed it  
> installing Debian Wheezy.
[...]

I looked at the driver source code and there is certainly an attempt to
use a country code from NVRAM.  But maybe it hasn't actually been read
from NVRAM at the point this is done.  'US' seems to be the default if
the country code is blank.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: brcm80211 not setting correct country code?

[Arend van Spriel]

On 04/30/2011 07:04 AM, Ben Hutchings wrote:

> I looked at the driver source code and there is certainly an attempt to
> use a country code from NVRAM.  But maybe it hasn't actually been read
> from NVRAM at the point this is done.  'US' seems to be the default if
> the country code is blank.
>
> Ben.

Please refer to the information on wireless.kernel.org:
http://wireless.kernel.org/en/users/Drivers/brcm80211#Regulatory_Implementation

You could investigate whether the NVRAM/SROM country code is indeed 
blank or really configured with 'US'. For the driver itself channel 13 
can be used as long as your access point is transmitting beacons, 
because it is regarded as a passive channel.

Reading the logs listed in bug #622842 I would suggest running the 
following command after loading the brcm80211 driver:
$ iw set reg EU

You should see following in the log:
Apr 30 10:05:22 myhost kernel: [ 3967.072332] cfg80211: Calling CRDA for 
country: EU

Gr. AvS

Re: brcm80211 not setting correct country code?

[Wenceslao González-Viñas]

After
iw reg set EU
I do not get any answer in dmesg log.

and if I do (after)  : iw reg get , I get:

country 98:
	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 40), (N/A, 17)
	(5250 - 5330 @ 40), (N/A, 20), DFS
	(5490 - 5600 @ 40), (N/A, 20), DFS
	(5650 - 5710 @ 40), (N/A, 20), DFS

So, something is not working properly.

Thanks and best regards,

Wenceslao


Arend van Spriel <arend@broadcom.com> ha escrito:

> On 04/30/2011 07:04 AM, Ben Hutchings wrote:
>
>> I looked at the driver source code and there is certainly an attempt to
>> use a country code from NVRAM.  But maybe it hasn't actually been read
>> from NVRAM at the point this is done.  'US' seems to be the default if
>> the country code is blank.
>>
>> Ben.
>
> Please refer to the information on wireless.kernel.org:
> http://wireless.kernel.org/en/users/Drivers/brcm80211#Regulatory_Implementation
>
> You could investigate whether the NVRAM/SROM country code is indeed  
> blank or really configured with 'US'. For the driver itself channel  
> 13 can be used as long as your access point is transmitting beacons,  
> because it is regarded as a passive channel.
>
> Reading the logs listed in bug #622842 I would suggest running the  
> following command after loading the brcm80211 driver:
> $ iw set reg EU
>
> You should see following in the log:
> Apr 30 10:05:22 myhost kernel: [ 3967.072332] cfg80211: Calling CRDA  
> for country: EU
>
> Gr. AvS
>
>



----------------------------------------------------------------
Este mensaje ha sido enviado desde https://webmail.unav.es

Re: brcm80211 not setting correct country code?

[Arend van Spriel]

On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
> After
> iw reg set EU
> I do not get any answer in dmesg log.

I assume you did this as root or used sudo. You may have to check 
whether you have the proper udev rules in place. See 
http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA

> and if I do (after)  : iw reg get , I get:
>
> country 98:
> 	(2402 - 2472 @ 40), (N/A, 20)
> 	(5170 - 5250 @ 40), (N/A, 17)
> 	(5250 - 5330 @ 40), (N/A, 20), DFS
> 	(5490 - 5600 @ 40), (N/A, 20), DFS
> 	(5650 - 5710 @ 40), (N/A, 20), DFS
>
> So, something is not working properly.

I get country US (after iw reg set EU). I tried 'iw reg set ES' after 
that and another message showed up in the log:
[ 1613.052044] cfg80211: Calling CRDA for country: EU
[ 1845.365115] cfg80211: Pending regulatory request, waiting for it to 
be processed...

It seems cfg80211 expects CRDA to respond to the country setting for EU. 
I am not familiar what modules are involved in this usage scenario.

Gr. AvS

Re: brcm80211 not setting correct country code?

[Ben Hutchings]

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

On Sat, 2011-04-30 at 13:30 +0200, Arend van Spriel wrote:
> On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
> > After
> > iw reg set EU
> > I do not get any answer in dmesg log.
> 
> I assume you did this as root or used sudo. You may have to check 
> whether you have the proper udev rules in place. See 
> http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA

They are.

> > and if I do (after)  : iw reg get , I get:
> >
> > country 98:
> > 	(2402 - 2472 @ 40), (N/A, 20)
> > 	(5170 - 5250 @ 40), (N/A, 17)
> > 	(5250 - 5330 @ 40), (N/A, 20), DFS
> > 	(5490 - 5600 @ 40), (N/A, 20), DFS
> > 	(5650 - 5710 @ 40), (N/A, 20), DFS
> >
> > So, something is not working properly.
> 
> I get country US (after iw reg set EU). I tried 'iw reg set ES' after 
> that and another message showed up in the log:
> [ 1613.052044] cfg80211: Calling CRDA for country: EU
> [ 1845.365115] cfg80211: Pending regulatory request, waiting for it to 
> be processed...
> 
> It seems cfg80211 expects CRDA to respond to the country setting for EU. 
> I am not familiar what modules are involved in this usage scenario.

I added 'EU' to wireless-regdb in Debian for backward-compatibility.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: brcm80211 not setting correct country code?

[Wenceslao González-Viñas]

I do not understand.

I did of course as root. The rule in udev was not defined, though. I  
defined it , I restarted it , but no change. It does not matter if I  
use EU, ES or whatever.   ??????

Anyway, I think that is not iw / udev or similar problem as if I put a  
ralink stick, it works perfectly with regulatory domains and so.

I think is a problem with driver ... (as hardware worked in MSW7)

Best and thanks again,


Wenceslao

Arend van Spriel <arend@broadcom.com> ha escrito:

> On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
>> After
>> iw reg set EU
>> I do not get any answer in dmesg log.
>
> I assume you did this as root or used sudo. You may have to check  
> whether you have the proper udev rules in place. See  
> http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA
>
>> and if I do (after)  : iw reg get , I get:
>>
>> country 98:
>> 	(2402 - 2472 @ 40), (N/A, 20)
>> 	(5170 - 5250 @ 40), (N/A, 17)
>> 	(5250 - 5330 @ 40), (N/A, 20), DFS
>> 	(5490 - 5600 @ 40), (N/A, 20), DFS
>> 	(5650 - 5710 @ 40), (N/A, 20), DFS
>>
>> So, something is not working properly.
>
> I get country US (after iw reg set EU). I tried 'iw reg set ES'  
> after that and another message showed up in the log:
> [ 1613.052044] cfg80211: Calling CRDA for country: EU
> [ 1845.365115] cfg80211: Pending regulatory request, waiting for it  
> to be processed...
>
> It seems cfg80211 expects CRDA to respond to the country setting for  
> EU. I am not familiar what modules are involved in this usage  
> scenario.
>
> Gr. AvS
>
>

----------------------------------------------------------------
Este mensaje ha sido enviado desde https://webmail.unav.es

Re: brcm80211 not setting correct country code?

[Wenceslao González-Viñas]

Dear Ben,

If you want, I could try with this modified of wireless-regdb ... Just  
tell me how to obtain it .

Best and thanks again,

Wenceslao


Ben Hutchings <ben@decadent.org.uk> ha escrito:

> On Sat, 2011-04-30 at 13:30 +0200, Arend van Spriel wrote:
>> On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
>> > After
>> > iw reg set EU
>> > I do not get any answer in dmesg log.
>>
>> I assume you did this as root or used sudo. You may have to check
>> whether you have the proper udev rules in place. See
>> http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA
>
> They are.
>
>> > and if I do (after)  : iw reg get , I get:
>> >
>> > country 98:
>> > 	(2402 - 2472 @ 40), (N/A, 20)
>> > 	(5170 - 5250 @ 40), (N/A, 17)
>> > 	(5250 - 5330 @ 40), (N/A, 20), DFS
>> > 	(5490 - 5600 @ 40), (N/A, 20), DFS
>> > 	(5650 - 5710 @ 40), (N/A, 20), DFS
>> >
>> > So, something is not working properly.
>>
>> I get country US (after iw reg set EU). I tried 'iw reg set ES' after
>> that and another message showed up in the log:
>> [ 1613.052044] cfg80211: Calling CRDA for country: EU
>> [ 1845.365115] cfg80211: Pending regulatory request, waiting for it to
>> be processed...
>>
>> It seems cfg80211 expects CRDA to respond to the country setting for EU.
>> I am not familiar what modules are involved in this usage scenario.
>
> I added 'EU' to wireless-regdb in Debian for backward-compatibility.
>
> Ben.
>
> --
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.
>




----------------------------------------------------------------
Este mensaje ha sido enviado desde https://webmail.unav.es