Puppy Linux Discussion Forum

I'm trying to boot Vanillapup 9.3.30 from an sd card with a savefile on the sd card using grub2.config.
It boots fine but loads the savefile from an identical install on my Kingston SSD partition which is normally booted using Limine.
I dont see any issues with my grub.config file.entry as shown below.

menuentry 'Vanilladpup 9.3.30 (sdb1/vanilladpup)'{
search --no-floppy --set=root --fs-uuid 428E-7487
linux /vanilladpup/vmlinuz pmedia=usbflash psubdir=/vanilladpup pfix=fsck
initrd /vanilladpup/initrd.gz

Is there a way short of renaming the pupsave file on the SSD each time that I can get around this?

I also have the same setup for F96 on both the sd card and the SSD and both boot and load the respective save files correctly.

TIA

I'm not real familiar with grub2 stanzas, so I don't know exactly where to add it, but puppies have a boot parameter "psave=" that indicate where exactly to find a particular save. It's explained here: viewtopic.php?t=5484

@geo_c

Thank you for the link.
No luck as yet.

Tahrbaby wrote: Fri Sep 08, 2023 7:26 am

@geo_c

Thank you for the link.
No luck as yet.

It looks to me from the grub2 stanza you provided that the sd card is drive sdb1 and for booting you have it identified by uuid, which boots correctly from the sd card. So I believe you should be able to add "psave=[uuid]" to the third line of the stanza. If you tried that already, it appears from the forum topic that you can also specify the filename itself, "psave=YourUUID/YourPATH/YourSAVEFILE"

if you are stii having trouble,
could you run blkid in the terminal and post the output?
also post your entire grub.cfg

@williwaw @geo_c

Thanks for the help guys.
Probably a simple solution but I have had no luck as yet

/dev/sdb1: LABEL_FATBOOT="dos82a4f6cb" LABEL="dos82a4f6cb" UUID="428E-7487" TYPE="vfat" PARTUUID="82a4f6cb-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: UUID="022be4d8-c6a8-4264-95e5-59852d44c7d9" TYPE="ext4"
/dev/nvme0n1p1: LABEL_FATBOOT="ESP" LABEL="ESP" UUID="6499-8543" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9ca6b80e-58a9-4eec-8c30-b7f09d0010be"
/dev/nvme0n1p3: LABEL="Acer" UUID="C4F4AD9AF4AD8EEC" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="558506a1-c843-47e6-ac0f-40de7213e1ee"
/dev/nvme0n1p4: LABEL="Recovery" UUID="1A2EB99E2EB9737D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b23c2343-a3b7-4d8b-9c77-a38fbb11777a"
/dev/sda1: UUID="F0AA-881F" TYPE="vfat" PARTUUID="2359e1c8-01"
/dev/sda2: UUID="361dc6e7-ad35-409b-b9a5-75bc4bab300f" TYPE="ext4" PARTUUID="2359e1c8-02"
/dev/sda3: UUID="da28bf25-5df4-45cd-b584-37e61b34283e" TYPE="ext4" PARTUUID="2359e1c8-03"
/dev/sda4: UUID="9a104561-017e-47ec-ae64-9d520bf63099" TYPE="ext4" PARTUUID="2359e1c8-04"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="44292241-ccc2-471e-9259-866eba294748"
/dev/zram0: UUID="a448ee1f-d3f2-463d-a365-745b33133f90" TYPE="swap"
#

# grub.cfg produced by grub2config 2.0.1
set default=0
set timeout=10
set menu_color_normal=white/blue
set menu_color_highlight=black/cyan

loadfont $prefix/fonts/DejaVuSansMono18.pf2
set gfxmode=auto
insmod all_video
insmod gfxterm
terminal_output gfxterm

# Puppy Linux

menuentry 'Fossapup64 9.6 (sdb1/f96)'{
search --no-floppy --set=root --fs-uuid 428E-7487
linux /f96/vmlinuz pmedia=usbflash psubdir=/f96 pfix=copy
initrd /f96/initrd.gz
}

menuentry 'Fossapup64 9.6 (sdb1/f96) RAM mode'{
search --no-floppy --set=root --fs-uuid 428E-7487
linux /f96/vmlinuz pmedia=usbflash psubdir=/f96 pfix=ram
initrd /f96/initrd.gz
}

menuentry 'S15pup64 22.12 (sdb1/s15pup64)'{
search --no-floppy --set=root --fs-uuid 428E-7487
linux /s15pup64/vmlinuz pmedia=usbflash psubdir=/s15pup64 pfix=fsck
initrd /s15pup64/initrd.gz
}

menuentry 'Vanilladpup 9.3.30 (sdb1/vanilladpup)'{
search --no-floppy --set=root --fs-uuid 428E-7487
linux /vanilladpup/vmlinuz pmedia=usblash psubdir=/vanilladpup pfix=fsck
initrd /vanilladpup/initrd.gz
}

menuentry 'Fossapup64 9.6 (sda2/f96)'{
search --no-floppy --set=root --fs-uuid 361dc6e7-ad35-409b-b9a5-75bc4bab300f
linux /f96/vmlinuz pmedia=atahd psubdir=/f96 pfix=fsck
initrd /f96/initrd.gz
}

menuentry 'Vanilladpup 9.3.30 (sda2/vanilladpup)'{
search --no-floppy --set=root --fs-uuid 361dc6e7-ad35-409b-b9a5-75bc4bab300f
linux /vanilladpup/vmlinuz pmedia=atahd psubdir=/vanilladpup pfix=fsck
initrd /vanilladpup/initrd.gz
}

# Other Linux

menuentry 'Linux Mint 21 Vanessa (sda3/boot)'{
search --no-floppy --set=root --fs-uuid da28bf25-5df4-45cd-b584-37e61b34283e
configfile /boot/grub/grub.cfg
}

menuentry 'LMDE 5 Elsie (sda4)'{
search --no-floppy --set=root --fs-uuid 9a104561-017e-47ec-ae64-9d520bf63099
linux /vmlinuz/initrd.img root=UUID=9a104561-017e-47ec-ae64-9d520bf63099 quiet splash
initrd /initrd.img
}

menuentry 'LMDE 5 Elsie (sda4/boot)'{
search --no-floppy --set=root --fs-uuid 9a104561-017e-47ec-ae64-9d520bf63099
linux /boot/vmlinuz5.10.0-25-amd64 root=UUID=9a104561-017e-47ec-ae64-9d520bf63099 quiet splash
initrd /boot/initrd.img-5.10.0-25-amd64
}

if [ $grub_platform = "efi" ] ; then
menuentry 'Windows uefi boot'{
search --no-floppy --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
fi

if [ $grub_platform = "efi" ] ; then
menuentry 'debian uefi boot'{
search --no-floppy --set=root --fs-uuid F0AA-881F
chainloader /EFI/debian/shimx64.efi
}
fi

if [ $grub_platform = "efi" ] ; then
menuentry 'UEFI boot from sda1'{
search --no-floppy --set=root --fs-uuid F0AA-881F
chainloader /EFI/BOOT/BOOTX64.EFI
}
fi

if [ $grub_platform = "efi" ] ; then
menuentry 'UEFI boot from sda2'{
search --no-floppy --set=root --fs-uuid 361dc6e7-ad35-409b-b9a5-75bc4bab300f
chainloader /EFI/boot/bootx64.efi
}
fi

if [ $grub_platform != "efi" ] ; then
menuentry 'Windows mbr boot'{
search --no-floppy --set=root --file /bootmgr
chainloader +1
}
fi

if [ $grub_platform = "efi" ] ; then
menuentry 'UEFI Firmware Settings'{
fwsetup
}
fi

# custom menu
if [ -f /custom.cfg ] ;then source /custom.cfg ;fi

menuentry 'Previous menu'{
configfile /grub-prev.cfg

If the save file you want to use is under /dev/sdb1 (UUID is 428E-7487), try to add psave=428E-7487.

dimkr wrote: Sat Sep 09, 2023 7:18 am

If the save file you want to use is under /dev/sdb1 (UUID is 428E-7487), try to add psave=428E-7487.

@dimkr

Added that but it boots 9.3.30 without loading the save folder.
The save file I'm using is the exact same for sda and sdb1.

Reran Grub2 bootloader config to the sd card (sdb1) to see if it would make a difference.
It still boots 9.3.30 but loads the savefile from sda2

To clarify:
1) Which save save file/folder do you want it to pick up, that on sdb1 or sda2?
2) Is the save file/folder under both partitions inside a sub-directory named "vanilladpup"?

dimkr wrote: Sat Sep 09, 2023 10:36 am

To clarify:
1) Which save save file/folder do you want it to pick up, that on sdb1 or sda2?
2) Is the save file/folder under both partitions inside a sub-directory named "vanilladpup"?

