Puppy Linux Discussion Forum

I followed the instructions below

bigpup wrote: Wed Aug 05, 2020 5:16 pm

Drive labels are going to depend on number of drives on the computer.
So, you do need to be careful to select the correct drive label, when offered to select.

8<------ snipped------
Instructions up to this point worked fine.

Select the boot button.
Select the location of the frugal install, on the USB stick.
Select the small 300MB partition on the USB stick, as location to install the boot loader. (may need to scroll the selection window)
Select the boot loader type.
UEFI
mbr ->legacy bios boot
both

You can install the UEFI for UEFI computers.
mbr for legacy bios computers.
both, to boot anything. (best option for USB drives installs)

8<------ snipped------
I was unable to install the bootloader to the FAT32 drive, because it does not show up in the dialog box of the Frugal installer.
Do I need an updated Frugal installer?
Would this work as an alternative:
https://www.supergrubdisk.org/category/ ... sk-stable/

Thanks.
PS. Sorry about the unreadable menu titles, but that is not me, they were designed that way.
.

I was unable to install the bootloader to the FAT32 drive, because it does not show

something did not work fine

unplug all the drives except the one you booted with and the new drive
http://www.fishprogs.software/puppy/fru ... index.html
e3StickPup will do the formatting for you, just select the correct drive

you should end up with something like......
sdb1 fat32 for bootloader
sdb2 ext3 for fossapup folder

williwaw wrote: Tue Jun 04, 2024 8:20 am

I was unable to install the bootloader to the FAT32 drive, because it does not show

something did not work fine

unplug all the drives except the one you booted with and the new drive
http://www.fishprogs.software/puppy/fru ... index.html
e3StickPup will do the formatting for you, just select the correct drive

you should end up with something like......
sde1 fat32 for bootloader
sde2 ext3 for fossapup folder

Ok, did that, but what about the boot parameters?

grub.cfg has these settings, but none of the usual boot parms.

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

menu.1st has only this:

timeout 0
default 0

title grub2
  kernel /boot/grub/i386-pc/core.img

https://forum.puppylinux.com/viewtopic. ... 99#p121699
1. unless specified KLV saves all persistence automatically in /upper_changes
2. RAM2 which allows the user to save on demand or choose to save at system reboot or shutdown also written to /upper_changes
3. RAM0 which loads no persistence and does not save. So fresh system after each boot

I'd like to have a choice of the 3 boot methods on screen. How?
Thanks.

Governor wrote: Tue Jun 04, 2024 10:03 am

williwaw wrote: Tue Jun 04, 2024 8:20 am

I was unable to install the bootloader to the FAT32 drive, because it does not show

something did not work fine

unplug all the drives except the one you booted with and the new drive
http://www.fishprogs.software/puppy/fru ... index.html
e3StickPup will do the formatting for you, just select the correct drive

you should end up with something like......
sde1 fat32 for bootloader
sde2 ext3 for fossapup folder

Ok, did that, but what about the boot parameters?

grub.cfg has these settings, but none of the usual boot parms.

Code: Select all

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

menu.1st has only this:

Code: Select all

timeout 0
default 0

title grub2
  kernel /boot/grub/i386-pc/core.img

rockedge wrote: Mon Jun 03, 2024 5:35 pm

If it's running it's saving unless you have added a parameter in the kernel command line not too.

There are 3 modes of operation...
1. unless specified KLV saves all persistence automatically in /upper_changes
2. RAM2 which allows the user to save on demand or choose to save at system reboot or shutdown also written to /upper_changes
3. RAM0 which loads no persistence and does not save. So fresh system after each boot

If you installed it and the boot stanza that starts it doesn't have a w_changes=RAM0 or the parameter w_changes=RAM2 on the kernel command line it should be saving everything as you go.

It is possible to use normal mode (#1) some of the time and then use RAM2 mode (#2) after that to select when to save a session again.
It is possible to use normal mode (#1) some of the time and then use RAM2 mode (#2) after that to select when to save a session again.

I'd like to have a choice of the 3 boot methods on screen. How?
I have not tried booting with it yet.
Thanks.

Governor wrote: Tue Jun 04, 2024 10:03 am

Ok, did that, but what about the boot parameters?.............

https://forum.puppylinux.com/viewtopic. ... 99#p121699
1. unless specified KLV saves all persistence automatically in /upper_changes
2. RAM2 which allows the user to save on demand or choose to save at system reboot or shutdown also written to /upper_changes
3. RAM0 which loads no persistence and does not save. So fresh system after each boot

I'd like to have a choice of the 3 boot methods on screen. How?
Thanks.

frugalpup will provide boot entrys for puppy,
if you want klv boot parameters ask in the klv section

Lucky for us @wiak has written a script to write valid boot stanza's for KLV called wd_grubconfig.

Place wd_grubconfig in the KLV root file system and run it. The output is on the terminal or saved in grub_config.txt

williwaw wrote: Tue Jun 04, 2024 5:11 pm

Governor wrote: Tue Jun 04, 2024 10:03 am

Ok, did that, but what about the boot parameters?.............

https://forum.puppylinux.com/viewtopic. ... 99#p121699
1. unless specified KLV saves all persistence automatically in /upper_changes
2. RAM2 which allows the user to save on demand or choose to save at system reboot or shutdown also written to /upper_changes
3. RAM0 which loads no persistence and does not save. So fresh system after each boot

I'd like to have a choice of the 3 boot methods on screen. How?
Thanks.

frugalpup will provide boot entrys for pppy,
if you want klv boot parameters ask in the klv section

I need this for fossapup. I tried the frugalpup install as instructed and, and it didn't work. I posted a screenshot here:
viewtopic.php?p=121744#p121744

I received new instructions and used e3StickPup instead. I have the boot stick, but have not yet tested it. I would like to get the boot menu straight before I boot it.

I want to boot from the thumb drive and load Puppy completely into RAM, and also be certain that nothing gets written to my internal drive or any external drive, at any time without my knowledge or consent (not during boot or at any time afterward).

This is what I would hope to see in a boot menu on my writable drive thumb drive or CD/DVD (not closed/locked media):

1) A choice of a clean boot, which boots from the boot media only without loading any saves, and allows the user to save on demand or choose to save at system reboot or shutdown (saves only to the boot media).

2) List the choices of which saves to use (if any are found).
Instead of searching for boot files (saves) on every partition of the internal or external drive, search the current boot media only.

