Salix Forums

FYI, I've updated my slkbuild for the broadcom firmware after zAchAry had better luck with a different version.

I'll have a look next chance I have for a play. My chip is a bcm4312 802.11 b/g. Itd be my first venture using a slkbuild. Where is your slkbuild located again?

The slkbuild is located here [link]

Just create an empty directory and copy the contents of the script into a file called SLKBUILD then execute slkbuild -X from a terminal (right click then open a terminal in that directory). The source will be automatically downloaded and compiled into a package. You can then use installpkg <package_name> to install it.

Note, you'll need to compile and install b43-fwcutter first then b43-firmware. Read the b43-firmware script as you may need to uncomment the later version of the firmware for your card.

...
# Note: If you have a device with a low-power PHY (LP-PHY) e.g. BCM4312
# use version 4.178.10.4 else use version 4.150.10.5.
pkgver=4.150.10.5
#pkgver=4.178.10.4
...

Hope this helps.

The slkbuild gives me an error

Code: Select all

,snip>2010-08-25 06:33:13 (12.3 KB/s) - `b43-fwcutter-013.tar.bz2' saved [15359/15359]

build-b43-fwcutter.sh has been created
tar -xf b43-fwcutter-013.tar.bz2
./build-b43-fwcutter.sh: line 170:  : command not found
./build-b43-fwcutter.sh: line 171:  : command not found
build() failed.
root[build-cutter]# top

I also tried Caitlin's suggestion at slackbuids however after running the slackbuild and installing the package I get this

Code: Select all

root[Downloads]# depmod -a
root[Downloads]# modprobe wl
FATAL: Error inserting wl (/lib/modules/2.6.33.4/kernel/extra/wl.ko): Invalid module format

I am having a problem using tar as mentuioned in a new thread which has me wondering if something is wrong with my install.

Um, well lines 170 and 171 in my build-b43-fwcutter.sh are these:

Code: Select all

cd $startdir/src/$pkgname-$pkgver
make || return 1

Neither should cause a problem. Can you post the same lines (for lines 170 and 171) form your script please.

I'll do that this weekend

OK, I did fresh slkbuilds on both the cutter and then the firmware last night.

The firmware package contains a /lib/firmware/b43 directory containing items with a .fw extension. Is that all there is? Shouldn't there be a module wl.ko somewhere?

b43-firmware-4.150.10.5:

Code: Select all

./
usr/
usr/src/
usr/src/b43-firmware-4.150.10.5/
usr/src/b43-firmware-4.150.10.5/SLKBUILD
install/
install/slack-desc
lib/
lib/firmware/
lib/firmware/b43/
lib/firmware/b43/a0g1initvals13.fw
lib/firmware/b43/b0g0bsinitvals13.fw
lib/firmware/b43/ucode13.fw
lib/firmware/b43/ucode5.fw
lib/firmware/b43/pcm5.fw
lib/firmware/b43/b0g0initvals13.fw
lib/firmware/b43/a0g1bsinitvals5.fw
lib/firmware/b43/ucode9.fw
lib/firmware/b43/lp0initvals13.fw
lib/firmware/b43/b0g0initvals9.fw
lib/firmware/b43/lp0initvals14.fw
lib/firmware/b43/lp0bsinitvals14.fw
lib/firmware/b43/a0g1initvals9.fw
lib/firmware/b43/lp0initvals15.fw
lib/firmware/b43/ucode11.fw
lib/firmware/b43/b0g0initvals5.fw
lib/firmware/b43/a0g0bsinitvals9.fw
lib/firmware/b43/b0g0bsinitvals5.fw
lib/firmware/b43/a0g1bsinitvals9.fw
lib/firmware/b43/a0g1bsinitvals13.fw
lib/firmware/b43/a0g1initvals5.fw
lib/firmware/b43/ucode14.fw
lib/firmware/b43/a0g0initvals9.fw
lib/firmware/b43/a0g0initvals5.fw
lib/firmware/b43/lp0bsinitvals13.fw
lib/firmware/b43/lp0bsinitvals15.fw
lib/firmware/b43/n0absinitvals11.fw
lib/firmware/b43/n0bsinitvals11.fw
lib/firmware/b43/a0g0bsinitvals5.fw
lib/firmware/b43/b0g0bsinitvals9.fw
lib/firmware/b43/n0initvals11.fw
lib/firmware/b43/ucode15.fw

b43-firmware-4.178.10.4:

Code: Select all

./
usr/
usr/doc/
usr/doc/b43-firmware-4.178.10.4/
usr/doc/b43-firmware-4.178.10.4/README
usr/src/
usr/src/b43-firmware-4.178.10.4/
usr/src/b43-firmware-4.178.10.4/SLKBUILD
install/
install/slack-desc
lib/
lib/firmware/
lib/firmware/b43/
lib/firmware/b43/a0g1initvals13.fw
lib/firmware/b43/b0g0bsinitvals13.fw
lib/firmware/b43/ucode13.fw
lib/firmware/b43/ucode5.fw
lib/firmware/b43/pcm5.fw
lib/firmware/b43/b0g0initvals13.fw
lib/firmware/b43/n0initvals16.fw
lib/firmware/b43/a0g1bsinitvals5.fw
lib/firmware/b43/ucode9.fw
lib/firmware/b43/ucode16.fw
lib/firmware/b43/lp0initvals13.fw
lib/firmware/b43/b0g0initvals9.fw
lib/firmware/b43/lp0initvals14.fw
lib/firmware/b43/lp0bsinitvals14.fw
lib/firmware/b43/a0g1initvals9.fw
lib/firmware/b43/lp0initvals15.fw
lib/firmware/b43/sslpn0initvals16.fw
lib/firmware/b43/lp0bsinitvals16.fw
lib/firmware/b43/ucode11.fw
lib/firmware/b43/b0g0initvals5.fw
lib/firmware/b43/a0g0bsinitvals9.fw
lib/firmware/b43/b0g0bsinitvals5.fw
lib/firmware/b43/a0g1bsinitvals9.fw
lib/firmware/b43/a0g1bsinitvals13.fw
lib/firmware/b43/a0g1initvals5.fw
lib/firmware/b43/ucode14.fw
lib/firmware/b43/a0g0initvals9.fw
lib/firmware/b43/a0g0initvals5.fw
lib/firmware/b43/lp0bsinitvals13.fw
lib/firmware/b43/lp0bsinitvals15.fw
lib/firmware/b43/n0absinitvals11.fw
lib/firmware/b43/n0bsinitvals11.fw
lib/firmware/b43/a0g0bsinitvals5.fw
lib/firmware/b43/b0g0bsinitvals9.fw
lib/firmware/b43/n0initvals11.fw
lib/firmware/b43/ucode15.fw
lib/firmware/b43/sslpn0bsinitvals16.fw
lib/firmware/b43/lp0initvals16.fw
lib/firmware/b43/n0bsinitvals16.fw

These packages just contain the firmware, the kernel module should already exist on your system from the kernel-modules package(s).

AFAIK all you need to do now is modprobe b43 as root, unless I'm wrong. It's been a while since I've owned any of this kit!

justwantin wrote:OK, I did fresh slkbuilds on both the cutter and then the firmware last night.

The firmware package contains a /lib/firmware/b43 directory containing items with a .fw extension. Is that all there is? Shouldn't there be a module wl.ko somewhere?

The wl driver is part of the Broadcom-STA (proprietary) driver. You can use b43 or wl, not both. Some Broadcom 4312 chipset revisions do NOT work with b43 and the firmware cutter. For those (like the one in my HP Mini 110 netbook) the STA driver is the only choice.

I compiled the wl.ko driver but it would not install due to wrong module format. I googled that and this was a fairly common error with nothing very conclusive with regards to my situation.

I have to blacklist the b43 module to boot. if I go this route do I have to take a leap of faith and un-blacklist it? Does fwcutter just cut out what's needed and put it in /lib/firmware/b43, or does it have a role to play afterwards? i.e. what tells the b43 module to have a look in the /lib/firmware/b43 directory and get what it what it needs to do its job?

Salix Forums

problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless

Re: problem setting up wireless