Username: Password: Remember me
Search Criteria Advanced
Package Details

broadcom-wl 5.10.91.9.3-3
http://www.broadcom.com/support/802.11/linux_sta.php
Broadcom 802.11abg Networking Drivers

unsupported :: modules
Maintainer: doorknob60
Votes: 310

License: MIXED/Proprietary

Last Updated: Mon, 04 Jan 2010 00:30:31 +0000
First Submitted: Mon, 01 Sep 2008 18:22:27 +0000

Tarball :: Files :: PKGBUILD

Dependencies kernel26<2.6.33

Sources
http://www.broadcom.com/docs/linux_sta/hybrid-portsrc--v5.10.91.9.3.tar.gz
wl_linux.patch
Comment by: bardo on Sat, 30 Jan 2010 12:46:29 +0000
For those who are interested in using wl with a 2.6.33-rc kernel, I posted a quick PKGBUILD mod to make it compile here: http://bbs.archlinux.org/viewtopic.php?pid=697002#p697002
Comment by: doorknob60 on Mon, 11 Jan 2010 23:30:25 +0000
hollunder: probably install this package under one kernel, and then manually compile it again under another kernel. I assume that would work.
Comment by: x-demon on Mon, 11 Jan 2010 11:26:56 +0000
this package builds module for currently running kernel.
Comment by: hollunder on Mon, 11 Jan 2010 11:14:53 +0000
This package seems to work relatively fine if you run one kernel, but as soon as you have a second one you have a problem. Install it with one and the other one has no network. What's the solution to this?
Comment by: doorknob60 on Mon, 04 Jan 2010 00:27:41 +0000
Wow, I leave for 3 days and have like 30 emails from AUR :P I already knew about the added dependency, just didn't have time before I left to a wifi-less place out of town.

My previous comment:

"Comment by: doorknob60 on Sun, 13 Dec 2009 17:42:47 +0000

That doesn't change the fact that kernel26-headers is only in the [testing] kernel right now, so I can't add it to makedepends yet."
Comment by: rlblaster on Sat, 02 Jan 2010 22:39:44 +0000
I'm using BCM4322, I have a custom kernel and had some issues connecting to my network with WPA.
You can read about the problem here: http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-12/msg05762.html
The fix in the thread is to enable IPW2200 as module (this enables some hidden kernel option which is needed by this broadcom module, which means that you don't need to load it) and recompile the kernel. It worked for me. This shouldn't be a problem in the stock kernel though.
Comment by: theccr2 on Fri, 01 Jan 2010 22:01:15 +0000
The kernel26-headers needs to be added as a dependency.
Comment by: blixawillbargeld on Fri, 01 Jan 2010 19:26:35 +0000
i just compiled and installed the package with the 2.6.32 kernel...works perfect so far...
Comment by: coolpyrofreak on Fri, 01 Jan 2010 16:47:51 +0000
@kralyk:

This package is out-of-date because there are changes that need to be made to the PKGBUILD in order for the package to install with the 2.6.32 kernel, which is now in [core]. The install fails without those changes.
Comment by: kralyk on Fri, 01 Jan 2010 13:44:04 +0000
How is this package out of date? I dont see...
Comment by: dapolinario on Thu, 31 Dec 2009 17:27:35 +0000
Add the line makedepends=('kernel26-headers>=2.6.29' 'kernel26-headers<2.6.33') in the PKGBUILD.
The kernel26-headers is only needed to compile the package, then can be removed later.

My PKGBUILD:
# Maintainer: Austin ( doorknob60 [at] gmail [dot] com )

pkgname=broadcom-wl
pkgver=5.10.91.9.3
pkgrel=2
pkgdesc="Broadcom 802.11abg Networking Drivers"
arch=('i686' 'x86_64')
[ "$CARCH" = "i686" ] && ARCH=x86_32
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.broadcom.com/support/802.11/linux_sta.php"
license=('MIXED/Proprietary')
depends=('kernel26>=2.6.29' 'kernel26<2.6.33')
makedepends=('kernel26-headers>=2.6.29' 'kernel26-headers<2.6.33')
install=broadcom-wl.install
source=("http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-${ARCH}-v${pkgver}.tar.gz" 'wl_linux.patch')
md5sums=('15890e1f9afe844adf2e251d390e28ac' '32ff612baa296c08fdf0f4e837479e7b')
[ "$CARCH" == "x86_64" ] && md5sums=('ed255d2c98690ef76757d95b2d9e6b32' '32ff612baa296c08fdf0f4e837479e7b')

build() {
# Adding line license
sed -i '190i\MODULE_LICENSE("Mixed/Proprietary"); \n' ${srcdir}/src/wl/sys/wl_linux.c

# Patching file for Kernel 2.6.32
patch ${srcdir}/src/wl/sys/wl_linux.c wl_linux.patch

# Building
KBUILD_NOPEDANTIC=1 make -C /lib/modules/$(uname -r)/build M=`pwd` || return 1
install -D -m 755 wl.ko ${pkgdir}/lib/modules/$(uname -r)/kernel/drivers/net/wireless/wl.ko || return 1
}
Comment by: muunleit on Thu, 31 Dec 2009 09:31:15 +0000
@notizblock:
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express [14e4:1713] (rev 02)
05:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04b5]

@coolpyrofreak:
Sorry, I think I was not clear in my post. My wlan doesn't work with the 2.6.32 kernel and it's buildin driver. With this broadcom-wl-pkg it works like with the 2.6.31 kernel without problems.
Comment by: notizblock on Wed, 30 Dec 2009 20:39:46 +0000
@muunleit
can you provide the output of:
lspci -vnn | grep 14e4
Comment by: coolpyrofreak on Wed, 30 Dec 2009 18:05:12 +0000
@muunleit:

Here's what you do:

Download the sources for this package as listed above into the same directory as the PKGBUILD. Edit the PKGBUILD to include kernel26-headers as depends. Update to the new kernel and then reboot your computer. Once you're running the new kernel, return to the broadcom-wl directory and run makepkg -is.
Comment by: muunleit on Wed, 30 Dec 2009 17:59:19 +0000
No, I still need this pkg.
The kernel 2.6.32 don't work with my "Broadcom Corporation BCM4312 802.11b/g (rev 01)" for more then 5 minutes.
Comment by: kgas on Wed, 30 Dec 2009 17:26:37 +0000
works fine with kernel 2.6.32.edit the PKGBUILD accordingly.
Comment by: darose on Wed, 30 Dec 2009 16:17:03 +0000
Uninstall broadcom-wl, then (using wired networking) upgrade your kernel, and then rebuild broadcom-wl (using the latest PKGBUILD, which doesn't have the dependency on kernel2.6.31) and reinstall.
Comment by: chessboxing on Wed, 30 Dec 2009 16:08:30 +0000
I get this with, pacman -Syu:
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: broadcom-wl: requires kernel26<2.6.32

What should I do, because it won't update anything unless this get fixed.
Comment by: coolpyrofreak on Wed, 30 Dec 2009 16:01:39 +0000
It doesn't really matter if kernel26-headers is makedepends or depends. As long as it's installed, it'll work. After installing the headers, wl works on my system without a hitch.
Comment by: luinuz on Wed, 30 Dec 2009 15:42:58 +0000
Good news!!!
My wireless card is 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
and it is only supported by wl driver.

With the new kernel 2.6.32, b43 driver support this card with all features; monitor mode, promiscuous mode, etc.

A very good description containing detailed steps is provided by the wireless-kernel wiki (scroll down to see the actual steps).
http://wireless.kernel.org/en/users/Drivers/b43#fw-b43-lp
Comment by: yannsen on Wed, 30 Dec 2009 14:07:47 +0000
for the kernel 2.6.32 a new dependency is required: kernel26-headers
Comment by: Rothsdad on Wed, 30 Dec 2009 11:21:27 +0000
make: Entering directory `/lib/modules/2.6.32-ARCH/build'
make: *** no target and cannot find makefile. stop?.
make: Leaving directory `/lib/modules/2.6.32-ARCH/build'
Comment by: notizblock on Wed, 30 Dec 2009 09:59:26 +0000
i guess 'kernel26-headers" should be in makedepends rather than depends:
http://www.archlinux.org/news/477/
Comment by: lenglemetz on Tue, 29 Dec 2009 21:09:53 +0000
please add kernel26-headers in "depends="
Comment by: fettouhi on Tue, 29 Dec 2009 18:52:27 +0000
Tried the suggestion from Saend in order to build it for the new 2.6.32 kernel nut it doesn't work.
Comment by: coolpyrofreak on Wed, 23 Dec 2009 20:03:41 +0000
@bouloumag:

I've gotten that same answer, which is weird because the little sticker on my wireless card says that Broadcom is that manufacturer.
Comment by: bouloumag on Wed, 23 Dec 2009 19:27:24 +0000
I asked Broadcom about an issue with hidden ssid and also about how long may it take until they offer a new tarball with support for the new kernel. Here is the (strange) answer I got :

==========
Broadcom is currently evaluating our support strategy for Linux users. As the chipset supplier, Broadcom provides Linux support to our customers - the manufacturers of wireless devices - that ultimately provide products to end customers, such as wireless LAN vendors, cable modem vendors, and notebook providers. It is up to these manufacturers to provide Linux client support to their end customers. Broadcom does not make a Linux client version available for end users at this time, however this may change in the future. In the meantime, please contact the manufacturer of your wireless device for Linux drivers. Linux support for certain products may also be available from Linuxant, and third party provider at http://www.linuxant.com/driverloader/

Regards,
Broadcom Support Team
Comment by: dimaka on Wed, 23 Dec 2009 15:37:43 +0000
When it will be available for kernel-2.6.33? Or is there another way to make broadcom BCM4312 working?
Comment by: Saend on Tue, 22 Dec 2009 19:38:45 +0000
I had the same issue:
make: *** /lib/modules/2.6.32-ARCH/build: No such file or directory.

I just did:
# mkdir /lib/modules/2.6.32-ARCH
# mkdir /lib/modules/2.6.32-ARCH/build

And it worked.
Maybe it was obvious to everybody, but not for me, that's why I'm posting it =)
Comment by: doorknob60 on Sun, 13 Dec 2009 17:42:47 +0000
Okay, nevermind, it's the base-devel group that is assumed is always installed, not base. That doesn't change the fact that kernel26-headers is only in the [testing] kernel right now, so I can't add it to makedepends yet. Proof: http://www.archlinux.org/packages/?q=kernel26-headers
Comment by: coolpyrofreak on Sun, 13 Dec 2009 15:13:55 +0000
@doorknob60:

Actually, I think it just means that it's installed on new installations. I don't have it installed on mine, and I'm still running 2.6.31.
Comment by: doorknob60 on Sun, 13 Dec 2009 09:17:34 +0000
Actually, this seems to be new for 2.6.32 in [testing], as there's no kernel26-headers package in [extra], so I'll wait until 2.6.32 hits extra to do it. I also noticed it's in the "base" group though, which means it should be implied that it's already installed, am I right about that?
Comment by: doorknob60 on Sun, 13 Dec 2009 09:15:25 +0000
Ah, so that's why it wouldn't build :P I'll add that to makedepends, they must have changed something because I don't remember the kernel headers ever being in a seperate package...oh well.
Comment by: warriant on Sat, 12 Dec 2009 08:35:30 +0000
Problem: make: *** /lib/modules/2.6.32-ARCH/build: No such file or directory. Stop.
Solution: # pacman -S kernel26-headers

Both drivers seem to work fine.
Comment by: gee on Fri, 11 Dec 2009 07:45:55 +0000
Alright, I've done that.
I'll see next time I restart how it goes.
Thanks.

Any option to look at why the wireless is not working? ^_^
Comment by: coolpyrofreak on Fri, 11 Dec 2009 05:43:20 +0000
@gee:

The best way to get eth0 and eth1 in the right order is to edit rc.conf and load your wired ethernet driver before the wl driver. Works like a charm.
Comment by: gee on Fri, 11 Dec 2009 05:09:58 +0000
Funny thing, I tried to play with udev to always get the right order for eth0 and eth1, but it is the exact opposite of what I ask for...

I've been playing with iwconfig for some time today but no luck :(
Comment by: gee on Thu, 10 Dec 2009 08:30:02 +0000
yes, without restarting:

iwconfig
lo no wireless extensions.

eth0 IEEE 802.11bgn ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:14 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth1 no wireless extensions.
Comment by: coolpyrofreak on Thu, 10 Dec 2009 07:58:05 +0000
@gee:

Are you sure that eth0 is your wireless card? Sometimes this driver causes eth0 and eth1 to flip randomly.
Comment by: gee on Thu, 10 Dec 2009 07:32:55 +0000
I tried
ifconfig eth0 up
iwconfig eth0 essid "my essid"
(not protected network for this test)
dhcpcd eth0 :
dhcpcd: version 5.1.3 starting
dhcpcd: eth0: broadcasting for a lease
dhcpcd: timed out

