[SOLVED] Should Slackware "autodetect" my Linux-Compat. wireless NIC?
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.
From the 'dmesg' output it seems you do not have the 'wlan1' device configured. Since I do not use wicd any longer it would be a shot in the dark.
If I were trouble-shooting the problem then the first thing I would do is stop using wicd and configure things manually. Disable the wlan0 device and enable the wlan1 then configure manually from cli as root. Do a 'iwlist wlan1 scan' (omit the ticks) from cli to get the available access. If the device doesn't scan then you still have hardware issue. If you get a scan and if there is a security setup you will need the keys to configure.
If you can do the scan then do;
/sbin/ifconfig wlan1 192.168.0.18 #available IP
/sbin/route add default gw 192.168.0.1 #your Gateway
/sbin/iwconfig wlan1 essid "access"
/sbin/iwconfig wlan1 key <PLACE KEY>
/sbin/iwconfig wlan1 ap <00:00:00:00:00:00> <<you get this from the 'iwlist wlan1 scan' above
~#route -n #show the kernel route table
~#ifconfig wlan1 up #should be up already
~#ping 192.168.0.1 #ping your gateway
~#ping 22.214.171.124 #google.com IP(one of many)
~#ping google.com #test DNS, if fail then
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.
If the manual test works then you should setup the manager. Hope this helps!
Click here to see the post LQ members have rated as the most helpful post in this thread.
Maybe I should try and be a little clearer, onebuck!
I am currently able to utilize my D-Link DWA-125 rev. A1 wirekess NIC for connecting to all aspects of my network, including my Samba network AND the internet!
When I insert this NIC into a USB slot, its INDICATOR LED begins to flash at a "regular" rate almost immediately (once I am booted-up and logged-on, of course!). It is configured correctly as wlan1! I did NOT have anything to do with this...; I just used wicd and wicd-client-kde, and the rest sort of "fell into my lap" so to speak!
However (and here comes the MAIN POINT!) - When I insert my TL-WN722N wireless NIC into a USB slot (the same slot, as if that matters!), the INDICATATOR LED does NOT begin to flash! wicd and wicd-client-kde do NOT see a valid wireless interface!
I don't think my wlan1 needs any kind of "manual" tweaking...; I installed the firmware (which was the FIRST ISSUE, that dugan assisted me with), but now, that NIC is still NOT "acting normal" in my system! Pop out the TL-WN722N, replace it with the D-LINK NIC, wlan1 works OK AGAIN!
You see my dilemma?
I hope that makes the issue a little clearer (and, hey, if I'm WRONG, and some of that "manual configuration" is required, then my bad!).
I am sort of leaning towards a driver issue as being the culprit, but because dugan said HIS TL-wN722N NIC was working FINE on his system,
I am stumped as to why my NIC won't work!
I MUST point out that the TL-WN722N *DOES* work perfectly under windoze, so it isn't the NIC hardware itself! As a matter of fact, the TL was my FIRST USB wireless NIC, and I have been using it under windoze for over a year!
I was really kind of in the middle of a whole bunch of stuff when I posted the "issue solved post"!
Here we go...
I have WAY too much experience with windoze, I think! The resolution came down to my understanding (or LACK OF!) of the mechanisms by which my wireless NICS were being utilized. I though that I had either a "wlan0" on ONE MACHINE, and then, for some strange reason, it was called "wlan1" on ANOTHER MACHINE! I would insert the TL-WN722N NIC into my old notebook (a Toshiba Satellite), and the thing just wouldn't seem to function! Of course, at the time, I couldn't get the INTERNAL wireless NIC to work EITHER, not knowing yet about wicd and all that...; I was generally using windoze to surf the net when I went wireless! I thought that Slackware simply did not support my internal NIC!
Once I found out about wicd, I realized that my internal NIC worked just fine, as wlan0...; but when I inserted the TL-WN722N (let's just call it the TP-LINK from now on...), it's indicator would not begin to "flash" as the indcator did on my OTHER USB wireless NIC (the D-LINK...). OK, now here's the "kicker" - I simply did NOT KNOW that every time I inserted a new NIC into the usb port, it was AUTOMATICALLY ASSIGNED the next "wlan[n]" spot! So, while I was trying to use the TP-LINK, the system was still using wlan0 (the INTERNAL NIC on the notebook!). Thus, the TP-LINK appeared NOT to be functioning! Through a series of cooincidences, sometimes wicd was trying to use either wlan0, wlan1 OR wlan2 (my D-LINK USB NIC!)...; you see the problem?
I had to discover (quite by accident, I might add) that wlan0 "belonged" to the internal wireless NIC, wlan1 belonged to the TP-LINK NIC, and so on, and that I had to tell wicd WHICH DEVICE TO USE! Once I knew to select wlan1 when I wanted to use the TP-LINK NIC, everything worked PERFECTLY! Still, for some reason, the D-LINK NIC begins to flash (usually right away!) when it is inserted, while the TP-LINK usually simply "lights up" and really never "flashes" much under Linux. Now, under windoze, the rate of its flashing is indicative of how well it is functioning (sending / receiving packets)!!!
So, to make a long story short, it was really my understanding of how Linux handles those devices that was the problem, and I know that there will be at least one of you whose going to say "it was in the book", or something like that...; I know it is probably ALL written down somewhere, but I can't pick up every bit of information from every book I have! Thats generally not how I learn best! I find a quick example makes the information in a book make more sense, and from there the reading becomes much more interesting and pertinent! I guess what I mean to say is, I haven't read the entire Slackbook yet, let alone any of my books on Linux "cover-to-cover"; for me, that's too boring!
Once I knew about wicd, I read the MAN pages on it, and looked into the folders where it stores its config. files. That is how I found out about "rc.inet1", and "rc.inet1.conf". And, by looking into those files, I finally figured out how Linux / Slackware handles network interface cards! Sort of like an "array" of devices, where "eth0" can stand in for the FIRST "wired" NETWORK INTERFACE CARD, "eth1" the SECOND, and on down to the WIRELESS devices, which by default begin with "wlan0", "wlan1", and so on. Now, apparently, these names are ARBITRARY; you could easily name your first WIRELESS NIC "eth0", and NEVER use "wlan[n]" at all! It just makes it easier to determine which of the NICS are wired, and which are the wireless...
So, the issue is "closed", with my great thanks to every one of you that helped me with this issue! I would like to say that in the future I will learn these things BEFORE I call on you good folks, but in my haste to get a decent, "working" system running, I find there is just WAY too much to soak in all at once, so be patient with me I beg you!
For anyone who might be reading the original posting of this topic, and its subsequent replies, that is looking for similar help and not finding their answers HERE, you might like to check out this link (I wish I'd known about it BEFORE I posted my question in the first place!):