(old)Puppy Linux Discussion Forum

peebee wrote:Should I construct 2 pets just for you..

I want to include it in the iso, so 2 separate pets will be preferred I think

Thanks

01micko wrote:

peebee wrote:Should I construct 2 pets just for you..

I want to include it in the iso, so 2 separate pets will be preferred I think

Thanks

Sent by PM....

Tested - work...

Cheers
Peter

Update:

Precise 5.4.2 k3.2.29 (the pae version) from BarryK now has the wl driver built-in to the iso.

(n.b. Retro-Precise 5.4.2 k3.2.32 nopae still requires the add-on pet in post #1)

Both Slacko 5.4 k3.2.33-4g & k3.4.17-PAE from 01micko also have the wl driver built-in to the isos.

Upup-Precise 54X4 k3.2.29 from pemasu comes similarly equipped OOTB.

Cheers
peebee

[EDIT]This post is already out of date as 01micko has uploaded the next testing version 5.4.0.3 in which he has reverted to the 5.4 kernels and therefore the wl driver is included in the iso.

I'll leave it here in case further 5.4.1 Beta's use the 3.4.28-PAE kernel.
[/EDIT]

I haven't needed to post delta pets for some time as most recent new puppies have the Broadcom wl driver built in to the iso.....

01micko has released Slacko 5.4.0.2 as an 5.4.1 Beta which doesn't include the wl driver....

The delta file for Slacko with kernel 3.4.28-PAE is attached in case anybody need to install with wl driver....

Cheers
peebee

Here is the delta file for Precise 5.5 beta with kernel 3.8.0

Just load this followed by the multi-kernel pet from post #1 and reboot

[edit]I've made the multi-kernel driver a dependency.....from download #7[/edit]

Here is the delta file for Racy 5.5 with kernel 3.0.66

Just load this followed by the multi-kernel pet from post #1 and reboot

[edit]I've made the multi-kernel driver a dependency.....from download #5[/edit]

Hi Peebee, i'm about to build what I hope is the final beta for mage2.

I was wondering that since there is no change to the kernel or associated components, is there a need to get a new delta pet or will it be ok to use the earlier one?

I do intend having it already built into the iso.

thanks

scsijon wrote:Hi Peebee, i'm about to build what I hope is the final beta for mage2.

I was wondering that since there is no change to the kernel or associated components, is there a need to get a new delta pet or will it be ok to use the earlier one?

I do intend having it already built into the iso.

thanks

Hi scsijon

The latest mage2 delta is dated 10 sept 12 for k3.3.8-mage2-p64gsw-i586 and is attached - as long as the kernel is still exactly the same including the name then it will work to generate the correct wl.ko (as long as you have xdelta3 in your build).

Are you using the latest woof2? If so all should be fine as BK has built all the necessary support files produced by rerwin in.

Cheers
peebee

@peebee yes, thanks and good. So any problem is mine! Great to know.

Here is the delta file for PHATSlacko with kernel 3.8.2.

Load this followed by the multi-kernel pet from post #1

Attached are the delta files for:

• ThinSlacko 5.5.01 with kernel 3.8.5.0 (non-PAE)
  
  and
  
  PhatSlacko 5.5.02 with kernel 3.8.5.1 (PAE)

Load the delta then load the multi-kernel pet from post #1 and reboot

Delta can then be unloaded if desired

Cheers
peebee

Hi there, I want to download "post #1".pet files but always shows "An Error Occurred". Do you know any other links? (I have a problem to connect to wifi with broadcom wifi adaptor...)

jayjays wrote:Hi there, I want to download "post #1".pet files but always shows "An Error Occurred". Do you know any other links? (I have a problem to connect to wifi with broadcom wifi adaptor...)

Looks like it's a forum error.....

I've uploaded the multi-kernel pet here

The smaller delta files seem to download OK still.

Which Puppy version do you have the problem with?

Cheers
PeeBee

Thanks, PeeBee. I've loaded and reboot but... nothing changed.

Puppy version: 528 jp (Japanese Version)
Machine: eMachines eM350 model NAV51
Wife adapter: Broadcom 801.11 Network Adapter

Would appreciate if you could give any hints.

Cheers

jayjays

jayjays wrote:Thanks, PeeBee. I've loaded and reboot but... nothing changed.

Puppy version: 528 jp (Japanese Version)
Machine: eMachines eM350 model NAV51
Wife adapter: Broadcom 801.11 Network Adapter

Would appreciate if you could give any hints.

Cheers

jayjays

Hi jayjays

Derivatives based on lupu528 need a pet with extra logic as lupu528 doesn't contain the logic that is now built-in to more up-to-date puppies.

I've uploaded the pet with the added logic for lupu528 here.

Cheers
PeeBee

Thanks, PeeBee. My Japanese pal on another BBS showed the link of pet file and it has fixed the problem.

http://www.murga-linux.com/puppy/viewto ... 43c14c88bf

Thanks for your concerning and help. Much appreciated.

Cheers

jayjays

jayjays wrote:Thanks, PeeBee. My Japanese pal on another BBS showed the link of pet file and it has fixed the problem.

http://www.murga-linux.com/puppy/viewto ... 43c14c88bf

Thanks for your concerning and help. Much appreciated.

Cheers

jayjays

That is the older 5.6.48.36 version of the driver - pleased to hear it worked for you.

Failure on Lucid 528-005. On the recent distros the driver wl works well for the public wifi.
However thanks to you helping us to improve Lucid 528, which is moreover a nice distro.
Sure i can work with eth0. But i have a laptop Medion P7624. I'd like to do not have a chain in the leg at home. The electric cable is fixed yonder on my chandelier so that I am not caught the feet inside.
It's not a disaster...
Bonne journée.

OK this seems as good a place as any to ask for help.

My broadcom driver is :

10:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01

2.6.33.2 SMP mod_unload modversions 486

I'm using lupu_525 on a full hard disk install.
Have been doing so for a while with no problems, when I set it up I installed the broadcom-5.10.27.14-k2.6.25.16.pet as I did with all previous puppies and all was fine.

Today I tried running precise 5.5 on a live CD and the weird thing is that it
sees my neighbours' wi-fi networks but not my own! No clue atall.
Some neighbours are using WPA2, just like me.

When I go back to my full install, everything is fine again.

Can anyone suggest why this might be and what I need to install/uninstall?


EDIT: I scanned this thread and installed the closest pet I could find (Precise 5.2 version) but I get an error message "incorrect kernel for this data".

redandwhitestripes wrote:OK this seems as good a place as any to ask for help.

My broadcom driver is :

10:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01

2.6.33.2 SMP mod_unload modversions 486

I'm using lupu_525 on a full hard disk install.
Have been doing so for a while wtth no problems, when I set it up I installed the broadcom-5.10.27.14-k2.6.25.16.pet as I did with all previous puppies and all was fine.

Today I tried running precise 5.5 on a live CD and the weird thing is that it
sees my neighbours' wi-fi networks but not my own! No clue atall.
Some neighbours are using WPA2, just like me.

When I go back to my full install, everything is fine again.

Can anyone suggest why this might be and what I need to install/uninstall?


EDIT: I scanned this thread and installed the closest pet I could find (Precise 5.2 version) but I get an error message "incorrect kernel for this data".

Hi there

Seen you've had some advice already over on the Precise 5.5 thread.

Precise 5.5 contains all the logic and drivers - b43 and wl - to support Broadcom wifi - you don't need to install any additional pets.

The fact that you can see neighbours signals indicates that the Puppy part of the system is behaving correctly.

Do you think your router might be set to hidden SSID? Have you tried typing the SSID explicitly into whichever Network Manager you are using?

Have you tried all 3 available Network Managers - SNS, Frisbee and NetWiz? If not find the Internet Connection Wizard in the Setup menu and try Frisbee.

If that doesn't work I recommend that you try going through the manual methods described in How to configure wifi from the commandline to see where things are going wrong.

Otherwise, post the evidence produced by running the pdiag command to the forum in the above thread.

Hope this helps
Cheers
PeeBee