Broadcom 4318 driver with ndiswrapper do not work anymore

I experience the same problem with NDISWRAPPER and a Netgear WG511 v2. It worked just fine in dapper.

yup, same here. if you look at 'dmesg' output, it says, "can not initialize the device using windows driver". this worked fine in Dapper, and still works in other distros (at least Suse). i had to switch for the time being.

Please use attachments in the future. Can anyone please try this in the latest development release of Ubuntu (Feisty)?

In comparsion to dapper, Edgy will always try to load bcm43xx driver when your wireless-device has a broadcom-chip. You'll need to blacklist bcm43xx driver, additionally you may need to add ndiswrapper to /etc/modules. I used to run wifi-radar, which loaded ndiswrapper automatically after blacklisting bcm43xx. While Edgy-Kernel provides a really buggy version of bcm43xx (keyboard-lockups etc.), in Feisty everything works very well with the native driver.

ndiswrapper+wpasupplicant stopped working for me since Feisty. I don't know if ndiswrapper or wpasupplicant is defect.

$ ndiswrapper -v
utils Error: no version specified!
driver version: 1.38
vermagic: 2.6.20-15-generic SMP mod_unload 586

$ lspci
(...)
02:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
(...)

$ dmesg
[ 30.101521] ndiswrapper version 1.38 loaded (preempt=no,smp=yes)
[ 30.203492] ndiswrapper: driver bcmwl5a (Broadcom,12/22/2004, 3.100.46.0) loaded
[ 30.203775] ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 22
[ 30.212061] ndiswrapper: using IRQ 22
[ 30.978894] wlan0: ethernet device 00:14:a5:xx:xx:xx using NDIS driver: bcmwl5a, version: 0x3642e00, NDIS version: 0x501, vendor: '', 14E4:4318.5.conf
[ 30.978936] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[ 31.112767] usbcore: registered new interface driver ndiswrapper
[ 31.187930] ndiswrapper: changing interface name from 'wlan0' to 'eth1'

Please test with hardy with the latest kernel 2.6.24-7. If it works we can close this bug.

No response in 5 months. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!