Puppy Linux Discussion Forum

Hello,

I installed BookworkmPup64 onto the first partition of a new USB stick, which was formatted to FAT32.

I followed the Frugal Installer: Puppy Button → This Puppy → sdf1
After that, I was prompted to create the boot files, which were saved onto sdf1.

FSTAB ENTRY
I created an entry in FSTAB to mount the UUID for sdf1 to mnt/lee_puppy_stuff, and a bash script that I execute manually to mount, since it doesn't mount automatically.

UUID=B333-9A75 /mnt/lee_puppy_stuff vfat defaults,noatime 0 0

Everything worked, and when shutting down, I chose to save the session (mnt/lee_puppy_stuff/puppy/dpupbw64save66.tar.gz). I get asked whether or not to save on every shutdown, which is good (PUPMODE=66), but is that PUPMODE the right one?

When I take the USB to different computers, three work fine and load the saved session, but some others fail at bootup when loading the save archive.

Last lines of kernel log:

FND_MULTIFOLDER=
--SAVEARCHIVE-- /mnt/dev_save/puppy/dpupbw64save66.tar.gz
adding /pup_rw66 to aufs stack failed.

overlayfs: "xing" feature enabled using 4 upper inode bits.
loop5: detected capacity change from 0 to 167232
overlayfs: "xing" feature enabled using 4 upper inode bits.
hid_uclogic: module verification failed: signature and/or required key missing - tainted kernel
Pausing for 60 seconds

-----------
Should this be missing?

# modprobe aufs
modprobe: FATAL: Module aufs not found in directory /lib/modules/6.1.106

----------
Pupsave - it is there but Pupsave Backup tells me otherwise.
----------
FrugalPup Settings:

acpi_osi=Linux libata.noacpi=1 intel_pstate=disable net.ifnames=0
net.ifnames=0

-----------
Here is the directory of /mnt after mounting to lee_puppy_stuff

# tree /mnt
/mnt
├── cdrom
├── data
├── dvd
├── flash
├── floppy
├── lee_puppy_stuff
│ ├── EFI
│ │ └── boot
│ │ ├── bootia32.efi
│ │ ├── bootx64.efi
│ │ ├── grub.cfg
│ │ ├── grubia32.efi
│ │ ├── grubx64.efi
│ │ ├── mmia32.efi
│ │ └── mmx64.efi
│ ├── appimages
│ │ ├── LibreOffice-fresh.basic-x86_64.AppImage
│ │ ├── LibreOfficeIcon.svg
│ │ ├── LibreWolf.x86_64.AppImage
│ │ └── LibreWolf_icon.svg
│ ├── boot
│ │ └── grub
│ │ ├── fonts
│ │ │ └── DejaVuSansMono18.pf2
│ │ ├── grub.cfg
│ │ └── grubenv
│ ├── grub.cfg
│ ├── mount_lee_puppy_stuff.sh
│ ├── puppy
│ │ ├── AUTOSAVE
│ │ ├── SAVESPEC
│ │ ├── adrv_dpupbw64_10.0.8.sfs
│ │ ├── bdrv_dpupbw64_10.0.8.sfs
│ │ ├── boot
│ │ │ ├── EFI
│ │ │ ├── bootinst.bat
│ │ │ ├── bootinst.sh
│ │ │ ├── bootlogo.png
│ │ │ ├── extlinux.exe
│ │ │ ├── extlinux.x32
│ │ │ ├── extlinux.x64
│ │ │ ├── help.txt
│ │ │ ├── initrfs.img
│ │ │ ├── isolinux.bin
│ │ │ ├── isolinux.boot
│ │ │ ├── isolinux.cfg
│ │ │ ├── ldlinux.c32
│ │ │ ├── ldlinux.sys
│ │ │ ├── libcom32.c32
│ │ │ ├── libutil.c32
│ │ │ ├── mbr.bin
│ │ │ ├── pxelinux.0
│ │ │ ├── runadmin.vbs
│ │ │ ├── samedisk.vbs
│ │ │ ├── syslinux.cfg
│ │ │ ├── syslinux.com
│ │ │ ├── syslinux.exe
│ │ │ ├── vesamenu.c32
│ │ │ ├── vmlinuz
│ │ │ └── zblack.png
│ │ ├── changes
│ │ ├── dpupbw64initmodules.txt
│ │ ├── dpupbw64save66.tar.gz
│ │ ├── fdrv_dpupbw64_10.0.8.sfs
│ │ ├── initrd.gz
│ │ ├── kbuild-6.1.106.sfs
│ │ ├── modules
│ │ │ ├── 01-core.sb
│ │ │ ├── 01-firmware.sb
│ │ │ ├── 02-xorg.sb
│ │ │ ├── 03-desktop.sb
│ │ │ ├── 04-apps.sb
│ │ │ └── 05-chromium.sb
│ │ ├── puppy_dpupbw64_10.0.8.sfs
│ │ ├── ucode.cpio
│ │ ├── vmlinuz
│ │ └── zdrv_dpupbw64_10.0.8.sfs
│ └── puppy.cer
├── msdos
├── ram1
├── swap
└── zip

