The compat_firmware_class was having some issues which should now be
hopefully addressed:
* Use a different subsystem name for sysfs registration, now compat_firmware
* The new subsystem name change required a new udev rule to be added
The new compat-wireless for 2.6.33-rc4 has been pushed out with the
new changes. Unfortunately 2.6.33-rc5 hasn't been pushed out yet so I
just overwrote the old rc4 package (next time I'll just add an extra
extra version when this happens). The new sha1sum for this release is:
c007d7c8649d6149f415ea87dc7a34d4ee808766 compat-wireless-2.6.33-rc4.tar.bz2
Just kicked out a bleeding edge release with the same fixes:
65bb3cd6565f1788a2c63bfe8ccfdd8dfc1fb368 compat-wireless-2010-01-20.tar.bz2
Please let us know if there are any issues. I should note that the new
compat_firmware_class will be used *every time* compat-wireless is
used firmware needs to be uploaded, not just for the new
request_firmware_nowait().
Luis
Luis --
I also seem to be having issues with firmware loading. Any clues would
be helpful.
I have a Gumstix Overo Fire with a built in libertas_sdio, and an ar9170usb
It finds the libertas firmware just fine, but not the ar9170 firmware.
I'm using a 2.6.29 kernel. This worked fine with
compat-wireless-2009-11-17. All the firmware files are in /lib/firmware.
Here's some dmesg output:
[ 18.834564] lib80211: common routines for IEEE802.11 drivers
[ 18.834564] lib80211_crypt: registered algorithm 'NULL'
[ 18.951324] libertas_sdio: Libertas SDIO driver
[ 18.951354] libertas_sdio: Copyright Pierre Ossman
[ 18.974456] libertas_sdio mmc1:0001:1: firmware: requesting
sd8686_helper.bin
[ 21.569885] Generic kernel compatibility enabled based on linux-next
next-20100113
[ 21.583374] libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin
[ 21.845703] cfg80211: Calling CRDA to update world regulatory domain
[ 22.728393] ar9170usb 2-2.4:1.0: usb_probe_interface
[ 22.728424] ar9170usb 2-2.4:1.0: usb_probe_interface - got id
[ 22.818023] usb 2-2.4: reset high speed USB device using ehci-omap
and address 3
[ 23.028930] libertas: 00:19:88:21:57:9e, fw 9.70.3p24, cap 0x00000303
[ 23.044372] eth0 (libertas_sdio): not using net_device_ops yet
[ 23.091583] libertas: PREP_CMD: command 0x00a3 failed: 2
[ 23.107025] libertas: PREP_CMD: command 0x00a3 failed: 2
[ 23.107238] libertas: eth0: Marvell WLAN 802.11 adapter
[ 23.973846] usb 2-2.4: firmware: requesting ar9170.fw
[ 83.974090] usb 2-2.4: ar9170.fw firmware file not found, trying old
firmware...
[ 83.981536] usb 2-2.4: firmware: requesting ar9170-1.fw
[ 143.982055] usb 2-2.4: file with init values not found.
[ 143.987365] ar9170usb: probe of 2-2.4:1.0 failed with error -2
On Thu, Jan 21, 2010 at 1:39 PM, Adam Wozniak <[email protected]> wrote:
> Ok, I see what's going on now. The openembedded recipe I'm working with
> didn't copy the udev stuff.
OK so not our fault? You just had to update your install target?
Luis
Ok, I see what's going on now. The openembedded recipe I'm working with
didn't copy the udev stuff.
Adam Wozniak wrote:
> Luis R. Rodriguez wrote:
>> BTW Haukes posted a fix for the compile build against ARM. Try that.
>> That patch applies to compat.git but you should be able to mangle it
>> to apply to compat-wireless easily too.
>>
> That worked, thank you.
>> OK so it failed here, you may want to try to debug udev stuff now
>> then, what distribution do you have? Where are your udev rules put?
>> Where is the original udev rule for firmware for your box?
>>
>> You can debug udev stuff by using 'udevadm monitor'
>>
> I'm using openembedded. Rules are in /etc/udev/rules.d
> It contains a file 50-udev-default.rules with a line:
>
> SUBSYSTEM=="firmware", ACTION=="add", RUN+="firmware.sh"
>
> If I copy & paste and change the SUBSYSTEM to "compat_firmware" things
> seem to load ok.
>
> --Adam
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Default udev from this package confirmed working on Gentoo.
Tested-by: Rick Farina
Thanks,
Rick Farina
Luis R. Rodriguez wrote:
> The compat_firmware_class was having some issues which should now be
> hopefully addressed:
>
> * Use a different subsystem name for sysfs registration, now compat_firmware
> * The new subsystem name change required a new udev rule to be added
>
> The new compat-wireless for 2.6.33-rc4 has been pushed out with the
> new changes. Unfortunately 2.6.33-rc5 hasn't been pushed out yet so I
> just overwrote the old rc4 package (next time I'll just add an extra
> extra version when this happens). The new sha1sum for this release is:
>
> c007d7c8649d6149f415ea87dc7a34d4ee808766 compat-wireless-2.6.33-rc4.tar.bz2
>
> Just kicked out a bleeding edge release with the same fixes:
>
> 65bb3cd6565f1788a2c63bfe8ccfdd8dfc1fb368 compat-wireless-2010-01-20.tar.bz2
>
> Please let us know if there are any issues. I should note that the new
> compat_firmware_class will be used *every time* compat-wireless is
> used firmware needs to be uploaded, not just for the new
> request_firmware_nowait().
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Correct. In this case, not your fault. There is no openembedded recipe
for compat-wireless, so I had to roll my own, and I flubbed it by
leaving out the udev stuff.
Luis R. Rodriguez wrote:
> OK so not our fault? You just had to update your install target?
compat-wireless-2010-01-20.tar.bz2 does not compile cleanly on ARM
architectures.
Commenting out line 9 of compat-2.6.32.h (#include <asm/compat.h>) fixes
the issue.
There is no arch/arm/include/asm/compat.h
I suspect there are several other architectures which have similar issues.
Luis R. Rodriguez wrote:
> The compat_firmware_class was having some issues which should now be
> hopefully addressed:
>
> * Use a different subsystem name for sysfs registration, now compat_firmware
> * The new subsystem name change required a new udev rule to be added
>
> The new compat-wireless for 2.6.33-rc4 has been pushed out with the
> new changes. Unfortunately 2.6.33-rc5 hasn't been pushed out yet so I
> just overwrote the old rc4 package (next time I'll just add an extra
> extra version when this happens). The new sha1sum for this release is:
>
> c007d7c8649d6149f415ea87dc7a34d4ee808766 compat-wireless-2.6.33-rc4.tar.bz2
>
> Just kicked out a bleeding edge release with the same fixes:
>
> 65bb3cd6565f1788a2c63bfe8ccfdd8dfc1fb368 compat-wireless-2010-01-20.tar.bz2
>
> Please let us know if there are any issues. I should note that the new
> compat_firmware_class will be used *every time* compat-wireless is
> used firmware needs to be uploaded, not just for the new
> request_firmware_nowait().
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On Thu, Jan 21, 2010 at 11:32 AM, Hauke Mehrtens <[email protected]> wrote:
> ARM does not provided the include file asm/compat.h. Use linux/compat.h
> instead, it includes asm/compat.h if needed.
> This patch is from OpenWRT:
> https://dev.openwrt.org/browser/trunk/package/mac80211/patches/020-fix_compat_h.patch?rev=19063
>
Thanks applied.
Luis
On Thu, Jan 21, 2010 at 12:08 PM, Adam Wozniak <[email protected]> wrote:
> Luis --
>
> I also
BTW Haukes posted a fix for the compile build against ARM. Try that.
That patch applies to compat.git but you should be able to mangle it
to apply to compat-wireless easily too.
> seem to be having issues with firmware loading. Any clues would be
> helpful.
>
> I have a Gumstix Overo Fire with a built in libertas_sdio, and an ar9170usb
>
> It finds the libertas firmware just fine, but not the ar9170 firmware.
>
> I'm using a 2.6.29 kernel. This worked fine with
> compat-wireless-2009-11-17. All the firmware files are in /lib/firmware.
>
> Here's some dmesg output:
>
> [ 18.834564] lib80211: common routines for IEEE802.11 drivers
> [ 18.834564] lib80211_crypt: registered algorithm 'NULL'
> [ 18.951324] libertas_sdio: Libertas SDIO driver
> [ 18.951354] libertas_sdio: Copyright Pierre Ossman
> [ 18.974456] libertas_sdio mmc1:0001:1: firmware: requesting
> sd8686_helper.bin
> [ 21.569885] Generic kernel compatibility enabled based on linux-next
> next-20100113
> [ 21.583374] libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin
> [ 21.845703] cfg80211: Calling CRDA to update world regulatory domain
> [ 22.728393] ar9170usb 2-2.4:1.0: usb_probe_interface
> [ 22.728424] ar9170usb 2-2.4:1.0: usb_probe_interface - got id
> [ 22.818023] usb 2-2.4: reset high speed USB device using ehci-omap and
> address 3
> [ 23.028930] libertas: 00:19:88:21:57:9e, fw 9.70.3p24, cap 0x00000303
> [ 23.044372] eth0 (libertas_sdio): not using net_device_ops yet
> [ 23.091583] libertas: PREP_CMD: command 0x00a3 failed: 2
> [ 23.107025] libertas: PREP_CMD: command 0x00a3 failed: 2
> [ 23.107238] libertas: eth0: Marvell WLAN 802.11 adapter
> [ 23.973846] usb 2-2.4: firmware: requesting ar9170.fw
> [ 83.974090] usb 2-2.4: ar9170.fw firmware file not found, trying old
> firmware...
OK so it failed here, you may want to try to debug udev stuff now
then, what distribution do you have? Where are your udev rules put?
Where is the original udev rule for firmware for your box?
You can debug udev stuff by using 'udevadm monitor'
Luis
Confirm; this fixes the compile issue for ARM
Hauke Mehrtens wrote:
> ARM does not provided the include file asm/compat.h. Use linux/compat.h
> instead, it includes asm/compat.h if needed.
> This patch is from OpenWRT:
> https://dev.openwrt.org/browser/trunk/package/mac80211/patches/020-fix_compat_h.patch?rev=19063
>
> Signed-off-by: Hauke Mehrtens <[email protected]>
> ---
> include/linux/compat-2.6.32.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/compat-2.6.32.h b/include/linux/compat-2.6.32.h
> index c3e4dbe..11060d8 100644
> --- a/include/linux/compat-2.6.32.h
> +++ b/include/linux/compat-2.6.32.h
> @@ -6,7 +6,7 @@
> #if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,32))
>
> #include <linux/netdevice.h>
> -#include <asm/compat.h>
> +#include <linux/compat.h>
> #include <net/iw_handler.h>
> #include <linux/workqueue.h>
>
>
ARM does not provided the include file asm/compat.h. Use linux/compat.h
instead, it includes asm/compat.h if needed.
This patch is from OpenWRT:
https://dev.openwrt.org/browser/trunk/package/mac80211/patches/020-fix_compat_h.patch?rev=19063
Signed-off-by: Hauke Mehrtens <[email protected]>
---
include/linux/compat-2.6.32.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/compat-2.6.32.h b/include/linux/compat-2.6.32.h
index c3e4dbe..11060d8 100644
--- a/include/linux/compat-2.6.32.h
+++ b/include/linux/compat-2.6.32.h
@@ -6,7 +6,7 @@
#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,32))
#include <linux/netdevice.h>
-#include <asm/compat.h>
+#include <linux/compat.h>
#include <net/iw_handler.h>
#include <linux/workqueue.h>
--
1.6.3.3
Luis R. Rodriguez wrote:
> BTW Haukes posted a fix for the compile build against ARM. Try that.
> That patch applies to compat.git but you should be able to mangle it
> to apply to compat-wireless easily too.
>
That worked, thank you.
> OK so it failed here, you may want to try to debug udev stuff now
> then, what distribution do you have? Where are your udev rules put?
> Where is the original udev rule for firmware for your box?
>
> You can debug udev stuff by using 'udevadm monitor'
>
I'm using openembedded. Rules are in /etc/udev/rules.d
It contains a file 50-udev-default.rules with a line:
SUBSYSTEM=="firmware", ACTION=="add", RUN+="firmware.sh"
If I copy & paste and change the SUBSYSTEM to "compat_firmware" things
seem to load ok.
--Adam
On Thu, Jan 21, 2010 at 10:07 AM, Adam Wozniak <[email protected]> wrote:
> compat-wireless-2010-01-20.tar.bz2 does not compile cleanly on ARM
> architectures.
> Commenting out line 9 of compat-2.6.32.h (#include <asm/compat.h>) fixes the
> issue.
> There is no arch/arm/include/asm/compat.h
> I suspect there are several other architectures which have similar issues.
>
Thanks for the report, the asm/compat.h was needed as otherwise there
was a compile issue, not sure how to address this, hrm...
Luis