so no luck here either :(
Comment by: doorknob60 on Thu, 10 Dec 2009 02:29:07 +0000
Does it let you connect to a network, or is it just scanning that doesn't work?
Comment by: gee on Thu, 10 Dec 2009 00:55:37 +0000
Hello,

I installed the driver (a couple times now :D) following the wiki, I am able to see it in iwconfig:

eth1 IEEE 802.11bgn ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:14 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


but I cannot get it to find any network and I don't know where to look...

iwlist scan (as root)
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 No scan results


Any idea? I tried with the 2.6.31 and 2.6.32 kernel.

Thanks
Comment by: gborzi on Tue, 08 Dec 2009 10:09:16 +0000
I tested b43 (from 2.6.32) with both b43-firmware and b43-firmware-newest on my BCM4328 802.11a/b/g/n (rev 03) and it didn't worked. I'll test b43 on the netbook, which has a low power bcm4312 when 2.6.32 will be in core.
Comment by: x-demon on Tue, 08 Dec 2009 09:52:08 +0000
guys with draft/n modules still need to use that module, i believe
Comment by: x-demon on Tue, 08 Dec 2009 09:51:11 +0000
.32 hits [testing]. My bcm4312 works fine with b43 from .32 since there is support for LP-PHY (low-power devices)
Comment by: gborzi on Tue, 08 Dec 2009 08:53:57 +0000
I forgot to mention that I tested it with a WPA wifi. The license of this package isn't correctly dealt with. From the PKGBUILD page of the wiki, you should use
license=('custom')
and install the license file found under lib, e.g.
install -Dm644 ${srcdir}/lib/LICENSE.txt ${pkgdir}/usr/share/licenses/$pkgname/LICENSE
Comment by: Tapan on Tue, 08 Dec 2009 08:07:07 +0000
doorknob60: Works fine (x86_64, kernel26 2.6.32-1 from [testing], WEP wifi), but it works fine on this kernel before adding this patch.
Comment by: doorknob60 on Mon, 07 Dec 2009 23:58:46 +0000
I just added the patch, but can't test it right now since I don't use the new kernel on my Broadcom computer. Please post your results :)
Comment by: gborzi on Mon, 07 Dec 2009 22:08:31 +0000
There is a better patch (the package will compile with kernel26>=2.6.29 and kernel26<2.6.33) in this gentoo bug report
http://bugs.gentoo.org/show_bug.cgi?id=295930
Comment by: gborzi on Mon, 07 Dec 2009 21:42:05 +0000
There is already a patch to compile the wl driver with the 2.6.32 kernel. Look at this ubuntu package
http://packages.ubuntu.com/lucid/bcmwl-kernel-source
You just need to download the bcmwl_5.10.91.9+bdcom-0ubuntu5.diff.gz file, extract it with
zcat bcmwl_5.10.91.9+bdcom-0ubuntu5.diff.gz |patch -p1
and take the 0006-broadcom-sta-5.10.91.9-linux-2.6.32.patch under debian/patches. Or simply open src/wl/sys/wl_linux.c and add this line
#include <linux/sched.h>
between
#include <linux/pci_ids.h>
#define WLC_MAXBSSCFG 1
so that it reads
#include <linux/pci_ids.h>
#include <linux/sched.h>
#define WLC_MAXBSSCFG 1
Tested it on 64bit, BCM4328 802.11a/b/g/n (rev 03) and kernel26 2.6.32 from testing.
Comment by: muunleit on Fri, 04 Dec 2009 18:38:55 +0000
Ok, thanks, I will wait and try it when the kernel hits core.
Comment by: x-demon on Fri, 04 Dec 2009 14:58:30 +0000
well, i tested .32 from -rc4 for ~2 weeks, b43 is stable woth that module.
Comment by: sm217 on Fri, 04 Dec 2009 14:45:48 +0000
I am running 2.6.32 kernel from testing, everything works fine so far. <1 hour uptime though.
Comment by: x-demon on Fri, 04 Dec 2009 09:00:23 +0000
well, if you have bcm4312 with lp-phy, b43 module in .32 suport it.
Comment by: muunleit on Fri, 04 Dec 2009 08:44:54 +0000
The 2.6.32 kernel is relaesed as stable and this package doesn't support it.
How long may it take until broadcom offer a new tarball with support for the new kernel?
Comment by: coolpyrofreak on Tue, 17 Nov 2009 04:10:43 +0000
What doorknob60 said. Personally, I keep the source and PKGBUILD locally specifically for this reason. I just delete the pkg and src folders and the pkg.tar.gz file so I can rebuild the package.
Comment by: doorknob60 on Tue, 17 Nov 2009 03:57:45 +0000
Yeah, it's annoying, but you need to rebuild the package (not just reinstall) after each kernel upgrade. Best to keep the PKGBUILD and source files stored locally for this reason.
Comment by: sqwishy on Tue, 17 Nov 2009 01:14:09 +0000
@coolpyrofreak:

The first time it was because uname was telling it 2.6.30-ARCH instead of 2.6.31-ARCH. After the reboot, I didn't have access to the AUR repo. I thought I had cached the PKG and the source file because when I tried to install it (after the kernel upgrade) I saw that it had downloaded the source file. I also ran it a second time to make sure it would detect the file there and wouldn't try to download it again. If I had the PKGBUILD I would try and build the package, but I don't know where it went.
Comment by: coolpyrofreak on Tue, 17 Nov 2009 00:49:48 +0000
@sqwishy:

How did the package fail when you were trying to install it? Also, if you can, download the source tarball listed above and place it in the same directory as the PKGBUILD and build it with makepkg instead of yaourt or aurbuild.

I meant rebuilding the package with makepkg. Sorry for the confusion.
Comment by: sqwishy on Tue, 17 Nov 2009 00:30:57 +0000
@coolpyrofreak:

After the kernel update I had to reboot because since uname was confused. After the reboot, the broadcom-wl package did not exist. I uninstalled the package, upgraded the kernel, and went to install the package which it failed. So then I reboot, and the package no longer exists. I figured I had cached the package and it would be fine after I rebooted.

I'm not sure what you mean by rebuilding the PKGBUILD. You mean rebuilding the package or rewriting the PKGBUILD script???
Comment by: coolpyrofreak on Mon, 16 Nov 2009 22:38:40 +0000
@sqwishy:

As stated before on this page, you need to rebuild the PKGBUILD after doing a kernel update. Somehow, kernel updates make the modules incompatible with the new kernel, but rebuilding the package fixes the problem.
Comment by: sqwishy on Mon, 16 Nov 2009 20:44:26 +0000
Arrrrgggg. After doing a kernel update, I had to reboot so uname-r would be correct. Now, the broadcom-wl package does not exist... So is there anything I can do before I can get a wired connection?
Comment by: doorknob60 on Fri, 06 Nov 2009 04:44:21 +0000
Adopted. My parents' laptop uses this driver, so I thought I might as well adopt it, as this package is crucial to them and many other Arch users :)
Comment by: leprosys on Sun, 18 Oct 2009 16:01:37 +0000
I've started forum thread for broadcom-wl:
http://bbs.archlinux.org/viewtopic.php?id=82613
Comment by: benji.ijneb on Sun, 18 Oct 2009 15:01:43 +0000
ever since the upgrade to 2.6.31 (and i did reboot, then reinstall the driver) wireless with this module hasn't worked at all. any ideas?
Comment by: LiteHacker on Wed, 14 Oct 2009 21:38:36 +0000
I also confirm that rebuilding the package on the new kernel got it to work.
Comment by: bickman2k on Wed, 14 Oct 2009 16:02:24 +0000
I can verify that a recompile with the new kernel corrects the issue of the disappearing wl. :) Thanks for the suggestion, AkiraYB.
Comment by: AkiraYB on Wed, 14 Oct 2009 00:50:34 +0000
Actualy you have to build the broadcom-wl with the new kernel, if you've done that just after upgrading the kernel without a reboot, for example, you were compiling the module against the old kernel, not the new one. Just recompile the package again and hopefully it will work. :)
Comment by: LiteHacker on Tue, 13 Oct 2009 23:47:56 +0000
I upgraded my kernel and broadcom-wl at the same time. Unfortunately, the wireless connection no longer works. The little wireless network light doesn't go on any more. I tried modprobing wl.. it tells me the module doesn't exist. Anybody know what's wrong?
Comment by: darose on Tue, 13 Oct 2009 03:55:09 +0000
I was able to dig up an old PKGBUILD, and rebuild the old driver. (Got it off of Leprosys' Github site.)

If anyone else runs into similar problems with the new (5.10.91.9.3) driver freezing up, and needs me to make the old (5.10.91.9) PKGBUILD available, post a comment here.
Comment by: darose on Mon, 12 Oct 2009 14:30:28 +0000
This new version of the module seems to be making my laptop freeze up. Anyone else seeing this and/or have any suggestions on how to workaround?

I'm in a bit of a pickle now since I just upgraded to the 2.6.31 kernel, and the previous version of the driver (which doesn't freeze up) will no longer build against the new kernel.
Comment by: toketin on Mon, 12 Oct 2009 10:47:09 +0000
@piroflip thanks i've been able to compile it, works everything :D
Comment by: piroflip on Mon, 12 Oct 2009 10:36:10 +0000
@toketin
You have to reboot in order to get right build root directory (uname -r gives you old one).
Comment by: toketin on Mon, 12 Oct 2009 09:54:27 +0000
with the upgrade of kernel to 2.6.31 i had to delete the package and now i try to recompile it but i obtain this error:
make: *** /lib/modules/2.6.30-ARCH/build: No such file or directory. Stop.
==> ERRORE: Compilazione non riuscita.
Comment by: leprosys on Mon, 21 Sep 2009 17:20:45 +0000
Updated to 5.10.91.9.3
Comment by: raulin on Mon, 21 Sep 2009 16:19:39 +0000
(using a Broadcom 4353 a/g/n-draft card)

First of TKIP doesn't seem to work very well since I get tons of:
TKIP: RX tkey->key_idx=2 frame keyidx=1 priv=f6bf3300

During this TKIP error my wifi drops connection and regain it after a minute or so. Workaround is to disable TKIP in router.

The second thing is making me more worried though:

$sudo iwlist txpower

eth0 2 available transmit-powers :
0 dBm (1 mW)
25 dBm (255 mW)
Current Tx-Power:32 dBm (1496 mW)

Is it really healthy to have the wireless card at 32dBm? Will it break my card?
Comment by: dapolinario on Sun, 20 Sep 2009 04:04:59 +0000
Try the new version of leprosys.

http://github.com/leprosys/pkgbuilds/tree/master/broadcom-wl/
Comment by: x-demon on Fri, 18 Sep 2009 20:17:44 +0000
wow, really. Looks like patches not needed anymore...
Comment by: dapolinario on Fri, 18 Sep 2009 20:11:30 +0000
new version available on 17/09/2009, 5.10.91.9.3

http://www.broadcom.com/support/802.11/linux_sta.php
Comment by: darose on Fri, 18 Sep 2009 17:08:17 +0000
FYI - I've uploaded the PKGBUILD (and related files), the x86_64 source from broadcom, and a fully-built x86_64 Arch package here:

http://www.darose.net/broadcom-wl/
Comment by: x-demon on Fri, 18 Sep 2009 16:28:08 +0000
if someone can provide me 64bit build env, i can setup also 64bit repo without any problem.
Comment by: veovis-muaddib on Fri, 18 Sep 2009 15:57:26 +0000
I got all excited, and then noticed that your repo is 32bit only.

Sad panda.