Thank you,

Lee

To Puppy Linux.

I installed BookworkmPup64

This is information we always need, but this is not enough.
We need to know the exact full name of the Puppy version.
This could be:
BookwormPup64 10.0.3
BookwormPup64 10.0.6
BookwormPup64 10.0.7
BookwormPup64 10.0.8

Yes it matters all of these versions are different.

Read this about why it is using pupmode 66:
https://forum.puppylinux.com/viewtopic.php?t=12419
Read all the posts in this topic.

This is really designed for doing a live install to a USB stick that has one partition and it is formatted fat 32.
nothing else is on the USB stick but bookwormPup64.
It is suppose to make it easier for new user, so they do not really need to understand how to make a save with choices.
It just shuts down and auto saves.
Because of type save it makes, it gets around the fat 32 max file size limit of 4GB. Well to a point.
Save being a compressed file, it can hold more, before it reaches this max size limit.

Need some more info:

Is this a USB stick with multiple versions of Puppy Linux installed on it?
If yes.

What is being used as the boot loader?

I followed the Frugal Installer: Puppy Button → This Puppy → sdf1
After that, I was prompted to create the boot files, which were saved onto sdf1.

This is how I do frugal installs to a USB stick using Frugalpup installer:
https://forum.puppylinux.com/viewtopic.php?t=11171

This will allow different pupmodes ,save options, ability to save to a folder not a file, have multiple frugal installs of different Puppy versions, etc........

baggins wrote: Fri Sep 20, 2024 7:04 am

--SAVEARCHIVE-- /mnt/dev_save/puppy/dpupbw64save66.tar.gz
adding /pup_rw66 to aufs stack failed.

The most likely reason for this error is failure to extract dpupbw64save66.tar.gz to RAM - it could be corrupt, or maybe RAM is insufficient.

/initrd/tmp/bootinit.log might contain extra information that can explain this error. If it doesn't, try to add loglevel=7 to make this log file more verbose.

bigpup wrote: Fri Sep 20, 2024 9:30 am

To Puppy Linux.

Thank you. And thank you for your great reply.

This is information we always need, but this is not enough.
We need to know the exact full name of the Puppy version.
This could be:
BookwormPup64 10.0.3
BookwormPup64 10.0.6
BookwormPup64 10.0.7
BookwormPup64 10.0.8

BookwormPup64 10.0.8 x86_64
Kernel: 6.1.106

My USB has three partitions:
sdx1: FAT32
sdx2 and dsx3 are EXFAT for my files that can be used on Windows and Linux.

Is this a USB stick with multiple versions of Puppy Linux installed on it?

No. Only one adorable Puppy.

This is how I do frugal installs to a USB stick using Frugalpup installer:
https://forum.puppylinux.com/viewtopic.php?t=11171

Thank you. That's a more standard Linux partition scheme.

This will allow different pupmodes ,save options, ability to save to a folder not a file, have multiple frugal installs of different Puppy versions, etc........

Thanks again,

Lee

Thank you for your insightful reply.

The most likely reason for this error is failure to extract dpupbw64save66.tar.gz to RAM - it could be corrupt, or maybe RAM is insufficient.

Ah! I'll see what the RAM is in the PCs that fail. But they do complete booting with no saved settings of course.

/initrd/tmp/bootinit.log might contain extra information that can explain this error. If it doesn't, try to add loglevel=7 to make this log file more verbose.

Okay.

Thank you.
Regards,

Lee

Setting up the partitions properly did the trick.

Quick boot-ups now, and it boots on one of the not working PCs, so I expect the ones at work to boot up as well.
I had to go into the grub.cfg to change the pmedia to 'usbflash' so that the PUPPYMODE=13 not 12.

Thank you very much for the assistance. I look forward to not dealing with Windows 7 and all of the adware and malware people install on the PCs at work.

All the best,

Lee