SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a fresh install of Slackware 13.1 on my Samsung N150 plus. I've been fiddling around with it for a couple of days trying to get the wireless to work. Below are the network controllers of my laptop.
05:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller
I included wireless and wired, not sure it would help or not.
After many Google searches on the subject I installed and setup Wicd. I am able to get a wired connection but not a wireless. I can see other networks, I am unable to connect to them though. Also when I installed Slackware I didn't setup the network. The Readme for Wicd said that having a network configured can mess it up. But is having no network set up worse. I know there is easier way to setup wireless networks, I just cant figure it out. Help is appreciated.
*Edit* If I'm missing some information that would help fix this, please tell me. Thanks
What part of the script do I replace. I looked through and didn't see a part that made sense to change. Or do you want me to replace the whole script with iwconfig wlan0 essid mywireless key 0123-4567-89? Im hesitant because the last time I removed a script I caused the computer to not be able to boot.
Also will having Wicd installed mess any thing up?
If you don't want to dump all your /etc/rc.d/rc.wireless, just rename it so that you can put it back in place if anything goes wrong. All you need in rc.wireless is that line
iwconfig wlan0 essid mywireless key 0123-4567-89
Don't forget to chmod +x rc.wireless to make it executable.
mastemmer
I did what you said and I did get a wireless connection. There are a couple of things I do have problems with though. I wouldn't be able to connect to another wireless internet without having to edit files.
Code:
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:1F90-3F62-F4
Power Management:off
Well, did you configure the key anywhere?
You know, without the apropriate key and the ssid (networkname) you cannot authenticate at the accesspoint.
If you're running wicd there should be an icon anywhere in your Windowmanager, if you click the icon with the righthand button, you'll get some options, when you go onto the "connection" field with the mousepointer, wicd scans for the available wireless networks. You may chose yours and when wicd asks, you'll have to enter your key.
Be sure that wicd is running
Code:
ps -e | grep wicd
if this doesn't show any output you'll have to start wicd as root
Code:
/etc/rc.d/rc.wicd start
This should all work without changing the script rc.inet1.conf
Wicd runs fine. It doesn't ask me for my WEP key though. I'm using the version I got with the disk. Do you think it might be a bug that is fixed in a future release of it?
You edit the /etc/rc.d/rc.inet1.conf (it is selfexplaining) and the /etc/wpa_supplicant.conf (there's an examplefile in the /usr/share/wpa_supplicant directory. And uninstall wicd before!
After configuring rc.inet1.conf and wpa_supplicant.conf you can start your wlan0 with
Wicd runs fine. It doesn't ask me for my WEP key though. I'm using the version I got with the disk. Do you think it might be a bug that is fixed in a future release of it?
You have to configure the options under preferences for that adapter. There's a check mark for using encryption, then a spot to input your key. Wicd does not prompt you encryption keys, you have to put them in manually. Once these preferences are set, they are remembered though.
If your wireless router is set with 64 bit WEP encryption, the key is a ten digit hexadecimal number such as 1234-5678-9A. There is also the network ID (ESSID) which is the name of you network connection.
You may use wicd to find the essid of wireless networks in the neighborhood. It won't tell anything about WEP keys because that is intended to be secret.
The command
iwconfig wlan0 essid mywireles key 1234-5678-9A
sets the essid and key so that it can connect to a wireless network.
The script /etc/rc.d/rc.inet1 uses DHCP to get an IP.
OK. The method i recommended is not flexible, but works if you don't
have to change your wireless station frequently.
The original script may be better, automatically detecting the surrounding networks, but did not work for me.
Wicd runs fine. It doesn't ask me for my WEP key though. I'm using the version I got with the disk. Do you think it might be a bug that is fixed in a future release of it?
Thanks for all of the help guys but I kind of gave up. I installed Debian and it fixed most of my problems. But of course it still doesn't do what I want it to do. I still am unable to view other wireless networks available and switch to them. It picks one network at boot up and sticks to it. Since I hate Debian with a passion I was wondering if there was a better solution with Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.