But thank you x-demon, that is exactly what I am after.
Comment by: x-demon on Fri, 18 Sep 2009 15:40:12 +0000
you can get latest broadcom-wl from my repo, see repo.x-demon.org for more info.
Comment by: veovis-muaddib on Fri, 18 Sep 2009 12:58:57 +0000
Can someone please just set up a mirror somewhere? Every time I go to download this, the links are broken or something. I asked before where to get it, and fearuth was kind enough to give me the links. They worked then. However, now I need to install this again, and yet again, I can't find it, even with the links I used before.
Comment by: notizblock on Fri, 18 Sep 2009 05:29:06 +0000
thx, Peasantoid for the tip. i'll give it a try.
Comment by: notizblock on Wed, 16 Sep 2009 05:18:16 +0000
i've the same name-swapping problem as andre.ramaciotti since .30. Is there any solution available?
Comment by: x-demon on Tue, 15 Sep 2009 19:58:22 +0000
all supported by b43 driver.
Comment by: chessboxing on Tue, 15 Sep 2009 19:54:46 +0000
Which one, does allow it?
Comment by: x-demon on Tue, 15 Sep 2009 19:53:01 +0000
not with wl driver.
Comment by: chessboxing on Tue, 15 Sep 2009 19:37:02 +0000
question. I read this card also supports injection. Anyone tried this with aircrack-ng yet?
Comment by: andre.ramaciotti on Tue, 15 Sep 2009 18:18:10 +0000
I have the same problem. Both network devices keep swapping their names (eth0 and eth1), and I haven't come to a solution yet. What gave me best results was using /etc/iftab and ifrename, but it's still not perfect and sometime I have to reboot so I can get my wireless to work. Udev rules didn't work, using 'alias' in /etc/modprobe.d/modprobe.conf didn't work...
Comment by: Sagattarii on Tue, 15 Sep 2009 17:41:53 +0000
Well my wireless stopped working when I was rebooting my notebook after a kernel update. I though this packages needs an update, but after the next reboot it worked again without changing anything.
Comment by: andre.ramaciotti on Tue, 15 Sep 2009 16:56:33 +0000
When 2.6.31 is in [core], it'll be.
Comment by: Sagattarii on Tue, 15 Sep 2009 16:46:12 +0000
Will this packages be updated?
Comment by: brute on Fri, 11 Sep 2009 11:43:02 +0000
@leprosys also works for me on 2.6.31_x86_64. Thanks!
Comment by: x-demon on Fri, 11 Sep 2009 05:28:27 +0000
@leprosys, thx, all works.
Comment by: leprosys on Fri, 11 Sep 2009 04:03:25 +0000
This is my pkgbuild:
http://github.com/leprosys/pkgbuilds/tree/master/broadcom-wl/
Comment by: Square on Fri, 11 Sep 2009 03:47:07 +0000
x-demon: I figured it out. Add the patch in the PKGBUILD after the hidden-essid.patch (apply the new patch last), and use -p4.
Comment by: x-demon on Fri, 11 Sep 2009 03:27:57 +0000
leprosys, in which order you use patches? I tried it before license.patch, but no way... can you please post an updated pkgbuild?
Comment by: leprosys on Thu, 10 Sep 2009 20:30:28 +0000
Gentoo patch works for me :D
Comment by: Square on Thu, 10 Sep 2009 20:20:31 +0000
Tried the gentoo patch, no go.
I was excited for 2.6.31, too :/
Comment by: x-demon on Thu, 10 Sep 2009 17:32:55 +0000
in fact, i can't get it to work - maybe some patch conflicts with it
Comment by: x-demon on Thu, 10 Sep 2009 17:20:11 +0000
and here is gentoo patch for 2.6.31: http://paste.x-demon.org/61
Comment by: x-demon on Thu, 10 Sep 2009 17:17:22 +0000
doesnt work with .31 which is now in [testing]
patches from gentoo: http://bugs.gentoo.org/278470
Comment by: Jedipottsy on Tue, 01 Sep 2009 01:05:40 +0000
after re-installing my system again i have found that having DBUS installed causes my wireless to not function. This has never happened before. running PekWM system with wicd installed. DMESG shows the phys device cannot be identified with DBUS installed
Comment by: Jedipottsy on Mon, 31 Aug 2009 17:11:04 +0000
After installing this module, this works untill i reboot then it doesnt detect my hardware. Nothing i can do except reinstall works but again after only installing this and wicd a reboot kills my hardware.
Comment by: fettouhi on Sat, 29 Aug 2009 19:28:58 +0000
Any success with connecting to hidden wpa2 networks?

Regards

André
Comment by: Ajendrex on Fri, 28 Aug 2009 18:42:23 +0000
thank you guys!

Now it's working. I though that uninstalling b43-fwcutter the b43 module would not be loaded... each day we learn something new :)
Comment by: x-demon on Fri, 28 Aug 2009 13:16:06 +0000
4312 rev 1. Only ssb blacklisted =) but blacklisting b43, b43legacy, b44 also preferred, but not essential.
Comment by: gborzi on Fri, 28 Aug 2009 13:08:17 +0000
@x-demon
The need to blacklist ssb, b43 and b44 depends on which version of the broadcom chipset you have. On my netbook I have the BCM4312 (rev. 1) chipset, i.e. the same of Ajendrex. On another laptop I have a BCM4328 and it doesn't need blacklisting. Which is your chipset version?
Comment by: x-demon on Fri, 28 Aug 2009 08:40:52 +0000
About LP-PHY support in b43 in 2.6.31 kernel, reply from b43 coder:
"No, the merge window for .31 is already long closed, only regression
fixes are accepted.
The target is 2.6.32 (but full support may well be in the 2.6.33 timeframe)."
Comment by: x-demon on Fri, 28 Aug 2009 08:38:16 +0000
i'm not blacklistet b43, and it works. I only need to blacklist ssb.
Comment by: gborzi on Fri, 28 Aug 2009 00:11:10 +0000
@Ajendrex
I think you need to blacklist the following modules: ssb, b43, b44. I had the same problem and realized that it was due to the kernel loading ssb and b43 which prevents wl to work. So I blacklisted them (and b44 too just to be sure) and after reboot the wireless worked. I needed the blacklisting after the last kernel update.
Comment by: Ajendrex on Thu, 27 Aug 2009 21:38:53 +0000
Not working...

$ uname -a
Linux truncatula 2.6.30-ARCH #1 SMP PREEMPT Mon Aug 17 18:04:53 CEST 2009 i686 Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel GNU/Linux
$ lspci | grep 4312
0e:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
lsmod | grep wl
wl 1278664 0
lib80211 5832 1 wl

but iwconfig does not show any wireless interface :(
I'm working with a external usb wireless card (wlan0)

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"ubi-cgna"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:BF:D9:FB:8C
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-38 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Comment by: kdas on Thu, 27 Aug 2009 21:25:34 +0000
This package is not working for me... It is not associating with any APs.
Comment by: x-demon on Thu, 20 Aug 2009 11:56:56 +0000
no i can't. From root it gives me netlist, from non-root it says that devices doesn't support scanning
Comment by: thiagoc on Thu, 20 Aug 2009 11:42:37 +0000
@x-demon

You can do `iwlist ethX scan` with a non-root user?
Comment by: x-demon on Thu, 20 Aug 2009 06:53:31 +0000
I'm using NetworkManager and it's working.
Comment by: thiagoc on Wed, 19 Aug 2009 22:55:57 +0000
@leprosys

[thiagoc@minishit ~]$ groups
network video audio optical storage power users

in rc.conf I have: MODULES=(r8169 wl !b43 !ssb !pcspkr)

FYI, as root I can connect using iwconfig, but not with wicd.
Comment by: leprosys on Wed, 19 Aug 2009 22:47:06 +0000
Tiago, your user is in network group?
Comment by: thiagoc on Wed, 19 Aug 2009 22:18:28 +0000
Anyone having sucess with this package and the latests packages (kernel, wicd, etc)?

I'm unable to connect using a non-root user, wicd as root doesn't work too.
Comment by: thiagoc on Mon, 17 Aug 2009 04:19:36 +0000
I'm unable to scan networks with a non-root user. Wicd doesn't work too.
Comment by: x-demon on Sat, 08 Aug 2009 19:38:51 +0000
Is it really improves intel gma performance? Half-life 2 will be playable? =)
BTW, I think it will work with .31, what the difference? Huge changes in wireless stack?
Comment by: quadomatic on Sat, 08 Aug 2009 19:26:10 +0000
will we see a version that works with kernel 2.6.31 soon? I hear 2.6.31 really improves performance on intel gfx chipsets so I'm holding out for that
Comment by: Amnon82 on Fri, 07 Aug 2009 20:42:23 +0000
Arg. My wlan works as eth0 but my lan-card not. 13d3:349 IMC Networks. I used sky2 driver but now nothing ...
Comment by: Amnon82 on Fri, 07 Aug 2009 20:03:53 +0000
I've HP 701EG Compaq Mini with Chakra Alpha3pre installed. I have lib80211_crypt_tkip wl in my modules list and disabled ssb b43 and even b44 with !ssb !b43 !b44. My wirlescard was known as eth1. Lan-card uses sky2 driver. I don't see it with ifconf only eth0 which is the sky2-card. What can I do? Card-ID: 14e4:4312 "Broadcom Corporation BCM4312 802.11a/b/g"
Comment by: x-demon on Tue, 04 Aug 2009 09:59:50 +0000
no problem
Comment by: Virun on Tue, 04 Aug 2009 09:51:24 +0000
Thanks, all works :)
Comment by: Virun on Tue, 04 Aug 2009 09:41:29 +0000
Hm. Thanks for answer.
Comment by: x-demon on Tue, 04 Aug 2009 09:08:04 +0000
it works. i need to blacklist "ssb" module to get it working.
Comment by: Virun on Tue, 04 Aug 2009 09:06:51 +0000
This driver not work after I update kernel from 2.6.30.2 to 2.6.30.4
P.S. Sorry for my English :)
Comment by: habarnam on Sun, 02 Aug 2009 13:38:45 +0000
I have some really bad problems with packet loss and latency.
Anyone else experiencing that ?
Comment by: fettouhi on Mon, 13 Jul 2009 07:15:50 +0000
@x-demon: Really? How did you do that? I've never been able to get the driver to connect to a hidden WPA2 network. What method did you use?

Regards

André
Comment by: x-demon on Sun, 12 Jul 2009 20:13:34 +0000
yes, me. But that driver sucks - i got random freezes every day because of broadcom STA.
Comment by: fettouhi on Sun, 12 Jul 2009 20:06:00 +0000
Has anybody been able to connect tp hidden wpa2 networks yet with this driver?

Regards

André
Comment by: Cracker on Tue, 07 Jul 2009 08:22:14 +0000
It's all fine. I forgot to load some module first. tnx man. everything works fine!
Comment by: Cracker on Mon, 06 Jul 2009 21:10:32 +0000
i've compiled it at new stock kernel and compilation was ok. but when i execute a command insmod /some/path/wl.ko i get the message
insmod: error inserting '/some/path/wl.ko': -1 Unknown symbol in module

Any guess?
Comment by: Peasantoid on Mon, 06 Jul 2009 19:35:18 +0000
miguimon: See my first comment on the page -- you can work around it by disabling "reconnect automatically on connection loss" or some such in wicd preferences.
Comment by: miguimon on Fri, 03 Jul 2009 08:13:47 +0000
I'm having some issues with the latest version + kernel 2.6.30-5 (x86_64). OK, wicd is actually showing all the networks and I can get an IP but after several seconds it automatically disconnects. No idea what it could be but lately with some AP's the channel switch to 5GHz frequencies which is unusual. I also have disabled the ssb module and tried manually with iwconfig. Output after loading the wl module:

wl 0000:02:00.0: PCI INT A disabled
wl 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
wl 0000:02:00.0: setting latency timer to 64
eth1 (wl): not using net_device_ops yet
eth1: Broadcom BCM4328 802.11 Wireless Controller 5.10.91.9
Comment by: lgolebio on Sun, 28 Jun 2009 14:11:37 +0000
@UncombedCoconut:
The 'ssb' module is a part of b43 module. So disabling it in /etc/rc.conf is a must. It will not burn your computer ;).
Comment by: ekse on Sun, 28 Jun 2009 05:51:19 +0000
Thank you for this great package, saved me a lot of time!
Comment by: UncombedCoconut on Sat, 27 Jun 2009 16:14:21 +0000
Thank you, lgolebio! This same problem had been driving me nuts for a while. I'm a while away from a reboot, so I'll just ask: would adding !ssb to MODULES in /etc/rc.conf give me working wireless on boot, or would it just break wireless completely? :)
Comment by: veovis-muaddib on Fri, 26 Jun 2009 10:51:08 +0000
Ah, the links were the same, just replace 32 with 64 if you're on 64 bit.
Comment by: veovis-muaddib on Fri, 26 Jun 2009 10:49:42 +0000
I'm going to try it, but I'm going to ask so I have an answer when my system is broken or this just doesn't work. The URL's all say 32bit, I'm on 64bit. Is that okay?
Comment by: fearuth on Fri, 26 Jun 2009 10:48:11 +0000
You can get it from this link (http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5_10_91_9.tar.gz or http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5_10_91_9.tar.gz)
Comment by: veovis-muaddib on Fri, 26 Jun 2009 09:55:24 +0000
http://www.broadcom.com/docs/linux_sta/hybrid-portsrc--v5_10_91_9.tar.gz is gone. Is there an alternate source for this?
Comment by: piroflip on Fri, 26 Jun 2009 09:50:12 +0000
I build package from scratch right now (to check), everything is ok. Which tarball you can't get?
Comment by: veovis-muaddib on Fri, 26 Jun 2009 09:45:09 +0000
Ummm.... the tarball is no longer on their site. Makes it kind of difficult to install.
Comment by: scosu on Thu, 25 Jun 2009 19:55:47 +0000
i meant the package "patch". It's a build-dependency ;)
Comment by: kgas on Thu, 25 Jun 2009 15:33:39 +0000
It is now working. The problem is that when first saved the PKGBUILD it was not updated.Thanks piroplip
Comment by: madalu on Wed, 24 Jun 2009 17:19:40 +0000
Installed on MacBook 4,1 (x86_64). Can detect access point with iwlist scan. But cannot set essid with iwconfig (run as root). Anyone else have this problem? Any workarounds?
Comment by: notizblock on Wed, 24 Jun 2009 13:47:55 +0000
Thx lgolebio! problem solved here as well.
Comment by: lgolebio on Wed, 24 Jun 2009 10:28:18 +0000
Problem SOLVED:
1. Unload 'wl' module=> rmmod wl
2. Unload 'ssb" module=> rmmod ssb
3. Load 'wl' module=> modprobe wl

