Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Check that the kernel headers you installed correspond to the kernel that you are using. To find your kernel number, run:
$ uname -a
Make sure that the kernel headers you installed track that kernel number. That error message is typical of a mismatch between kernel and kernel headers.
The generic kernel matches your generic headers so that should work if you have wireless support compiled in your kernel. You can tell if it doesn't because there will be no /proc/net/wireless file. If that file isn't there, wireless support was not compiled into your kernel. You could recompile and make sure CONFIG_NET_RADIO is set to enabled. It is very rare to not have wireless support configured in but without it, you won't have the wireless extensions you need.
An alternative would be to switch to the server kernel which appears to have the wireless extensions enable since madwifi compiled against its kernel headers.
On non-debian based systems that's easy to do. You just put the commands you want to run at the end of /etc/rc.d/rc.local. In non-debian distros, rc.local is the last init script to run and it runs with root privileges as do all init scripts. Accordingly, any commands you put in there will run at the end of the boot process. It's an easy way to customize your boot setup like you want to do.
One of the more aggravating things about debian is they refuse to put in an rc.local script even though people have been complaining, questioning this for years. Since ubuntu is debian based you probably have no rc.local script. Not to worry, here's a link that describes more succinctly than I ever could how to create an rc.local on a debian system:
Use these lines in your /etc/network/interfaces file to describe your ath0 interface. You can use madwifi instead of wext, of course, but it probably won't matter either way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.