CRDA regression in lbm compared with main kernel package

Bug #349001 reported by Max Bowsher
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-backports-modules-2.6.28 (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Jaunty by Rocko

Bug Description

[This bug forked out of bug 337929]

Using Jaunty's standard kernel 2.6.28-11.37, I am able to connect to my wireless (802.11g) access point running on non-US channel 13. Related dmesg:
[ 14.451280] cfg80211: Calling CRDA to update world regulatory domain
[ 14.599949] cfg80211: World regulatory domain updated:
[ 14.599960] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.599967] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.599972] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 14.599978] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 14.599983] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.599989] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

Using linux-backports-modules (a snapshot taken from current ubuntu-jaunty-lbm.git, including the update to master-2009-03-24), I cannot connect to this AP. Related dmesg:
[ 14.740421] cfg80211: Using static regulatory domain info
[ 14.740445] cfg80211: Regulatory domain: US
[ 14.740451] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.740459] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 14.740466] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740473] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740481] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740488] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740496] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 14.740609] cfg80211: Calling CRDA for country: US
[ 14.882164] cfg80211: Regulatory domain changed to country: US
[ 14.882175] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.882182] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 14.882188] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 14.882193] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.882199] (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.882205] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

I am located in the UK, my hardware is an Acer Aspire One, and the relevant driver is ath5k.

Revision history for this message
Max Bowsher (maxb) wrote :

I forgot to note that adding modprobe configuration of "options lbm_cw_cfg80211 ieee80211_regdom=EU" allows connection, with related dmesg:
[ 14.800218] cfg80211: Using static regulatory domain info
[ 14.800236] cfg80211: Regulatory domain: EU
[ 14.800248] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.800264] (2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 14.800279] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.800294] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.800310] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.800327] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 14.800352] (5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 14.800469] cfg80211: Calling CRDA for country: EU

Also, should I be concerned that this explicit configuration allows a max_antenna_gain of 600 mBi compared with 300 in the non-backports "world regulatory domain" configuration?

Revision history for this message
Rocko (rockorequin) wrote :

I confirm this in version 2.6.28-11.12 of linux-backports-modules. CRDA is always incorrectly selecting the US domain even though I am in Australia.

CRDA incorrectly selecting the US domain might explain why I kept getting kicked off the AP every 5 to 10 minutes.

I can fix it by using the lbm_cw_cfg80211 ieee80211_regdom=AU option, in which case it first says it is using the static data (US) and then later says it is choosing Australia:

Apr 6 15:23:23 pegasus-jaunty kernel: [17914.655567] cfg80211: Regulatory domain changed to country: AU
Apr 6 15:23:23 pegasus-jaunty kernel: [17914.655570] ^I(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 6 15:23:23 pegasus-jaunty kernel: [17914.655572] ^I(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Apr 6 15:23:23 pegasus-jaunty kernel: [17914.655573] ^I(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
Apr 6 15:23:23 pegasus-jaunty kernel: [17914.655575] ^I(5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
Apr 6 15:23:23 pegasus-jaunty kernel: [17914.655576] ^I(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Changed in linux-backports-modules-2.6.28 (Ubuntu):
status: New → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Max,

This is actually a duplicate of bug 288401. Bug 288401 should likely open a linux-backports-modules-2.6.28 task if it's still an issue for lbm. If you could post a comment there it would be great. For now I'm marking this as a duplicate of that bug. Thanks.

Revision history for this message
DiVoRaM (m-fabbrini) wrote :

I have the same problem...but I heard you can usethe command iw (apt-get install iw) to set the country code:

EX. iw reg set US

You can find a good documentation here http://wireless.kernel.org/en/developers/Regulatory/CRDA

p.s. Speaking of the ath5k driver, am sure you get those nasty messages "ath5k phy0: noise floor calibration timeout (2412MHz)"...a bunch of!

Revision history for this message
DiVoRaM (m-fabbrini) wrote :

Forgot something...by the way, if you download from
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf
the wpa_supplicant.conf and edit it (and after copy it to /etc) with COUNTRY=??, untag the update=1 (useful to automatically update the conf when needed) and set the country with iw reg set ?? you will have solve your problem...

cheers!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.