The interface shows up. :)
Comment by: piroflip on Wed, 24 Jun 2009 10:10:07 +0000
Any traces in dmesg?
Did it work on .29?
Comment by: lgolebio on Wed, 24 Jun 2009 10:07:45 +0000
Doesn't work form me also. Same problem as notizblock. The nterface doesn't show up.
Comment by: notizblock on Wed, 24 Jun 2009 05:35:15 +0000
Doesn't work for me on .30. Build was successful but the interface does not show up: ifconfig -a only shows wired and lo.
any hints?
Comment by: Riooo on Tue, 23 Jun 2009 22:25:23 +0000
Yes. that's the problem. Works fine. Sorry for stupid questions :D
Comment by: thiagoc on Tue, 23 Jun 2009 22:06:46 +0000
You upgrade your system and not did a reboot. Do it, should work.

PS: sorry about my poor english guys :^)
Comment by: Riooo on Tue, 23 Jun 2009 22:04:02 +0000
Yes, I run makepkg, it checks dependencies, all its OK but when it starts build , there is error.
"/lib/modules/2.6.29-ARCH/build: No such file or directory. Stop." This directory doesn't exist.
Comment by: thiagoc on Tue, 23 Jun 2009 21:56:45 +0000
@Riooo
No, you don't need the old one. Why you can't build the package? Is there any error?
Comment by: Riooo on Tue, 23 Jun 2009 21:50:51 +0000
I remove the old broadcom-wl, update system but now I can't build this package. Here is the question: this package is patch, so i must have the old or can I remove the old and install this one?
Comment by: andre.ramaciotti on Tue, 23 Jun 2009 21:44:36 +0000
piroflip, I think scosu is saying that 'patch' is a build-dependency, but I guess that packages from base-devel shouldn't appear as make-dependencies.

PS: it's working fine on a x86_64 intall, thanks.
Comment by: thiagoc on Tue, 23 Jun 2009 17:41:16 +0000
Just FYI, my system broke with the leprosys package.
Comment by: thiagoc on Tue, 23 Jun 2009 17:12:42 +0000
@kgas, works in my Dell Mini 9 without problems.

What you have to do:

- remove the old broadcom-wl package
- update the system with a wired network
- download, build and install this package
- reboot
Comment by: piroflip on Tue, 23 Jun 2009 17:11:56 +0000
@ scosu
What dependency are you talking about?
@ kgas
What kind of "did not work"? No interface appears after inserting module, problems with encryption or something else?
Comment by: kgas on Tue, 23 Jun 2009 16:56:35 +0000
sorry, it did not work with bcm4312 in dell mini 9 any help...
Comment by: scosu on Tue, 23 Jun 2009 16:02:55 +0000
There is another obvious build-dependency, patch ;)
Comment by: piroflip on Tue, 23 Jun 2009 15:49:59 +0000
Working with new 2.6.30 kernel. Please check x86_64 version.
Comment by: x-demon on Thu, 18 Jun 2009 13:12:35 +0000
i got it to work but not with leprosys's patches
Comment by: x-demon on Wed, 17 Jun 2009 13:37:40 +0000
Beta NOT works with 32-bit kernel 2.6.30
Comment by: Peasantoid on Mon, 15 Jun 2009 21:36:42 +0000
habarnam: I had an issue where the kernel would panic if I loaded the module at all. Turns out the .ko was just corrupted (I think) -- rebuilding it by hand solved the problem. (Mind you, this was with 2.6.29.4, custom kernel.)
Comment by: habarnam on Mon, 15 Jun 2009 18:27:50 +0000
Well, for me it still doesn't work.

I don't know what I'm doing wrong, but now with the required crypt modules it generates a kernel oops if I load it at boot time.
However if I load it by hand it doesn't crash but nothing wrong (or good) appears in the logs and still the wireless device is not available (also as a side notice:the wifi led doesn't light up, which does on 2.6.29).
Comment by: alperkanat on Sun, 14 Jun 2009 13:30:24 +0000
Works fine here after unloading ssb module.. Using Macbook Pro Aluminium with x86_64 Arch Linux btw..
Comment by: bardo on Sun, 14 Jun 2009 12:27:45 +0000
For encrypted networks I remind you that you have to load lib80211_crypt_wep or lib80211_crypt_tkip. If you don't have it, install compat-wireless from the aur.
Comment by: habarnam on Sun, 14 Jun 2009 11:02:31 +0000
@leprosys

I can't get the driver to work on my 32bit machine.

Dmesg says :
lib80211_crypt: unregistered algorithm 'NULL'
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'

So it seems it doesn't find TKIP to load. This happens for default arch kernel and for your ICE version.
Comment by: x-demon on Sat, 13 Jun 2009 04:47:51 +0000
Oh yes, i have a 32bit cpu
Comment by: bardo on Fri, 12 Jun 2009 22:05:38 +0000
Works fine for me with the latest 5.10.91.9-1. Arch x86_64, Broadcom BCM4322 (Macbook Aluminium). Tested with all 2.6.30 release candidates and with a custom built 2.6.30.
Comment by: x-demon on Fri, 12 Jun 2009 15:53:48 +0000
Tested on kernel 2.6.30 from [testing], not working. Gives me smthn about invalid frame size when compiling
CC [M] /root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/wl/sys/wl_linux.o
CC [M] /root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/wl/sys/wl_iw.o
/root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/wl/sys/wl_iw.c: In function ‘wl_iw_get_range’:
/root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/wl/sys/wl_iw.c:587: warning: the frame size of 1168 bytes is larger than 1024 bytes
CC [M] /root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/shared/linux_osl.o
/root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/shared/linux_osl.c: In function ‘osl_printf’:
/root/hybrid_wl/leprosys-pkgbuilds-9bde8bf3e009bfa119ab4ed5f37cf963280368af/broadcom-wl/src/src/shared/linux_osl.c:465: warning: the frame size of 1028 bytes is larger than 1024 bytes


and smthn anbout patch that ends in middle...
Comment by: x-demon on Thu, 11 Jun 2009 12:58:57 +0000
Tested it on kernel26zen-git from AUR. Gives me framebuffer panic (KMS enabled) and hang up. So not working for me.
Comment by: leprosys on Wed, 10 Jun 2009 20:43:03 +0000
I am currently on 2.6.30, the driver works with a new patch.
PGBUILD interested in this link:
http://tinyurl.com/mdsgns

Greetings
Comment by: piroflip on Wed, 10 Jun 2009 18:15:05 +0000
currently, no, but I'll renew PKGBULD when .30 will be in stable repository.
Comment by: x-demon on Wed, 10 Jun 2009 18:04:54 +0000
can it be build on new 2.6.30 kernel?
Comment by: Peasantoid on Sat, 06 Jun 2009 21:24:52 +0000
Update: No, it hasn't fixed itself, although there is something *VERY* unusual going on here: the driver only reports signal strength properly when I'm running a certain Python script that has NOTHING to do with networking. WTF?
Comment by: Peasantoid on Sat, 06 Jun 2009 16:23:22 +0000
Permissioning issue: I used `sudo iwconfig eth1`... it showed much less information than it should.
Network manager: Meh, it gave me a myriad of interesting problems when I tried to use it.

Curious thing, though -- wicd now seems to be working properly. I guess the driver problem fixed itself...?
Comment by: darose on Thu, 04 Jun 2009 20:45:19 +0000
Probably due to the permissioning issue - i.e., the driver code is written in such a way that only root user can query it for connection info. (See: http://bbs.archlinux.org/viewtopic.php?pid=536337#p536337)

Dumb code on Broadcom's part, IMO. I tried to write a fix for it (see my earlier comments here) but didn't do it correctly. If you're comfortable with C code and coding at the driver/kernel level, feel free to take a stab at a fix.

Frankly, though, dumb code on wicd's part too. They shouldn't key off of signal strength, but rather something like whether the driver is associated, whether dhcp loses the address, etc.

Dunno if this is much of a help for you though. Maybe you can switch to network manager as a workaround?
Comment by: Peasantoid on Thu, 04 Jun 2009 20:42:11 +0000
Forgot to add that it's a vanilla kernel (not from anything Arch-related).
Comment by: Peasantoid on Thu, 04 Jun 2009 20:38:13 +0000
Hey, I've noticed what seems to be a bug where the driver does not report certain essential status information (such as signal strength). One symptom of this is wicd constantly thrashing around and trying to reconnect because it thinks the connection has been lost. (Workaround: Wicd applet -> Preferences -> uncheck "Automatically reconnect on connection loss".)

This seems to be related to a number of Ubuntu bug reports:
https://bugs.launchpad.net/ubuntu/+source/wicd/+bug/334445
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/364413

Using kernel version 2.6.29.4.
Comment by: kralyk on Tue, 26 May 2009 17:44:17 +0000
tymiboss, thanks a millions for your comment!

I also forget to turn it on physically :D
lol such a banal mistake, anyway youre the man,
saved another hour of research, damnit :D
Comment by: andrew123456 on Mon, 11 May 2009 23:52:59 +0000
sudo iwconfig eth1 essid weefee key off
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.

anyone know why i'm getting this error?
also, iwconfig as normal user will not return link status.
Comment by: Sagattarii on Tue, 05 May 2009 09:07:22 +0000
@jaapvisser: i686 or x86_64? Kernel version? Testing? Yaourt?

For me it worked fine...
Comment by: jaapvisser on Mon, 04 May 2009 19:38:30 +0000
compile problem for linux-2.6.29-ARCH anybody a clue?

patching file wl_iw.c
make: Entering directory `/usr/src/linux-2.6.29-ARCH'
include/config/auto.conf:1: *** missing separator. Stop.
make: Leaving directory `/usr/src/linux-2.6.29-ARCH'
==> ERROR: Build Failed.
Comment by: tymiboss on Sun, 03 May 2009 19:01:53 +0000
And I finally solved my problem...I just forgot to turn the adaptator physically on with the switch...
It's indeed working better this way ! Sorry if I made you guys worry for your patches :-)
Comment by: bardo on Sat, 02 May 2009 22:26:15 +0000
Works fine with 4322 (MacBook 5,1) on x86_64. I can also add that it works under 2.6.30-rc4 after inclusion of this small patch: http://bugs.gentoo.org/attachment.cgi?id=189250 (and after installing the trace headers, but that's a kernel26 issue).
Comment by: cmlr on Sat, 02 May 2009 22:14:11 +0000
Works for me with broadcom 4328, arch 686, but not on hidden networks.
Comment by: leprosys on Sat, 02 May 2009 15:42:31 +0000
Work fine for me on x86_64

Greetings
Comment by: piroflip on Sat, 02 May 2009 12:26:00 +0000
Strange o_O What type of arch do you have x86 or x86_64?
Comment by: tymiboss on Sat, 02 May 2009 08:44:57 +0000
Mine is not working...:(

For example with "sudo iwlist scan" :
eth1 Failed to read scan data : Invalid argument


Argh !
Comment by: piroflip on Sat, 02 May 2009 04:18:43 +0000
Here is a version bump. Please check. Mine is working well :)
Comment by: tymiboss on Fri, 01 May 2009 23:46:44 +0000
"there is a new (patched?)"
It's not patched for 2.6.29 compiling, that I can assure ! It may be patched for hidden_essid...who knows...
Comment by: snowpine on Fri, 01 May 2009 23:27:05 +0000
Yup, there is a new (patched?) version of the broadcom driver as of 5/1, and as luck would have it, today is my first day using Arch! I am using ndiswrapper for the time being.
Comment by: tymiboss on Fri, 01 May 2009 23:10:31 +0000
Broadcom updated the drivers (now hybrid-portsrc-x86_64-v5_10_91_9). Anyway it does no compile on 2.6.29 and the patch can't be applied either...
I'm not good enough to fix that...I'm counting on you ! :)
Comment by: luinuz on Sat, 25 Apr 2009 19:52:48 +0000
The driver works fine with the new broadcom 4312 wireless, but it still doesn't support monitor mode to work with aircrack and airsnort.
Comment by: buttons on Sat, 18 Apr 2009 14:47:16 +0000
I tried darose's suggestion first, and it seems to be OK. It's at least made it through a few minutes of use, connecting and updating packages, which is far longer than it would go with the permissions patch (usually to getting the IP from dhclient or shortly thereafter.) It might be a fluke. I'll post back if it crashes again.
Comment by: darose on Fri, 17 Apr 2009 17:53:50 +0000
piroflip: perhaps you should remove the permissioning code from the broadcom-sta-5.10.79.10-linux-2.6.29.patch to address buttons' lockup issue. I suspect that code caused my system to crash as well, and I haven't had any such problems since I took it out.
Comment by: piroflip on Fri, 17 Apr 2009 17:09:41 +0000
buttons: What about compiling under .28 with patches applied? It should also compile.
Comment by: buttons on Fri, 17 Apr 2009 17:05:33 +0000
After downgrading to kernel 2.6.28 and removing the patches, it stops locking.
Comment by: buttons on Fri, 17 Apr 2009 17:05:08 +0000
This driver hard locks my computer in Ad-hoc mode. No response, no magic sysrq, nothing.
Comment by: scubanator87 on Fri, 17 Apr 2009 15:26:23 +0000
Whooohoo!! I just test WPA/2 Ent also and i can second that it works with the new kernel. This is teh best!!!!
Comment by: warriant on Fri, 17 Apr 2009 08:09:08 +0000
Good news: Doesn't freeze with WPA2 Enterprise anymore.
Comment by: scubanator87 on Thu, 16 Apr 2009 21:52:59 +0000
I can confirm this is working with 2.6.29-ARCH kernel and i will test the WPA/2 enterprise tomorrow.
Comment by: sm217 on Thu, 16 Apr 2009 20:05:27 +0000
Is this compatible with 2.6.29.1? I have problems, wl module builds and loads normally, but on ifconfig there are error messages. Part of dmesg after modprobe and ifconfig: https://gist.github.com/9080258f0e23dc2512ee
Comment by: piroflip on Thu, 16 Apr 2009 18:06:03 +0000
Yes, from http://www.broadcom.com/docs/linux_sta/wl_iw_v2.patch
Comment by: scubanator87 on Thu, 16 Apr 2009 18:01:11 +0000
So you included the WPA enterprise patch also?
Comment by: piroflip on Thu, 16 Apr 2009 14:12:53 +0000
That is a good point, darose. I'll check iwlist sources to see restrictions.
Comment by: darose on Thu, 16 Apr 2009 13:54:03 +0000
Thanks for checking it out piroflip. Are you 100% sure though? What if the ioctl call was attempting to alter the driver state - i.e., to set bit rate instead of query it? Is that not a possibility? It's obviously not a problem to let queries through, but I'd think we wouldn't want to let updates through too without a securty check. Am I wrong here, and that scenario's not possible?

