Ubuntu modules

[sjoeboo at sjoeboo.com (Matthew Nicholson)]

I would go into /etc/modprobe.d/blacklist anything in there "shouldn't"
be loaded at boot.  

since the bcm43xx modules attempting to load at boot, I assume we're
talking about the 6.06 (dapper) release. in which case, you can use the
bcm43xx module, you just need the firmware (aka, the same windows driver
files that ndiswrapper needs, sigh). you can either compile, or find a
copy of fwcutter (also called bcm43xx-fwcutter, or something of the
like) you use this to extract the firmware file from teh windows .sys
file. They then go in /lib/firmware/`uname -r`/

the bcm43xx modules are getting better. ndiswrapper is...okay. i
honestly flip back and forth on my dell laptop and can't decide which is
more stable. as for my powerbook, bcm43xx is the only way to go, and it
works fairly well.

i hope this helped.


On Thu, 2006-05-25 at 11:17 -0400, Jerry Feldman wrote:
> Just a followup since I don't know Ubuntu and I'm heling someone remotely.
> 
> The problem is that he has a broadcom wireless. He installed ndiswrapper and 
> the Windows driver successfully, BUT upon boot, Ubuntu tries to load the 
> bcm43xx kernel module before it loads the ndiswrapper kernel module 
> requiring the user to rmmod bcm43xx. 
> 
> Normally, I would simply comment out the line in /etc/modprobe.conf, but 
> there is no modprobe.conf file on his system. Further, he certainlay has a 
> modprobe.d directory containing ndiswrapper, and ndiswrapper does get 
> loaded. When we unload bcm43xx (with rmmod or modprobe -r) then his 
> wireless works fine. 
> 
> My hack was to simply go into /lib/modules/<kernel>/... and rename the 
> bcm43xx.ko so it can't load, but that is not a good hack. I'm sure if I had 
> an ubuntu (dapper) system or a 2.6 kernel debian available I could easily 
> figure it out, but I have neither available to look at.
-- 
Matthew Nicholson <sjoeboo at sjoeboo.com>
sjoeboo.com