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.
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.
I'm using Ndiswrapper 0.8 in my 2.4.29 kernel and it works great. However, I obviously have to rebuild it to use it in my 2.6 kernel, but the problem is it won't compile!
I decided to make a copy of the ndiswrapper directory before I compiled it, so that there would be less likely of a chance of conflict between the original version and the new one. However, when I did a make install I got the following errors...
too many arguments to funtion 'pci_save_state'
too many arguments to funtion 'pci_restore_state'
within a couple different funtions within the ndiswrapper source files
and an overall Error 2 for make.
I'm thinking that perhaps 0.8 is not the best version of ndiswrapper for the 2.6 kernel, so I think I'll try a different version. The reason I used it in the first place, however, is that other (newer) versions seemed to make my system crash when I wanted to eject my wireless card (through cardctl eject).
Too bad I can't just convert my current module to the 2.6 version. Out of curiousity I copied the module over to the 2.6 module tree and renamed it with a .ko extension. It didn't work as expected (yet hoped).
Anybody have any suggestions on this matter?
thanks,
I've heard there are issues with the recent 2.6 smp kernels and ndiswrapper. If you are using an smp kernel, try a non-smp version. Your error messages indicate a problem with acpi which has been a known issue on recent 2.6 smp kernels as well.
I only have one processor (Pentium II), so I did not enable SMP on my kernel.
I did try and load a newer version (1.4), and it compiled but seems to have parameter errors when I try and load the module. There might be an issue with the stack space, but I'm not sure. When I compiled it a couple of warnings were shown telling me that newer Windows drivers might require an 8k stack space versus a 4k space. I don't think I have an 8k space enabled, but I think I was still using the older drivers (2000) anyways (not to mention that if the stack space WERE a problem my computer would have crashed). Perhaps the 1.4 version only works with the XP drivers, so I might try that after I make sure I have a stack space big enough for it. I also did not unistall the old ndiswrapper version first so that could very well be a problem.
If the newer version requires an 8k stack space because it will only work with the newer drivers I think I'd rather use the older version if it is able to work with the 2.6.13 kernel.
What do you think? did I totally miss what you were saying to me?
completely unistalling the ndiswrapper and doing a fresh intall with the 1.4 version with the XP driver worked just fine. By doing this, however, I decided to scrap wireless support for my 2.4 kernel. I don't really care much about the 2.4 kernel anymore anyways since I've tweaked the 2.6 kernel so much it works beautifully in every aspect. My only problem now with my system is the fact that when I switch between X and the consoles that my X desktop (Xfce) is dark. I've had this problem since I originally installed slackware and haven't found a solution. I previously made a separate thread about the issue...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.