[Bug 188621] Re: Conflict between Ndiswrapper and ssb

[Jason Wigg]

Agreed, I tend to recommend adding scripts to /etc/rc.local, as it is a
touch simpler, however creating a new init script is equally valid. This
bug is due to the initramd set up that Ubuntu uses, as explained in my
earlier post. For update-initramfs to actually do anything, it needs a
change in config file so that it knows to do something.

For a cleaner fix (ie. removing the bug, instead of an ugly workaround),
edit your /etc/initramfs-tools/initramfs.conf and ensure the BOOT
variable is set to local, and then change the DEVICE variable from eth0
to lo. The variable is actually irrelevant unless a network boot is
occurring, in which case networking would need to be available
immediately. Once you've done that, run update-initramfs -u, remove the
junk you've put in /etc/rc.local, blacklist b43 and b44 (b43 should be
blacklisted anyway, you shouldn't be removing it in /etc/rc.local, as it
should never be loaded), and add ndiswrapper to /etc/modules. Then
you'll get a proper clean boot. b44 may not be necessary to blacklist,
it may get auto-loaded after ndiswrapper anyway, and you'll need to load
it if you need to bring up your wired interface, but that should happen
automatically.

The best option by far is to compile your own kernel, and compile
b44/ssb as a part of the kernel rather than modules and don't compile
b43 at all. Then none of this is an issue.

-- 
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to ndiswrapper in ubuntu.