LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 10-07-2016, 02:00 PM   #16
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,610
Blog Entries: 34

Rep: Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793
Member response


Hi,

I think you are making things harder than it should be;
Quote:
From https://slackbuilds.org/howto/

For more information on using, editing, and creating SlackBuild scripts, have a look at these and other tutorials at SlackWiki.com.
The Slackbuilds howto explains clearly what to do for For b43-firmware
Quote:
b43-firmware (6.30.163.46)

Broadcom's wireless chip(s) firmware.

See project homepage http://linuxwireless.org/en/users/Drivers/b43
for technical details and copyright information.

This requires: b43-fwcutter
Maintained by: Robby Workman
Keywords: broadcom,bcm43xx,bcm,firmware,b43
Homepage:
http://linuxwireless.org/en/users/Drivers/b43
Source Downloads:
broadcom-wl-6.30.163.46.tar.bz2 (6fe97e9368d25342a1ab943d3cf3496d)
Download SlackBuild:
b43-firmware.tar.gz
b43-firmware.tar.gz.asc (FAQ)
(the SlackBuild does not include the source)


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 ;
Quote:
14.2 > Network > b43-fwcutter (019)

b43-fwcutter is a tool to extract Broadcom's wireless chip(s) firmware.

Maintained by: Robby Workman
Keywords: broadcom,b43,bcm3xx,bcm,firmware,cutter,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.
Quote:
From man pkgtool;

pkgtool - software package maintenance tool.

SYNOPSIS
pkgtool

pkgtool [ --sets #a#b#c# ] [ --source_mounted ] [ --ignore_tagfiles ] [ --tagfile tagfile ] [ --source_dir directory ] [ --target_dir
directory ] [ --source_device device ]

DESCRIPTION
pkgtool is a menu-driven package maintenance tool provided with the Slackware Linux distribution. It allows the user to install, remove,
or view software packages through an interactive system. Pkgtool can also be used to re-run the menu-driven scripts normally executed at
the end of a Slackware installation. This is useful for doing basic reconfiguration (like changing the mouse type).
Quote:
From 'man installpkg'
installpkg - install Slackware packages.

SYNOPSIS
installpkg [ --warn ] [ --md5sum ] [ --root /otherroot ] [ --infobox ] [ --menu ] [ --terse ] [ --ask ] [ --priority ADD|REC|OPT|SKP ] [
--tagfile /somedir/tagfile ] packagename [ packagename2 ... ]

DESCRIPTION
installpkg installs single or multiple *.tgz (or .tbz, .tlz, .txz) binary packages designed for use with the Slackware Linux distribution
onto your system.
A few references that will help you; Hope this helps.
Have fun & enjoy!
 
Old 10-07-2016, 02:07 PM   #17
johnmeehan
Member
 
Registered: Oct 2016
Posts: 68

Original Poster
Rep: Reputation: Disabled
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.

Last edited by johnmeehan; 10-07-2016 at 02:12 PM.
 
Old 10-07-2016, 03:24 PM   #18
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,610
Blog Entries: 34

Rep: Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793
Member response

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.
Quote:
b43-fwcutter is a tool to extract Broadcom's wireless chip(s) firmware.

And the;

b43-firmware (6.30.163.46)
Broadcom's wireless chip(s) firmware. See project homepage http://linuxwireless.org/en/users/Drivers/b43 for technical details and copyright information.
For the build then;
Quote:
Make the script executable with chmod if necessary:
chmod +x sometool.SlackBuild

Then run the script:
./sometool.SlackBuild
To run the Slackbuild script to create the package that is to be installed for usage
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!

Last edited by onebuck; 10-07-2016 at 03:27 PM. Reason: add a comment
 
Old 10-07-2016, 04:07 PM   #19
johnmeehan
Member
 
Registered: Oct 2016
Posts: 68

Original Poster
Rep: Reputation: Disabled
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!
 
Old 10-07-2016, 04:22 PM   #20
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 658

Rep: Reputation: 264Reputation: 264Reputation: 264
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

Last edited by Gordie; 10-07-2016 at 06:29 PM.
 
Old 10-07-2016, 08:42 PM   #21
johnmeehan
Member
 
Registered: Oct 2016
Posts: 68

Original Poster
Rep: Reputation: Disabled
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?
 
Old 10-08-2016, 09:36 AM   #22
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,610
Blog Entries: 34

Rep: Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793
Member response

Hi,
Quote:
Originally Posted by Gordie View Post
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 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.
Old 10-08-2016, 12:55 PM   #23
johnmeehan
Member
 
Registered: Oct 2016
Posts: 68

Original Poster
Rep: Reputation: Disabled
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.
 
Old 10-08-2016, 01:05 PM   #24
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 658

Rep: Reputation: 264Reputation: 264Reputation: 264
fwcutter NEEDS to be installed before continuing with the firmware

Last edited by Gordie; 10-21-2016 at 09:22 PM.
 
Old 10-08-2016, 01:41 PM   #25
johnmeehan
Member
 
Registered: Oct 2016
Posts: 68

Original Poster
Rep: Reputation: Disabled
you are beautiful people, thank you for the help.
 
Old 10-08-2016, 03:23 PM   #26
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, Void
Posts: 3,502

Rep: Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159
Quote:
Originally Posted by johnmeehan View Post
you are beautiful people, thank you for the help.
Does that mean you've got it up and running? If so, good to hear!
 
Old 10-08-2016, 03:38 PM   #27
johnmeehan
Member
 
Registered: Oct 2016
Posts: 68

Original Poster
Rep: Reputation: Disabled
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.
Old 10-08-2016, 04:34 PM   #28
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, Void
Posts: 3,502

Rep: Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159Reputation: 1159
Quote:
Originally Posted by johnmeehan View Post
Yes, it is up and running. I saved the created installation files to a usb stick just in case I need them again.
Good idea, I do that myself with some files for my system that doesn't have a NIC for when I reinstall it.
 
Old 10-08-2016, 05:09 PM   #29
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 658

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

Last edited by Gordie; 10-09-2016 at 07:39 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kubuntu 11.04 and Broadcom BCM4311 wireless not working NeilForde Ubuntu 9 02-21-2015 03:08 PM
Kubuntu 11.04 and Broadcom BCM4311 wireless not working NeilForde Linux - Newbie 4 06-09-2011 05:28 PM
[SOLVED] Slackware wireless networking setup w/Broadcom Wireless BCM4311 NIC on HP DV9000 astanton Slackware 14 12-30-2010 07:37 PM
Slackware 12.2 -- Dell e1405 Wifi "Broadcom BCM4311" DirkDD Linux - Newbie 5 03-27-2009 07:26 AM
Broadcom bcm4311 driver issues conway.federico Linux - Wireless Networking 1 10-07-2008 07:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 05:40 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration