Still having problems with wireless connection
 

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

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

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.

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

ifconfig eth1
lspci -vnn -d 14e4:

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.

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

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.

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.

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.

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.

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.

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...
(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) .

After you've done that, run (as root) the command . 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.

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

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

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.

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


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

Ok, well I tried all of the suggestions given me, and probably did them wrong as I assumed from how long it took me to type it, it should be up and running by now. So to answer your question, nothing happened. I would get messages like, blank is a directory, so type it as a directory and blank does not exist. I now have a bunch of downloaded stuff lying around what was a nice clean file or two doing nothing. I would love to clean it all out but am afraid I will really screw something up and have to start over.

Don't worry about it. Did you try the sbopkg stuff that I mentioned? That's the easiest way to use the many packages that are available at slackbuilds.

Got a mess here. I think my downloads are going to different places. I also get errors that my files have the wrong ending. I download them as .gz but it wants tgz or something of that nature.

I will put some more effort in tomorrow, got early classes. I teach young police officers to survive the streets. Helps to stay awake in class. Thanks for the attention and patience.

Many thanks to *you* for that. (I grew up on a farm, was a soldier for 12 years, and do the software stuff now. I got out in 1992, so nobody ever shot at me to the best of my knowledge. Unlike a lot of police in the US now. [I'm going to stop there since there should be a couple of places on the web that aren't political.])

When you get back to this, please use the sbopkg program to deal with slackbuilds. The stuff that you downloaded aren't packages, they are containers of source code that you have to turn into a package (or containers of stuff that can be used to create packages).

FWIW, I view myself as an engineer. I make stuff for people to use. It bugs me if my stuff can't be used. I have nothing to do with Slackware other than I use it. I like using it and I think that other people can enjoy using it as well. The only thing that I would ask of you for my help is a post in the thread that only says "Hey, it works!" and marking it as solved (only, of course, if that's what actually happened). I suspect that the others that have tried to help would only want the same.

Wow, started following the menu, downloaded built and installed all three. Said successfully. It is still not working but looked like it did and that was cool. Tried reboot but that did not fix it. I no longer have any of the stuff I downloaded as it asked I allowed it to get rid of it once it was installed. Will work on it and see what I can do.

I don't have one of those broadcom devices, so any help that I can provide from this point may or may not be worth reading. :-/ Hopefully, someone will step in and correct any misinformation that I may provide by mistake.

From what I've read, the wl driver may bring your wireless card up as eth1. Could you re-run the and commands as root and post the results here?

It did, I now have Lo and eth1. Standby attempting to bring up slackbox

ok I am having to type all this now because evidently bringing up the wireless did something to make it where the cable will not work now. So;
Whew!

If I remember correctly, you're running KDE. Is /etc/rc.d/rc.networkmanager executable? If it is, there should be an icon in the system tray that you can right-click to configure access to your access point.

We'll figure out what's going on with your ethernet connection afterwards.

I suspect that the new driver messed up the mappings in /etc/udev/rules.d/70-persistent-net.rules, which is how the system decides to assign the device names for network devices.

Yes running KDE. Found NW in the hidden icons, it says NW not running please start it, but cant seem to make it work

As root, you'll have to run /etc/rc.d/rc.networkmanager restart.

You can also run /etc/rc.d/rc.networkmanager status to see if it is running or not.
If /etc/rc.d/rc.networkmanager is not executable, you'll get an error when you try to run the command.

Ok got the KDE wallet that time, have not had that happen yet. WLAN is back up and wireless info displayed but did not hook up. Should wicd be discontinued now because i think both are started at boot

Let me correct me. The wireless is up and running not the cable.

Oh, yes. I'd uninstall wicd. I haven't had any problems with networkmanager when I used it in 14.1 or 14.2.

You're connected via wireless?

Now I'm afraid to tell you to touch anything. :)

I agree. Yes I am wireless. Again wicd and nw are or were executable. Since wicd is not connecting wireless should I dump it? Or at least change it from executable? And if so how? ah seen your post. Will uninstall WICD

Ok went to "root@scythempress:/etc/xdg/autostart" and did "rm wicd-tray.desktop" will that do it or is there something else I should do?

I want to reboot and see if it works but I am afraid too. I am going to anyway, standby.

Did you also uninstall the wicd package?

Heh. You'll have to do it eventually. Grasp the nettle!

Ok, well wicd is still there. I had to restart NW but once I put my KDE wallet password in, it hooked right up

At this point, you can reconfigure NW to manage both your wired and wireless connections. Then again, you may want to go to bed.

Please run the command and provide the output.

On my machine, the output looks like...
When you compare it against the output of ifconfig...
...you can see how the ifconfig ether entries match what is in 70-persistent-net.rules.

Ok used the following:
Now will that do it or do I need to do something else?

BTW I am in rural Texas on a satellite feed if that has any bearing

If you run (as root) , that would solve the problem.

The other option would be to run (as root) . If you think that you might want to wicd later, then choose this option.

Hmm. Ok. As root, run the command and then run ifconfig to see if your ethernet card magically appears.

EDIT: If the insmod command fails, please give me the error message. I didn't run it locally.

Am on other machine again. But Wicd is gone!

Well close, will try again tomorrow

Ok, run as root chmod +x /etc/rc.d/rc.networkmanager and that should fix that problem when you reboot.

See you tomorrow. At least we all know that your wireless can be made to work again.

That was it. We are up and running again. I actually get to put solved on something. Thanks that was great. I hope the rest of this works out as well. Will talk to you later.

After checking, I really should have told you to run (as root) instead (insmod wants a path to a file, while modprobe is smart enough to look in the right places). "b44" is the kernel module that your system was using to bring up your wired connection before and it comes with the slackware kernel. Your system really should be able to load b44 without any help from you, but first things first.

If eth0 does come back to life, you can use NM to configure your wired connection too. Some folks use NM for the wireless connections and /etc/rc.d/rc.inet1 for wired connections, but if you have a laptop you might as well have NM handle both types of connections for you.

Yep that took care of cable problem too.