[SOLVED] Still having problems with wireless connection

scythempress · 07-14-2016, 09:00 PM

Thinking that perhaps the problem might be the wireless card, I formatted and reinstalled win 7. As always it came right up, so figuring that the card is not the problem I reinstalled slack 14.1 from the cd set. Again with cable hook up works fast and perfect. Wireless network not found. Wicd is installed and daemon running in background. I also found a secon sata drive so I added it and made it 200gb of Linux 83. Not sure if it is working or what to do with it. Here are what was asked for previously:

bash-4.2# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

bash-4.2# lspci -k | grep -iA3 net
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
Subsystem: Dell Device 01f2
Kernel driver in use: b44
Kernel modules: b44
--
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
bash-4.2# cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST9160827AS Rev: 3.AD
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST9200827AS Rev: 3.BH
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
Vendor: TSSTcorp Model: DVD+-RW TS-L632H Rev: D400
Type: CD-ROM ANSI SCSI revision: 05
bash-4.2# groups
root bin daemon sys adm disk lp wheel floppy audio video cdrom scanner

I would like to get wireless up and running, and then decide what if anything to do with the additional drive

frankbell · 07-14-2016, 09:20 PM

The Broadcom chipset is the issue. This post will be a good starting point: http://www.linuxquestions.org/questi...ux-4175434970/

scythempress · 07-14-2016, 10:22 PM

Ok well got them downloaded. Tried installs but no go. Will get on it again tomorrow, it is 10:21 and I get up at 5a. Thanks to all and see you again tomorrow.

wladwolkow · 07-15-2016, 03:15 AM

Hello, I have no troubles with my BCM4313. I have compiled broadcom-sta from Slackbuilds dot org. And have this output:

ifconfig eth1

