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 just switched from cable internet to dsl (at&t) and didn't think about getting any wireless drivers before switching.
I have a D-link DI-524 wireless router hooked up to my Mini Mac and using a DWL-510 wireless nic in my PC tower system. Using Slack 12 with default kernel. Everything works without problems on Debian Sid.
I was able to get and install the madwife drivers and to me, everything seems to be installed correctly, but I'm not able to connect to a website or ping a site using IP address or the name. Error comes back showing 'Host not available'.
When I used cable internet, /etc/resolv.conf had the cable info in it. I ran 'netconfig' and for domain name, added dsl, att.net. Is this correct to add att.net for domain? Also, if I remember correctly, it had an IP address but now no IP address is showing, only att.net.
When I ran /sbin/iwconfig, I see info for ath0 but it show no wireless extension for eth0 and no extension for lo.
Kwifinetwork show the wireless card as active, with green bars in the system tray.
When I type lsmod, I see the driver installed, ath_pci.
Thanks to all. I'm up and running wirelessly...this is what I like about Slackware & Debian, the so-called hard distros, they're the easiest to use of all distros, IMHO!
I'm having dependency hell with Fedora getting wifi working, but will work on it.
I just switched from cable internet to dsl (at&t) and didn't think about getting any wireless drivers before switching.
I have a D-link DI-524 wireless router hooked up to my Mini Mac and using a DWL-510 wireless nic in my PC tower system. Using Slack 12 with default kernel. Everything works without problems on Debian Sid.
I was able to get and install the madwife drivers and to me, everything seems to be installed correctly, but I'm not able to connect to a website or ping a site using IP address or the name. Error comes back showing 'Host not available'.
Any ideas on fixing this?
Hi,
You could look at Alien_Bob's wiki for Slackware and using the Atheros Madwifi.
Eric has done a great job to assist you with problems of this sort. You should look in the configuration section. He has covered the '/etc/rc.d/rc.inet1.conf' file very well. The wiki is based on Slackware 10.2 but applicable to 12 as a guide.
Last edited by onebuck; 09-03-2007 at 01:06 PM.
Reason: clarity
You could look at Alien_Bob's wiki for Slackware and using the Atheros Madwifi.
Eric has done a great job to assist you with problems of this sort. You should look in the configuration section. He has covered the '/etc/rc.d/rc.inet1.conf' file very well. The wiki is based on Slackware 10.2 but applicable to 12 as a guide.
OK ok got the hint :-)
I did an update of the page, adding some new info, deleting some old cruft.
Especially worth noting for Slackware 12.0 users is that you can use the Slackware 12.0 wpa_supplicant package without modification with my madwifi package. Starting with kernel 2.6.14, the "wext" driver of wpa_supplicant can be used to let madwifi and wpa_supplicant communicate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.