one more time: ongoing problem making AR5007 card work with FC8, madwifi
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
one more time: ongoing problem making AR5007 card work with FC8, madwifi
okay, i'm now moving this question to the newbie forum, cause my previous two on the same problem just sort of died. if that was because i'm annoying y'all, or i'm asking the wrong questions, somebody tell me instead of just ignoring the thread, willya? otherwise i sit here for weeks waiting...
the problem is me trying to get an Atheros AR5007 card (lspci misidentifies it as an AR5006) working with madwifi, under Fedora Core 8, on a crap Toshiba Equium laptop. previously i've installed various madwifi versions, the AR5007 patched one included, and tried them all with varying degrees of success, but never been able to connect to any wireless network.
what i think i need to do is uninstall everything and start from clean, but being a noob, i got no idea how to do that. i'd really appreciate it if someone could a. tell me how to uninstall tarballs and b. help me out with trying to get madwifi installed and working. i can provide any hardware details and network details ya need.
Looks like you left one of two threads dangling yourself, the other has you saying the AP requires WPA-TKIP. That said not being able to connect to a WLAN doesn't necessarily mean you got the madwifi module stuff wrong could be the wpa_supplicant auth stuff. You know (from the madwifi docs) how to diagnose all is installed && up and running so you can move on to checking the auth stuff?
yeah, i wasn't yelling at anyone. that's why i moved the thread. any case, that's my point - i have absolutely no clue what i'm doing, i don't even know what wpa_supplicant is; right now, the madwifi is supposedly all installed, but when i tried some kinda script with the last guy, it didn't work, i deleted it again and now no wifi at all even tries to load.
if nothing else, can ya just tell me how to remove a tarball so i can remove everything and start again?
ed. i haven't verified it, no, idk how.
Last edited by lepht; 03-07-2008 at 06:56 AM.
yeah, i really do need help here - i'm in so far over my head... like i said, i'm really not trying to be a jerk here; sorry if i gave the wrong impression, i appreciate anything you guys can offer.
lspci: (edited to remove the irrelevant devices)
05:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
07:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)
Linux SHODAN.citadel 184.108.40.206-137.fc8 #1 SMP Sun Feb 10 17:48:34 EST 2008 i686 i686 i386 GNU/Linux
(i'm using the older kernel because of a weird bug in the new version with Compiz)
steps i've already done:
1. found card didn't work out of the box, installed regular stable version of madwifi
2. had to boot into core and not xen to make it compile, got it compiled and installed, didn't create any ath devices
3. tried installing the special AR5007 patched madwifi version, didn't create any devices either
4. excluded the older, non-working wireless kernel module and manually modprobed the madwifi ones. after this it seemed to have a device, though not an ath0 one, that tried (failed) to get IP info at startup
5. Brian1 told me to use a script in the network config folder that included network details - this didn't work, which is why i was telling him it needed AKIP on the other thread. after i deleted it, the device and all the startup stuff is gone, so i'm back here.
seriously though, how do you uninstall a source tarball? i'm not gonna remove anything just yet, i just want to know and google won't tell me... thanks guys, i honestly am grateful for the help.
Deleting files from a tarball you installed with the './configure && make && make install' mantra can be done with 'make uninstall' (in the directory you installed from and *if* the Makefile provides uninstall). Else you could 'make -n install 2>&1|tee ./installer.tee'. This won't install again ("-n") but only list what it would do, read the output ('less ./installer.tee') and locate the files. IIRC the only thing Madwifi does is place modules in /lib/modules/kernel-$VERSION, so if you remove those and 'depmod' again you should be clean if the modules aren't mentioned elsewhere.
You're saying you're in far over your head, and you already indicated you're close to throwing your towel in the ring. But if the Madwifi modules loaded OK and if it created a usable device (whatever the name, it's configurable) then you're already halfway through. You just have to understand what Wireless under GNU/Linux needs and how it works. Any Madwifi doc should show the dependencies:
- kernel with Wifi enabled (apparently OK since modules load w/o problems),
- Madwifi modules (apparently OK),
- Wireless tools (use the CVS version since it fixes *a lot* of things),
- Wpa_supplicant (for auth to the AP, this is where you configure WPA-TKIP),
- Dhclient if not static IP.
That's why I asked you if you knew from the madwifi docs how to diagnose things installed and configured OK so we could move on to the auth stuff.
aight, i'll bear that in mind. like i said, i'm not gonna uninstall anything until i have to. thanks!
as for the towel, it's tied to my hand: i ain't throwing that thing anywhere... i just got frustrated, is all. sorry bout that. i'm not so sure the devices i ended up creating were entirely configurable - usually they'd give warnings at boot where "set mode" had failed, but it was always a hex code, so i have no idea which mode was failing to be set.
okay. kernel - check. modules are still showing up in lsmod - check. which particular wireless tools are we talking about here? i have wifiRadar, but that's about it. i've not messed with wpa_supplicant or dhclient at all, but i will be needing dhclient for sure.
in that case, i guess we can move on and figure out the auth. whatever needs doing, i'll do it - i'm seriously not anywhere close to giving up.
OK. Cool. The tools I talked about is the package that provides iwconfig, iwlist, iwspy and such. You probably already have them but check with 'yum install wireless-tools wpa_supplicant', just in case. In your other thread you posted 'lsmod' output and IIRC it's missing some related modules. In any case, try to 'modprobe -r ath_pci' and all related modules. Now try 'modprobe ath_pci autocreate=sta' check your lsmod output and see if it's got *all* Madwifi modules loaded included (check the dir they're installed in). Now 'modprobe wlan_scan_sta; ifconfig ath0 up'. Then 'iwlist ath0 scan' should spit out info about AP's near. Post any errors you get.
sir yes sir... tools and the supplicant are all installed and updated already. but when i rebuilt the patched madwifi version, modprobe -r'd the ath_pci module out and then tried to reinsert it, i got this:
[root@SHODAN madwifi-ng-r2756+ar5007]# modprobe ath_pci
FATAL: Error inserting ath_pci (/lib/modules/220.127.116.11-137.fc8/net/ath_pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)
not sure what's with that, i was able to do it fine before.
dive: it worked this time; i dunno what happened there. as for modprobe.d settings, i've got the following:
blacklist blacklist-ath5k blacklist-visor madwifi
blacklist-compat floppy-pnp modprobe.conf.dist
the ath5k module we had to blacklist last time because the hardware seemed to still be using it (it's the wrong one.) not sure what the madwifi one is.
unSpawn: i can remove all modules except ath_hal, which it says is in use. it doesn't give me any problems when i modprobe autocreate, which gives me ath_pci, wlan_scan_sta, ath_rate_sample, wlan, and ath_hal modules loaded, and i can then modprobe in all the extra authentication modules (wlan_wep, wlan_tkip, wlan_ccmp, wlan_acl, wlan_xauth) and wlan_scan_ap without a problem. it all shows up in the lsmod. the other two i didn't modprobe in are the ONOE and AMRR rate control algos, which i don't need.
when i try to ifconfig ath0 up, i get this:
ath0: unknown interface: No such device
it never did create an ath0 device on my machine in the first place, usually it was called wlan0. i don't know why, or whether that's a bad thing, but i can ifconfig up the wlan0 interface without errors, and i get this dump:
it never did create an ath0 device on my machine in the first place, usually it was called wlan0. i don't know why,
That's a default AFAIK, you'll have to tell it to name it "ath" somewhere IIRC. Have to do this blindfolded since I nuked my hardware real good :-]
Originally Posted by lepht
i can ifconfig up the wlan0 interface without errors
Yessss! OK, so the AP named "Interweb" is the one to use, right? Post the contents of your /etc/sysconfig/network-scripts/wlan0, /etc/(wpa_supplicant)/wpa_supplicant.conf (and /etc/sysconfig/network/profile/* if any and related) if you have them but leave out the auth keys.
yeah, the Interweb one is the right AP, though after that i'm gonna need to configure it with the University APs too, which are a total snarl... there's no sysconfig script for the interface though. this is wpa_supplicant.conf:
So what happens:
- you boot the box, the Madwidi kernel modules get loaded,
- network comes up which takes care of 'ifconfig up wlan0' and 'dhclient wlan0' (check interface and process dhclient)
so all you're missing is the wpa_supplicant auth stuff. Run this from the console: 'wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -Dmadwifi -w -dd' and see if it throws back ugly errors or not.
yo, sorry for the delay. questions - do i need to edit those files to look like your examples myself, or is that what we're trying to achieve as an end result? also when you say wedge in an entry, what exactly do you mean by an entry? sorry for the confusion, i'm still new to all this =]
also wrt booting, no - no wireless info comes up like it used to on boot. on and off whilst i've been trying to fix this, i've seen the wireless try to up itself on boot and fail, but right now, it isn't even present in the errors.
last up, the AP actually uses AKIP and not TKIP - i can switch those around in your examples with no problem, right?