When choosing from my grub menu on sdb1 Vanilladpup 9.3.30,I want it to find and load the save file which is on sdb1.

Yes,the save files on both sda2 and sdb1 are both named the same (vanilladpupsave).

Which boot loader configuration file did you change - the one in the internal drive or the one in the flash drive?

Tahrbaby wrote: Sat Sep 09, 2023 11:00 am

dimkr wrote: Sat Sep 09, 2023 10:36 am

2) Is the save file/folder under both partitions inside a sub-directory named "vanilladpup"?

Yes,the save files on both sda2 and sdb1 are both named the same (vanilladpupsave).

each partition has /vanilladpup/vanilladpupsave ?

I also have the same setup for F96 on both the sd card and the SSD and both boot and load the respective save files correctly.

how can you tell F96 works and vanilla doesnt?

dimkr wrote: Sat Sep 09, 2023 4:13 pm

Which boot loader configuration file did you change - the one in the internal drive or the one in the flash drive?

I changed the grub.cfg file on the flash drive sdb1 because I want to boot from the sd card (sdb1) in this instance.

I'm using Limine to boot the internal drive/s when required.

williwaw wrote: Sat Sep 09, 2023 4:32 pm

Tahrbaby wrote: Sat Sep 09, 2023 11:00 am

dimkr wrote: Sat Sep 09, 2023 10:36 am