Don't mean to be paranoid, but my system mysteriously crashed yesterday after I tried this change, which makes me a bit suspicious. But if you've got strong knowledge of driver code and you say it's OK, I'll trust your judgment.
Comment by: pygi on Thu, 16 Apr 2009 13:53:34 +0000
So um, you patched what to remove the need for lib80211_crypt_tkip in rc.conf?
Comment by: pygi on Thu, 16 Apr 2009 13:49:24 +0000
Congrats to everyone involved. So when will we do a barbecue? :P
Comment by: piroflip on Thu, 16 Apr 2009 12:39:27 +0000
darose:
You patch is absolutely harmless and that is just a matter of security level. Personally, I think that common user should be able to request wireless scan info with no restrictions.
Comment by: darose on Thu, 16 Apr 2009 11:58:13 +0000
@piroflip:

Just a heads up: I'm not sure that the permissioning patch I did is correct. My system crashed yesterday afternoon after integrating that, so I'm wondering if the module is responsible. I'd strongly suggest that someone knowledgeable about the inner workings of the driver review/vet the code I did and verify that removing the CAP_NET_ADMIN check on all ioctl calls won't have any negative consequences before you include that in the broadcom-sta-5.10.79.10-linux-2.6.29.patch.

Anyone around here who might be able to do that? If not, then I'd suggest you back that out of the patch to be safe. Better not to muck with kernel driver code if we don't know what we're doing.
Comment by: macros78 on Thu, 16 Apr 2009 11:31:14 +0000
Does channel 12 and 13 works for you? I have no luck. What do I need to make them work?
Comment by: fettouhi on Thu, 16 Apr 2009 07:56:05 +0000
Awesome, many thanks. I'll this package when I get home from work :).

Regards

André
Comment by: piroflip on Thu, 16 Apr 2009 04:35:01 +0000
You did a great job too, leprosys.
Comment by: leprosys on Thu, 16 Apr 2009 04:17:26 +0000
thank for the update piroflip :)
Comment by: piroflip on Thu, 16 Apr 2009 04:07:15 +0000
Thanks everybody, finally I sorted out "module dance" problem (thanks pygi). So I decided to patch driver sources to include lib80211_crypt_tkip module reques so you don't need to insert it to your rc.conf. Also I included all patches (hidden-essid, permissions) to satisfy all of you. I really appreciate you help.
Please test and report x86_64 problems.
Comment by: pygi on Wed, 15 Apr 2009 20:22:38 +0000
Piroflip,

not even with this dance?

sudo rmmod wl
sudo modprobe lib80211_crypt_tkip
sudo modprobe wl

Since I've put lib80211_crypt_tkip in rc.conf modules before wl, it works for me.
Comment by: darose on Wed, 15 Apr 2009 20:01:26 +0000
Ah. Found the permission issue. The driver is checking for CAP_NET_ADMIN before allowing any ioctl calls. I'm thinking this might not be necessary and/or overkill - can someone knowledgeable confirm?

When I apply the following patch, all is well and non-root users can successfully query connection info. Are there any potential negative consequences of this though?

[darose@daroselin broadcom-wl]$ cat cap-net-admin-removal-patch.diff
diff -uar src/wl/sys/wl_linux.c src-new/wl/sys/wl_linux.c
--- src/wl/sys/wl_linux.c 2009-02-09 16:43:32.000000000 -0500
+++ src-new/wl/sys/wl_linux.c 2009-04-15 15:44:11.574249224 -0400
@@ -1247,11 +1247,11 @@
}

WL_LOCK(wl);
- if (!capable(CAP_NET_ADMIN)) {
- bcmerror = BCME_EPERM;
- } else {
+// if (!capable(CAP_NET_ADMIN)) {
+// bcmerror = BCME_EPERM;
+// } else {
bcmerror = wlc_ioctl(wl->wlc, ioc.cmd, buf, ioc.len, wlif->wlcif);
- }
+// }
WL_UNLOCK(wl);

done1:
Comment by: piroflip on Wed, 15 Apr 2009 18:23:58 +0000
pygi: This is great, but I can't connect with any PKGBUILD and patches I tried so far, may be you give me working PKGBUILD and if it will work on my box I'll update PKGBUILD.
Comment by: darose on Wed, 15 Apr 2009 17:28:54 +0000
Is there a permissions issue with this driver that prevents non-root users from being able to query connection info details?

See: http://bbs.archlinux.org/viewtopic.php?pid=536337#p536337
Comment by: notizblock on Wed, 15 Apr 2009 15:38:30 +0000
that would be great.
Comment by: pygi on Wed, 15 Apr 2009 15:15:38 +0000
If this package won't be updated soon, I'll create a new, updated one and host it on AUR under different name with Replaces=(broadcom-wl) and Conflicts=(broadcom-wl).
Comment by: suicideducky on Wed, 15 Apr 2009 09:18:13 +0000
OK wireless is working, following the manual instructions on leprosys blog http://www.leprosys.info/2009/03/broadcom-80211-linux-sta-driver-en.html

But the PKGBUILD didn't work for me.
Comment by: fettouhi on Wed, 15 Apr 2009 06:13:23 +0000
Can we please get the hidden ESSID patch included for this package? I would like to know if this patch actually works with hidden wpa2.

Regards

André
Comment by: suicideducky on Tue, 14 Apr 2009 21:14:33 +0000
Here are the md5sums for the files inhttp://leprosys.net/arch/PKGBUILD/broadcom-wl/files/
md5sums=('7dd0b216ce8b9b4289425e6a71628232'
'54eb0f80837b978c214b2c33e891a992'
'ce34ee16287c2d4092ee5705e304b5e2')
generated via makepkg -g
I swapped them over with the ones in the PKGBUILD I have locally and all went fine :)

Also for the record, before I made this pkg, an iwconfig would still report my interface as being wireless ??
Comment by: suicideducky on Tue, 14 Apr 2009 21:10:06 +0000
When building a package with the files from http://leprosys.net/arch/PKGBUILD/broadcom-wl/files/ makepkg is now throwing invalid checksums for both wl_iw_v2.patch and hybrid-portsrc-x86_32-v5_10_79_10.tar.gz
Comment by: lenglemetz on Tue, 14 Apr 2009 20:00:54 +0000
@bigkahunaca : Thanks, it's good for my broadcom BCM4312 802.11b/g (rev 01) in x86_64
Comment by: bigkahunaca on Tue, 14 Apr 2009 19:49:25 +0000
EDIT: @fettouhi: It did not work when I hid the ESSID though.
Comment by: bigkahunaca on Tue, 14 Apr 2009 19:48:30 +0000
Using the files found @ http://leprosys.net/arch/PKGBUILD/broadcom-wl/files/ I was able to get my Broadcom BCM4311 802.11b/g WLAN (rev 02) card to work with my router using WPA2-PSK [AES]. Thus far no lockups or other negative effects. I'm using a HP dv6404ca laptop btw.

@fettouhi: It did not work when I hit the ESSID though.

@leprosys: Kudos my friend, thank you for this.
Comment by: pygi on Tue, 14 Apr 2009 11:35:43 +0000
If you don't want to maintain this package/don't have time, please orphan it so someone else could take it.
Comment by: suicideducky on Tue, 14 Apr 2009 11:01:27 +0000
So is this the wl_iw patch? but NOT the wl_iwv2 patch?
And also the STA patch?
Comment by: ziarkaen on Mon, 13 Apr 2009 20:26:47 +0000
People have this driver working with the aforementioned patch, which depends on kernel26<=2.6.29 rather than kernel26<2.6.29. Can the package maintainer not update this package to use the patch, as .29 is now the stable kernel in the main Arch repos. This package is necessary to avoid repeated file copying after kernel upgrades to install the kernel modules.
Comment by: bardo on Mon, 13 Apr 2009 08:22:40 +0000
@fettouhi: I don't have any hidden WPA network to test, sorry.
Comment by: fettouhi on Mon, 13 Apr 2009 06:04:36 +0000
@bardo: does that include hidden WPA networks also, i.e. where the ESSID is hidden?

Regards

André
Comment by: bardo on Sun, 12 Apr 2009 23:07:07 +0000
Sorry, I'm late to the party. I have a perfectly working wl driver (in fact, a lot better than with 2.6.28). I use two patches: wl_iw.patch and http://www.leprosys.net/files/broadcom-sta-5.10.79.10-linux-2.6.29.patch. This alone wasn't enough: I use a custom kernel, and I had no 'lib80211_crypt_tkip' module, don't know why. I compiled compat-wireless from the AUR and everything is now perfect. I can also connect to the WPA networks that I had problems with before.
Comment by: suicideducky on Sun, 12 Apr 2009 00:16:42 +0000
I moved to b43 and still had the same problems, so its almost definitely wpa-supplicant as far as I can tell.
Comment by: mythicllama on Sat, 11 Apr 2009 17:43:50 +0000
scubanator87: I tried ndiswrapper with the drivers off of HP's website for mine yesterday and it didn't work. Wouldn't bring up an interface for me.
Comment by: scubanator87 on Sat, 11 Apr 2009 17:33:22 +0000
Has any one tried switching back to ndiswrapper witht he new kernel to see if it works. Thats how i was working originally.
Comment by: mythicllama on Sat, 11 Apr 2009 16:45:42 +0000
I believe I'm having trouble with wpa_supplicant also on my HP dv4's Broadcom 4312. I can iwlist scan my network perfectly fine (WPA-PSK with TKIP) but after about 9-10 seconds, it cuts out and throws that it recieves invalid crypts. I don't have a GUI at the moment to test wicd or NetworkManager.
Comment by: piroflip on Sat, 11 Apr 2009 13:33:33 +0000
I have been using netcfg2 which, I believe, is using wpa_supplicant. I was not able to connect. So I decided to try wicd. No connection either.
I can see wireless networks near me by scanning though.
Comment by: suicideducky on Sat, 11 Apr 2009 08:50:35 +0000
piroflip: are you using wpa_supplicant per chance?
Can you detect your wireless access point by scanning?
ie; sudo iwist eth0 scan
If so it may not be the driver but may infact be wpa_supplicant, I beleive I am having the same issue.
Comment by: piroflip on Sat, 11 Apr 2009 07:55:30 +0000
Sorry guys, but I couldn't connect to my access (WPA-passphrase) point with any patches I tried so far. Not even with your PKGBUILD, leprosys.
Comment by: scubanator87 on Fri, 10 Apr 2009 16:28:51 +0000
The WPA ent patch i mentiond is here: http://www.broadcom.com/support/802.11/linux_sta.php
Comment by: scubanator87 on Fri, 10 Apr 2009 16:28:14 +0000
Pleas update since .29 is now in core. Also is there any way you can apply the patch that they have on the site that fixes enterprise WPA? as of now every time i try to connect to a WPA/2 enterprise network, it will cause a hard lockup on my machine and requrie a hard reset.

