I have a Linksys PCMCIA card and it was working fine with the old kernel, but now it says ath0 cannot be found in the new 2.6.20.7 vanilla sources. Did the name change or something? I make a ln -s /etc/init.d/net.lo to /etc/init.d/net.ath0 and kernel support and modules wlan_scan_sta and ath_pci in modules.autoload and pcmcia-cs and rc-update add pcmcia default but still no working. What's the problem here?
Last edited by orangecakez on Tue Jul 10, 2007 4:57 pm, edited 1 time in total.
lsmod - do you have ath_pci module loaded? I only ask because after making a new kernel you have to re-emerge madwifi-ng to get it into the new kernel's /lib/modules/.. directory.
Reason: for some reason at least on my laptop, the order of brining up the modules matter which is kinda stupid?
Anyways I hope this helps
It still says device not found after all that and a reboot too
pdr wrote:lsmod - do you have ath_pci module loaded? I only ask because after making a new kernel you have to re-emerge madwifi-ng to get it into the new kernel's /lib/modules/.. directory.
Yes it's loaded because I didn't just get the new kernel, I did a full Gentoo install with the same exact settings as my old install
I wouldn't think so (udev problem) - I've never had a problem. Although I believe I DO autoload ath_pci (you only need that - it will pull in it's dependency modules). However mine is PCI, not pcmcia..
Maybe there is some new features in the kernel I need to select? I have a WPC55AG v1.3; can someone tell me all the kernel stuff it needs to work automatically?
When I do iwconfig, I see lo, eth0 (my hardline) and sit0 (I have no clue what that is). So no ath0 is showing up yet even though I have madwifi-ng and wpa_supplicant and dhclient.
pdr's right. this happened to me all the time (and it was really frustrating.) When doing a kernel upgrade, I'd forget to re-emerge madwifi after a kernel upgrade, and then wifi fails on boot. the module still has to be compiled against the current kernel, unless you're doing a very incremental kernel upgrade.
right. I'm sorry, I've forgotten, but I believe wpa_supplicant is built against the driver, so you may have to re-emerge that, too. And, just to be safe, go ahead and reboot so you know you're not dealing with the old module. Then see what happens.
If it still doesn't work after recompiling wpa_supplicant and after reboot, try disabling WPA on your router and just connecting with the barebones driver, no wpa_supplicant. If it works, it's not the driver directly causing the problem, it's probably wpa_supplicant.
sketelsen wrote:what interfaces do iwconfig and ifconfig list?
orangecakez wrote:When I do iwconfig, I see lo, eth0 (my hardline) and sit0 (I have no clue what that is). So no ath0 is showing up yet even though I have madwifi-ng and wpa_supplicant and dhclient.
So I just unmerged pcmcia-cs and emerged pcmciautils or something (the new one). It tells me to add "pcmcia" and "yenta-socket" (since that's what I use) to /etc/modules.autoload.d/kernel.2.6 but it says both of the modules are not found when I try to modprobe both of them
If you compiled them into the kernel (statically linked them instead of select to build as a module) you won't find them. Hopefully it should not matter, but I saw at least one software (don't remember what it was) that actually required a module - it was checking via the equivalent of lsmod and, if not found, failed to run.
if you do ath_pci and the module now correctly loads, but cant see the ath0 interface
its probably because you need to load the modules in the correct order now.
Is this the genkernel thing? I'm gonna be no help with that because I have never used it - I always compile my kernel (specific to my hardware).
However if you do "modprobe ath_pci" and lsmod does not show ath_pci (and a few dependencies that it pulls in), then if it said that it could not find the module, madwifi-ng was not compiled against the currently running kernel and is not in /lib/modules/<currently running kernel's version> directory. If it does not say it could not find the module then the module exists but it failed to load - you have to check /var/log/messages to see why it failed. If it says it could not find an atheros chip then either 1) you don't actually have an atheros-based chip, or 2) the kernel cannot access the hardware because intermediate drivers are not loaded (pcmcia, etc).