After the above is determined, then the following:
Load the chosen save, or none (for clean boot), and allow the user to save on demand or choose to save at system reboot or shutdown.

My computer has 10,145,308 KiB of memory. And I intend to use a swap file on the NVMe internal drive each time I boot, in case of overflow.

If I want to boot from the internal drive, I will point to it as #2 in the BIOS, and remove the thumb drive, so no need to do boot the internal drive from the thumb drive.

Governor wrote: Wed Jun 05, 2024 9:43 am

have not yet tested it

test it and report back what happens (lots of pic please if something fails)
if it works, ask in the klv section if you still want to add the klv parameters (and how to back up your working configs before editing files in the boot partition)

If I want to boot from the internal drive, I will point to it as #2 in the BIOS, and remove the thumb drive, so no need to do boot the internal drive from the thumb drive.

this seems outside the scope of Frugalpup V41
please start a new topic in the approiate section once your frugalpup USB boots

I found there seems to be a problem for for a computer that has BookwormPup64_10.0.7 or 10.0.6.
If a USB stick also has BookwormPup64_10.0.7 and is connected to a computer which is booted,
the computer will only boot the USB and not the internal drive.
The following is similar to testing done from another topic to confirm this:
(viewtopic.php?p=129148#p129148)

I verified the results and eliminated the possibility of Ventoy causing the problem.

I'm using qemu that has BookwormPup64_10.0.7 installed directly from the iso.
From this I plugged in a USB stick to make a frugal install on it from BW menu > Setup > FrugalPup Installers > e4StickPup.
Then using this USB stick booted on the laptop, I re-partitioned the internal drive and installed BookwormPup64_10.0.7 by using menu > Setup > FrugalPup Installers > DiskPup

When either the internal drive or the USB is booted up, both show they have GRUB version 2.03 on them.

If I connect the USB to the laptop that has boot order set to internal drive first and USB second and leave it connected, it always boots to the USB.
If the internal drive is selected by the computer's boot menu using its function key on power up, it boots to the USB
If the computer has the feature in its bios to disable the USB boot - it boots to the USB
The only time you can again boot to the internal drive is if the USB is disconnected.
This means that even if the bios has disabled the USB boot, that this can be overridden by plugging in a USB like this. This is a physical security risk.

To make this work like it normally should, I ran the GRUB update patch on the internal drive (see viewtopic.php?t=10028).
This makes the GRUB version 2.06
Now it works properly whether the USB is plug in or not on boot like it should.

If the USB is connected to the computer when it is booted:
If the internal drive is selected, the internal drive boots
If the USB drive is selected, the USB drive is selected.
If the USB drive is disabled, only the internal drive boots.

This happens on all three of my different brand laptops. But I could only make the GRUB update on two of them.
The third one is a Lenovo Ideapad 100S-11IBY that has a peculiar 32 bit efi and 64 bit operating system.

JusGellin wrote: Mon Aug 19, 2024 2:43 pm

I found there seems to be a problem for for a computer that has BookwormPup64_10.0.7 or 10.0.6.
If a USB stick also has BookwormPup64_10.0.7 and is connected to a computer which is booted,
the computer will only boot the USB and not the internal drive.
The following is similar to testing done from another topic to confirm this:
(viewtopic.php?p=129148#p129148)

8<-----snipped

I tried several times and the native Frugal installation did not work for me either.

I have an ext3 partition and I have successfully used e3StickPup. This program seems to work properly and consistently (so far).
http://www.fishprogs.software/puppy/fru ... index.html

Cheers!

I have uploaded https://www.mediafire.com/file/hw30yr10 ... ar.xz/file.

This new version of 'grub2-efi.tar.xz' contains the signed Debian grub2.06 efi binaries, as announced in,
viewtopic.php?p=131598#p131598

If you have FrugalPup installed as an AppDir, you can simply replace the old file with the new one.
Otherwise just drop it into '/usr/local/frugalpup'.

Edit:
This is no -longer the file used by FrugalPup to provide ".efi" binaries.
See the next post.

FrugalPup v42 is available.

FrugalPup v42, DiskPup v42, StickPup v42 and f2StickPup v42 - Puppy frugal installer.
Along with e3StickPup v42 and e4StickPup v42.

'frugalpup_42.sfs'(3.1 MiB) or 'frugalpup-42.pet'(3.1 MiB) or 'FrugalPup_AppDir-42.tar.gz'(3.1 MiB) can be downloaded from https://www.mediafire.com/folder/rdyc5l ... /frugalpup.

Includes 5 significant changes:

1) The main 'frugalpup' script uses a more obvious method for starting a facility script and killing itself,
in response to a facility button click.

2) The 'frugalpup-installers' script from BookwormPup has been assimilated, though with some "fixes".
Thanks to ???, well whoever wrote it.
There are now "bogus" '.desktop' files to hide the old real '.desktop' files for each of the indivual utilities.
These will probably be removed in a future release.