Thank you.
Comment by: leprosys on Fri, 10 Apr 2009 16:25:32 +0000
Here other PKBUILD:
http://leprosys.net/arch/PKGBUILD/broadcom-wl/files/

greetings
Comment by: nuovodna on Fri, 10 Apr 2009 11:56:27 +0000
On this post there are another way to patch the drivers:

http://ubuntuforums.org/showthread.php?p=6976510
Comment by: L0cutus on Thu, 09 Apr 2009 14:30:02 +0000
seems 2.6.29 is in core now :)
Comment by: fettouhi on Thu, 09 Apr 2009 13:18:32 +0000
2.6.29 kernel is instable now can we get this updated maybe?

Regards

André
Comment by: sm217 on Wed, 08 Apr 2009 12:52:41 +0000
None of above instructions helps, still get segfault on loading wl.
Comment by: nuovodna on Tue, 07 Apr 2009 11:00:52 +0000
Here there is the instructions to compile this driver on the 2.6.29 kernel

http://divilinux.netsons.org/index.php/archives/960
Comment by: piroflip on Sun, 05 Apr 2009 06:03:54 +0000
Current kernel version is kernel26-2.6.28.8-1. No mismatch. Unflagging.
Comment by: freeobject on Sat, 04 Apr 2009 21:31:50 +0000
Mismatch new kernel dependencies. Outdated it.
Comment by: sm217 on Sat, 04 Apr 2009 08:06:19 +0000
Fixed, I suddenly had TKIP crypting disbled :P
Comment by: leprosys on Sat, 04 Apr 2009 07:13:17 +0000
Hi guys, I prefer to do this manually in my blog I put the method (in Spanish):
http://www.leprosys.info/2009/03/broadcom-80211-linux-sta-driver-en.html
Comment by: sm217 on Sat, 04 Apr 2009 07:04:00 +0000
@D1G1T: Did you apply any patches to your kernel? And could you please share your .config?
I tried with 29.1 & wicd, got some errors when loading wl and kernel panic on wicd daemon start.
Comment by: D1G1T on Wed, 01 Apr 2009 03:52:09 +0000
I am using wicd and no prolem with it.
Comment by: sm217 on Tue, 31 Mar 2009 12:53:40 +0000
For me it's not random. It crashes either when wl module is loaded or when I do 'netcfg wifi'.
Comment by: clarious on Tue, 31 Mar 2009 11:06:50 +0000
@sm217: Same here, I patched it myself and I am experiencing random hanging
Comment by: sm217 on Mon, 30 Mar 2009 19:55:53 +0000
Hmm, patched wl crashes my 2.6.29 kernel :<
Comment by: habarnam on Sun, 29 Mar 2009 15:32:34 +0000
Also I guess you need to modify the broadcom-wl.install file:

post_install() {
KERNEL_VERSION=$(uname -r)
depmod $KERNEL_VERSION
}

post_upgrade() {
post_install
}

post_remove() {
post_install
}
Comment by: D1G1T on Sun, 29 Mar 2009 12:32:11 +0000
I modified PKGBUILD for 2.6.29 make things working again, because I hate downgrade:

# Maintainer: Alexandr Kotov nektokot at gmail dot com
# Contributor: Carl Mueller math at carlm dot e4ward dot com
pkgname=broadcom-wl
pkgver=5.10.79.10
pkgrel=2
pkgdesc="Broadcom 802.11abg Networking Drivers"
arch=('i686 x86_64')
[ "$CARCH" = "i686" ] && ARCH=x86_32
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.broadcom.com"
license=('MIXED/Proprietary')
depends=('kernel26>=2.6.29')
install=broadcom-wl.install
source=('http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-'$ARCH'-v5_10_79_10.tar.gz'
'http://www.leprosys.net/files/broadcom-sta-5.10.79.10-linux-2.6.29.patch'
'wl_iw.patch'
'license.patch')
md5sums=('7dd0b216ce8b9b4289425e6a71628232'
'ce34ee16287c2d4092ee5705e304b5e2'
'a04371c0a56178369104b3d283ed8e01'
'd06739b5136096cffc949051e3edc119')
[ "$CARCH" = "x86_64" ] && md5sums=('72af629785af3777bc7398f742fb87af')

