Puppy Linux Discussion Forum

Hello @measter So sorry for my delay getting back to answer your question(s). If still there is interest get back here and I will follow thru.

OK. PSAVE= is a Puppy parm...not a Ventoy parm. Ventoy's only responsibility is to launch an ISO or IMG file. Once launched, the distro (namely the ISO ...

Unfortunately, since yesterday I've lost the ground I had gained w/ BWP64 in terms of booting with my previously saved settings; now my Pup desktop is a pristine setup. What I see has been saved on the sdb2 is a dir dpupbw64save-Mike52 (not a .sfs file) and a tiny txt file dpupbw64initmodules.txt ...

I'm making useful progress here. I can now boot BWP64 from a ventoy and add the boot parameter psave=sdb2 from a message in a thread here (in which he was looking for another way to do it) and also get the session and system changes saved to another boot.

I'm a little confused over grub4dos vs ...

I'm familiar w/ the concept of using an added boot parameter, but since Ventoy allows an F6 transition to a grub cfg in the ventoy dir (which was my strategy for booting Easy (the boot worked, but saving from it didn't), it seems that I could configure something in the grub cfg.


I'm making ...

rockedge wrote: Sat Mar 01, 2025 9:02 pm

Should now be able to reach the link again!

Yes indeed; thanks to whoever for the fixing.

I recently put BWP64 on a ventoy stick and it booted fine from the ventoy alternate grub choice. I'm not fully understanding the concept of a sessions save and the above link's Notes REQUIRES session-save parm (PSAVE=), manually added, to GRUB2 Menu stanza for boot for proper session-save ...

Like YOU, I use Ventoy and/or SG2D to launch the ISO file and it affords me the ability to save all of my work in a Sessions folder. It is trouble-free and its boot performance equals/exceeds the old traditional efforts for a running forum distro desktop.

I have published this on the forum many ...

Frugalpup installer can do frugal installs to any type drive.

you can select to only do the frugal install.

Good.


You will be given a choice to use it to install a boot loader.
You have to select boot in it's main window to let it install a boot loader.
So you have a choice to install one ...

I need to have 'total control' of how the booting is handled, considering that I don't even get to see the boot manager on the part with the boot flag and I don't want to change anything about the boot flag or even its unseen manager, because the last time I did that I lost the ability to boot ...

I recently went thru' some struggles with Easy OS on a 'difficult' to access sata ssd that didn't work out. I successfully installed it on the 2nd partition after Linux Mint using a USB Ventoy menu + F6 grub cfg to boot it, but when it allegedly saved, the only thing saved was the files dir. I have ...

Presumably I'll be able to save on the ssd part and everything will be wonderful.


Since easy on the ssd doesn't save anything but what has been saved in files, I'm putting it on the back burner for now. I've written the latest Bookworm pup to a 1G USB, done a frugal install to the ext4 space ...

You could use gnome disk utility (gnome disks) to view the SMART Data of the SSD.


There's still a lot of confusion on my part about why things are 'being so difficult' but I don't think it is the fault of the ssd/s.

I have a fair amount of good news; but due to my windiness I'll give some ...

The string of errors was all about 'cp can't preserve ownership .... ' related to the .sfs.



mike@Compaq:/media/mike/F7FF-FDC2$ sudo chown -R nobody easyos
[sudo] password for mike:
chown: changing ownership of 'easyos/vmlinuz': Operation not permitted
chown: changing ownership of 'easyos ...

Back to a previous attempt via Ventoy. Corrected the changes from the ventoy grub cfg, different uuid, different dir name.

Boot failed w/ a lot of errors which scrolled off-screen. The last developer one was:
Line 2112:Failed to mount easy.sfs



The string of errors was all about 'cp can't ...

Back to a previous attempt via Ventoy. Corrected the changes from the ventoy grub cfg, different uuid, different dir name.

Boot failed w/ a lot of errors which scrolled off-screen. The last developer one was:
Line 2112:Failed to mount easy.sfs

I suspect that is because some conditions change the ...

