Puppy Linux Discussion Forum

[mistfire]

@Terry H

Please place this file attached on /usr/sbin to fix the issue. Dont forget to set the permission by typing this command

[Terry H]

Saves now working as expected with updated snapmergepuppy. All working well now.

Thank you.

[mistfire]

TazPuppy 5.0 beta 52

Changes:
* Smaller initrd. (1.4Mb compressed, 3.3Mb expanded)
* Improved write caching (PUPMODE 3, 7, and 13)
* Improved boot and shutdown process
* Some bugfixes

Download: https://drive.google.com/open?id=11EW9gxfp2ts0EQ7Mi5YL79Vjbs698XEH
MD5 Checksum: eee29935e68cf8f1a3c731f73fd74648

Build kit: https://drive.google.com/open?id=1GshmJ8093rQaLLhTt7TkoBa1dGMbrG7s

[Terry H]

Tested beta 52.

Initial test was to test upgrading existing save folder. This was done after deleting the previously provided snapmergepuppy from the save folder. Saves and reboots working OK.

I then did a clean install (pfix=ram). Save and reboot working OK. All other software is OK

There is on observation, which may be intentional. On initial save when creating save folder, there is no option provided to add a chosen suffix to the save folder name. The save folder creation does however create unique names adding -n to the name.

Thanks mistfire, looking really good now.

[mistfire]

I found something weird. the shutdownconfig script works fine without problems on previous releases of TazPuppy then recently the dialog inputbox suddenly don't work on commandline upon shutdown process while the menubox works fine. However when it launched from commandline shell the dialog and gui version of shutdownconfig works.

[mistfire]

On my latest experiment the GUI version of shutdownconfig is now working on first shutdown if Xorg was running. Also GUI version of Save Session messagebox upon shutdown for PUPMODE 3/7/13 is added.

The only problem we need to solve was the commandline version where the dialog was buggy. But shutdownconfig works nicely if it was launched from logged in shell.

[mistfire]

TazPuppy 5.0 Beta 53 released

Changes:
* Build from recent Slitaz release
* First shutdown dialog now runs on both GUI mode and commandline mode
* Dialog asking to save session for PUPMODE 3/7/13 now runs on both GUI and commandline mode
* Fixed bugs on shutdown script
* More bugfixes

Download:https://drive.google.com/open?id=18pg3dWctCPmtVCLBhngTBLGVeUqczl1b
MD5 Checksum: 382026ee90fb17206741d475f0630750

Build kit: https://drive.google.com/open?id=1aMGyB9y4CBFvr55h5b4xtutho9Vl9nlx

[Terry H]

New frugal install of Beta 53 on Sandisk USB Flash drive., on Dell Latitude 3350 Laptop with Core i5-5200U 8GB Ram Intel 7265 AC wifi card.

I first tested first shutdown to check save file/folder creation, including adding suffix to name. All OK, with all changes made contained in save folder created. I then booted with pfix=ram and checked first save against reboot. Save folder creation OK. with all changes being saved.

[Terry H]

In this lot of testing I have encountered an issue with the fdrv. I normally don't use the fdrv. I generally just manually load my own firmware and do a modprobe to load it and have it included in the save folder. for this testing I just used the fdrv provided, which encountered strange behaviour.

I found thet the iwlwifi-7265D*.ucode wasn't loaded, when checking the /lib/firmware there was only 1 directory inside NXP-linux-firmware-67b7579. Checking this directory showed that all the linux firmware was contained in this directory.

I viewed the content of the fdrv, which does not contain such a directory name. I did notice another issue with the supplied fdrv with in the tazpuppy.iso. With in the /lib/firmware directory there is another nested directory firmware which contains all the firmware. This is different to the fdrv contained in other versions of puppy.

[mistfire]

On my latest experiment, I successfully upgraded xorg and mesa on TazPuppy the problem was mesa requires llvm libs which makes tazpup sfs larger by 6Mb+

[didit]

is there any chance to make hardware acceleration work in browser?
cpu load 90% while on windows7 30% on the same web sites/apps

Problems Detected
GPU process was unable to boot: GPU process launch failed.
Disabled Features: all

[mistfire]

TazPuppy 5.0 beta 54 released

Changes:
* Xorg version 1.20.3 (with glamor acceleration)
* Mesa 17.3.4 (for supporting newer graphics card)
* Improved save session manager for PUPMODE 3/7/13
* Improved xorg auto configuration

Download: https://drive.google.com/open?id=1WyCnIcRkFjTDmBWyvzf_6An3cYnRz9vA
MD5 Checksum: 62799e075f563f5e7f802518c4138bd9

Build kit: https://drive.google.com/open?id=192ujWXSvWacBXNA6vUSc4d0vLqQfF7_Q

NOTICE: On this version, don't update xorg drivers when upgrading packages.

[Terry H]

Frugal install to USB flash drive. As a clean install saved with new save folder. All seems OK.

For information only :
This version won't boot to X desktop using any previously created save folders, tried with 3 different save folders. Only boots to CLI. I assume it is due to xorg changes.

[TiredPup]

[didit]