I found that this bug is affecting me (in Germany), too. Got my sister a
new notebook (with bcm4313 wifi...) and had Maveric installed where wifi
worked without a problem. Then recently updated to Natty and it stopped
working. Instead of about 10 networks it only found 4 and hers was not
among them. As this was just a few weeks from the release of Oneiric I
didn't bother investigating as I assumed it to be a driver problem that
might be fixed in Oneiric.
So today I finally got to install Oneiric and the behaviour didn't
improve. So digging a lot through problem reports and apparent solutions
for the broadcom chip nothing of that worked for me. In the end I found
the messages in dmesg that channels have been disabled because of
regulations that apply to US. And that's where it hit me: channel 13 is
not used in the US but widely used in Europe. And that is exactly where
another notebook found the missing network. And that other notebook
would probably also have not found it if there weren't messages about
the driver ignoring CRDA commands therefore leaving "world" active.
To sum it up: Oneiric configures US reg domain although being in Germany.
This was tested linux-image-3.0.0-12-generic 3.0.0-12.20.
from "dmesg | grep cfg80211":
[ 15.750571] cfg80211: Calling CRDA to update world regulatory domain
[ 16.012946] cfg80211: World regulatory domain updated:
[ 16.012950] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 16.012952] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 16.012955] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
2000 mBm)
[ 16.012957] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
2000 mBm)
[ 16.012960] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 16.012962] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 16.047723] cfg80211: Updating information on frequency 2412 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047728] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047730] cfg80211: Updating information on frequency 2417 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047732] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047734] cfg80211: Updating information on frequency 2422 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047737] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047739] cfg80211: Updating information on frequency 2427 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047742] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047743] cfg80211: Updating information on frequency 2432 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047746] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047748] cfg80211: Updating information on frequency 2437 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047750] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047752] cfg80211: Updating information on frequency 2442 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047755] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047756] cfg80211: Updating information on frequency 2447 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047759] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047761] cfg80211: Updating information on frequency 2452 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047763] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047765] cfg80211: Updating information on frequency 2457 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047766] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047768] cfg80211: Updating information on frequency 2462 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047769] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047771] cfg80211: Updating information on frequency 2467 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047772] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047774] cfg80211: Updating information on frequency 2472 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047776] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.047777] cfg80211: Updating information on frequency 2484 MHz for a 20
MHz width channel with regulatory rule:
[ 16.047779] cfg80211: 2474000 KHz - 2494000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.053209] cfg80211: Calling CRDA for country: US
[ 16.057146] cfg80211: Updating information on frequency 2412 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057150] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057152] cfg80211: Updating information on frequency 2417 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057153] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057155] cfg80211: Updating information on frequency 2422 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057157] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057158] cfg80211: Updating information on frequency 2427 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057160] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057161] cfg80211: Updating information on frequency 2432 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057163] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057164] cfg80211: Updating information on frequency 2437 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057166] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057167] cfg80211: Updating information on frequency 2442 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057169] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057170] cfg80211: Updating information on frequency 2447 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057172] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057173] cfg80211: Updating information on frequency 2452 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057175] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057176] cfg80211: Updating information on frequency 2457 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057178] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057179] cfg80211: Updating information on frequency 2462 MHz for a 20
MHz width channel with regulatory rule:
[ 16.057181] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 16.057182] cfg80211: Disabling freq 2467 MHz
[ 16.057183] cfg80211: Disabling freq 2472 MHz
[ 16.057184] cfg80211: Disabling freq 2484 MHz
[ 16.057186] cfg80211: Regulatory domain changed to country: US
[ 16.057187] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 16.057189] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
2700 mBm)
[ 16.057191] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
1700 mBm)
[ 16.057192] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 16.057194] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 16.057195] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 16.057197] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
3000 mBm)
Where does the crda gets the country information from? I mean, that can't be
from internal information (config file) but would be required to come from
access points. Is there something like that in the data from APs? And if yes,
would one wrong AP (either misconfigured or simply bought abroad) be enough to
trigger wrong settings?
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Tags removed: kernel-request-3.0.0-11.18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/836133
Title:
wifi regulatory domain is set to US while I live in Italy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836133/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
