Ndiswrapper no longer works after upgrade to Dapper

Bug #41722 reported by inspired
6
Affects Status Importance Assigned to Milestone
ndiswrapper (Ubuntu)
New
Medium
Unassigned

Bug Description

I updated to Dapper tonight and when I rebooted my wireless network card was no longer working. I have an Fujitsu Siemens Amilo Pro laptop and I used to have to press Fn+F12 when Ubuntu began booting to enable the Broadcom wireless card and a led would light up. The led no longer lights up, although ndiswrapper reports that the driver is installed and the hardware is present. I also noticed that the interface name has changed from wlan0 to eth1.

I am using ndiswrapper 1.11 from the ndiswrapper's sourceforge page and it worked just fine before I upgraded to Dapper. I use the bcmwl5 driver and my kernel version is 2.6.15-21-686 from the Dapper apt repository.

I see that others have experienced problems with wireless cards after upgrading as well, but I can't find any conclusion.

Revision history for this message
inspired (mikael-upnet) wrote :

Sorry. Found the following URL and got it working again with ndiswrapper. I suppose the bcm43xx module is better and supports WPA so I will try it later:
https://wiki.ubuntu.com/WifiDocs/Driver/Broadcom43xx

Revision history for this message
Olivier Bilodeau (plaxx) wrote :

I experienced similar problem while upgrading to dapper's release candidate.

I'll attempt to clarify the issue:

Hotplug finds a more suitable driver for your wireless card so it loads it before ndiswrapper but the driver is buggy and the card doesn't work with it.

The fix is easy: rmmod ndiswrapper and prism54 (in my case) and modprobe ndiswrapper. Then to prevent it from re-occuring, you add prism54 in /etc/modprobe.d/blacklist

This is annoying and not intuitive for new linux users I guess but I can't really see an easy fix for this.

for info: I have a WG511 "Made in China" (v3) pcmcia
https://wiki.ubuntu.com/WifiDocs/Device/NetgearWG511andNdiswrapper

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

This seems to be a duplicate of bug 42067, please reopen if this is not the case.

Revision history for this message
Olivier Bilodeau (plaxx) wrote :

Well bug 42067 is a user error and the user did tried blacklisting it's buggy driver from start.

The thing that should be fixed regarding an upgrade to ubuntu dapper is that when ndiswrapper is installed some drivers with known problems should be blacklisted in /etc/modprobe.d/blacklist.

But I'm just trying to be "upgrading users" friendly here and I can't find a way to properly do it.

Original reporter found a solution, everyone's happy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.