LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Slackware, rc.wireless.conf help. (https://www.linuxquestions.org/questions/linux-wireless-networking-41/slackware-rc-wireless-conf-help-751424/)

Avacado 08-31-2009 03:28 AM
Slackware, rc.wireless.conf help.
 
Hi guys.

Hopefully someone can help here.
Slackware seems to load my Laptops intel pro wireless driver at boot as I see something similar to

-Intel wireless 2100 found at eth1
-loading ipw2100.fw

When I startx into KDE then use Kwifimanager I need to also "activate" config 1 for kwifi to pick my card up, then I need to dhcpcd to obtain IP/gateway etc. Real hassle, no fun and irrelevant when I'm using fluxbox instead.

Understand I need to edit rc.wireless.conf to some degree but (and it sounds stupid) what do I need to put and where, do I put my ssid where it says any essid? Also what do I need to edit for it to come on at boot so I don't need to go through the above KDE hassle.

Kind regards

Hangdog42 08-31-2009 07:29 AM
To be honest, for wireless using wicd beats the living bejesus out of using rc.wireless.conf or some other tool. Have a look in the extra directory of your Slackware install disk for the package. Once you have it installed, make sure /etc/rc.d/rc.wicd is executable (and start it if you haven't rebooted) and then when you're in your favorite GUI, run wicd-client. You can get wicd-client to run automatically in both KDE and Fluxbox. If you're using Slackware 13, there is also wicd-curses which runs in console mode. Good for freaking out the Apple fanbois in the coffee shop.

Avacado 08-31-2009 02:47 PM
Quote:
Originally Posted by Hangdog42 (Post 3663841)
To be honest, for wireless using wicd beats the living bejesus out of using rc.wireless.conf or some other tool. Have a look in the extra directory of your Slackware install disk for the package. Once you have it installed, make sure /etc/rc.d/rc.wicd is executable (and start it if you haven't rebooted) and then when you're in your favorite GUI, run wicd-client. You can get wicd-client to run automatically in both KDE and Fluxbox. If you're using Slackware 13, there is also wicd-curses which runs in console mode. Good for freaking out the Apple fanbois in the coffee shop.
Hi, thanks for the reply.

No probs, finally worked out wireless.conf and set dhcp in rc.inet
everything works on boot up and got wireless connectivity from terminal and beyond.

woot!

Fish_Kungfu 04-18-2010 06:32 PM
Quote:
Originally Posted by Hangdog42 (Post 3663841)
To be honest, for wireless using wicd beats the living bejesus out of using rc.wireless.conf or some other tool. Have a look in the extra directory of your Slackware install disk for the package. Once you have it installed, make sure /etc/rc.d/rc.wicd is executable (and start it if you haven't rebooted) and then when you're in your favorite GUI, run wicd-client. You can get wicd-client to run automatically in both KDE and Fluxbox. If you're using Slackware 13, there is also wicd-curses which runs in console mode. Good for freaking out the Apple fanbois in the coffee shop.
I owe you a beer for the "wicd" tip. :-) I was able to get my Asus N10J-A1 with Slackware 13 & Fluxbox up and surfing on wireless in less than 10 minutes.

Hangdog42 04-19-2010 07:02 AM
Mmmmmmmmmmmmmmmmmmmmm. Beer.

Glad it worked so quickly. That isn't always the case with wireless in Linux.


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