TazPuppy 5.0 rc2

[mistfire]

TazPuppy 5.0 Beta 49 released

Changes:
* Optimized boot process
* Improved package management
* Improved SFS module loading
* Improved system script

Download: https://drive.google.com/open?id=1g-bvK ... _TJzE42AA9
MD5 Checksum: c65fa77ed7a3ea9b4752f9ba8fbc21b6

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

[didit]

@diditt does your slacko use nvidia proprietary drivers? TazPuppy uses nouveau xorg driver for nvidia video cards

[mistfire]

@diditt

Try to use this nvidia package from official nvidia website

https://www.nvidia.com/en-us/drivers/unix/

[mistfire]

TazPuppy 5.0 Beta 50 released

Changes:
* Glibc now upgraded to version 2.28
* GCC libs now upgraded to 8.2.0
* Critical bugfix and improvements on SFS module loading
* Critical bugfix and improvements on package management
* Improvements on default file associations
* Improvements on rc.update script
* Improved sanderdog
* Added support for major desktop environment.

Download: https://drive.google.com/open?id=1YJun8 ... kSBYqWbQr3
MD5 Checksum: 5dc17364ebb5f93a609668ffc1d56f97

Build kit: https://drive.google.com/open?id=1-LyYt ... uCCuNb-JLY

[didit]

@diditt

Try to use this nvidia package from official nvidia website

https://www.nvidia.com/en-us/drivers/unix/

i tried it also but i just can't make it work
and also i would like to know how to install a newer tazpuppy on top of older without wiping the entire partition

[mistfire]

@didit

Use frugal method to install TazPuppy without wiping a whole partition. Use save to folder if TazPuppy was installed on a Linux partition.

[Terry H]

A new clean frugal install of TazPuppy Beta 50 on SanDisk UltraFit USB Flash drive booting in UEFI mode. I created a new Save Folder. All software so far is working well. Only addition is I have installed Palemoon 28.9.1.

The problem I am having is that it is running in PUPMODE=12, instead of 13. I have pmedia=usbflash in the kernel line. It also boots the same if I remove pmedia statement. I have set Save Manager to +0 to Ask at Shutdown, but as PUPMODE is 12 it has no effect.

Why is it booting in this PUPMODE? How can I get it to boot PUPMODE=13?

Thanks in advance.

[didit]

@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

[mistfire]

To achieve PUPMODE 13 it requires large ram, the computer has a battery, and the battery was in good health.

[Terry H]

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.

[mistfire]

@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

[mistfire]

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?

[Terry H]

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.

[mistfire]

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

[Terry H]

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.

[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

Code: Select all

chmod +x /usr/sbin/snapmergepuppy

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

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

[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.