Public bug reported:

My laptop has a BCM4328 draft-N wireless chipset that requires
ndiswrapper.  This broke between 2.6.24-10-generic and 2.6.24-11-generic
because the ssb module now grabs the device before ndiswrapper.

$ lspci -nn | grep 4328
03:00.0 Network controller [0280]: Broadcom Corporation BCM4328 802.11a/b/g/n 
[14e4:4328] (rev 01)
$ ndiswrapper -l
bcmwl5 : driver installed
        device (14E4:4328) present (alternate driver: ssb)
$ diff -u /lib/modules/2.6.24-{10,11}-generic/modules.pcimap
…
+ssb                  0x000014e4 0x00004328 0xffffffff 0xffffffff 0x00000000 
0x00000000 0x0

Blacklisting ssb allows ndiswrapper to work again.

(Are free drivers supposed to actually support the 4328 yet?  This would
make me happy, but I didn’t think they do.)

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  My laptop has a BCM4328 draft-N wireless chipset that requires
  ndiswrapper.  This broke between 2.6.24-10-generic and 2.6.24-11-generic
  because the ssb module now grabs the device before ndiswrapper.
  
  $ lspci -nn | grep 4328
  03:00.0 Network controller [0280]: Broadcom Corporation BCM4328 802.11a/b/g/n 
[14e4:4328] (rev 01)
  $ ndiswrapper -l
  bcmwl5 : driver installed
        device (14E4:4328) present (alternate driver: ssb)
- $ diff -u 2.6.24-{10,11}-generic/modules.pcimap
+ $ diff -u /lib/modules/2.6.24-{10,11}-generic/modules.pcimap
+ …
  +ssb                  0x000014e4 0x00004328 0xffffffff 0xffffffff 0x00000000 
0x00000000 0x0
  
  Blacklisting ssb allows ndiswrapper to work again.
  
  (Are free drivers supposed to actually support the 4328 yet?  This would
  make me happy, but I didn’t think they do.)

-- 
ssb module breaks BCM4328 with ndiswrapper (regression from 2.6.24-10)
https://bugs.launchpad.net/bugs/197558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to