Re: b43 and WPA-PSK
Yan Seiner wrote: On Tue, February 23, 2010 4:57 pm, Larry Finger wrote: What I do know is that the BCM4318 does work with WPA/WPA2, although my device is Cardbus format in an old laptop. Using Broadcom's proprietary firmware, as you seem to be doing, the encryption/decryption is done in the hardware. The issues seems to be with the version of wireless utils in the latest openwrt snapshot. Sure looked like a driver issue,though. I'm a little confused on your usage of the device. As an AP, I see no need to scan. Are you using it as a station, or as a wireless bridge? In these modes, would not the bridging code to eth0 get in the way? I am using it in STA mode. I set up a separate network for the wireless and do not use bridging. I have to wan ports in effect - one for the wireless and one for wired. I don't use the wired port. It works quite well (or did, until I tried the b43 drivers at which point I also got the broken version of iwconfig/iwlist.) --Yan Hi, Someone reports that the station mode is not working for him in OpenWRT with ath9k driver after the last update of compat-wireless in OpenWRT. It was reported in https://dev.openwrt.org/ticket/6712 probably this is not an issue in the ath9k/b43 driver but in some other part of OpenWRT. Please try if it helps using an older version of compat-wireless or using an older version of the hostapd/wpa-supplicant combination. (Just go back some revisions in the svn for that directories) Hauke signature.asc Description: OpenPGP digital signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: A problem loading ssb module
Tim Gardner wrote: Luis R. Rodriguez wrote: On Thu, Sep 24, 2009 at 5:04 PM, Tim Gardner tim.gard...@canonical.com wrote: Luis R. Rodriguez wrote: On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens ha...@hauke-m.de wrote: Bryan Wu wrote: Mauro Di Domenico wrote: Hi, I'm testing new b43 modules for my 14e4:4315 broadcom card. I've compiled and installed compat-wireless-2009-09-16 in a debian machine with kernel version 2.6.30-6. During the boot I experience this problem: $ dmesg|egrep b43|ssb [2.384463] b43-pci-bridge :06:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [2.384477] b43-pci-bridge :06:00.0: setting latency timer to 64 [2.544344] ssb: Sonics Silicon Backplane found on PCI device :06:00.0 [6.968981] b43: disagrees about version of symbol ssb_device_is_enabled [6.968986] b43: Unknown symbol ssb_device_is_enabled [6.969280] b43: Unknown symbol ssb_pmu_set_ldo_paref [6.969407] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable [6.969410] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable . ... I faced the exactly same issue as Mauro did. +1 from me, but currently have no time to take a deeper look. Thanks Hi, I had the same problem with the ssb module and compat-wireless in ubuntu 9.04. The problem is that the ssb module is integrated into the initramfs image. The version out of the initramfs image is loaded on startup and not the version of compat-wireless. Running sudo update-initramfs -u after installing compat-wireless and restaing the system fixes the problem for me. Either Debian/Ubuntu should remove ssb form default initramfs image or compat-wireless should update the image with the install command. At least the compat-wireless documentation needs an update. Hauke (adding Luis and linux-wireless list) Tim, do you guys update the initramfs upon installation of lbm? If a user does not use lbm and uses compat-wireless I suppose we need to do something similar. Luis No, initramfs is not updated when LBM is installed. I think maybe its a bug that ssb is in the initramfs modules list since AFAIK its not a boot essential device. Even in the netboot case, ssb/b44 should be in a udeb. That would make life much easier. Luis I'm looking at the Karmic initramfs-tools package and am not seeing _any_ reference to ssb or b44. Hi Tim, I have decompressed initrd.img-2.6.31-11-generic from karmic and initrd.img-2.6.28-15-generic form jaunty. In both packages I found the ssb.ko and b44.ko module. Hauke signature.asc Description: OpenPGP digital signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: A problem loading ssb module
Bryan Wu wrote: Mauro Di Domenico wrote: Hi, I'm testing new b43 modules for my 14e4:4315 broadcom card. I've compiled and installed compat-wireless-2009-09-16 in a debian machine with kernel version 2.6.30-6. During the boot I experience this problem: $ dmesg|egrep b43|ssb [2.384463] b43-pci-bridge :06:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [2.384477] b43-pci-bridge :06:00.0: setting latency timer to 64 [2.544344] ssb: Sonics Silicon Backplane found on PCI device :06:00.0 [6.968981] b43: disagrees about version of symbol ssb_device_is_enabled [6.968986] b43: Unknown symbol ssb_device_is_enabled [6.969280] b43: Unknown symbol ssb_pmu_set_ldo_paref [6.969407] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable [6.969410] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable . ... I faced the exactly same issue as Mauro did. +1 from me, but currently have no time to take a deeper look. Thanks Hi, I had the same problem with the ssb module and compat-wireless in ubuntu 9.04. The problem is that the ssb module is integrated into the initramfs image. The version out of the initramfs image is loaded on startup and not the version of compat-wireless. Running sudo update-initramfs -u after installing compat-wireless and restaing the system fixes the problem for me. Either Debian/Ubuntu should remove ssb form default initramfs image or compat-wireless should update the image with the install command. At least the compat-wireless documentation needs an update. Hauke (adding Luis and linux-wireless list) signature.asc Description: OpenPGP digital signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[PATCH 1/2] [b43-fwcutter] Firmware FW14 and FW15 are the same.
The extracted files have the same md5sum.
The package broadcom-wl-4.178.10.4.tar.bz2 was extracted from
wrt610n_v1.00.00.018_us.tgz as the package from the Linksys is not
available any more. Changed the link to the
broadcom-wl-4.178.10.4.tar.bz2 package.
The FW_FLAG_UNSUPPORTED flag was removed because it is not set for the
other files.
Signed-off-by: Hauke Mehrtens ha...@hauke-m.de
---
fwcutter/fwcutter_list.h |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fwcutter/fwcutter_list.h b/fwcutter/fwcutter_list.h
index 5175bbd..3cf8ea9 100644
--- a/fwcutter/fwcutter_list.h
+++ b/fwcutter/fwcutter_list.h
@@ -393,18 +393,18 @@ static const struct file files[] =
.extract= _cb8d70972b885b1f8883b943c0261a3c,
},
{
- /*
ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz
*/
+ /*
http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2 */
.name = wl.o,
.id = FW14,
.ucode_version = 478.104,
.md5= 2dd738b8feb8b3559fd9d8fbaf3bfffc,
- .flags = FW_FLAG_LE | FW_FLAG_V4 | FW_FLAG_UNSUPPORTED,
+ .flags = FW_FLAG_LE | FW_FLAG_V4,
.extract= _2dd738b8feb8b3559fd9d8fbaf3bfffc,
},
{
/*
ftp://downloads.netgear.com/files/GPL/WNDR3300-V1.0.29_gpl_src.zip */
.name = wl_apsta.o,
- .id = FW15,
+ .id = FW14,
.ucode_version = 478.104,
.md5= 1a258b2d93efa641c32ddf3c3a962028,
.flags = FW_FLAG_LE | FW_FLAG_V4,
@@ -413,7 +413,7 @@ static const struct file files[] =
{
/*
http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2 */
.name = wl_apsta.o,
- .id = FW15,
+ .id = FW14,
.ucode_version = 478.104,
.md5= bb8537e3204a1ea5903fe3e66b5e2763,
.flags = FW_FLAG_LE | FW_FLAG_V4,
--
1.6.2.1
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
