So if I get this, right; Solidpup users can use the wl driver by manually blacklisting the b43 driver and manually loading the wl ... if the wl driver isn't loaded first. Please forgive my ignorance; I've been using straight wired LAN connection since... forever.

Not quite I'm afraid - the file "/root/Startup/00-broadcom-sta.sh" which I think comes from piratesmack's original pet is pretty heavy handed and circumvents the module loading system completely and force loads wl no matter what - it should really only be there if a need for the wl driver has been identified.

There are therefore 3 problems with your current build:
1. the fight between b43 and wl on bootup which leads to (I think):
2. any connection created by wl is not persistent between boots
and 3. eth% is created instead of wlan%

However, I have success to report - yippee

If I load an experimental pet that rerwin supplied recently for testing AFTER loading the delta pet and the multi-kernel pet from post #1 then I get a working, persistent through reboots connection on wlan0.

This has given me the impetus to discuss with rerwin incorporating the Experiment 8 logic into the Multi-kernel pet - I'll do that shortly hopefully.

Yeesss! That is good news, indeed. That was some terrific troubleshooting. Thanks for helping me out with this, Peebee.. broadcom wifi owners should be pleased.

Rerwin is now working on the official release of the Experiment 8 solution - when he finishes it there will be a new stripped back to basics multi-kernel pet which just installs the driver. I'll test the result on solidpup when its available. Thanks for giving the impetus to get this sorted. The aim will then be to get the Rerwin pet accepted for inclusion in woof so that all new woof based pups will have it built in.

This means that new woof based pups from now on will come ready equipped with rerwin's pup_event_backend_modprobe with extended preference processing

At the same time Barry has also decided to move the various "firmware" packages out into separate pets which pup builders will need to include in their pup builds. (although the theory is they can be "retrofitted" if the builders forget them or choose not to include them).

In preparation, I will shortly rearrange post #1 to make the rerwin_woof_fixes-delta-3f method the "preferred" one.

Now what EXACTLY do I need to integrate these into their respective builds at build time? I will ship with wl in final so might as well get it in to the next and hopefully final beta for a bit of testing. I have settled on these kernels unless of course their is some major issue with them. I hope not, that is why I have been following the LTS branches.

Now what EXACTLY do I need to integrate these into their respective builds at build time? I will ship with wl in final so might as well get it in to the next and hopefully final beta for a bit of testing. I have settled on these kernels unless of course their is some major issue with them. I hope not, that is why I have been following the LTS branches.

Cheers

Hi Mick

Should I construct 2 pets just for you 2* 1MB

Or 1 pet with drivers for both kernels? (2MB+)

Or....

Do you foresee the wl driver itself being included in the iso (its 1MB), or will the pet be available in the repository?

There are various ways we could go - I'm happy to go whichever you want.

Barry for precise has chosen to go with a specialised pet built into the iso. He could have gone with delta's built-in and the multi-kernel pet in the repository....but didn't.

My feeling is that having 1 multi-kernel pet is the most flexible...

My aim for the "official" puppies is that the one multi-kernel pet will have the delta files included - so if you've fixed on the kernels now I can put the slacko deltas into the pet.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum