WL and B44 Not Properly Configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt | ||
Hardy |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Undecided
|
Martin Pitt | ||
Jaunty |
Fix Released
|
Undecided
|
Martin Pitt |
Bug Description
I originally reported this issue as part of bug #263097, but was asked to file a new bug.
I am using the latest Intrepid on a Dell XPS M1210 laptop with a Broadcom BCM4328 wifi.
In my case, B44 was being loaded (and thus ssd) prior to jockey attempting to utilize "wl". B44 was being loaded dur to my ethernet adapter. However, because ssd was loaded prior to wl, my wireless networking adapter (wlan0) never showed up.
I had to work around this problem by forcing the loading of wl prior to b44 and ssd -- which I did via the following command:
echo -e '#ssb workaround, added `date`\ninstall wl modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install wl $CMDLINE_OPTS; modprobe b44;' | sudo tee -a /etc/modprobe.d/wl
At this point, both my ethernet adapter and my wireless adapter are both working just fine -- at the same time.
Thanks; I discussed that with Mario, and he suggested something similar. Either we keep the blacklisting of b43/ssb and install such a modprobe.d file if b44 is available, or we use an rmmod/modprobe script like you proposed.
I just generally try to avoid rmmod, since at least in the past it was not generally safe, and also leads to unwanted effects like NetworkManager disconnecting/ reconnecting.