These firmware packages are kernel version spesific. The one 01micko posted a link to rpm which I packaged as pet is meant to kernel 3.2.X and and then there is firmware package for older kernels.

So...I wouldnt make firmware update request for woof....since Barry posted that he wants to stick with 3.0.17 due to unionfs support for it.
01micko and I have used aufs with our 3.1.X and 3.2.X experiments...so there is no kernel version restriction like with unionfs.

What is the practical difference, I dont know...
But of course you can experiment.

I just can speculate, that there are newer supported hw with newer kernel...so there is need for new firmware package and maybe due to b43 driver update...not all older firmwares does work optimally, but as I said....just my speculation.

Oh...I have forgotten to post my test feelings. Nothing much to tell. My troublesome touchpad works like charm, wlan connection with no problem. Installing pets...extracting stuff with rox right click pet stuff....downloaded latest woof2 commit, updated my building platform...posting....using...all works what I have needed.

drblock2, good you found a work-around, kernel source is in the main post.

mavrothal, wl is only compiled for Slacko with 2.6.37 (MAIN), you could try it. I can do it for later kernels, already have the latest source.

lol a@ u pemasu

Quote:

...Mostly harmless....

. Also I have the woof patch ready, just doing a build for sanity check. Compiled 3.2.2 too in the hope it solves Jim1911's logitech wireless mouse. Only manual step is to insert the b43 firmware in the kernel pet so that will be a sanity check too making sure it overwrites the woof firmware._________________Woof Mailing List | keep the faith |

Just testing 3.2.1 kernel, compiled in dpup. Seems to work. I think it is that symlink from 3.2.1-dpup to 3.2.1 in /lib/modules/ which gives hiccup for me at 3builddistro stage. It did when I last used Iguleders vanilla kernel kit.

But...thank you of this updated kernel kit. It didnt demand much editing. And it worked oob. Great stuff. Almos as good as chocolate.

Just testing 3.2.1 kernel, compiled in dpup. Seems to work. I think it is that symlink from 3.2.1-dpup to 3.2.1 in /lib/modules/ which gives hiccup for me at 3builddistro stage. It did when I last used Iguleders vanilla kernel kit.

But...thank you of this updated kernel kit. It didnt demand much editing. And it worked oob. Great stuff. Almos as good as chocolate.

I wonder why a symlink is needed? Perhaps ask Iguleder if it can be done without the symlink._________________http://bkhome.org/news/

After getting that rpm (from another site and on my other lappy) and finding how to un-rpm an rpm I had the contents of lib/firmware/b43. First try was with a pfix=ram start, then copy the firmware into the original spot. This did not bring up the wireless.

2nd try was also with a pfix=ram,

but this time renamed the original ././b43 to b43_old,

then copied the new one in.

Then in the network wizard unloaded the b43 module,

then reloaded it.

When I tried scanning for a wireless network the blue status light
came on, and then I was called to dinner so I shutdown with save.
After a normal boot the blue light came on and I was able to set up
the wireless in the usual way.

Thanks for all the work and knowledge - and straightforward advice.

So - steps are:
- get the right firmware files
- rename the old firmware files
- copy in the new ones
- unload the b43 module (has rwong firmware)
- reload the b43 module (now has right FW)
- configure wireless. "

"""""""""""""

Then I saw that lurker >> pemasu ....post his
b43-firmware-5.100.138.pet

""""""""""

A one time moment of knowledge came upon me.
Do a combo of the 2 fixes above.

So I renamed >> b43 to b43_old

in >> /lib >> /firmware

now unload the >> b43 module >>(which has the wrong firmware)

Go back to >>> /lib >> /firmware

and add a new folder b43....
you probably should have done it before....

Now load the >>> b43-firmware-5.100.138.pet
from the mighty >> pemasu

Look in your new b43 folder....there are all the new 117 firmware files

Use the network wizard...not simple network wizard

with the usual steps....and it's all go for Broadcom wireless.

Once again you 2....bloody brilliant.

micko....seamonkey works great.

::::::

Despite contrary advice...I'm going to test this in Saluki
and others.

Just testing 3.2.1 kernel, compiled in dpup. Seems to work. I think it is that symlink from 3.2.1-dpup to 3.2.1 in /lib/modules/ which gives hiccup for me at 3builddistro stage. It did when I last used Iguleders vanilla kernel kit.

But...thank you of this updated kernel kit. It didnt demand much editing. And it worked oob. Great stuff. Almos as good as chocolate.

I wonder why a symlink is needed? Perhaps ask Iguleder if it can be done without the symlink.

I don't know why it's there either.. I'm just going to delete it and forget the woof patch. Should still work ok.. although I wonder if it's there for the kernel source? I'll test that too.

Edit: Bummer.. the link is there for the kernel source.. and I discrded my patch! Easy enough though.

Barry, I put the symlink there for users who don't know about uname and want the exact kernel version - nothing more, nothing less. You can remove it - no harm done._________________My homepageMy GitHub profile