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.
Hi I've been bashing my head against this for a couple of days now. First I tried editing rc.inet.conf and wpa_supplicant. When that didn't work I tried changing them back the way they were. Then I set my router up to have a guest network with no key just to see if I could get it to work that way. I've been trying to use iwconfig to set the ESSID so far to no avail. I have been using:
iwconfig wlan0 essid GUEST_Network
I do not get any error messages, but when I check again the ESSID is not listed. It is set to off/any. I'm sure it has to be some stupid little thing I'm doing wrong as I am new at this.
Also, I don't know if it helps, but I can scan with iwlist and get a nice long list of all the access points so I think the wireless adapter is working.
Do you have either NetworkManager or Wicd running? If so, they may be interfering with your attempts at manual configuration. Also, is there a reason you are trying manual configuration of your wireless adapter rather than using one of the aforementioned tools? (Not that you need to use one; there are perfectly valid reasons for manual configuration.)
Mike_M: I have no idea how to see if NetworkManager or Wicd are running. I would assume not as it is a fresh install and I have only set up a user account and attempted to connect to the internet. I'm probably doing this completely backwards. Its just that I was going by the configuration guide in docs.slackware.com, and I am a perfectionist and have to follow instructions exactly and I know you probably don't have to do it like that, but one of the first things it said to do was update I think, and I didn't have a way to do that. Also, now that I've started doing it like this, I just think it would be neat to do manually. I guess a good question would be in what order should I be setting up these things.
ttk: There are entries for acer-wireless and phy0 and neither of them are hard or soft blocked.
So network manager is running. That will get in the way of your approach. If you want to continue attempting to manually configure your wireless network, run the following as root to turn off NetworkManager and keep it from starting in the future:
# rfkill list
0: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
# lsmod|grep acer
acer_wmi 19581 0
sparse_keymap 3016 1 acer_wmi
wmi 8403 1 acer_wmi
rfkill 15428 3 cfg80211,acer_wmi
Even with NetworkManager out of the way, I think the acer_wmi module may also cause problems. After you stop NetworkManager see if you can use iwconfig to associate with your access point. If you still are unable to you may want to try blacklisting the acer_wmi module it to keep it from loading. This can be done by doing the following (again, as root) and rebooting:
I suggest doing this only if you still have problems after stopping NetworkManager because keeping that module from loading may reduce the functionality of your computer in some way (certain special buttons may not work, etc.)
Last edited by Mike_M; 01-14-2013 at 01:49 AM.
Reason: Was missing the word "stop" after /etc/rc.d/rc.networkmanager
Okay, thanks very much.
Kind of off topic, but, I'm trying to decide on a desktop environment. It's going to be on a little netbook so I'm leaning towards xfce. Should I choose xfce or kde and if I do should I still go about setting it up manually, or try to get it running in the de? If I do get it running in the de will I still need to do the stuff above?
Which DE to use is a matter of personal taste. Either XFCE or KDE should be fine. Both of them will have an applet to configure wireless using NetworkManager, so I'd suggest giving that a shot at some point.
There is nothing wrong with learning how to manually configure wireless networking so that you know what is going on in the background, but NetworkManager is pretty simple to use and makes connecting to multiple access points a snap. If you do decide to skip configuring things manually, leave everything the way it is now and see if you're able to associate with your access point using the NetworkManager applet within whichever DE you choose.
Okay. Is there a way to turn off NetworkManager for a second to play around with it? I will probably go ahead and use xfce as I am distro hopping and I already have kde running under openSUSE and Openbox running under Crunchbang. I really like Crunchbang so far. It's so plain. I used to think I enjoyed having a bunch of flashy stuff going on and I guess I still do to some extent, but I'm really starting to like simplicity. KDE/openSUSE is nice so far but a little buggy at times and I guess I have a fear it's going to use up too many resources. I was using Ubuntu and Unity which I liked okay, but it started to get really laggy so I gave it up. I think I got a bit teary eyed when I had to give it up because it's the first one I ever really used. Silly, I know. And now I'm trying Slackware. Honestly, I had no idea what I was getting myself into, but I've begun to learn some command line stuff which is great. Still not picking up on what all the lsmod, grep chmod stuff is though. I can get around the file system and edit stuff so far, and now I can use iwconfig, I think. I really need to read up on this stuff. sorry to be so long winded.
Okay. Is there a way to turn off NetworkManager for a second to play around with it?
The following will stop it:
# /etc/rc.d/rc.networkmanager stop
To start it again:
# /etc/rc.d/rc.networkmanager start
Originally Posted by nepeta
Still not picking up on what all the lsmod, grep chmod stuff is though. I can get around the file system and edit stuff so far, and now I can use iwconfig, I think. I really need to read up on this stuff. sorry to be so long winded.
We all have to start somewhere, and everyone learns at their own pace. No worries at all. Man pages are a great way to learn about commands, although they aren't always the easiest documentation to read. If you are interested to see what those command are/do, run "man <command name>" from a terminal. For example:
Run "man man" to learn more about what man pages are and how they are laid out.
The first step stops it from running. The second step removes executable permission from the script that starts it, so it won't start up when your system boots. That way you can switch to it latter if you feel like without the need to reinstall.