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 just installed Slack 10.1 from CDs and I saved most of the files I had from my previous installation. Unfortunately, my reinstallation wasn't flawless. My pcmcia driver is working. I have my rc.wireless.conf configured with the exact same as it was. When the system boots I get something like this...
dchcp MAC Address: **some numbers**
Now, usually the next line would normally be the assignment of an IP address 192.168.something). Instead, there is no IP address assignment. When I run "iwconfig" the settings look good. The ESSID is correct and my wep key is correct, but there is something wrong.
If your card requires firmware the location changed between 10 and 10. In 10.1 it is now in /lib/firmware.
If your card required a module to be compiled it will have to be recompile and loaded into kernel modules
Check the output of dmesg if the above two suggestions do not help and post it back here.
Edit: I also recall in the current changelog that the wireless init scripts were changed within the last few days.
Sat Jul 30 13:01:25 PDT 2005
a/smartmontools-5.33-i486-1.tgz: Upgraded to smartmontools-5.33.
a/udev-064-i486-2.tgz: Commented out the new lines in udev.rules. It seems
like these aren't really needed now that the symlink in
/etc/hotplug.d/default/ was restored, and having them there causes a race
race condition that can cause things like wireless adaptors that need to
load firmware to fail to initialize.
n/wireless-tools-27-i486-1.tgz: Upgraded to wireless_tools.27.
Thanks to Eric Hameleers for the improved rc.wireless scripts.
rootdisks/install.*, rootdisks/network.dsk, rootdisks/pcmcia.dsk:
Fix /dev/urandom device (thanks to Daniel de Kok).
Bumped version number to 10.2.
Fri Jul 22 13:54:50 PDT 2005
The KDE Wifi tool shows that I have signal strength (although it is eratic even when I am 10 feet from the router. It will be strong and then drop out at random. I had the same issue with my previous installation. Perhaps we can fix that while we're at it.) but there is no IP address. I did a netconfig and it should be setup for the the dchcp to just assign an IP address.
when connecting using wireless card my computer will have an ip address provided by the wifi card or I will have to do any alias wifh my eth0 card or something? I have two WiFi cards (to bem honest I will get the second this afternoon) One is a Broadcom with ndiswrapper and the other is a DWL 610 pcmcia. Both of them are working perfect. So I can configure my broadcom I have to do what? This is what I suppose:
#ifconfig wlan0 up
#iwconfig wlan0 ap [mac address]
#iwconfig wlan0 essid [name gatered on iwlist scan]
This is right ?? Im going to connect today for the first time using linux but the AP doesnt have any encryptation key so I suppose I dont need configure anything more, right? But if I have a WEP encryptation key or a WPA what file I must edit to put this to information ( /etc/rc.d/rc.wireless?) ??
Originally posted by maginotjr How do I set a WEP ou WPA key ? ....................But if I have a WEP encryptation key or a WPA what file I must edit to put this to information ( /etc/rc.d/rc.wireless?) ??
This one I can answer. You edit the rc.wireless.conf file. That is where I have my info, ESSID, Key (wep), and Rate.
[What is lo (loopback) and is it supposed to be installed?]
lo no wireless extensions.
eth0 IEEE 802.11-DS ESSID:"myESSID" Nickname:"todd"
Mode:Managed Frequency:2.427GHz Access Point: 01:00:09:00:01:00
Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:6/3
Retry min limit:1 RTS thr: off Fragment thr=1536 B
Encryption key:2056-3127-17 Security mode: open
Power Management period:0us mode:All packets received
Link Quality:0/92 Signal level:107/153 Noise level:67/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Sample from rc.wireless.conf
## NOTE : Comment out the following five lines to activate the samples below ...
## --------- START SECTION TO REMOVE -----------
## Pick up any Access Point, should work on most 802.11 cards
Connected to "my SSID"
AccessPoint: "some long number"
Local IP: Unavailable
Signal Strength:71 (the level will change constantly even with the laptop 5 feet from the router)
Im starting to think that the problem isnt on your configurations, maybe on your AP ... maybe your ap is not running a dhcp server? I dont know. But its strange that it dont work.
Have you tryed #iwlist scan to see if your networks are being show and if your ESSID its realy the one you are using?
Lo or Loopback or 127.0.0.1 is the IP address of your on machine, this is why its call loopback, everytime you enter localhost or 127.0.0.1 you´re fetching your on computer, its a way for your computer find itself... and yes, it must be configurated and installed.
Originally posted by dunric What did you meant by "flashing not ready" in sentence ?
My wireless PCMCIA card has 2 lights on it. One light is simply as a power indicator. The other has to do with wireless connection. If the connection is established it is a solid green. If the connection is NOT established, the light flashes.
I have a feeling I forgot to install something when I installed Slack 10.1. I am going to reinstall Slack....this time I will use a Slack-Current ISO from 8/1 and install EVERYTHING....like I used to do.