3) When installing grub2, it will try to install into '/EFI/Puppy' in preference to '/EFI/boot' if the destination partition is on an internal drive,
and 'efibootmgr' is available to register '/EFI/Puppy' as a "boot" with the uefi/bios.

4) It includes, and uses, the recently published 'grub2-efi-bin.tar.xz' and 'grub2-efi-font.tar.xz' files, to install grub2.

5) Support for "Secure Boot" via a local MOK has been implemented.
If the 'signKernelUtils' are installed, and a local MOK is found:
When installing grub2 the 'grub....efi' binaries will be signed, if they are currently unsigned.
When generating a new 'grub.cfg' it will include code to fix the "Secure Boot" font issue.
When installing Puppy files, the 'vmlinuz' file and the kernel modules in 'zdrv...sfs' will be signed if the 'vmlinuz' file is currently unsigned.

Note for translators:
The addition of the strings in 'frugalpup-installers' are the only changes from v41, that should be needed.

There's a bug in v42, so there will be a FrugalPup v43.

When FrugalPup is installing grub2 in a "signed" environment, it fails to copy the '/MOK/local.cer' file to the root of the "boot" partition.
This is annoying when you run any of the StickPup's, and then try to boot the USB stick in a "Secure Boot" enabled computer that does not have your local MOK enrolled.
The work-around is to manually copy the '/MOK/local.cer' file to the USB stick.

Hi - have sent you a PM as the new grub2-efi-bin.tar.xz breaks Woof-CE builds which include FrugalPup

I have a possible FrugalPup v43 ready to go once this is sorted.

FrugalPup v43 is available.

FrugalPup v43, DiskPup v43, StickPup v43 and f2StickPup v43 - Puppy frugal installer.
Along with e3StickPup v43 and e4StickPup v43.

'frugalpup_43.sfs'(3.1 MiB) or 'frugalpup-43.pet'(3.1 MiB) or 'FrugalPup_AppDir-43.tar.gz'(3.1 MiB) can be downloaded from https://www.mediafire.com/folder/rdyc5l ... /frugalpup.

This is a bug-fix version.

There are only 2 changes:

1) When "signing" grub2 binaries, it now copies the public key ".cer" file, to the destinatoin partition.

2) The 'pinstall.sh' file has been removed from the ".pet".
It didn't actually achieve anything, and this eases the burden on Woof-CE itself.

gyrog wrote: Tue Oct 01, 2024 7:10 am

Note for translators:
The addition of the strings in 'frugalpup-installers' are the only changes from v41, that should be needed.

Thanks.
The Japanese translation has been updated to suit the version 43.

The topic "Frugalpup" in the Japanese forum
https://sakurapup.com/forum1/viewtopic.php?f=25&t=3633

@thinkpadfreak,
Thanks for doing the translation.
And you are welcome.

FrugalPup v44 is available.

FrugalPup v44, DiskPup v44, StickPup v44 and f2StickPup v44 - Puppy frugal installer.
Along with e3StickPup v44 and e4StickPup v44.

'frugalpup_44.sfs'(3.1 MiB) or 'frugalpup-44.pet'(3.1 MiB) or 'FrugalPup_AppDir-44.tar.gz'(3.1 MiB) can be downloaded from https://www.mediafire.com/folder/rdyc5l ... /frugalpup.

There no changes to the working of the code, or the text displayed.

This is to fix an icon issue with some Puppies.

Current FrugalPup depends on the file '/usr/share/pixmaps/gnibbles.png' being present in Puppy, for it's icons.
This can no-longer be relied upon.
The script 'frugalpup-installers' has been modified to dynamically fix this issue,
if '/usr/share/pixmaps/gnibbles.png' file is not present, using an internal 'gnibbles.png'.

Yes, if the Puppy you are running has this issue, the menu entry will be missing an icon.

@gyrog

Thanks for this

@Jasper,
You are welcome.

@gyrog ............ oops should have also mentioned at the same time, it always functions perfectly with Fossapup64-95.

I only use the binaries as shown in the screenshot as I am booting up on a x64 PC.