@damNageHack
Thanks for the heads up, I saw this as well on Slashdot afew days ago.
When the source moves out of git, i.e. there is a stable release, then I'll gladly package it for Salix (unless anyone beats me to it
)
@zAchAry
Here what you need to know for testing.
1) You only need b43-fwcutter for compiling the b43-firmware package so unless I update it you don't need to uninstall it.
2) Once the b43 and ssb modules are loaded at boot they wont be unloaded unless you run
modprobe -v -r b43 ; modprobe -v -r ssb as root. So, uninstalling the b43-firmware package won't unload the modules.
3) There is now a
/etc/rc.d/rc.b43 script for loading and unloading the
b43 and
ssb kernel modules and unloading the conflicting
wl and
lib80211 modules associated with the
broadcom-sta package (this is the reverse in the
/etc/rc.broadcom-sta script).
I was previously blacklisting the conflicting
wl and
lib80211 modules in
/etc/modprobe.d/blacklist.conf and editing the
/etc/rc.d/rc.modules file to load the
b43 and
ssb modules on boot (still with me?). This is less flexible and generally not such a good idea, hence the new script and the splash of red on the first post!
4) You'll be happy to know all the red on the first post is about to go as I'm going to include the rm.broadcom.sh and a few tweaks in the next (and hopefully final) package (I can test this part myself).
5) Here's where the work comes in, I need you to test the
/etc/rc.d/rc.b43 script from the next package (release 2) which I'll hopefully post tonight.
Boot your computer, your wireless will probably already be working, then login as root on a terminal.
Run this to see if the b43 and ssb modules are loaded:
If you see something like this then they're loaded:
If you receive no output (and no wireless) then they're not.
From here on in you need to make sure the /etc/rc.b43 is doing it's job. There are four arguments
start,
stop,
restart,
status to be execute in the following fashion:
When you load a module you should see something like this (I'm using my rc.kvm script here):
Code: Select all
root[pwatk]# /etc/rc.d/rc.kvm start
/etc/rc.d/rc.kvm: /sbin/modprobe -v kvm:
insmod /lib/modules/2.6.33.4-smp/kernel/arch/x86/kvm/kvm.ko
/etc/rc.d/rc.kvm: /sbin/modprobe -v kvm_intel:
insmod /lib/modules/2.6.33.4-smp/kernel/arch/x86/kvm/kvm-intel.ko
If you run the same command twice you should also get a message saying the modules are already loaded or unloaded:
Code: Select all
root[pwatk]# /etc/rc.d/rc.kvm start
/etc/rc.d/rc.kvm: `kvm' module already loaded
/etc/rc.d/rc.kvm: `kvm_intel' module already loaded
Here's a few more examples:
The
restart (stop and start) argument:
Code: Select all
root[pwatk]# /etc/rc.d/rc.kvm restart
/etc/rc.d/rc.kvm: /sbin/modprobe -v -r kvm_intel:
rmmod /lib/modules/2.6.33.4-smp/kernel/arch/x86/kvm/kvm-intel.ko
rmmod /lib/modules/2.6.33.4-smp/kernel/arch/x86/kvm/kvm.ko
/etc/rc.d/rc.kvm: `kvm' module already unloaded
/etc/rc.d/rc.kvm: /sbin/modprobe -v kvm:
insmod /lib/modules/2.6.33.4-smp/kernel/arch/x86/kvm/kvm.ko
/etc/rc.d/rc.kvm: /sbin/modprobe -v kvm_intel:
insmod /lib/modules/2.6.33.4-smp/kernel/arch/x86/kvm/kvm-intel.ko
You'll notice the kvm module is already unloaded by unloading the kvm-intel module, this may also happen for the
ssb module when the
b43 module is unloaded and I'd like to know if it does.
The
status argument:
Code: Select all
root[pwatk]# /etc/rc.d/rc.kvm status
/etc/rc.d/rc.kvm: `kvm' module loaded
/etc/rc.d/rc.kvm: `kvm_intel' module loaded
If anything looks a miss or if your generally not sure then post it here and I'll either provide an answer or fix the problem.
Bottom line, if the modules are loaded you should be able to use your wireless and if they're not then you wont. This script should perform that function and give you feedback regarding the status of the modules concerned.
Thanks for your help as always and happy testing.
(I'll have a look into it again)