You are not logged in.
Hi, I've got a problem with a BCM4322 chip and broadcom-wl since the last update (yesterday?).
The module loads OK, I can see the wireless networks with Wicd, but when I try to connect I got this message :
"Connection failed, could not contact the wireless access point"
I tried with and without WPA, I use static IP and DNS. The other computers connect successfully to the network.
The module worked with kernel 2.6.32, before the last update.
Nothing unusual in the logs (dmesg and messages.log)
I'm using Archlinux 64 bits
Any ideas ?
Offline
BCM4312 works fine after rebuilding the driver for the latest kernel without any problem (Lenovo S10e and Dell mini 9). wicd is the network manager.
Offline
Hi, I have a BCM4322 chipset. I followed the wiki installing the driver from AUR and from the Broadcom site. After loading the modules, the Wifi led remains off and the card is not recognized, even though wl and lib80211_crypt_tkip seem to be on. What can I do?
P.S. I've also rebuilt the kernel, but still no luck.
Offline
I have a similiar problem...
I'm trying to use the AUR package but it don't work. After installing, "iwconfig" show the interface but "iwlist eth1 scan" returns "No scan results".
I've tried the b43 module + firmware too, but the system hangs up minutes after boot.
Offline
try sudo iwlist eth1 scan
Offline
@darose: thanks, it works (I swore that I had tried it...)
but wicd doesn't work yet
Offline
When it will be available for kernel 2.6.33? Or is there any other way to implement driver? I have to use 2.6.33, cause there's fixed in alsa, to work properly with dell vostro 1015... But now problem with broadcom-wl
It can work with 2.6.33, although it also needs a modification on the kernel side. I just modified the original PKGBUILD, so that it compiles, even though I didn't test it, I still have to reboot.
# Maintainer: Alexandr Kotov nektokot at gmail dot com
pkgname=broadcom-wl-rc
pkgver=5.10.91.9.3
_kernver=2.6.33-rc5-rc
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=('MIXED/Proprietary')
depends=('kernel26-rc>2.6.32' 'kernel26<2.6.33')
install=broadcom-wl.install
source=(http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-${ARCH}-v${pkgver}.tar.gz
license.patch)
md5sums=('15890e1f9afe844adf2e251d390e28ac' '3b6631f6e19232690298cd23e51e3fcb')
[ "${CARCH}" = "x86_64" ] && md5sums=('ed255d2c98690ef76757d95b2d9e6b32'
'3b6631f6e19232690298cd23e51e3fcb')
build() {
patch -p1 -d ${srcdir}/src/wl/sys < license.patch
find ${srcdir} -type f -name '*.[ch]' -exec sed -i 's/CONFIG_WIRELESS_EXT/CONFIG_CFG80211_WEXT/g' {} \;
KBUILD_NOPEDANTIC=1 make -C /lib/modules/${_kernver}/build M=`pwd` || return 1
install -D -m 755 wl.ko $pkgdir/lib/modules/${_kernver}/kernel/drivers/net/wireless/wl.ko || return 1
}
In the kernel, you have to compile support for an old wireless driver even if you don't have the chip, so that it activates the hidden CONFIG_WEXT_PRIV option. The IPW2200 driver, for example, is a good one. Once you have this support in the kernel, you can run makepkg. Note that this package is called 'broadcom-wl-rc', and depends on 'kernel26-rc', which I use to prevent conflicts with the official kernel.
dreaming in digital / living in realtime / thinking in binary / talking in ip / welcome to our world
Offline
Hi,
I've installed the broadcom-wl package via yaourt. I've followed the instructions on the wiki page and I'm able to see my wireless adapter.
The module b43 was removed before the install of the wl module.
Nevertheless I'm having some problems with my wireless device on my Lenovo Ideapad S12 (Intel Chipset).
My wlan switch is turned on and I've executet every command as root.
root:~$ ifconfig eth0 up
root:~$ iwconfig eth0
eth0 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key: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
Well everything is fine so far. Now I've wanted to set the essid of my netwok per iwconfig and try to find it per iwscan....
root:~$ iwconfig eth0 essid xerxes
root:~$ iwconfig eth0
eth0 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key: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:0root:~$ iwlist eth0 scan
eth0 No scan results
It seems that the iwconfig command does nothing (AP essid is not hidden), no essid was set.
But the main problem is the output of iwlist. Some people around seem to have the same problem.
Is there a solution to this problem?
Some aditional information:
Kernel: 2.6.32 (i686)
Output of lspci -vnn:
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04b5]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 38-52-00-ff-ff-f0-00-21
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: wl
Kernel modules: wl, ssb
It would be nice to get some help with this.
Offline
Try removing ssb module also before you start. Both b43 and ssb should be blacklisted and not loaded before you try to load the wl module.
Offline
Hello I can't compile broadcom-wl 5.60.48.36-1 against vanilla-kernel 2.6.33
==> Making package: broadcom-wl 5.60.48.36-1 x86_64 (Thu Feb 25 21:46:58 CET 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found hybrid-portsrc-x86_64-v5.60.48.36.tar.gz in build dir
==> Validating source files with md5sums...
hybrid-portsrc-x86_64-v5.60.48.36.tar.gz ... Passed
==> Extracting Sources...
-> Extracting hybrid-portsrc-x86_64-v5.60.48.36.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
make: Entering directory `/root/linux-2.6.33'
CC [M] /root/broadcom-wl/src/src/shared/linux_osl.o
In file included from /root/broadcom-wl/src/src/shared/linux_osl.c:19:
/root/broadcom-wl/src/src/include/linuxver.h:23:28: error: linux/autoconf.h: No such file or directory
make[1]: *** [/root/broadcom-wl/src/src/shared/linux_osl.o] Error 1
make: *** [_module_/root/broadcom-wl/src] Error 2
make: Leaving directory `/root/linux-2.6.33'
==> ERROR: Build Failed.
Aborting...
Question at broadcom: Why you deliver ugly and hated closed-source drivers? And why you deliver at stand of 2.6.33-rc8 (last rc!) an new driver ten days before final release, while you KNOW that it doesn't work with the new kernel? And why to hell, you are completly insane kernel-options "CONFIG_WEXT_PRIV" is not for public use, don't use it!
Think about that (and what microsoft/apple will do, if you make something like that a week before windows 8/os x 10.7).
Patch?
http://gentoo-portage.com/AJAX/Ebuild/104416
Last edited by hoschi (2010-02-25 21:11:43)
Offline
my findings: 2.4ghz (wireless-G) works o-k for me (aes/tkip), though there's the occasional random disconnect. 5ghz (wireless-N) is strange and buggy, i only see the access point every 4-5 (re)boots, and even then only 1 in about 3 associations succeed. if anyone has tips to improve wifi-N performance let me know, but i assume it's probably just the driver...
peasantoid posted an older version of the driver on the AUR page but that doesn't change anything for me, same results.
ᶘ ᵒᴥᵒᶅ
Offline
Just for the record, the make errors are most probably because you didn't reboot after the kernel update. Try downloading the pkgbuild and the related files before rebooting, and than use makepkg and pacman -U accordingly.
Hello I can't compile broadcom-wl 5.60.48.36-1 against vanilla-kernel 2.6.33
==> Making package: broadcom-wl 5.60.48.36-1 x86_64 (Thu Feb 25 21:46:58 CET 2010) ==> Checking Runtime Dependencies... ==> Checking Buildtime Dependencies... ==> Retrieving Sources... -> Found hybrid-portsrc-x86_64-v5.60.48.36.tar.gz in build dir ==> Validating source files with md5sums... hybrid-portsrc-x86_64-v5.60.48.36.tar.gz ... Passed ==> Extracting Sources... -> Extracting hybrid-portsrc-x86_64-v5.60.48.36.tar.gz with bsdtar ==> Removing existing pkg/ directory... ==> Starting build()... make: Entering directory `/root/linux-2.6.33' CC [M] /root/broadcom-wl/src/src/shared/linux_osl.o In file included from /root/broadcom-wl/src/src/shared/linux_osl.c:19: /root/broadcom-wl/src/src/include/linuxver.h:23:28: error: linux/autoconf.h: No such file or directory make[1]: *** [/root/broadcom-wl/src/src/shared/linux_osl.o] Error 1 make: *** [_module_/root/broadcom-wl/src] Error 2 make: Leaving directory `/root/linux-2.6.33' ==> ERROR: Build Failed. Aborting...
Question at broadcom: Why you deliver ugly and hated closed-source drivers? And why you deliver at stand of 2.6.33-rc8 (last rc!) an new driver ten days before final release, while you KNOW that it doesn't work with the new kernel? And why to hell, you are completly insane kernel-options "CONFIG_WEXT_PRIV" is not for public use, don't use it!
Think about that (and what microsoft/apple will do, if you make something like that a week before windows 8/os x 10.7).
Offline
Can anyone get ad-hoc mode to work with this driver?
Offline
I started using the b43 now with kernel .35. Before it gave me troubles loading modules during boot and I had to revert to the wl driver...
There I walked into an issue doing pacman -U on the broadcom-wl. So this thread has been helpful figuring out that the package needs to be rebuild against the updated kernel....
I keep the wl driver in place for backup though......just blacklisted in rc.conf:
MODULES=(!usblp !lib80211_crypt_tkip !wl b43 ssb !b43-legacy
Offline
I thought I'd just reply in here with my wl story (and to see if anyone has any ideas.
I'm stuck with kernel .34 due to Intel video issues. I had to re-install my 4322 wireless card in my notebook and to my surprise, everything actually seemed to work installing and setting it up! It even saw my wireless networks! But here is where it gets weird. At my house, WPA2, it won't get an ip address unless the wired network is plugged in first to the same network. Otherwise I get iP4 time out errors in the logs.
For now...I turn on the system, connect to my physical wire (thankfully it's a light notebook), connect to the wireless, then disconnect the wire and resume normal operation.
For now, it works. I'm just hoping it 'goes away' in the next kernel.
"He is no fool who gives what he cannot keep to gain that which he cannot lose." -Jim Elliot
Offline
Great news, Broadcom has GPL'd it's 802.11n drivers, which will be included in 2.6.37:
http://thread.gmane.org/gmane.linux.ker … eral/55418
http://twitter.com/gregkh/status/24027482819
ᶘ ᵒᴥᵒᶅ
Offline
Great news, Broadcom has GPL'd it's 802.11n drivers, which will be included in 2.6.37:
http://thread.gmane.org/gmane.linux.ker … eral/55418
http://twitter.com/gregkh/status/24027482819
But what about their older models? the A/B/G models?
*sigh* I hate broadcom
Offline
But what about their older models? the A/B/G models?
Those work with b43 don't they?
ᶘ ᵒᴥᵒᶅ
Offline
Most of them should afaik. The 802.11n PHYs are the ones that aren't supported by the open source drivers.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
which will be included in 2.6.37
excellent news. soon, no more recompiling.
Offline
Can anyone explain why my eth0 (broadcom wireless) is sometimes unavailable and a reboot is necessery to hopefully get access to it.
Offline
DrathIntruder wrote:But what about their older models? the A/B/G models?
Those work with b43 don't they?
ah ok, then it is great news.
Offline
For those of you that have a Dell 1564 (I don't know if other models have this issue) I've experienced a very strange behaviour for that wireless card. Sometimes, without an apparent cause, it won't detect any wireless network until you _shutdown_ the machine, and then boot again. Rebooting does not work. I've seen this both in Windows XP and Linux.
So if you followed the instructions from the wiki and you can see the interface when invoking iwconfig, try if it works after a shutdown. That was my case; iwlist was telling "No scan results" until I remembered that problem with Windows.
Thanks for such an awesome distro.
Offline
For those of you that have a Dell 1564 (I don't know if other models have this issue) I've experienced a very strange behaviour for that wireless card. Sometimes, without an apparent cause, it won't detect any wireless network until you _shutdown_ the machine, and then boot again. Rebooting does not work. I've seen this both in Windows XP and Linux.
So if you followed the instructions from the wiki and you can see the interface when invoking iwconfig, try if it works after a shutdown. That was my case; iwlist was telling "No scan results" until I remembered that problem with Windows.
Thanks for such an awesome distro.
Great hint, thanks.
Shutting down did indeed work, where rebooting didn't.
After messing now effectively for days with wireless I finally found the culprit, b43.
b43 does still not work with BCM4315 (or according to lspci -vnn | grep 14e4 "BCM4312 802.11b/g [14e4:4315] (rev 01)")
I'm glad I could get broadcom-wl to work now, I just wonder how long it will keep working and whether it will break with every kernel update..
Offline
I just realized that I'm using a vintage version of b43 (4.80.53.0), which is working good for me. I also see that some of you are having problems with updating to the new kernel release and similar. It didn't happen with the version I have. So far. The only bad thing is that pacman is not tracking the firmware files I installed with b43-fwcutter. Even I can't track em, I forgot where the files are. (They should be in /lib/firmware, but they aren't there. At least wl_apsta.o...)
Also, a quote from the link above:
The difference with broadcom-wl driver compared to b43/b43legacy is that broadcom-wl can only offer connection to AP or Ad-Hoc network, it does not offer AP modes and Monitor modes.
No monitor mode?? Thanks, no thanks!
Last edited by archman-cro (2010-10-07 14:59:34)
Offline