Slackware wireless configure

allend · 02-07-2016, 10:54 PM

It looks as though all the necessary driver stuff is in place.
To use NetworkManager, it is necessary to:
1) Revert to a clean /etc/rc.d/rc.inet1.conf
2) Make /etc/rc.d/rc.networkmanager an executable script so that the networkmanager daemon is started at boot.
3) Configure your wireless connection using nm-applet

From the email to root titled "Welcome to Linux (Slackware 14.1)!"

Code:

If you will be using wireless (or even a wired interface), you might
want to let NetworkManager handle your network connections.  This is
a choice during the initial installation, but may also be selected
later by rerunning netconfig, or by setting the startup script
to executable (chmod 755 /etc/rc.d/rc.networkmanager).  When Network
Manager is used to handle connections, a nice interface is provided
to scan for wireless access points and make changes to the network
configuration.  This interface runs automatically with KDE or Xfce.
In fluxbox, the nm-applet program will need to be launched.  Other
window managers lack a system tray to display nm-applet, so for those
you might want to look at wicd in /extra, which also provides a nice
GUI tool for connecting to wireless (or wired) networks.  For window
managers that do not provide a tray for running programs, start
"wicd-client" to make changes.  With NetworkManager or wicd, it's
a good idea to remove any existing network configuration in
/etc/rc.d/rc.inet1.conf first.  This can be done by running netconfig
and setting the machine to use loopback.  Then, if you're using
NetworkManager run it a second time and select NetworkManager.

ReaperX7 · 02-07-2016, 11:19 PM

Quote:

Originally Posted by SenseSpheres

OK, I switched to fluxbox and I see the networks.
It says Ethernet Network
disconnected and Wi-Fi Networks disconnected
And I can see networks

Okay. If you can see networks now, enter your information in the appropriate places and it should connect you.

bassmadrigal · 02-08-2016, 12:03 AM

Quote:

Originally Posted by ReaperX7

BTW, eth1 won't be your wireless connection device. eth1 is usually a secondary ethernet port used for networking connections and pass-throughs.

This depends on the driver. As you can see from his iwconfig output, eth1 is the device name for his wireless. He'd probably need to modify some udev rules to change that (although, it isn't relevant to his issue, as Network Manager and wicd will both handle alternative device names).

@OP, since you're running 14.1, you may want to look at more updated wireless drivers, which would mean upgrading the kernel. You can try the kernel from -current, just make sure you use installpkg instead of upgradepkg so you don't overwrite your existing kernel. You'd want kernel-firmware, kernel-generic, kernel-huge, kernel-modules, and kernel-source. All but the last are in the a/ series and the last is in the k/ series. Then just update your lilo.conf to add an entry for the new kernel (don't replace your existing entry so you have a fallback kernel in case something goes wrong), run lilo, and reboot.

SenseSpheres · 02-09-2016, 05:19 PM

I had to work a few days and didn't have time to access a wireless network. I live somewhere w/o Wi-Fi. I went to a cafe and configured with nm-applet and I have a connection! Thank you so much, I have trying get online for weeks. (;