2) Is the save file/folder under both partitions inside a sub-directory named "vanilladpup"?

Yes,the save files on both sda2 and sdb1 are both named the same (vanilladpupsave).

each partition has /vanilladpup/vanilladpupsave ?

I also have the same setup for F96 on both the sd card and the SSD and both boot and load the respective save files correctly.

how can you tell F96 works and vanilla doesnt?

My save files on both drives are named vanilladpupsave-vandpup.4fs (my allocated named choice)

I can watch F96 at boot and it shows the correct savefile being loaded for each drive.
Also,the drive mount icons on the desktop show which drive is mounted.
Whereas,if I boot Vanilladpup from sdb1(sd card),it shows sda2 as mounted.

Tahrbaby wrote: Sat Sep 09, 2023 7:08 pm

My save files on both drives are named vanilladpupsave-vandpup.4fs (my allocated named choice)

I can watch F96 at boot and it shows the correct savefile being loaded for each drive.
Also,the drive mount icons on the desktop show which drive is mounted.
Whereas,if I boot Vanilladpup from sdb1(sd card),it shows sda2 as mounted.

I cannot recall if the indicator on the icon indicates just mounting or indicates savefile also. Maybe two different indicators, one for each? (not using vanilla at the moment)

I suppose you could rename your install folders and saves to somthing discrete for each drive and see if it helps. Do you have a specific usage that requires identical naming and paths?

williwaw wrote: Sat Sep 09, 2023 8:13 pm

Tahrbaby wrote: Sat Sep 09, 2023 7:08 pm

My save files on both drives are named vanilladpupsave-vandpup.4fs (my allocated named choice)

I can watch F96 at boot and it shows the correct savefile being loaded for each drive.
Also,the drive mount icons on the desktop show which drive is mounted.
Whereas,if I boot Vanilladpup from sdb1(sd card),it shows sda2 as mounted.

I cannot recall if the indicator on the icon indicates just mounting or indicates savefile also. Maybe two different indicators, one for each? (not using vanilla at the moment)

I suppose you could rename your install folders and saves to somthing discrete for each drive and see if it helps. Do you have a specific usage that requires identical naming and paths?

No,I was meaning when mounted shows a green marker.Its a greyed out marker I see which indicates that drives savefile is in use.
I already tried renaming the savefile and it didnt work but will try again.
However,that doesn't really answer my original question as to why F96 manages to find and load the correct savefile using the same method?

Tahrbaby wrote: Sat Sep 09, 2023 8:36 pm

I already tried renaming the savefile and it didnt work but will try again.
However,that doesn't really answer my original question as to why F96 manages to find and load the correct savefile using the same method?

when renaming the save or path you will have to make adjustments to the kernel line psave and/or psubdir.
(or let grubconfig or limine installer do it )

Why F96 works better for you? perhaps by accident... your identical paths could be challenging to the code,

Grub2

menuentry "Puppy vanilladpup 9.2.20" {
  insmod ext2
  search --no-floppy --fs-uuid --set=root fbb65611-fb5c-4b0c-8f21-331dabc54d23
  echo "Loading vmlinuz"
  linux /Puppy-vanilladpup-9.2.20/vmlinuz net.ifnames=0 pmedia=usbhd pdrv=fbb65611-fb5c-4b0c-8f21-331dabc54d23 psubdir=/Puppy-vanilladpup-9.2.20 pfix=fsck,fsckp 
  echo "Loading initrd.gz"
  initrd /Puppy-vanilladpup-9.2.20/initrd.gz
}

williwaw wrote: Sat Sep 09, 2023 10:12 pm

Tahrbaby wrote: Sat Sep 09, 2023 8:36 pm

I already tried renaming the savefile and it didnt work but will try again.
However,that doesn't really answer my original question as to why F96 manages to find and load the correct savefile using the same method?

when renaming the save or path you will have to make adjustments to the kernel line psave and/or psubdir.
(or let grubconfig or limine installer do it )

Why F96 works better for you? perhaps by accident... your identical paths could be challenging to the code,

@williwaw

Thank you for the info'.