Since I don't /get/ a grub2 menu booting the LM, I use the escape key during the boot to get a 'different looking' grub which has the Easy OS entry to try to boot into the frugal, BUT... something goes 'whacky' w/ the graphic during that boot; I'm thinking the boot parameter needs some mod such ...

my install of LMcinn on that sata ssd isn't behaving normally;


I have a degree of progress wlith some reconfiguration of the ssd.

To reiterate, my desktop legacy bios boot menu cannot display the ssd in the boot menu, altho' the bios can see everything about the ssd in its setup 'dash', but ...

I realize that this isn't really about Easy, except for how the ssd problem manifests itself in easy, causing it to perform as if it were NOT an ssd, but like a mostly unwritable usb, which is the way it acts on the usb.


I should take this discussion somewhere else because except for the Easy ...

The short form is: Done and done and successful boot of Easy on the ssd.

That sata ssd doesn't behave for me like a normal drive.


This departs from Easy, except to say that Easy doesn't perform as I would expect on the ssd. The quick start settings aren't saved; the only thing that is saved ...

Delete the Easy66 folder and recreate it (with the files easy.sfs vmlinuz and initrd). Use exactly this menu entry:
menuentry "EasyOS" {
insmod ext2
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinuz rw wkg_uuid=13dc283d-9553 ...

And no boot


Progress. More corrections of the ventoy grub cfg file and an advance in the progress of the boot before it failed. It was working toward the Easy of the sata ssd, but it didn't work out/ find it properly.

It got to: working partition sdb1, but it wasn't finding what it wanted; it ...

measter wrote: Mon Feb 24, 2025 1:26 am

Now I get Ventoy 'transition' to the EasyOS menu item, but then errors:

error: no such device --nofloppy
error: file '/Eas66/vmlinux' not found
error: you need to load the kernel first

And no boot

Oops. vmlinux above corrected to vmlinuz, but now the same errors w/ vmlinux>vmlinz.

n00b wrote: Mon Feb 24, 2025 12:05 am

Grub menu entry doesn't work without curly braces.

Doh! Fixed.

Now I get Ventoy 'transition' to the EasyOS menu item, but then errors:

error: no such device --nofloppy
error: file '/Eas66/vmlinux' not found
error: you need to load the kernel first

And no boot

Or Limine menu entry for EasyOS stick:

limine.cfg is on the first partition of the stick (boot partition)

:EasyOS Scarthgap-6-6-x
COMMENT=EasyOS Scarthgap-6.6.x bootup
RESOLUTION=800x600
PROTOCOL=linux
KERNEL_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/vmlinuz
MODULE_PATH=uuid ...

menuentry "EasyOS"
insmod ext2 ext4
insmod search_fs_uuid search --nofloppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinux rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkgdir=Easy66
initrd /Easy66/initrd


I fixed the condition of not starting the search ...

After I submit this from another system than Easy, I'll go back to that and paste in my ventoy_grub.cfg. I have some concerns about whether or not some lines end w/ return/newline.


menuentry "EasyOS"
insmod ext2 ext4
insmod search_fs_uuid search --nofloppy --fs-uuid --set=root 13dc283d-9553 ...

Write your menu and grub2 commands in a cfg file ventoy_grub.cfg under ventoy directory in the first partition, that is /ventoy/ventoy_grub.cfg and that's all.
Press F6 to load the customized menu when in Ventoy's boot menu.

https://easyos.org/install/easy-frugal-installation.html

menuentry ...

measter wrote: Sat Feb 22, 2025 8:12 pm

I'm able to find some limine 'stuff' in user/bin and usr/share but not a limine.cfg. I don't know how to do it.

And my boot dir is empty; I don't understand that.

measter wrote: Sat Feb 22, 2025 8:12 pm

I'm able to find some limine 'stuff' in user/bin and usr/share but not a limine.cfg. I don't know how to do it.

And my boot dir is empty; I don't understand that.

In order to boot into your SSD drive you'll have to add a new entry to the limine.cfg file. Make sure you add the uuid of your SSD drive there. And as well change the '-6-6-x' to the version number that you are using on your system.
:EasyOS Scarthgap-6-6-x
COMMENT=EasyOS Scarthgap-6.6.x bootup ...