(old)Puppy Linux Discussion Forum

Posted: **Thu 23 Apr 2020, 09:59**

didit wrote:
mistfire wrote:@didit

Use frugal method to install TazPuppy without wiping a whole partition. Use save to folder if TazPuppy was installed on a Linux partition.
grub4dos doesnt work on the latest tazpuppy

Here is the fix. run this command on terminal

Code: Select all

sudo ln -sr /usr/bin/bootlace /usr/bin/bootlace.com

Posted: **Thu 23 Apr 2020, 10:00**

Terry H wrote:
mistfire wrote:To achieve PUPMODE 13 it requires large ram, the computer has a battery, and the battery was in good health.
It's a Dell Latitude 3350 Laptop with i5-5200U CPU with 8GB RAM also 8GB Swap on internal SSD, the battery is good (capacity is down a bit) . Earlier iterations of TazPuppy woud boot to PUPMODE 13 on this laptop.

Does the battery of your computer was detected by the kernel?

Posted: **Thu 23 Apr 2020, 21:11**

mistfire wrote: Does the battery of your computer was detected by the kernel?

Other than it appears in dmesg, I don't know how to tell.

Code: Select all

tux@TazPuppy:~$ dmesg|grep battery
ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
ACPI: Battery Slot [BAT0] (battery present)

I've done some testing on older tazpuppies, on Beta 35 with kernel 4.14.150 save2flash was OK. On Beta45 with 4.14.156 (which is same as current kernel) save2flash was OK. So it appears that between Beta 45 and Beta 50, something has changed on how PUPMODE is being set.

The dmesg output checking for battery was the same on all versions that I checked.

Posted: **Wed 29 Apr 2020, 22:14**

TazPuppy 5.0 beta 51 released

Changes:
* Improved initrd
* Improved init and shutdown process
* Revised login screen
* Missing bootlace.com in grub4dos config fixed
* Some bugfixes

Download: https://drive.google.com/open?id=1eKMgv ... 9Ve8b_Aj3V
MD5 Checksum: 353c64168bd7b43d297268eb7102c31b

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

Posted: **Wed 29 Apr 2020, 23:34**

So far just a quick test to check PUPMODE, it is now being set to 13,shutdown and save2flash now OK.

Thanks mistfire, will continue and set up and test further.

Edit: I spoke too soon. Nothing is being saved. Created new document in /home/tux/Documents. Added Application Launchers to Panel. None of these are being retained over Shutdown/Reboot. I have manually ran save2flash as tux and root, it appears to run. I've checked with changing save interval to 0 or +0. No changes as stated above are retained. I have done multiple shutdown and reboots.

Note: I created a symlink to palemoon in /usr/bin and added a palemoon.desktop to /usr/share/applications and added an icon. These changes have been retained. So, it appears that changes within /home/tux aren't being saved.

This as a new clean frugal install on USB Flash drive, with a new save folder.

Posted: **Thu 30 Apr 2020, 03:54**

@Terry H

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

Code: Select all

chmod +x /usr/sbin/snapmergepuppy

Posted: **Fri 01 May 2020, 01:22**

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

Thank you.

Posted: **Sun 03 May 2020, 13:39**

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=11EW9g ... Vjbs698XEH
MD5 Checksum: eee29935e68cf8f1a3c731f73fd74648

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

Posted: **Sun 03 May 2020, 17:39**

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.

Posted: **Mon 04 May 2020, 10:14**

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.

Posted: **Tue 05 May 2020, 21:51**

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.

Posted: **Sat 09 May 2020, 13:49**

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=18pg3d ... GVeUqczl1b
MD5 Checksum: 382026ee90fb17206741d475f0630750

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

Posted: **Tue 12 May 2020, 01:11**

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.

Posted: **Tue 12 May 2020, 01:33**

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.

Posted: **Fri 15 May 2020, 03:30**

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+

Posted: **Thu 21 May 2020, 06:39**

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

Posted: **Thu 21 May 2020, 23:32**

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=1WyCnI ... n3cYnRz9vA
MD5 Checksum: 62799e075f563f5e7f802518c4138bd9

Build kit: https://drive.google.com/open?id=192ujW ... 0vLqQfF7_Q

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

Posted: **Sat 23 May 2020, 01:05**

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.

Posted: **Sat 23 May 2020, 18:14**

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

Hardware acceleration does not work in linux for chromium based browsers.

Posted: **Sun 24 May 2020, 00:04**

TiredPup wrote:
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
Hardware acceleration does not work in linux for chromium based browsers.

i had hardware acceleration and webgl on chrome in puppy slacko

(old)Puppy Linux Discussion Forum

TazPuppy 5.0 rc2

PUPMODE=13 set correctly