build() {
patch -p1 -d $srcdir/src/wl/sys < wl_iw.patch
patch -p1 -d $srcdir/src/wl/sys < broadcom-sta-5.10.79.10-linux-2.6.29.patch
patch -p1 -d $srcdir/src/wl/sys < license.patch
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` || return 1
install -D -m 755 wl.ko $pkgdir/lib/modules/$(uname -r)/kernel/drivers/net/wireless/wl.ko || return 1
}


#####################################

run makepkg and install created package using pacman -U. After that add wl and lib80211_crypt_tkip to rc.conf MODULES.

you can activate modules right after installation by modprobe.

Enjoy.
Comment by: piroflip on Thu, 26 Mar 2009 05:12:18 +0000
ieee80211_crypt_tkip have been renamed in 2.6.29. net/{ieee80211/ieee80211_crypt_tkip.c => wireless/lib80211_crypt_tkip.c}
Comment by: Bogart on Wed, 25 Mar 2009 21:34:58 +0000
I patched it manually and I've been running it for a while without issues. The only strange thing is that the module ieee80211_crypt_tkip is missing in kernel 2.6.29. However, my connections works ok without it.
Comment by: Bogart on Wed, 25 Mar 2009 17:31:57 +0000
I'm trying to use that patch from Gentoo but it fails for some reason, and I know nothing about patching. Could someone provide a working patch? I'd really like to test this because I need kernel .29 for my sound to work.
Comment by: Limoto on Tue, 24 Mar 2009 20:57:00 +0000
Thanks darose, i'll try it...
Comment by: bardo on Tue, 24 Mar 2009 20:22:03 +0000
An important caveat for those wanting to try this driver with 2.6.29: I didn't try it with the latest version, but I tested 5.10.27.14 with gentoo's patch on many 2.6.29-rc kernels and I experienced oopses and hangs at loading time.
I suggest to remove the wl module from your DAEMONS array, unless you want to have some fun with the recovery cd! I found it out the worst way.
Comment by: piroflip on Tue, 24 Mar 2009 17:59:33 +0000
Gentoo community has patch against 2.6.29 and, so when kernel package (2.6.29) will show up in core I'll make another release.
Comment by: Bogart on Tue, 24 Mar 2009 15:45:19 +0000
That package works for me, but I'm not using WPA, so I can't say if it fixes the bug or not.

I live in the EU and I also see 11 channels. Not sure what that means, anyway.

One question. Now that kernel 2.6.29 is out, will this driver work with it? Or will we need to wait for Broadcom to update it and then rebuild the package?
Comment by: piroflip on Mon, 23 Mar 2009 19:18:06 +0000
Here is an update with latest patch from the Broadcom. This patch cannot be applied straight from the site, so I had to cut the first hunk off to make it applicable. Please check. Mines works well.
Comment by: muczy on Mon, 23 Mar 2009 15:06:45 +0000
Oh yeah... That was a really naughty bug, I hope this fixes it. Please include this in the package!
Btw. Does anybody use this driver, who is living in a country that is non-US? I live in the EU, where I should see 13 channels. I set this with crda and iw, but I can still see only 11 channels with 'iwlist freq'...
Comment by: bardo on Mon, 23 Mar 2009 15:04:03 +0000
Hi all. Just wanted to point out that Broadcom has published on the driver's page (http://www.broadcom.com/support/802.11/linux_sta.php) a "Patch for WPA-ENterprise hang". This is official, so I think it should be applied; could be useful to someone.
Comment by: darose on Mon, 23 Mar 2009 14:28:46 +0000
I've got both:

http://www.darose.net/hybrid-portsrc-x86_64-v5_10_27_14.tar.gz
http://www.darose.net/broadcom-wl-5.10.27.14-1-x86_64.pkg.tar.gz

HTH,

DR
Comment by: Limoto on Sat, 21 Mar 2009 19:19:40 +0000
Have anybody a backup of 5.10.27.14 sources (or 64b package)? Current version isn't working for me :-(
Comment by: fettouhi on Fri, 06 Mar 2009 18:55:41 +0000
has anybody gotten trhe hidden essid patch to work with wpa2?

Regards

André
Comment by: bardo on Fri, 06 Mar 2009 11:22:15 +0000
Works fine, even though it didn't solve my WPA AP connection problems.

By the way, you don't need to resort to the cp/sed/mv game: sed accepts the -i parameter, which does in-place substitution and directly modifies the file. Also, I read on the gentoo bug tracker that the vlan patch isn't needed anymore: http://bugs.gentoo.org/show_bug.cgi?id=248450#c39
Comment by: piroflip on Fri, 06 Mar 2009 10:42:29 +0000
Version bump. Please check.
Comment by: muczy on Fri, 06 Mar 2009 10:35:11 +0000
New driver on 5. March: v5_10_79_10. Hope this will fix my problems about regulatory domain and PEAP...
Comment by: fettouhi on Thu, 26 Feb 2009 20:13:31 +0000
@Cleophas: Did you use the patch as mentioned before?

Regards

André
Comment by: Cleophas on Thu, 26 Feb 2009 02:44:13 +0000
I too was having problems getting connected to my home AP that uses a hidden SSID. I didn't want to give up so while reading the wpa_supplicant.conf file I noticed it mentioned that scan_ssid defaults to 0 and that setting it to scan_ssid=1 would "...(this can be used to find APs that do not accept broadcast SSID or use multiple SSIDs)..."

I added scan_ssid=1 to my home network block in wpa_supplicant.conf and after running the wpa_supplicant command; bingo it Associated no problems!

Comment by: warriant on Sun, 22 Feb 2009 09:20:41 +0000
I am experiencing the same problem as muczy... Ndiswrapped drivers somehow work in this case, though.
Comment by: cmlr on Sun, 15 Feb 2009 23:07:55 +0000
I tried the patch, but I still can't connect to my hidden network at home.
Comment by: muczy on Sat, 14 Feb 2009 13:46:32 +0000
This makes a kernelpanic, when I try to connect to a WPA2-Enterprise mschapv2 network...
Comment by: fettouhi on Sat, 07 Feb 2009 20:51:56 +0000
This looks interesting could we maybe get that patch added to this package :-).

Regards

André

PS. Thanks for the heads up bardo.
Comment by: bardo on Fri, 06 Feb 2009 00:24:43 +0000
For the hidden ESSID problem, did you take a look at the gentoo patch? You can find it here: http://bugs.gentoo.org/attachment.cgi?id=180679
Comment by: fettouhi on Sun, 01 Feb 2009 13:43:07 +0000
Then the driver is missing that feature for some reason, which I find very strange.

Regards

André
Comment by: tmrc on Tue, 27 Jan 2009 20:09:23 +0000
I can't connect to hidden wpa2 networks too...
works fine with broadcasted essid
Comment by: bardo on Sat, 24 Jan 2009 15:23:33 +0000
@André: sorry, I didn't understand yours was an inclusive "and"... didn't try with hidden SSID. They don't provide a driver changelog, though, so I think the only option you have is a quick test... :P
Comment by: fettouhi on Sat, 24 Jan 2009 12:41:15 +0000
@bardo: But are you using a hidden ESSID also? Is your ESSID being broadcasted or not because WPA2 is working for me too, no problem there as long as I don't use a hidden ESSID.

Regards

André
Comment by: bardo on Sat, 24 Jan 2009 12:21:54 +0000
This package has always worked for me with WPA2. In fact I'm using a WPA2 connection right now. It's the same WPA connection that gave me problems, upgraded to WPA2 it started working very well, and it never disconnects.
Comment by: fettouhi on Fri, 23 Jan 2009 22:03:23 +0000
Anybody know if this new version works with hidden ESSID and WPA2?

Regards

André
Comment by: muczy on Thu, 22 Jan 2009 16:44:56 +0000
New version works for me, however I still can see only channels 1-11... I've set my regdom to HU, or EU, but it does nothing... Anybody has this problem?
Comment by: piroflip on Thu, 22 Jan 2009 12:55:29 +0000
Version bump. Please check.
Comment by: total_noob on Thu, 22 Jan 2009 04:36:52 +0000
How can I get this installed since broadcom updated their version?

I tried to modify the PKGBUILD file to get the new tar.gz from broadcom, and changed the MD5 in PKGBUILD.
It downloaded fine, but didn't complete the build process.

I did pretty good getting arch installed onto this old laptop, just need to get the broadcom-wl driver working an i'm all set.
Comment by: henrikbrink on Thu, 22 Jan 2009 00:40:16 +0000
Hey guys,

just wanted to let you know that the version and links changed. Its now 5.10.27.14, and the new links can be found at:

http://www.broadcom.com/support/802.11/linux_sta.php
Comment by: odius on Tue, 20 Jan 2009 15:00:39 +0000
I corrected the problem after I posted here...

Basically I just uncommented the line below in the wireless_down() function of /usr/lib/network/wireless.subr.

#ifconfig $INTERFACE down

See http://bbs.archlinux.org/viewtopic.php?id=56093 for more information.
Comment by: cemsbr on Tue, 20 Jan 2009 05:51:51 +0000
odius, I'm also having this problem. Suspend fails because of this. I haven't tried to fix it yet.
Comment by: odius on Tue, 20 Jan 2009 04:35:29 +0000
Anyone else have the problem with netcfg failing to bring the adapter down? I haven't had a chance to look into it much, but deleting two files in /var/run/network (interfaces/eth1 and profiles/<profile name>) allows the network to start again. This happens with all three wireless networks I've setup thus far and it happens on a different laptop using the same card. Anyone have any thoughts?
Comment by: cemsbr on Tue, 20 Jan 2009 04:24:34 +0000
Does not work for me. No debug messages, no wlan0, nothing happens.
Comment by: piroflip on Sun, 18 Jan 2009 16:39:30 +0000
added dependency for 2.6.29.
Comment by: piroflip on Sun, 18 Jan 2009 16:08:32 +0000
Fixed. Please check.
Comment by: shining on Sun, 18 Jan 2009 15:55:32 +0000
Please fix the depends line to be similar to every other kernel modules.
This is wrong and dangerous :
depends=('kernel26>=2.6.27-2')

This dependency is satisfied by kernel 2.6.28, but a package built against 2.6.27 is not going to work after you upgrade to 2.6.28, so you lose wireless, which can be rather annoying.
http://bbs.archlinux.org/viewtopic.php?id=63187
Comment by: sense on Sun, 18 Jan 2009 03:04:06 +0000
In post_install() of broadcom-wl.install KERNEL_VERSION needs to be changed to 2.6.28-ARCH.
Comment by: atolbert on Sat, 17 Jan 2009 20:52:36 +0000
Don't see any reason why this was flagged out of date, Version is current at 5.10.27.2 and the package appears to be functional...unflagging it
Comment by: muczy on Sat, 17 Jan 2009 08:38:45 +0000
With kernel26 2.6.28, I can set my regdom, but I can only see 11 channels still...
Comment by: muczy on Sat, 10 Jan 2009 21:36:35 +0000
I have a 4312 b/g: [14e4:4315] (rev 01)
I've uncommented my country flag, then tried to start /etc/rc.d/wireless-regdom.
Comment by: bardo on Sat, 10 Jan 2009 21:32:50 +0000
Sorry for spamming, I forgot an important detail: I'm running 2.6.28-3 from [testing], which is also the repo where you can find crda. I don't think you can do that in kernels < 2.6.28.
Comment by: bardo on Sat, 10 Jan 2009 21:29:11 +0000
@muczy: what did you do exactly? I have a BCM4322 (the one you find in the new MacBooks), PCI ID 14e4:432b. I installed crda, uncommented my regdom (IT) in /etc/conf.d/wireless-regdom and started the wireless-regdom daemon, everything worked.
Comment by: muczy on Sat, 10 Jan 2009 13:39:15 +0000
@bardo: it says: command failed: Operation not supported (-95)... :(
Comment by: bardo on Sat, 10 Jan 2009 10:08:15 +0000
Same problem for me with openwrt-based WPA-PSK access points, specifically a Linksys reflashed WRT54G and a Fonera with the original firmware: the connection goes up & down every few minutes. No problems with a Linksys WAP54G (not reflashed).

@muczy: did you have a look at the crda package?
Comment by: tankmcp on Thu, 08 Jan 2009 16:39:07 +0000
Using WPA mixed connects then random disconnects, reconnects. No clue. Dmesg gives
TKIP: RX tkey->key_idx=1 frame keyidx=2 priv=f70280c0
Else I cannot see what is causing this. Used netcfg2 and network managager. Cannot shutdown interface while this is happening either.
Comment by: muczy on Tue, 06 Jan 2009 13:06:03 +0000
This works for me with WPA2-PSK on a not hidden network.
Btw. I can only see 11 frequencies, but in the EU (I'm in Hungary), we could use 13 frequencies. I've set options cfg80211 ieee80211_regdom=EU, but I can see 11 channels only... And ideas?
Comment by: scubanator87 on Tue, 06 Jan 2009 04:16:41 +0000
I had some time so i tested encryption. Im using wicd for my network management.

I was unable to get WPA2 to work at all using hidden and not using hidden.

WPA does work with showing my ssid but not on hidden.

I didnt test WEP.

Hidden works fine with out encryption
Comment by: fettouhi on Sun, 04 Jan 2009 19:41:52 +0000
Again can anybody get this package to work with WPA2 and hidden ESSID?

Regards

André
Comment by: scubanator87 on Fri, 02 Jan 2009 17:56:15 +0000
Agreed. If you have not already, vote please!
Comment by: scottishduck on Fri, 02 Jan 2009 16:53:07 +0000
Excellent package. Deserves a move to community!
Comment by: piroflip on Thu, 01 Jan 2009 07:11:46 +0000
Thank for help, updated the package. As soon as 2.6.28 goes to the core i'll update .install.
Comment by: odius on Wed, 31 Dec 2008 20:52:00 +0000
Good job, atolbert. Worked perfectly.
Comment by: odius on Wed, 31 Dec 2008 20:47:28 +0000
My guess is (someone please correct me if I am wrong) that the src/wl/sys/wl_linux.c file has changed enough that the lines being added by the PKGBUILD via sed are either in the wrong place or are no longer needed. I haven't tried it without those lines in the PKGBUILD, but the module seems to build fine when I follow Broadcom's brief instructions and run make myself.

I doubt it's a kernel specific issue. I'm still running 2.6.27.
Comment by: atolbert on Wed, 31 Dec 2008 20:44:51 +0000
Odius, got it working. PKGBUILD needs to be changed so:

\ ' -e '291 i\
extern int dev_wlc_intvar_set(struct net_device \*dev, char \*name, int val);\

is changed to

\ ' -e '284 i\
extern int dev_wlc_intvar_set(struct net_device \*dev, char \*name, int val);\

because the source changed, the extern needed to be moved up a few lines
Comment by: atolbert on Wed, 31 Dec 2008 20:36:02 +0000
I am having the same issue as you Odius on x86_64 with Kernel 2.6.28-ARCH. Looking into it as well.
Comment by: odius on Wed, 31 Dec 2008 19:56:27 +0000
New version of the driver fails to build with current package build.

/var/abs/local/broadcom-wl/src/src/wl/sys/wl_linux.c: In function ‘wl_if_setup’:
/var/abs/local/broadcom-wl/src/src/wl/sys/wl_linux.c:293: warning: ISO C90 forbids mixed declarations and code
/var/abs/local/broadcom-wl/src/src/wl/sys/wl_linux.c: In function ‘wl_attach’:
/var/abs/local/broadcom-wl/src/src/wl/sys/wl_linux.c:446: error: implicit declaration of function ‘dev_wlc_intvar_set’
/var/abs/local/broadcom-wl/src/src/wl/sys/wl_linux.c:293: note: previous declaration of ‘dev_wlc_intvar_set’ was here
make[1]: *** [/var/abs/local/broadcom-wl/src/src/wl/sys/wl_linux.o] Error 1
make: *** [_module_/var/abs/local/broadcom-wl/src] Error 2
make: Leaving directory `/usr/src/linux-2.6.27-ARCH'
==> ERROR: Build Failed.
Aborting...

This is on x86_64. I'll post again if I figure out what's wrong.
Comment by: atolbert on Wed, 31 Dec 2008 19:51:08 +0000
Looks like broadcom released a new driver just today. New link is:

http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86-32_5_10_27_12.tar.gz
Comment by: caskale13c on Wed, 31 Dec 2008 16:45:12 +0000
I made this package work with 2.6.28-1 by:

1. Modify the broadcom-wl.install file by changing the KERNEL_VERSION to 2.6.28-ARCH
2. Modify the PKGBUILD file by changing depends to ('kernel26>=2.6.28-1')
3. Remake the package with makepkg -f

troy
Comment by: fettouhi on Tue, 30 Dec 2008 13:05:06 +0000
scubanator87: You said that you could connect to your hidden network. What do you use to connect with and what encryption do you use?

Regards

André
Comment by: atolbert on Tue, 30 Dec 2008 01:51:06 +0000
not working for me either after upgrading to 2.6.28. I downgraded back to 2.6.27 and i'm up again. If you are like me and don't have access to an ethernet port you can do downgrade to get wireless working again:

sudo pacman -U /var/cache/pacman/pkg/nvidia-177.82-1-<ARCH>.pkg.tar.gz /var/cache/pacman/pkg/kernel26-2.6.27.10-1-<ARCH>.pkg.tar.gz

the nvidia pkg is only required if you have an Nvidia card.

See: http://wiki.archlinux.org/index.php/Kernel_Panics#Roll_back_to_previous_kernel_version for more information on downgrading your kernel.

Hoping to find a way around this, will post again if I can get it working in 2.6.28
Comment by: maledictvm on Mon, 29 Dec 2008 23:35:30 +0000
Has anyone been able to get it working with a 2.6.28-kernel?
Comment by: atolbert on Sat, 20 Dec 2008 02:46:02 +0000
Thank the heavens for this package! Following the instructions here: http://wiki.archlinux.org/index.php/Broadcom_BCM4312 , I was FINALLY able to get things right with WPA2. Works like a charm :)

Some tips: I'm not sure if my previous configurations helped or not, but be sure that if you are using wicd to use wext for WPA Supplicant Driver. Also, make absolutely sure that !b43 is somewhere in your MODULES list in /etc/rc.conf
Comment by: scubanator87 on Wed, 17 Dec 2008 17:15:25 +0000
i dont know about the WPA2 part but i know my hidden network works fine. Ill try and test it tonight.
Comment by: fettouhi on Wed, 17 Dec 2008 10:29:01 +0000
Can anyone get this driver to work with a hidden essid and wpa2? I can get it to work when the essid is broadcasting.

Regards

André

PS. Thanks for the update!
Comment by: piroflip on Sun, 14 Dec 2008 11:23:47 +0000
version update, please check 64-bit version
Comment by: buttons on Sat, 13 Dec 2008 18:28:01 +0000
404 error :(
Comment by: scubanator87 on Fri, 12 Dec 2008 22:35:00 +0000
Strange though, cant seem to find a change log or anything...
Comment by: fettouhi on Fri, 12 Dec 2008 22:02:23 +0000
New version is out 5_10_27_11.

Regards

André
Comment by: cemsbr on Thu, 20 Nov 2008 17:40:15 +0000
CONNECTION="wireless"
DESCRIPTION="wireless@home"
INTERFACE=eth1
HOSTNAME=sti
ESSID="cemsbrap"
TIMEOUT="5"
IP="static"
IFOPTS="192.168.0.100"
GATEWAY=192.168.0.1
DNS1=208.67.222.222
DNS2=208.67.220.220
Comment by: piroflip on Thu, 20 Nov 2008 12:47:49 +0000
cemsbr, please post your netcf2 config.
Comment by: cemsbr on Wed, 19 Nov 2008 19:51:17 +0000
I'm having problems with netcfg2, but network-manager works fine with this driver.
Comment by: scubanator87 on Wed, 19 Nov 2008 19:31:30 +0000
mente:

If it does not work for you and b43 does then you should just stick with b43. This driver really only is to fill the gap of b43 support (AFAIUI).

Also b43 is open source where as this driver is not. :-D
Comment by: mente on Wed, 19 Nov 2008 18:18:12 +0000
It doesn't work for me either. b43 works fine, this one - not :(. I have HP nx7400, wifi Broadcom BCM4311. Does anyone have any ideas?
Comment by: scubanator87 on Tue, 21 Oct 2008 11:47:24 +0000
piroflip, thank you for updating and including patch. SSH is now working.

Good job team!
Comment by: piroflip on Tue, 21 Oct 2008 07:34:11 +0000
Updated .install to work with yaourt.
Comment by: scubanator87 on Mon, 20 Oct 2008 23:19:38 +0000
so is the .install going to be updated to work with yaourt then?
Comment by: cmlr on Mon, 20 Oct 2008 18:43:52 +0000
It works with makepkg. To make it work with yaourt, delete the first line of broadcom-wl.install
Comment by: Sagattarii on Mon, 20 Oct 2008 12:42:28 +0000
does not work for me :(

it worked 3 days ago, really fine. But after fresh install (with new kernel?) it does not work anymore.

--------------- snip ----------------
==> Beginne build()...
make: Entering directory `/usr/src/linux-2.6.27-ARCH'
LD /tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/built-in.o
CC [M] /tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/src/wl/sys/wl_linux.o
CC [M] /tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/src/wl/sys/wl_iw.o
CC [M] /tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/src/shared/linux_osl.o
LD [M] /tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/wl.o
/tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/lib/wlc_hybrid.o_shipped: file not recognized: File format not recognized
make[1]: *** [/tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src/wl.o] Fehler1
make: *** [_module_/tmp/yaourt-tmp-root/aur-broadcom-wl/broadcom-wl/src] Fehler2
make: Leaving directory `/usr/src/linux-2.6.27-ARCH'
==> FEHLER: Build fehlgeschlagen.
Breche ab ...
Error: Makepkg was unable to build broadcom-wl package.

root@executor ~ #

--------------- snip ----------------

Please fix this :) Thanks for your work
Comment by: piroflip on Mon, 20 Oct 2008 07:46:27 +0000
cmlr, scubanator87, thanks for your help. Updated PKGBUILD.
Comment by: cmlr on Mon, 20 Oct 2008 04:24:34 +0000
OK, try this PKGBUILD. Don't forget to use the post install file included with the Package.

###################
pkgname=broadcom-wl
pkgver=5.10.27.6
pkgrel=5
pkgdesc="Broadcom 802.11abg Networking Drivers"
arch=('i686 x86_64')
[ "$CARCH" = "i686" ] && ARCH=x86_32
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.broadcom.com"
license=('Broadcom')
depends=('kernel26>=2.6.27-2')
install=broadcom-wl.install
source=('http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-'$ARCH'_5_10_27_6.tar.gz')
md5sums=('7f50d89179e637225bd97022b323c27e')
[ "$CARCH" = "x86_64" ] && md5sums=('d61e5ad289fc5f0b62e0656f90b451a7')

build() {
mv $srcdir/src/wl/sys/wl_iw.c $srcdir/src/wl/sys/wl_iw.c.old
sed -e 's/iwe_stream_add_.....(/&info, /' -e '127 c\
int' <$srcdir/src/wl/sys/wl_iw.c.old >$srcdir/src/wl/sys/wl_iw.c
mv $srcdir/src/wl/sys/wl_linux.c $srcdir/src/wl/sys/wl_linux.c.old
sed -e '441 i\
\/\* Work around\. Default vlan_mode to off \*\/\
dev_wlc_intvar_set(dev, "vlan_mode", 0);\
\ ' -e '291 i\
extern int dev_wlc_intvar_set(struct net_device \*dev, char \*name, int val);\
\ ' -e '248 i\
MODULE_LICENSE("MIXED\/Proprietary");\
\ ' <$srcdir/src/wl/sys/wl_linux.c.old >$srcdir/src/wl/sys/wl_linux.c
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` || return 1
install -D -m 755 wl.ko $pkgdir/lib/modules/$(uname -r)/kernel/drivers/net/wireless/wl.ko || return 1
}

Comment by: scubanator87 on Sun, 19 Oct 2008 22:01:29 +0000
There is a know bug in this driver that keeps ssh from working. It would be nice to get the patch added to the PKGBUILD

To see if this is affecting you, just try to ssh to a server you have access to, and after entering your password it will time out.

The deb form i found it:
http://forums.debian.net/viewtopic.php?t=30648

The bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/259816

A patch:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid-lrm.git;a=commit;h=6b764be76ffe165b7d815afab07a2c6df6eaa59f

Howto (including patches for Debian):
http://www.superjoesoftware.com/articles/dell-1525-debian-wireless
Comment by: piroflip on Fri, 17 Oct 2008 07:04:57 +0000
Updated package. Now it includes install script with "depmod". Since module "wl.ko" depends on "ieee80211_crypt" you don't need to put it your rc.conf. All you have to do is just add "wl.ko" in MODULES=().
Comment by: cmlr on Thu, 16 Oct 2008 23:50:16 +0000
Try 2.6.27 instead of 2.6.26.
Comment by: dandus on Thu, 16 Oct 2008 20:01:41 +0000
It doesn't work for me. When i give

insmod /lib/modules/2.6.26-ARCH/kernel/drivers/net/wireless/wl.ko

he says that he gives

-1 Invalid module format

and doesn't work.

knetworkmanager won't recognize any wireless
network, and he turs off once he fails. Lan
connection works fine though.
Comment by: jujibo on Wed, 15 Oct 2008 14:02:59 +0000
It's working fine, but you have to run depmod, isn't supposed it to be done after the install?
Comment by: piroflip on Wed, 15 Oct 2008 07:06:56 +0000
Thanks to everybody for comments and suggestions, please check new PKGBUILD.
Comment by: jaux on Wed, 15 Oct 2008 05:53:07 +0000
Good job, cmlr!
Comment by: scubanator87 on Wed, 15 Oct 2008 03:41:35 +0000
I can confirm that this is working
Comment by: cmlr on Wed, 15 Oct 2008 02:55:20 +0000
Here's a PKGBUILD that works with kernel26 2.6.27-2

################

pkgname=broadcom-wl
pkgver=5.10.27.6
pkgrel=3
pkgdesc="Broadcom 802.11abg Networking Drivers"
arch=('i686 x86_64')
[ "$CARCH" = "i686" ] && ARCH=x86_32
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.broadcom.com"
license=('Broadcom')
depends=('kernel26>=2.6.25-11')
source=('http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-'$ARCH'_5_10_27_6.tar.gz')
md5sums=('7f50d89179e637225bd97022b323c27e')
[ "$CARCH" = "x86_64" ] && md5sums=('d61e5ad289fc5f0b62e0656f90b451a7')

build() {
mv $srcdir/src/wl/sys/wl_iw.c $srcdir/src/wl/sys/wl_iw.c.old
sed 's/\(iwe_stream_add_.....(\)event/\1info, event/' <$srcdir/src/wl/sys/wl_iw.c.old >$srcdir/src/wl/sys/wl_iw.c
$pkgdir/src/wl/sys/wl_iw
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` || return 1
install -D -m 755 wl.ko $pkgdir/lib/modules/$(uname -r)/kernel/drivers/net/wireless/wl.ko || return 1
}
Comment by: jaux on Tue, 14 Oct 2008 18:47:30 +0000
Download the patch here:

http://jaux.net/uploads/2008/10/hybrid_wl-5.10.27.6_patch-2.6.27-ARCH
Comment by: jaux on Tue, 14 Oct 2008 06:22:35 +0000
The driver(5.10.27.6) won't be compiled on kernel26-2.6.27 and here is the patch to the problem:

--- hybrid_wl.old/src/wl/sys/wl_iw.c 2008-10-14 01:04:20.000000000 -0400
+++ hybrid_wl/src/wl/sys/wl_iw.c 2008-10-14 01:32:39.000000000 -0400
@@ -931,12 +931,12 @@
iwe.cmd = SIOCGIWAP;
iwe.u.ap_addr.sa_family = ARPHRD_ETHER;
memcpy(iwe.u.ap_addr.sa_data, &bi->BSSID, ETHER_ADDR_LEN);
- event = iwe_stream_add_event(event, end, &iwe, IW_EV_ADDR_LEN);
+ event = iwe_stream_add_event(info, event, end, &iwe, IW_EV_ADDR_LEN);

iwe.u.data.length = dtoh32(bi->SSID_len);
iwe.cmd = SIOCGIWESSID;
iwe.u.data.flags = 1;
- event = iwe_stream_add_point(event, end, &iwe, bi->SSID);
+ event = iwe_stream_add_point(info, event, end, &iwe, bi->SSID);

if (dtoh16(bi->capability) & (DOT11_CAP_ESS | DOT11_CAP_IBSS)) {
iwe.cmd = SIOCGIWMODE;
@@ -944,7 +944,7 @@
iwe.u.mode = IW_MODE_INFRA;
else
iwe.u.mode = IW_MODE_ADHOC;
- event = iwe_stream_add_event(event, end, &iwe, IW_EV_UINT_LEN);
+ event = iwe_stream_add_event(info, event, end, &iwe, IW_EV_UINT_LEN);
}

iwe.cmd = SIOCGIWFREQ;
@@ -952,13 +952,13 @@
CHSPEC_CHANNEL(bi->chanspec) <= CH_MAX_2G_CHANNEL ?
WF_CHAN_FACTOR_2_4_G : WF_CHAN_FACTOR_5_G);
iwe.u.freq.e = 6;
- event = iwe_stream_add_event(event, end, &iwe, IW_EV_FREQ_LEN);
+ event = iwe_stream_add_event(info, event, end, &iwe, IW_EV_FREQ_LEN);

iwe.cmd = IWEVQUAL;
iwe.u.qual.qual = rssi_to_qual(dtoh16(bi->RSSI));
iwe.u.qual.level = 0x100 + dtoh16(bi->RSSI);
iwe.u.qual.noise = 0x100 + bi->phy_noise;
- event = iwe_stream_add_event(event, end, &iwe, IW_EV_QUAL_LEN);
+ event = iwe_stream_add_event(info, event, end, &iwe, IW_EV_QUAL_LEN);

#if WIRELESS_EXT > 17

@@ -970,7 +970,7 @@
if ((ie = bcm_parse_tlvs(ptr, ptr_len, DOT11_MNG_RSN_ID))) {
iwe.cmd = IWEVGENIE;
iwe.u.data.length = ie->len + 2;
- event = iwe_stream_add_point(event, end, &iwe, (char *)ie);
+ event = iwe_stream_add_point(info, event, end, &iwe, (char *)ie);
}
ptr = ((uint8 *)bi) + sizeof(wl_bss_info_t);
while ((ie = bcm_parse_tlvs(ptr, ptr_len, DOT11_MNG_WPA_ID))) {
@@ -978,7 +978,7 @@
if (ie_is_wps_ie(((uint8 **)&ie), &ptr, &ptr_len)) {
iwe.cmd = IWEVGENIE;
iwe.u.data.length = ie->len + 2;
- event = iwe_stream_add_point(event, end, &iwe, (char *)ie);
+ event = iwe_stream_add_point(info, event, end, &iwe, (char *)ie);
break;
}
}
@@ -989,7 +989,7 @@
if (ie_is_wpa_ie(((uint8 **)&ie), &ptr, &ptr_len)) {
iwe.cmd = IWEVGENIE;
iwe.u.data.length = ie->len + 2;
- event = iwe_stream_add_point(event, end, &iwe, (char *)ie);
+ event = iwe_stream_add_point(info, event, end, &iwe, (char *)ie);
goto done;
}
}
@@ -1003,7 +1003,7 @@
else
iwe.u.data.flags = IW_ENCODE_DISABLED;
iwe.u.data.length = 0;
- event = iwe_stream_add_point(event, end, &iwe, (char *)event);
+ event = iwe_stream_add_point(info, event, end, &iwe, (char *)event);

