SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to get my WA3002-g1 wireless modem/router to work on my Acer Aspire 5100 laptop. It works in Windows.
I have 188.8.131.52 kernel which load bcm43xx by default. I have installed ndiswrapper 1.47. I coppied bcmwl5.inf and bcmwl5.sys from windows onto Slackware and installed them through ndiswrapper.
The out put of ndiswrapper -l is -
/etc/rc.d/netdevice loads ndiswraper.
Now, I want to know what modifications are to be made to /etc/rc.d/rc.inet1.conf and /etc/rc.d/rc.wireless.conf
Secondly, if I want to use ndiswrapper, do I have to unload bcm43xx? If so how do i do that?
Thanking in advance,
You should blacklist the bcm43xx module to keep it from loading at boot. You do that by adding blacklist bcm43xx to /etc/modprobe.conf.
The modifications you make to connect to the WLAN depends on your WLAN configuration. Do you use WEP so WAP? If don't use any encryption at all or WEP, you can configure the card using the ordinary net configuration file (not sure what it's called in Slackware). For WAP you need a program called wpa_supplicant. The easiest way though, is to use Network Manager and either knetworkmanager (plugin for KDE) or nm-applet (plugin for Gnome).
But first of all you should check if the interface is really up using ifconfig and iwconfig.
Thanks a lot friends, now I have a working wireless connection
However there a few things that are to be set right.
When I made the following changes to inet1.conf -
WLAN_WPA="wpa_supplicant" # wpa_supplicant is absent on my system
the wireless network was up and kicking. How ever when I rebooted, the booting process halted at -
dhcpd: mac address = xx:xx:xx:xx:xx:xx
for quite some time. And when was finally able to log onto my slack install, the wireless network was down.
I had to give the following commands to get it working
$sudo iwconfig wlan0 essid "RT2561_6"
How can I make these changes permanent so that I don't have to issue these commands each time I boot.
2Gnu, I may sound stupid, but I am not as stupid as to get the name of my distro wrong. I am using Slackware 11.0 since the time it was released. I have been experimenting with other distros, but my 'main' distro is Slackware. I always keep coming back to it. So kindly be rest assured that I am talking of slackware when I am talking of slackware and not ubuntu, I hope you are getting what I want to convey.
As far as 'sudo' is concerned, I find it more convenient and much more safe than having to log is as root.
Are you suggesting that 'true' slackers do not use sudo?
I'll answer for myself, the sudo is a fine way to access 'root' privileges.
The 'su' command is another means to access. Your 'sudo' is better in the sense that you can control who gains 'root' via the '/etc/sudoers' file.
2Gnu, I am using dhclient here because I was not familiar with the use of dhcpcd. And more over I didn't realise that the use of dhclient would automatically brand me as a Ubuntu user.
MrGoblin, I have made the changes you suggested and now I don't have to manually set essid.