[SOLVED] Still having problems with wireless connection

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

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.

Richard Cranium · 07-19-2016, 09:34 PM

Quote:

Originally Posted by scythempress

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.

scythempress · 07-19-2016, 09:43 PM

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.

Code:

root@scythempress:~# ls
b43-firmware/  b43-fwcutter/  broadcom-sta/  etc/  install/  lib/  usr/  var/
root@scythempress:~# cd /home/maddmaxx
root@scythempress:/home/maddmaxx# ls
b43-firmware.tar.gz       broadcom-wl-6.30.163.46.tar.bz2
b43-fwcutter-019.tar.bz2  hybrid-portsrc_x86_32-v5_100_82_112.tar.gz
b43-fwcutter.tar.gz       hybrid-v35-nodebug-pcoem-6_30_223_271.tar.gz
broadcom-sta.tar.gz       sbopkg-0.38.0-noarch-1_wsr.tgz
root@scythempress:/home/maddmaxx# installpkg b43-fwcutter-019.tar.bz2
Cannot install b43-fwcutter-019.tar.bz2:  file does not end in .tgz, .tbz, .tlz, or .txz
root@scythempress:/home/maddmaxx# tar zxfv b43-fwcutter-019.tar.bz2

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
root@scythempress:/home/maddmaxx#

scythempress · 07-19-2016, 09:45 PM

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.

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

Quote:

Originally Posted by scythempress

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.

scythempress · 07-20-2016, 07:31 PM

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.

Richard Cranium · 07-20-2016, 08:26 PM

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

Code:

lspci -k | grep -iA3 net

and

Code:

iwconfig

commands as root and post the results here?

scythempress · 07-20-2016, 08:42 PM

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

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

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;

Code:

 lspci -k | grep -iA3 net
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
        Subsystem: Dell Device 01f2
        Kernel modules: b44
03:01.0 Firewire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
--
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: wl
        Kernel modules: ssb, wl
root@scythempress:~# iwconfig
lo                no wireless extensions.

eth1              IEEE 802.11abg   ESSID:off/any
                  Mode: Managed Access Point: Not-Associated  Tx-Power=200 dBm
                  Retry  long limit:7  RTS thr:off  Fragment thr:off
                  Encryption key:off
                  Power Management:off

Whew!

Richard Cranium · 07-20-2016, 09:21 PM

If I remember correctly, you're running KDE. Is /etc/rc.d/rc.networkmanager executable?

Code:

root@hp635:/etc/rc.d# ls -l rc.networkmanager 
-rwxr-xr-x 1 root root 2646 Jun 13 07:35 rc.networkmanager*
root@hp635:/etc/rc.d#

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.

Richard Cranium · 07-20-2016, 09:25 PM

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.

scythempress · 07-20-2016, 09:34 PM

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

Richard Cranium · 07-20-2016, 09:37 PM

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.

Code:

root@hp635:~# /etc/rc.d/rc.networkmanager status
NetworkManager is currently running
root@hp635:~#

If /etc/rc.d/rc.networkmanager is not executable, you'll get an error when you try to run the command.

scythempress · 07-20-2016, 09:44 PM

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

scythempress · 07-20-2016, 09:45 PM

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