madwifi non-functional after kernel rebuild, reinstall, SW 12.1
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
madwifi non-functional after kernel rebuild, reinstall, SW 12.1
UPDATE: SOLVED
I think the problem was that I was missing one option to enable something important for the udev hotplug support junk. I'm not sure, because I just started enabling suspicious sections, and now it works. :-P
Hopefully, this thread will be helpful to someone else.
hi all,
I've come into a problem with the madwifi driver and I've exhausted all ideas in my noobie mind.
The backstory: A week ago, I was a happy slackware user on my toshiba satellite mx40 laptop. Everything was working, and I was able to install and use madwifi as instructed by http://madwifi.org/wiki/UserDocs/Distro/Slackware. I was using the smp kernel and my disk io was pretty ugly; I needed to recompile the kernel (one of those problems involving the hda -> sda labels). After some optimizations, I've configured the kernel to my liking; except that now I'm unable to get the madwifi drivers to work. It installs and appears to be working, but it does not detect or connect to any Access Points. The only error I can get happens when I try to scan using
Code:
# iwspy ath0 scan
Interface ath0 doesn't support IP addresses
ath0 Interface doesn't support IP addresses
No valid addresses found : exiting...
I've enabled and disabled certain kernel options according to the madwifi website, and have tried rebuilding my kernel many times, all with the same result. My eth0 interface does work, so I know that it's a wireless problem and not just network. I've included all the neccessary crypto in the kernel (and as modules on previous attempts). I've tried both packages on alien bob's site shown here: http://www.slackware.com/~alien/slac...madwifi/build/ .
I feel like I've done everything, and I don't know what to try next. Does anyone have any suggestions?
Last edited by original_jamingrit; 07-13-2008 at 07:32 PM.
Reason: edited line lengths
Yes, I've been using Alien Bob's build scripts. I tried both the 0.9.4 tarball and the build script that worked before, as well as the current-trunk package and buildscript on his site. I tried rebuilding for each kernel, using removepkg for old madwifi packages each time, even though it's probably not necessary.
Also, tried your other suggestion:
Code:
# iwlist ath0 scan
ath0 Interface doesn't support scanning : Network is down
I suspect this is a kernel thing. I configured my current kernel from scratch, so I might try making a copy of the smp .config file and deselecting the extra stuff instead.
update;
After several more kernel builds, still no luck. I tried using a Livecd to make sure my wireless wasn't just broken; the hardware does in fact work. I checked the lsmod on the LiveCD and made sure all of the appropriate modules were built and loaded on my slackware kernel. I'm not still sure if this is a kernel problem, but I'm open to any suggestions that anyone has...
Haven't tried anything new yet, but I'll do some reading and try to figure out if I'm just installing my new kernel incorrectly. This is the first time I've succesfully rebuilt a optimized kernel on this machine, so there may be something I missed.
----------------
UPDATE: SOLVED, READ OP
Last edited by original_jamingrit; 07-13-2008 at 07:41 PM.
Haven't tried anything new yet, but I'll do some reading and try to figure out if I'm just installing my new kernel incorrectly. This is the first time I've succesfully rebuilt a optimized kernel on this machine, so there may be something I missed.
----------------
UPDATE: SOLVED, READ OP
Thanks for a hint in the right direction. Can you give more information about your fix?
To be perfectly honest, I forget what it was exactly, but I think it the PCI-ISA bridge that was missing its driver. Like I'd said before, I've never succesfully compiled a kernel for this machine before, so most of it was hit and miss. I'm sure I enabled a few things I didn't need to in the process.
Are you unable to use wireless, or is it something else that you're missing?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.