if (bi->rateset.count) {
value = event + IW_EV_LCP_LEN;
@@ -1012,7 +1012,7 @@
iwe.u.bitrate.fixed = iwe.u.bitrate.disabled = 0;
for (j = 0; j < bi->rateset.count && j < IW_MAX_BITRATES; j++) {
iwe.u.bitrate.value = (bi->rateset.rates[j] & 0x7f) * 500000;
- value = iwe_stream_add_value(event, value, end, &iwe,
+ value = iwe_stream_add_value(info, event, value, end, &iwe,
IW_EV_PARAM_LEN);
}
event = value;
Comment by: Andre on Tue, 14 Oct 2008 02:55:32 +0000
Is there any incompatibility with Kernel 2.6.27-2? Since ndiswrapper got updated at the same time, I removed the wl module to try ndiswrapper, but then couldn't get it to work again...
Comment by: t.iglo on Wed, 08 Oct 2008 18:36:37 +0000
Works fine ... I have BCM4312 (rev02) in my HP Compaq 6715b and I had a little problem with connecting ESSID .. but now it's OK.
Comment by: Andre on Wed, 24 Sep 2008 01:59:44 +0000
Worked here :)
Maybe add a comment at the end of the build like
"depmod -a
modprobe wl"

Many thanks!
Comment by: piroflip on Tue, 23 Sep 2008 07:29:14 +0000
It will work with the following devices (you can check yours with lspci)

14e4:432b "Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller"
14e4:4329 "Broadcom Corporation BCM43XG"
14e4:4328 "Broadcom Corporation BCM4328 802.11a/b/g/n"
14e4:4315 "Broadcom Corporation BCM4312 802.11b/g"
14e4:4313 "Broadcom Corporation BCM4310 Ethernet Controller"
14e4:4312 "Broadcom Corporation BCM4312 802.11a/b/g"
14e4:4311 "Broadcom Corporation BCM4311 802.11b/g WLAN"
14e4:432d
14e4:432c
14e4:432a
Comment by: Andre on Mon, 22 Sep 2008 15:23:53 +0000
In the Broadcom site it's said to work with BCM4311-, BCM4312-, BCM4321-, and BCM4322-based hardware, but I found at the Gentoo Wiki
(http://gentoo-wiki.com/HARDWARE_Apple_MacBook#Macbooks_-_4th-5th_Generation)
that this works with BCM4328.

Is this for real?

Thanks!
Comment by: piroflip on Mon, 22 Sep 2008 12:24:53 +0000
Update for x86_64
Comment by: lindquist on Mon, 08 Sep 2008 21:00:25 +0000
works great for my broadcom 4312 (hp compaq 6720s)

v1.6.0