Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
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.
Hi all, i installed the madwifi driver for my netgear WG511T, reboot, it gets to the activating hardware detection /etc/rc.d/rc.hotplug and just stays there with a blinking cursor, the WG511T lights are blinking one at a time alternating. Does anyone have any suggestions on what i should try next? Ive already re-installed slackware 10.2 twice trying to get this wifi card going but no luck yet Sad Any help at all would be very appreciated.
For some reason even with acpi off (upgraded to the 18.104.22.168 kernel) the madwifi driver didnt want to work, i tried the ndiswrapper driver for my card and after altering the rc.wireless.conf and rc.inet1.conf it was up and running
The 22.214.171.124 kernel seemed to fix the 4K_STACK problem, unless something else did it
something went wrong with the ndiswrapper when doing "modprobe ndiswrapper" it makes the whole system hang. Anyone have any ideas on how to stop that happening?
I thought since ndiswrapper didnt seem to be working i'd give the madwifi driver another go. It seemed to install ok (no 4k stack errors) but when it came to loading the driver "modprobe ath_pci" the ath_pci module couldnt be found
I haven't built madwifi since I can't use it, but my guess is that an available Slackware build script is likely to be a good starting place. Personally I think that a native linux driver has got to be a better deal than ndiswrapper, but then again, if you have a working card under ndiswrapper, it is hard to argue that you should change.
I've been doing a bit of digging into the 4K stacks issue, and it sounds like the kernel team has decided that it will be the default for kernels. However, you can change the options under kernel hacking if you are building your own. What makes no sense to me is that I recently compiled a 126.96.36.199 kernel for my server and looking at the config, it appears to be using 8K stacks. I know I didn't change that option so maybe the kernel team hasn't completely settled the issue and Slackware is using them on its own.
Originally posted by Hangdog42 I've been doing a bit of digging into the 4K stacks issue, and it sounds like the kernel team has decided that it will be the default for kernels. However, you can change the options under kernel hacking if you are building your own. What makes no sense to me is that I recently compiled a 188.8.131.52 kernel for my server and looking at the config, it appears to be using 8K stacks. I know I didn't change that option so maybe the kernel team hasn't completely settled the issue and Slackware is using them on its own.
I had concluded as well that the 2.6 kernels that I build with Slackware (as well as the 2.6 kernels that ship with Slackware) have 8k stacks. You will have to explicitly enable 4k stacks in the kernel hacking section when configuring the kernel source tree.
Ndiswrapper's makefile just checks for the existence of the CONFIG_4KSTACKS parameter in the kernel source's .config (as I explained in this other thread) and when it does not find it, concludes incorrectly that your kernel uses 4k stacks.
Nothing to worry about (except that the ndiswrapper developers warn that many Windows NDIS drivers nowadays require even larger stack sizes (up to 32k) in order not to bring down your kernel after some time.
Try this madwifi.SlackBuild - maybe you've already used it, maybe not. Anyway, let us hear whether it helps you get your wireless card working.