Quote:

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.192.192.109 netmask 255.255.255.0 broadcast 192.192.192.255
inet6 fe80::ba76:3fff:fe0d:a489 prefixlen 64 scopeid 0x20<link>
inet6 fd8a:89f9:3cbc:0:b3fd:ccde:67a9:e18c prefixlen 64 scopeid 0x0<global>
inet6 fd8a:89f9:3cbc:0:9dc0:62ec:8559:3f34 prefixlen 64 scopeid 0x0<global>
ether b8:76:3f:0d:a4:89 txqueuelen 1000 (Ethernet)
RX packets 75571 bytes 101457053 (96.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 94748
TX packets 40207 bytes 4185398 (3.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

lspci -vnn -d 14e4:

Quote:

02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
Subsystem: Dell BCM4313 802.11bgn Wireless Network Adapter [1028:0015]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f7d00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] 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 00-00-3f-ff-ff-0d-b8-76
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: wl
Kernel modules: bcma, wl

scythempress · 07-15-2016, 10:44 PM

Ok this is what I now have.

root@scythempress:~# ls
b43-firmware/ b43-fwcutter.tar.gz etc/ usr/
b43-firmware.tar.gz broadcom-sta/ install/ var/
b43-fwcutter/ broadcom-sta.tar.gz lib/

WIth Slack essentials in hand and about 4 hours in, this is what I still have. So here go the questions.

1. Is there a command to see what processes are started with boot. I suspect that I have both WICD and Networkmanager executable and need to fix that. So I need commands for finding out what processes are running, and one to stop one of them from starting up.

2. Of the things above that I have downloaded, is there an order in which they have to be installed in order for them to work properly?

3. How do I know if they are extracted or if the install is being done, assuming of course that I am using correct commands and such.

Timothy Miller · 07-15-2016, 10:47 PM

I personally have had MUCH more success using broadcom-sta than b43.

scythempress · 07-17-2016, 10:38 PM

tap tap is this thing on? This is what I have:

b43-firmware/ b43-fwcutter.tar.gz etc/ usr/
b43-firmware.tar.gz broadcom-sta/ install/ var/
b43-fwcutter/ broadcom-sta.tar.gz lib/
root@scythempress:~#

I opened all, tar zxfv file tar.gz many things extracted but will not install. Also I think I am running both wicd and nwmanager at boot.

gegechris99 · 07-18-2016, 01:31 AM

To install the broadcom driver, you need to create and install Slackware packages. The suggested method is to us SlackBuilds scripts available at SlackBuilds.org.

Download the 3 scripts to build broadcom kernel module, firmware and tools for Slackware 14.1.

Follow the instructions to use the scripts.

Richard Cranium · 07-18-2016, 10:51 AM

Quote:

Originally Posted by scythempress

tap tap is this thing on? This is what I have:

Code:

root@scythempress:~# ls
b43-firmware/        b43-fwcutter.tar.gz  etc/      usr/
b43-firmware.tar.gz  broadcom-sta/        install/  var/
b43-fwcutter/        broadcom-sta.tar.gz  lib/
root@scythempress:~#

I opened all, tar zxfv file tar.gz many things extracted but will not install. Also I think I am running both wicd and nwmanager at boot.

Could you please use the [CODE][/CODE] tags around stuff that you're quoting from your computer versus what you're trying to tell us? I've done that to my quote of your post and you should see that it is a hell of lot easier to read. (I added the first line that you missed.) If you use the advanced editing screen, it's the button with the # character.

If you don't understand what @gegechris99 posted or you've already done that, please tell us.

scythempress · 07-18-2016, 08:56 PM

Sorry, I have a job and a 60 acre farm. When I get in at 4, I work until around 8 and that gives me an hour before bed. So I get about an hour to read, attempt, fail and hit the sack. I am not ignoring or not doing, just using the time I have. So while I try to get to this, sometimes it is difficult. Anyway if I am getting this right, if this all worked, then it should have been up and running in just minutes. Since it has now been weeks, I evidently am doing something wrong. Why would I want chemtool?

Richard Cranium · 07-18-2016, 10:31 PM

Quote:

Originally Posted by scythempress

Sorry, I have a job and a 60 acre farm. When I get in at 4, I work until around 8 and that gives me an hour before bed. So I get about an hour to read, attempt, fail and hit the sack. I am not ignoring or not doing, just using the time I have. So while I try to get to this, sometimes it is difficult. Anyway if I am getting this right, if this all worked, then it should have been up and running in just minutes. Since it has now been weeks, I evidently am doing something wrong. Why would I want chemtool?

I do not understand the chemtool comment.

There are scripts available at slackbuilds.org that will build slackware packages for you if you run them. There is a tool available that will download the source, run the script, and install the package for you before proceeding to the next potential package.

The bottom line is that your wireless chip is not supported by the out-of-the-box linux tools. (Or at least those used by Slackware.) The fact that it works fine under Windows is not particularly useful here, other than proving that your hardware is working.

@gegechris99 provided some links that should help you create the packages that you would need as well as a link to the instructions on how to run/use them. Do you intend to follow gegechris99's instructions or not? Do you believe that you have already followed his instructions and it didn't work? I can't read your mind and I, too, have a day job that doesn't involve supporting Slackware in any shape, form, or fashion.

scythempress · 07-19-2016, 06:07 PM

I have followed everyone's advice whom have contributed here. And the last guy you mentioned sent me to a page that showed me how to install chemtool. I am sorry to have bothered you, however this is a voluntary site I assume, and purports that if you need help you should come here for it, however if you do not have the patience of a teacher, you should not attempt to teach. Remember;
Give a man a fish and he eats for a day,
Teach a man to fish and he eats for a lifetime,
Adopt a narcissistic holier than thou attitude about how you are a guru worthy only of his praise, and you will probably be removing a fish from your backside.

Richard Cranium · 07-19-2016, 06:39 PM

I try to helpful to people around here; I didn't get those green dots under my name by being unhelpful.

However, it is difficult to get specific information out of you about what you've done and what happened when you did it.

You appear to believe that there is a web page somewhere with exactly the solution to your specific problem. Maybe there is, but you do appear to be able to provide the level of detail required to find that magical page. (In fact, you probably would have googled/binged it yourself by now if there were such a page.)

I followed the link in question. @gegechris99 gave you the link https://slackbuilds.org/howto/ which provides an example of how to use slackbuilds as the page rather clearly stated...

Quote:

Download the SlackBuild archive of the application you wish to build and extract it in your build environment. For example, after extracting the chemtool.tar.gz archive, you should have the following directory tree:

(emphasis added)

So, fine, you didn't understand that. No problem. There are other tools that you can use. In your case, I suggest that you download via your ethernet connection the sbopkg tool (https://github.com/sbopkg/sbopkg/rel...arch-1_wsr.tgz). Download that to your slackware machine, change directory into the directory where you downloaded it and then run (as root)

Code:

installpkg sbopkg-0.38.0-noarch-1_wsr.tgz

.

After you've done that, run (as root) the command

Code:

sbopkg

. You'll be asked if you want to create some directories, answer yes. You'll also need to set the version of slackware to 14.1 (this version of sbopkg will default to 14.2), but I am still at work and not in front of a slackware screen so I cannot tell you which submenu to go to. If you wish to wait, I'll be home in an hour or so and will update this thread accordingly.

If you do find the correct sub-menu on your own, after you've told sbopkg to use 14.1, you go back to the main menu, tell sbopkg to sync. Then you would search for the packages containing "broadcom". There should be three of them, as shown by @gegechris99's link to the 3 packages.

Select b43-fwcutter first, build and install it. The other two can be built and installed in any order.

Once that is done, you will have installed the broadcom support packages.

Richard Cranium · 07-19-2016, 07:53 PM

The appropriate menu is Utilities -> Repository You'd select 14.1.

Here's a trace of what it would look like (minus the colors)...

Code:

Dibble's First Law of Sociology:
	Some do, some don't.

0 ✓ cranium@testbed ~ $ su -
Password: 

Chapter 1:
	The story so far:
	In the beginning the Universe was created.  This has made
a lot of people very angry and been widely regarded as a bad move.

0 ✓ testbed ~ # sbopkg

The following directories do not exist:

Variable                   Assignment
--------                   ----------
TMP ---------------------> /tmp/SBo

You can have sbopkg create them or, if these values are incorrect, you can
abort to edit your config files or pass different flags.

(C)reate or (A)bort?: c

 Browsing the SBo repository for Slackware 14.2. ARCH: x86_64
 ──────────────────────────────────────────────────────────────────────────────

    ┌─────SlackBuilds.org Package Browser (sbopkg version 0.38.0)───────┐
    │                                                                   │  
    │ Choose one of the following or press <Exit> to exit.              │  
    │ ┌───────────────────────────────────────────────────────────────┐ │  
    │ │  Sync       Sync with the remote repository                   │ │  
    │ │  ChangeLog  View the ChangeLog                                │ │  
    │ │  Packages   List/uninstall installed SBo packages             │ │  
    │ │  Updates    List potential updates to installed SBo packages  │ │  
    │ │  Browse     Browse the active repository                      │ │  
    │ │  Search     Search the active repository                      │ │  
    │ │  Queue      Manage the queue                                  │ │  
    │ │  Utilities  Go to the utilities menu                          │ │  
    │ │  Help       Where to get sbopkg help                          │ │  
    │ └───────────────────────────────────────────────────────────────┘ │  
    ├───────────────────────────────────────────────────────────────────┤  
    │                   <  OK  >          < Exit >                      │  
    └───────────────────────────────────────────────────────────────────┘  
      



 Browsing the SBo repository for Slackware 14.2. ARCH: x86_64
 ──────────────────────────────────────────────────────────────────────────────


    ┌─────────────────────────Utilities Menu────────────────────────────┐
    │                                                                   │  
    │ Choose one of the following or press <Back> to go back.           │  
    │ ┌───────────────────────────────────────────────────────────────┐ │  
    │ │Cache                 View the contents of the cache directory │ │  
    │ │Log                   View the permanent build log             │ │  
    │ │Repository            Select repository [ SBo (14.2) ]         │ │  
    │ │Latest                Check for an update to sbopkg            │ │  
    │ │Uninstalled packages  View uninstalled packages                │ │  
    │ │Obsolete sources      View obsolete cached sources             │ │  
    │ └───────────────────────────────────────────────────────────────┘ │  
    ├───────────────────────────────────────────────────────────────────┤  
    │                   <  OK  >          < Back >                      │  
    └───────────────────────────────────────────────────────────────────┘  
      






    ┌───────────────────────Repository Selection─────────────────────────┐
    │ You are currently working with the SBo repository for Slackware    │  
    │ 14.2. If you would like to work with a different one, please       │  
    │ select it from the list below. If not, choose < Back >.            │  
    │ ┌────────────────────────────────────────────────────────────────┐ │  
    │ │SBo (14.2)           SBo repository for Slackware 14.2          │ │  
    │ │SBo (14.1)           SBo repository for Slackware 14.1          │ │  
    │ │SBo (14.0)           SBo repository for Slackware 14.0          │ │  
    │ │SBo (13.37)          SBo repository for Slackware 13.37         │ │  
    │ │SBo (13.1)           SBo repository for Slackware 13.1          │ │  
    │ │SBo (13.0)           SBo repository for Slackware 13.0          │ │  
    │ │SBo (12.2)           SBo repository for Slackware 12.2          │ │  
    │ │SBo (12.1)           SBo repository for Slackware 12.1          │ │  
    │ │SBo (12.0)           SBo repository for Slackware 12.0          │ │  
    │ │SBo (11.0)           SBo repository for Slackware 11.0          │ │  
    │ │local (local)        default local repository                   │ │  
    │ └────↓(+)────────────────────────────────────────────────78%─────┘ │  
    │                                                                    │  
    ├────────────────────────────────────────────────────────────────────┤  
    │                   <  OK  >          < Back >                       │  
    └────────────────────────────────────────────────────────────────────┘

I'm running 14.2, which is why the intermediate messages keep mentioning 14.2. I'm also running a specialized bash prompt that gives you the little checkmark or x if there was an error with the last command.

Richard Cranium · 07-19-2016, 08:56 PM

Quote:

Originally Posted by scythempress

I have followed everyone's advice whom have contributed here. And the last guy you mentioned sent me to a page that showed me how to install chemtool. I am sorry to have bothered you, however this is a voluntary site I assume, and purports that if you need help you should come here for it, however if you do not have the patience of a teacher, you should not attempt to teach.

If you don't have a desire to learn, you should not attempt to become a student.

Quote:

Remember;
Give a man a fish and he eats for a day,
Teach a man to fish and he eats for a lifetime,
Adopt a narcissistic holier than thou attitude about how you are a guru worthy only of his praise, and you will probably be removing a fish from your backside.

There's a beam in your eye there, skippy.