[SOLVED] ndiswrapper and 3.2.18-pclos1.pae.bfs

[Timothy]

I'm not sure if this should be in the "Testing" forum or here...  I've finally gotten around to building a system to use for testing the "testing" repository and yesterday I was loading it up with all the latest and greatest.  

First and foremost, I have an unsupported USB wireless dongle (Linksys AE2500) running ndiswrapper / WinXP driver.  

I installed my test system from the latest KDE Desktop distro, did a full upgrade, then replaced 2.6.38.8-pclos3.bfs with 2.6.38.8-pclos3.pae.bfs to access the full system RAM.  Since I'd come this far I thought I'd go the whole distance and try the 3.2.18 kernel.  I installed 3.2.18-pclos1.pae.bfs and that's when things got ugly...

Rebooted into 3.2.18-pclos1.pae.bfs, everything working except no wireless.  
Ran "lsusb"; returned "Bus 002 Device 009: ID 13b1:003a Linksys".  
Ran "ndiswrapper -l"; returned "bcmwlhigh5 : driver installed, device (13B1:003A) present".  
Ran "lsmod | grep ndis"; returned... nothing, nada, niente.  
Ran "modprobe ndiswrapper"; returned "FATAL: Module ndiswrapper not found".

Well, now I'm out of my depth.  I have built ndiswrapper from the sources, but that was long, long ago on a distro far, far away.  So I whimped out, regressed the system to 2.6.38.8-pclos3.pae.bfs, and started typing this missive.

Any suggestions anyone?  

[Just17]

If you want to build it then this should help

http://www.pclinuxos.com/forum/index.php/topic,107547.msg919178.html#msg919178

...  else of course you can use the working kernel. 

[Timothy]

Now I feel stupid...   

I followed the link that Just18 provided.  Downloaded, built and installed ndiswrapper.  Then fired up Control Centre to configure my wireless dongle.  That's when I discovered that the dongle is supported natively in 3.2.18.  Never even occurred to me that it might be.  Go figure...

Now I shall test it for a few days and if all is well, update my production system to match