Governor wrote: ↑Sun Jan 08, 2023 6:26 pmwilliwaw wrote: ↑Sun Jan 08, 2023 5:49 pmfossa works, limine works, and hopefully you can fine tune your Bios settings to get your screen working better at boot time.
Should you wish to add an additional puppy to your nvme in the future, follow steps 12 and 13, at viewtopic.php?p=77084#p77084 (with new naming apropos of your new pup of course)
you would also need to duplicate the stanza in liming.cfg and edit the path in KERNEL_PATH= and MODULE_PATH= to the new install folder name.You might also try to copy your Easy install from the USB to the NVME, in which case you could disable USB Boot in the bios and see if that makes a difference with your boot time issues. You could of course still use a USB to move files, but just not boot from it until the Bio config change was reverted.
To create an Easy frugal install on the NVME, you would
1. boot into the NVME,
2. insert your Easy USB, then copy /easyos over to the top directory of the nvme, alongside the fossapup dir
3. Copy the stanza from the Easy limine.cfg , appending it to the limine.cfg in the NVME. You would also need to edit the UUID in the duplicated stanza, deleting the USB's UUID and inserting the NVME UUID. (the nvme uuid can be seen in the stanza above).
@Tahrbaby
I am not a fossapup guy so you would know better, but the most recent boot parameters Gov posted was:Puppy Linux fossapup64 (partition nvme0n1p2, path fossapup)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=fossapuppmedia=ataflash
KERNEL_PATH=guid://e9b97f54-0ba4-4ff9-9e06-730900b8f08b/fossapup/vmlinuz
MODULE_PATH=guid://e9b97f54-0ba4-4ff9-9e06-730900b8f08b/fossapup/initrd.gzIf that line should be changed, what should the changes be?
KERNEL_CMDLINE=psubdir=fossapuppmedia=ataflash
Change pmedia=ataflash to pmedia=atahd,save it, reboot and see what happens.