Puppy Linux Discussion Forum

If you want to see something run FAST, put an NVME module in a USB3 enclosure and use it as an external hard drive.

Get the package libva-dev.

I have posted here PeasyPDF v5.2 for gtk3. Be aware that this package has dependencies that are specific to the Starter Kit.

mikeslr wrote: ↑Mon Apr 29, 2024 2:40 pm

Thanks bigpup for discovering it,

Localsend was first identified by gychang.

rockedge wrote: ↑Mon Apr 29, 2024 2:38 pm

Where is the not obsolete version? If it is to be an included application in future Puppy Linux variants it needs to be accessible for a woof-CE build run from a reachable repository.

It's in the Starter Kit project, available through Fred's repo. But that version is not Puppy-compatible.

MochiMoppel wrote: ↑Mon Apr 29, 2024 8:02 am

Did this ever work?

Yes. But years ago, busybox dc changed its syntax and PeasyPDF was updated accordingly. Puppy continues to use an obsolete version.

No reply. Message deleted.

Removed. See below for another kernel upgrade.

dimkr wrote: ↑Sat Sep 23, 2023 7:33 am

https://gitlab.freedesktop.org/pipewire ... issues/166

Can any mainstream Linux do this OOTB? ie. automatically set HDMI as the default audio output when the HDMI video is active?

Clarity wrote: ↑Tue Sep 19, 2023 2:01 pm

PS: PLEASE, Please, please post ANY shortcomings or issues you find in booting using this technology. This helps all of us.

How much RAM did your client machines have when booting Fatdog over PXE?

PeasyPDF is updated here and PeasyScale here.

This is PeasyPDF updated to be gtk3 compatible. It uses the new xdialog3 package which is posted above with PeasyMP3.

Just to be clear, a "Filter failed" error would be caused by using the wrong driver, NOT by a hardware problem like a blocked sensor.

The Daedalus k6.1.0-9-amd64 wifi driver pack is here.

It contains the rtl 88x2bu driver which supports the obda:b812 device. In your PeasyWifi Config, make sure to set "DRIVER=nl80211".

According to my notes, the old protocol "DRIVER=wext" no longer works with this device.

ozsouth wrote: ↑Fri Sep 01, 2023 12:58 pm

rebuilding it is hard when you can't easily find what is missing.

If you have a system with correct package management, you don't need to go looking for missing stuff.

ISObooter3 updated with an option that automatically adds the new menu entries to the grub.cfg files. See page 1.

ISObooter3 updated with an option that automatically adds the new menu entries to the grub.cfg files. See above.

rcrsn51 wrote: ↑Sun Aug 27, 2023 1:37 pm

Disconnect the old drives and get the machine booting off the new drive.

Have you done this?

Florian_13 wrote: ↑Sat Aug 26, 2023 6:45 pm

the name is: bionicpup32-19.03-230815.iso

I looked at this ISO and it appears to have LESS b43 firmware than previous versions. A member of the Bionic team needs to look at this. There may be a separate package of b43 firmware somewhere on the forum.

Disconnect the old drives and get the machine booting off the new drive.

Florian_13 wrote: ↑Fri Aug 25, 2023 5:40 pm

I am using bionicpup32

Please state the exact version and how you installed it.

The package bionicpup32-8.0-uefi.iso has an fdrv.sfs file that appears to contain the required firmware for your BCM4318.

Have you included this file in your install?

This machine sounds like a desktop/tower with multiple internal drives. Is sda the new drive?

On the other drives, rename any grub.cfg files so GRUB will ignore them.

Reboot.