Loaded madwifi drivers but still can't use wireless card
FedoraThis forum is for the discussion of the Fedora Project.
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.
Loaded madwifi drivers but still can't use wireless card
I'm very happy with Fedora Core 1 on my laptop. I got the ethernet pcmcia card working without a problem, but I have a wireless card for this laptop, too. I knew about the MADWIFI project for Atheros-chipset based cards like mine. I used the MADWIFI drivers in Slackware before on this same laptop.
These are the steps I took to get started installing the wireless card with MADWIFI:
installed the development and kernel source packages
installed sharutils package
downloaded the latest cvs tree from madwifi to a local folder
ran make install
The laptop sees that hardware is there, but I cannot get it to connect to the network.
I placed the following commands in /etc/rc.local:
ifconfig ath0 up
ifconfig ath0 192.168.1.21
iwpriv ath0 mode 1 <-- to force 802.11a
The device seems to be working but cannot ping other computers, much less ping a web site outside of my home network.
Well, since I might use this laptop else where besides my home network, I decided that the wifi card should use dhcp.
The thing is I was using the wrong command. I shouldve been using dhclient ath0 to get IP addy from my home dhcp server.
But there is still an issue. After typing dhclient ath0, I get the following output over and over:
/sbin/dhclient-script: configuration for ath0 not found.
Listening on LPF/ath0/00:06:25:0c:ad:c8
Sending on LPF/ath0/00:06:25:0c:ad:c8
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
So it is communicating with the dhcp server, but something is preventing the card from getting the offered addy. I goggled with the first line as a search criteria but nothing turns up that relates to my issue.
I dropped into the #redhat channel at irc.freenode.net and someone asked me if I had ifcfg-ath0 in place. I created the missing script, which was no easy task. It took some trial and error to get the script just right.
I saved the script in:
Note: I'll post the script contents when I get home today.
Well, even after putting tha script in place, I'm still having issues. The wireless card gets initialized, it grabs an IP address and I can surf the 'net or ping other computers for only 5 secs. The it drops the connection but it comes back. When the connection comes back, it is super slow.
RedHat 9 and Fedora 1 come with a useful configuration utility called 'redhat-config-network' or 'neat'. This utility works nicely in setting up the ifcfg-eth0 (...) files including wireless support. The only problem: you cannot enter ath0 as a hardware device. But there is an easy workaround:
1) delete the ifcfg-ath0 files (the one I have seen posted above, is wrong)
2) create a new wireless configuration using 'neat', naming the configuration ath0 using the device eth0.
3) edit the ifcfg-ath0 files and change the DEVICE entry from eth? to ath0
4) plugin your wireless card and everything should happen automagically.
here is my ifcfg-ath0 file:
[root@lopi network-scripts]# more ifcfg-ath0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
Fedora now stores WEP keys in a separate file. But 'neat' takes care of that.
some applications cache routing and resolve information such as kde, mozilla, and sendmail. So, if you have any of these running while your wireless network comes online, you need to restart them -- or, much better, do the following:
1) install and enable nscd.
2) create a script called '/etc/dhclient-exit-hooks' which contains the lines
sleep 5 # let's hope the interface is bound by now
/sbin/service nscd restart
/sbin/service sendmail restart
that's it, hope this helps
another RedHat caveat is that if you unplug the wireless card (or shutting down PCMCIA during suspend), hotplug (ie cardmgr) does not correctly down the iface: the dhclient daemon stays running. When the card is then activated again, there are two dhclient daemons. Therefore, in setups where the card is shut down during suspend I recommend killing all dhclient daemons in the suspend scripts.
I was not able to get the card configured by using the ifcfg script.
I have to issue the ifconfig and iwconfig commands manually for it to work.
I don't know why that is.
Also there is something flaky and I don't know if it's my AP or the card itself.
My final solution was to create a text file with the commands I typed in term and made that file executable. Then I placed a link to it on my desktop.
Oh! For some reason the card does not like to be in the system while is booting. LOL
After a shutdown or right before it starts loading the kernel, the card has to be out. Weird!
Thanks for everyone's input in this huge tinkering session.