| 2013-02-15 23:43:21 |
Tony Espy |
bug |
|
|
added bug |
| 2013-02-15 23:43:27 |
Tony Espy |
manhattan: status |
New |
Confirmed |
|
| 2013-02-15 23:43:35 |
Tony Espy |
manhattan: importance |
Undecided |
Medium |
|
| 2013-02-15 23:43:38 |
Tony Espy |
manhattan: importance |
Medium |
High |
|
| 2013-02-15 23:43:42 |
Tony Espy |
manhattan: assignee |
|
Tony Espy (awe) |
|
| 2013-02-25 20:21:08 |
Tony Espy |
attachment added |
|
output from running crda on nexus galaxy https://bugs.launchpad.net/manhattan/+bug/1126751/+attachment/3546797/+files/crda.out |
|
| 2013-02-25 20:21:15 |
Tony Espy |
manhattan: status |
Confirmed |
In Progress |
|
| 2013-02-26 04:11:38 |
Ricardo Salveti |
attachment added |
|
crda_mako.txt https://bugs.launchpad.net/manhattan/+bug/1126751/+attachment/3547191/+files/crda_mako.txt |
|
| 2013-02-26 16:52:30 |
Tony Espy |
description |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run /sbin/crda ( note, you need to make sure the env var COUNTRY is set first ), I get the following error:
# /sbin/crda
Failed to set regulatory domain: -7
I haven't looked at the crda code yet, so I'm not sure if this is an errno or not. If it is, it's E2BIG.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel. |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required |
|
| 2013-02-26 16:52:45 |
Tony Espy |
bug |
|
|
added subscriber Mathieu Trudel-Lapierre |
| 2013-02-26 19:52:02 |
Tony Espy |
description |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required
== Drivers ==
=== Galaxy Nexus (maguro) ===
The Galaxy Nexus uses the bcmdhd Wi-Fi driver. Which it turns out has code to set a custom world regdomain by default ( see /drivers/net/wireless/bcmdhd/wl_cfg80211.c ), and also appears not to play well with the kernel wireless regulatory framework.
This causes problems for wpa_supplicant, which actually queries the regdomain info from the kernel/driver, and uses this information to govern it's behavior.
This means it's probably time to revisit the delta between Android's version of wpa_supplicant, and the latest version in Ubuntu. |
|
| 2013-02-26 20:23:57 |
Tony Espy |
description |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required
== Drivers ==
=== Galaxy Nexus (maguro) ===
The Galaxy Nexus uses the bcmdhd Wi-Fi driver. Which it turns out has code to set a custom world regdomain by default ( see /drivers/net/wireless/bcmdhd/wl_cfg80211.c ), and also appears not to play well with the kernel wireless regulatory framework.
This causes problems for wpa_supplicant, which actually queries the regdomain info from the kernel/driver, and uses this information to govern it's behavior.
This means it's probably time to revisit the delta between Android's version of wpa_supplicant, and the latest version in Ubuntu. |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required
== Drivers ==
=== Galaxy Nexus (maguro) ===
The Galaxy Nexus uses the bcmdhd Wi-Fi driver. Which it turns out has code to set a custom world regdomain by default ( see /drivers/net/wireless/bcmdhd/wl_cfg80211.c ), and also appears not to play well with the kernel wireless regulatory framework.
This causes problems for wpa_supplicant, which actually queries the regdomain info from the kernel/driver, and uses this information to govern it's behavior.
This means it's probably time to revisit the delta between Android's version of wpa_supplicant, and the latest version in Ubuntu.
Also note, while doing some investigation on the bcmdhd driver, I ran into a reference of a private Broadcom-specific wpa_supplicant library.
== Nexus 4 (mako) ==
The Nexus 4 uses the wcnss_wlan driver ( aka prima ). The upstream git tree can be found at git://codeaurora.org/external/wlan/prima.git.
This driver also apparently doesn't react to 'iw reg set' either. It also doesn't appear to be integrated with cfg80211 either. |
|
| 2013-02-26 20:24:59 |
Tony Espy |
description |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required
== Drivers ==
=== Galaxy Nexus (maguro) ===
The Galaxy Nexus uses the bcmdhd Wi-Fi driver. Which it turns out has code to set a custom world regdomain by default ( see /drivers/net/wireless/bcmdhd/wl_cfg80211.c ), and also appears not to play well with the kernel wireless regulatory framework.
This causes problems for wpa_supplicant, which actually queries the regdomain info from the kernel/driver, and uses this information to govern it's behavior.
This means it's probably time to revisit the delta between Android's version of wpa_supplicant, and the latest version in Ubuntu.
Also note, while doing some investigation on the bcmdhd driver, I ran into a reference of a private Broadcom-specific wpa_supplicant library.
== Nexus 4 (mako) ==
The Nexus 4 uses the wcnss_wlan driver ( aka prima ). The upstream git tree can be found at git://codeaurora.org/external/wlan/prima.git.
This driver also apparently doesn't react to 'iw reg set' either. It also doesn't appear to be integrated with cfg80211 either. |
Our images currently are broken with respect to Wi-Fi CRDA ( Central Regulatory Domain Agent ) / Regulatory support.
We don't include the regulatory DB package ( wireless-regdb ) nor the user agent used to load regulatory information into the kernel ( crda ). The kernel requests CRDA updates by generating a uevent, which is caught by udevd, which in turn matches a simple role that causes /sbin/crda to be invoked. As we're missing the required packages and not running udev on our images, CRDA updates fail.
If you look /var/log/syslog on a Galaxy Nexus / maguro running phablet-image >= 83, you'll see the following messages whenever the phone boots:
cfg80211: Calling CRDA to update world regulatory domain
This may be related to some of the bugs we're seeing with 802.11an ( 5GHz band ) access points we've seen including bug # 1107943 ( maguro ) and bug # 1126264 ( manta ).
Also, I went ahead an installed wireless-regdb and crda on my maguro. When I run 'sudo iw reg set US', it has no effect.
Note, for more information on the Linux regulatory framework, please refer to:
http://wireless.kernel.org/en/developers/Regulatory
or Documentation/networking/regulatory.txt in the kernel.
In order for this to be fixed, we need to do the following:
1. Add wireless-regdb and crda to our builds
2. Figure out someway to properly set the REGDOMAIN in /etc/default/crda
( distro plans to fix by modifying the post-install script of crda, but I'm not sure this will work for us )
3. Fix one or more Wi-Fi drivers, if so required
== Drivers ==
=== Galaxy Nexus (maguro) ===
The Galaxy Nexus uses the bcmdhd Wi-Fi driver. Which it turns out has code to set a custom world regdomain by default ( see /drivers/net/wireless/bcmdhd/wl_cfg80211.c ), and also appears not to play well with the kernel wireless regulatory framework.
This causes problems for wpa_supplicant, which actually queries the regdomain info from the kernel/driver, and uses this information to govern it's behavior.
This means it's probably time to revisit the delta between Android's version of wpa_supplicant, and the latest version in Ubuntu.
Also note, while doing some investigation on the bcmdhd driver, I ran into a reference of a private Broadcom-specific wpa_supplicant library.
== Nexus 4 (mako) ==
The Nexus 4 uses the wcnss_wlan driver ( aka prima ). The upstream git tree can be found at git://codeaurora.org/external/wlan/prima.git.
This driver also apparently doesn't react to 'iw reg set' either. It also doesn't appear to be integrated with cfg80211 either.
Note, from the codearora.org site, it appears the Prima driver is for a Qualcomm MSM WLAN module ( which may use an Atheros chip internally ). |
|
| 2013-03-11 18:25:16 |
Seth Forshee |
bug |
|
|
added subscriber Seth Forshee |
| 2013-07-08 21:15:20 |
Tony Espy |
information type |
Proprietary |
Public |
|
| 2013-07-08 21:15:29 |
Tony Espy |
affects |
manhattan |
touch-preview-images |
|
| 2013-07-08 21:15:48 |
Tony Espy |
touch-preview-images: assignee |
Tony Espy (awe) |
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2013-08-21 08:33:43 |
Rex Tsai |
bug |
|
|
added subscriber Rex Tsai |
| 2013-12-03 01:43:36 |
Oz Wolfe |
bug |
|
|
added subscriber Oz Wolfe |
| 2014-07-02 08:47:15 |
Matthew Paul Thomas |
affects |
touch-preview-images |
system-image (Ubuntu) |
|
| 2014-07-02 08:47:39 |
Matthew Paul Thomas |
tags |
|
touch-preview-images |
|
| 2014-09-23 21:38:32 |
Douglas Sikora |
bug |
|
|
added subscriber Douglas Sikora |
