Hi,

I think you are making things harder than it should be; The Slackbuilds howto explains clearly what to do for For b43-firmware You would get the source via http://www.lwfinger.com/b43-firmware...163.46.tar.bz2 then do a 'md5sum <downloaded file and location) to confirm a valid download via the hash code at the builds page under the source. Then download the Slackbuild https://slackbuilds.org/slackbuilds/...irmware.tar.gz after download I suggest that you create a temporary then move both down loaded files for Slackbuild script and the source file to that directory then cd into the directory. to then untar the Slackbuild file; The https://slackbuilds.org/howto/ does provide a step by step procedure to perform the necessary tasks. Easy to follow. I like to do my tasks via a terminal as root via 'su -i' to have correct paths for the executions. If you follow the https://slackbuilds.org/howto/then the tasks are very simply explained. If you have difficulties then provide us with details where you are having problems.

You can install the package via pkgtool or installpkg.

The same would be true for b43-fwcutter ;Just follow the https://slackbuilds.org/howto/ but substitute the b43-fwcutter for the chemtool script name.
Once you create the package you can use pkgtool or installpkg to install the created package. A few references that will help you; Hope this helps.
Have fun & enjoy!

Okay let me see if I understand this:

I download the broadcom sta package to a directory I create like broad

I then expand the package using tar xzvf filename

I download the files listed in the .info file

I make the script (broadcom sta) executable with chmod +x filename.slackbuild

I then run the script by entering ./filename.slackbuild

I then locate the output file in the directory declare output in the script file (assuming filename.slackbuild)

I then run installpkg NameOfOutputFile

Is this even close to what I need to do?

But I run the cutter before the firmware.

Hi,

Source downloads are listed on the Slackbuilds page for each for your convenience. The '.info file is for the Slackbuild script user to have the download information locally.
So if you follow the https://slackbuilds.org/howto/ information then you should have success.
For the build then; By running the Slackbuild you will likely have a directory within the same directory as the Slackbuild script. 'cd' to that directory and you will find a 'filename_SBo.tgz' (notice SBo.tgz extension) and that will be your package for install.

Helpful information at; http://docs.slackware.com/slackbookackage_management

You do need the firmware before the cutter to create the kernel firmware.

You should also look at http://www.slackwiki.com/SlackBuild_Scripts so you fully understand the script build. Most SlackBuilds will create the package within your local current directory where you compiled within. If you cannot find the output file then either look within the Slackbuild script for creation location or check in the '/tmp' directory.

The linked information that I have provided should have all the information for you to have a successful build.

EDIT: Most new users do not setup their environment properly. That is why it is suggested that you use 'su -' so the environment is proper for the necessary PATH for the root user within the console/terminal.

Hope this helps.
Have fun & enjoy!

I think I got it.

So I have to run the firmware before the cutter?

Okay now final stupid question.

When I get both created and installed firmware then cutter or cutter then firmware do I only install once or do I need to include them as lines in the /etc/rc.d/rc.local file so they load on each boot.

THANK YOU TO ALL WHO HAVE ENDURED MY AMATEURISH QUESTIONS. YOUR HELP HAS BEEN GREATLY APPRECIATED!

You do NOT install the firmware before the cutter. Follow the instructions you find with b43-fwcutter.
B43-fwcutter gets installed (after you build a package).
b43-fwcutter is the tool you use to extract the firmware from the Broadcom download.

Don't loose heart. I did it when my understanding was what yours is. First you read and re-read all you can find about b43-fwcutter and try, try try until you understand and are successful. Some of the info you are getting in this thread may come from people who have never had to use b43-fwcutter and so may be misleading.

You download, build and install b43-fwcutter first and get that accomplished before you do any other thing regarding firmware. OK?
Do you know how to use a SlackBuild? Maybe there is too much for you to learn all at once. There sure was with me! If that is the case - tell us. We can work with that

I think I understand how to get both packages built. I will devote tomorrow (when my brain is fresh) to seeing how well I understand.

Luckily this is a new install so I do not have any data that would be lost should I have to do a reinstall.

The question remains though that do I just have to run these once or do I have to put them both (cutter and firmware) into a file so they run with each system start up?

Hi,
I agree that I may have given the wrong information for the B43. It's been a while since I used the B43 on my Dell 1501 that uses a BCM4315. So I was recalling from memory. This old guy does miss some things from the past. The Dell is still in use but with Slackware 13.1 and no need for upgrades. I looked at some old links/notes and one must use the b43-FWcutter and then get the source for the B43 driver.

My apologies to the OP for the miscue from a failing memory for tasks done long ago. Here are some old links for references; http://linuxwireless.org/en/users/Drivers/b43/
http://linuxwireless.org/en/users/Dr...#other_distros

Hope this helps.
Have fun & enjoy!

1 members found this post helpful.

Update:

FW cutter seems to be successfully built. Have not tried to install it yet.

Having trouble with the Firmware going to try another download site.

So far I have uttered some phrases that, if overheard, would prevent me from seeking the presidency.

fwcutter NEEDS to be installed before continuing with the firmware

Does that mean you've got it up and running? If so, good to hear!

Yes, it is up and running. I saved the created installation files to a usb stick just in case I need them again.

1 members found this post helpful.

Good idea, I do that myself with some files for my system that doesn't have a NIC for when I reinstall it.

johnmeehan, now would be a great time to mark this thread solved. Please take the time to do that johnmeehan