Puppy Linux Discussion Forum

A rebuild of BionicPup32 on GitHub thereby including updates to:
Woof-CE
Kernel - now 4.19.x and firmware
Ubuntu components
Puppy utilities
Some apps

= Some minor changes in behaviour compared to 'original' BionicPup32

Get the latest version from GitHub Actions: https://github.com/peabee/releases/rele ... anded=true

Hello.

I tried this version.
I see some messages which I usually don't see while it is booting.

The "network" icon is not displayed in the tray. And the "ime" icon is not, either. The ime (scim) is enabled as X starts, but the icon does not appear.

The toolbar of scim appears when I press the key to trigger it, and I can input Japanese. But it is inconvenient not to have the "ime" icon in the tray.

By the way, is this version intended to replace Bionicpup32 8.0, which is an official puppy, in the future?

thinkpadfreak wrote: ↑Sun Jan 01, 2023 8:24 am

Hello.

I tried this version.
I see some messages which I usually don't see while it is booting.

The "network" icon is not displayed in the tray. And the "ime" icon is not, either. The ime (scim) is enabled as X starts, but the icon does not appear.

The toolbar of scim appears when I press the key to trigger it, and I can input Japanese. But it is inconvenient not to have the "ime" icon in the tray.

By the way, is this version intended to replace Bionicpup32 8.0, which is an official puppy, in the future?

1. yes - that seems to be a consequence of using the Woof-CE kernel-kit 5.10 kernel which is based on a Debian configuration - other Pups also have messages but BionicPup32 seems to have more than most!! @dimkr ?

2. I will investigate the network icon when I have time. The scim icon may have similar causes.

3. Maybe - but not yet. It came about as a result of getting the Woof-CE build recipes up-to-date (and actually working).

peebee wrote: ↑Sun Jan 01, 2023 10:53 am

that seems to be a consequence of using the Woof-CE kernel-kit 5.10 kernel which is based on a Debian configuration

That also happens with 5.4.x and 5.15.x, so that's very unlikely. Silencing this harmless error is not my top priority at the moment, sorry.

netmon_wce was segfaulting........ fixed by turning it into a Woof-CE petbuild

+1 .iso uploaded

also small xdelta to convert just the puppy .sfs (renames needed): https://sourceforge.net/projects/zestyp ... a/download

scim / ime may also be segfaulting - try running the startup script in a terminal.

With this being a 32bit Puppy.

Needed for very old computers that can only use 32bit operating systems.

Are you sure a series 5 kernel will still have support for the older hardware?

Example:

Torvalds is now considering removing the venerable 486, writing: “We got rid of i386 support back in 2012. Maybe it's time to get rid of i486 support in 2022?”

bigpup wrote: ↑Sun Jan 01, 2023 3:03 pm

With this being a 32bit Puppy.

Needed for very old computers that can only use 32bit operating systems.

Are you sure a series 5 kernel will still have support for the older hardware?

Example:

Torvalds is now considering removing the venerable 486, writing: “We got rid of i386 support back in 2012. Maybe it's time to get rid of i486 support in 2022?”

Can be built with any kernel...... Woof-CE kernel kit are easiest - 4.19 is only non-5:

https://github.com/puppylinux-woof-CE/w ... el-kit.yml

kernel-kit-output-4.19.x-x86
223 MB
Delete artifact kernel-kit-output-4.19.x-x86
kernel-kit-output-4.19.x-x86_64
226 MB
Delete artifact kernel-kit-output-4.19.x-x86_64
kernel-kit-output-5.10.x-x86
272 MB
Delete artifact kernel-kit-output-5.10.x-x86
kernel-kit-output-5.10.x-x86_64
284 MB
Delete artifact kernel-kit-output-5.10.x-x86_64
kernel-kit-output-5.15.x-x86
293 MB
Delete artifact kernel-kit-output-5.15.x-x86
kernel-kit-output-5.15.x-x86_64
306 MB
Delete artifact kernel-kit-output-5.15.x-x86_64
kernel-kit-output-5.4.x-x86
236 MB
Delete artifact kernel-kit-output-5.4.x-x86
kernel-kit-output-5.4.x-x86_64
242 MB

You do understand I am talking about the kernel you are releasing the version using.

I think you need to keep it a series 4 kernel.

What you offer above, is more for very new computers, that people want to use a 32bit Puppy on.
A series 5 kernel is probably needed to support the newer hardware.

peebee wrote: ↑Sun Jan 01, 2023 2:32 pm

scim / ime may also be segfaulting - try running the startup script in a terminal.

You guessed right. I confirmed it by way of dmesg command. Thanks.

is there a good reasonvwhy i can't download a 32bit puppy iso from fossapup64-9.5? i want it for another pc.

boof wrote: ↑Wed Jan 11, 2023 4:31 am

is there a good reasonvwhy i can't download a 32bit puppy iso from fossapup64-9.5? i want it for another pc.

viewtopic.php?p=128#p128 or you can even go newer and download jammy viewtopic.php?p=55564#p55564 or even kinetic viewtopic.php?p=69985#p69985.

boof wrote: ↑Wed Jan 11, 2023 4:31 am

is there a good reasonvwhy i can't download a 32bit puppy iso from fossapup64-9.5? i want it for another pc.

Sorry - not enough info - you need to explain your problem better - is this specific to just this iso?? Or is it a SourceForge issue?

New version from: https://github.com/peabee/releases/releases/

Latest version 17-Feb from: https://github.com/peabee/releases/releases/ (scroll down page - click Assets)

Just dl'd it. But, does this mean it is NOT a replacement for a Delta to BionicPup32NG-8.1+1 ? Thank you.

tosim wrote: ↑Sun Feb 19, 2023 6:01 pm

Just dl'd it. But, does this mean it is NOT a replacement for a Delta to BionicPup32NG-8.1+1 ? Thank you.

It's a full new .iso built and stored on Github.
Not many changes

@peebee Thank you.

Hi,
For Run yagf_0.9.5-1_i386.deb yagf on sourceforge
need libQtGui.so.4. (cannot open shared)

(assembled fromTahrPuppy32)