Linux Cant get ndiswrapper working

As the topic states, ive fresly reinstalled, and am now trying to use ndiswrapper for my wireless netowrkcard (rather than the one built into the kernel) (its a bcm4318).
I can go through all the steps nicely, no complaints (I used the linva resp' for the ndis module). When i issue the command ndiswrappper -l I get

Code:

Installed drivers:
bcmwl5          driver installed, hardware present

and then do depod -a, and then modprobe ndiswrapper, but in dmesg I get (only the last little bit, as as far as I can telll that is all that is relevant.

Code:

ppdev: user-space parallel port driver
ppdev0: claim the port first
ppdev1: claim the port first
ppdev2: claim the port first
ppdev3: claim the port first
audit(1153943731.772:4): avc:  granted  { execmem } for  pid=2298 comm="Xorg" scontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tcontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tclass=process
audit(1153943731.776:5): avc:  granted  { execmem } for  pid=2298 comm="Xorg" scontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tcontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tclass=process
audit(1153943731.776:6): avc:  granted  { execmem } for  pid=2298 comm="Xorg" scontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tcontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tclass=process
audit(1153943731.776:7): avc:  granted  { execmem } for  pid=2298 comm="Xorg" scontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tcontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tclass=process
ndiswrapper version 1.18 loaded (preempt=no,smp=no)
[root@localhost bcmwl]# /usr/sbin/ndiswrapper -l

by the way, my system is fedora core 5, with the 2.6.17-1.2157_FC5 kernel. (yes, this is related to my wpa problems, but ill climb that hill again when I get to it, i managed to completly kill my install).

 

I think it should be working? Can't you get the wpa_supplicant working with the native linux drivers? (don't have to be in the kernel, Modules will work too)

 

When i was compiling wpa_supplicant, with the broadcom driver option, it wasnt compiling. But ive figured out my mistake, I had forgot to blacklist the broadcom driver. And the reason behind using the ndiswrapper this time through, was a lot more people seemed to be using it, so it should be easier to get support for.

 

Yeah, ndiswrapper is often used, but I tought mostly for chipsets that don't have Linux native support. I was lucky, I got 1 card that wouldn't work in any way, and 1 with native support...

I allways try to stay as native as possible, and emulate as least as possible...