Not loading from internal SSD nvme Fossapup64 9.5

[Ramachandra Iyer]

Any kernel with SSD nvme support like LVM etc. Fossapup64 etc are not loading from SSD internal SSD. Why searching USB while loading from internal disk. Not locating main SFS also. Strange behaviour while dual boot with SSD.

[ozsouth]

@Ramachandra Iyer - this may work better if you specify pdrv in your bootloader config (i.e. grub.cfg).
To use this you will need to boot with a usb stick puppy, run gparted and label the partition you are trying to boot.
I use the date & a letter, i.e. 200322a as a label.
Then you amend the kernel line in grub.cfg to include pdrv=200322a (or whatever you called it).
Upon reboot, desired drive partition will be accessed.

[Ramachandra Iyer]

I have applied the suggestion still not booting. You may please note that Antix Linux is booting from another ext4 partition without any glitch. Only simple menu entry. Antix was installed for testing purpose only. I feel, the issue may be with our construction like kernel or intird. just pointing only. The original fossapupp64 was even not detected nvme SSD. Latter I have changed the kernel provided by you something like 5.16.14 RE etc. (manually swapped the vmlinuz, fdrv, zdrv ) After that it detected nvme. However, still refind.conf not finding partition. Pease see attached file.

WhatsApp Image 2022-03-20 at 5.48.53 PM.jpeg (178.61 KiB) Viewed 1446 times

[Ramachandra Iyer]

Please see the output got from blkid command

blkidnvmessd.txt

(2.06 KiB) Downloaded 66 times

[ozsouth]

@Ramachandra Iyer - sorry I have no experience with refind. My suggestion works for standard Puppy installs.

[williwaw]

to direct refind to the proper partition, try using a volume line. for your Vanilla on /dev/nvme0n1p6, something like .....

menuentry "Vanilla" {
volume VanillaD22
loader /vmlinuz
initrd /initrd.gz
ostype Linux
options "rw"
}

[Ramachandra Iyer]

I don't think it is because of refind.conf. The refind.conf setting working at another HP Machine without any issue. Only problem occures when it comes to SSD nvme hard disk. I have been tinkering with this issue for the past one year. With simple settings as given by williwaw , Antix Linux booting instantly through refind.conf. So my strong believe that the problem lies either kernel or initrd, that is why my issue was posted on Kernel section. Antix Linux kernel can be inspected or compared so that we can pin point the issue. Only kernel expert can sort out my issue.

[ozsouth]

@Ramachandra Iyer - I've booted a new nvme ssd in a Celeron n4020 laptop using grub or syslinux by specifying the label of the partition to boot. I changed kernels & Puppy versions without issue. That's why I suggested it. Something in your setup seems incompatible with Puppy. Different bios/uefi settings perhaps.

[gychang]

@Ramachandra Iyer - this may work better if you specify pdrv in your bootloader config (i.e. grub.cfg).
To use this you will need to boot with a usb stick puppy, run gparted and label the partition you are trying to boot.
I use the date & a letter, i.e. 200322a as a label.
Then you amend the kernel line in grub.cfg to include pdrv=200322a (or whatever you called it).
Upon reboot, desired drive partition will be accessed.

Was having the same problem and labeling the partition worked for me. thanks ozsouth...

[Ramachandra Iyer]

@Ramachandra Iyer - this may work better if you specify pdrv in your bootloader config (i.e. grub.cfg).
To use this you will need to boot with a usb stick puppy, run gparted and label the partition you are trying to boot.
I use the date & a letter, i.e. 200322a as a label.
Then you amend the kernel line in grub.cfg to include pdrv=200322a (or whatever you called it).
Upon reboot, desired drive partition will be accessed.

Was having the same problem and labeling the partition worked for me. thanks ozsouth...

Please provide your boot stanza of grub. So that I can change accordingly.

[gychang]

Please provide your boot stanza of grub. So that I can change accordingly.

Here is mine:
menuentry "Puppy fossapup64 9.5" {
insmod ext2
search --no-floppy --fs-uuid --set 3175fd75-28c2-42f3-a932-02c39b596731
echo "Loading vmlinuz"
linux /FP64/vmlinuz pmedia=atahd pdrv=puppy psubdir=/FP64 psave=store:/mainSav/ pfix=fsck,fsckp,trim TZ=PST8PDT,M3.2.0,M11.1.0
echo "Loading initrd.gz"
initrd /FP64/initrd.gz
}

I used gparted and frugalpup to install. I modified grub.cfg. Note pdrv=puppy (this is the partition labeled "puppy" where FP files are placed-*.sfs etc, note I createds FP64 folder). I have my save file in another partition (don't need to do this) with "store" label in a folder named mainSav.

[bigpup]

Someone else had the same issues booting from an internal emmc drive.

To fix it.
They changed the kernel being used in Fossapup64 9.5 to one that had a better config setup for these internal drives.
May want to try it.
Discussion starts here:
viewtopic.php?p=54529#p54529

[bigpup]

Just a possibility.

I know it is an internal SSD drive.
However it could be seen as a USB device.
Depends on the computers interface setup.

Fossapup64 9.5 has a bug in the boot process.
The USB drive Fossapup64 is on, when booted, will not boot, if it is not the only USB drive plugged into computer.

So make sure you are booting from the internal SSD drive and no USB drives are plugged into the computer.

[Ramachandra Iyer]

gychang

I have done as per your grub cfg. Still it is not booting. It is not detecting my partition.

While booting no usb was inserted.

[gychang]

gychang

I have done as per your grub cfg. Still it is not booting. It is not detecting my partition.

While booting no usb was inserted.

would you mind putting up your grub.conf?

[Ramachandra Iyer]

menuentry "Vanila Dpup" {
search --no-floppy --fs-uuid --set 883a7a72-6eb2-45db-99a8-2a6bf04a262d
linux /WDL_endeavXFCE/vmlinuz w_bootfrom=UUID=883a7a72-6eb2-45db-99a8-2a6bf04a262d=/WDL_endeavXFCE
initrd /WDL_endeavXFCE/initrd.gz
}
menuentry "KLV AIRDALE" {
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root d9bb49e4-6dbc-4839-a255-d7e8021751c5
linux /klvair/vmlinuz w_bootfrom=UUID=d9bb49e4-6dbc-4839-a255-d7e8021751c5=/klvair w_changes=UUID=d9bb49e4-6dbc-4839-a255-d7e8021751c5=/klvair
initrd /klvair/initrd.gz
}
menuentry "Puppy fossapup64 9.5" {
search --no-floppy --fs-uuid --set 8f553b5c-05b2-4159-a93e-bb7df1c13b69
linux /puppy22/vmlinuz pmedia=atahd pdrv=rootantiX21 psubdir=/puppy22
initrd /puppy22/initrd.gz
}

menuentry "Power Off" {
halt
}

menuentry "Reboot" {
reboot
}

[gychang]

I only boot FP64 from my internal SSD, but yours is more complicated.
I don't see anything obviously wrong with your FP menu on the grub.conf. You may want to back up the grub.conf and boot just FP64 and see if boots up?

[Phoenix]

Has anyone happened to try swapping kernels with a known kernel that works? Don't forget your modules too otherwise a bunch of problems may arise.

[bigpup]

menuentry "Puppy fossapup64 9.5" {
search --no-floppy --fs-uuid --set 8f553b5c-05b2-4159-a93e-bb7df1c13b69
linux /puppy22/vmlinuz pmedia=atahd pdrv=rootantiX21 psubdir=/puppy22
initrd /puppy22/initrd.gz
}

Try this change to the entry.
Make pdrv= this:
pdrv=8f553b5c-05b2-4159-a93e-bb7df1c13b69

That identifies the drive using the UUID which should work better at this point in the boot process.

[Ramachandra Iyer]

No change ir. Still same message as above. not found 8f553b5c-05b2-4159-a93e-bb7df1c13b69.

[rockedge]

Not sure this will be valid but give it a try:

Code: Select all

pdrv=UUID=8f553b5c-05b2-4159-a93e-bb7df1c13b69

So:

Code: Select all

menuentry "Puppy fossapup64 9.5" {
search --no-floppy --fs-uuid --set 8f553b5c-05b2-4159-a93e-bb7df1c13b69
linux /puppy22/vmlinuz pmedia=atahd pdrv=UUID=8f553b5c-05b2-4159-a93e-bb7df1c13b69 psubdir=/puppy22
initrd /puppy22/initrd.gz
}

OR:

Code: Select all

menuentry "Puppy fossapup64 9.5" {
search --no-floppy --fs-uuid --set 8f553b5c-05b2-4159-a93e-bb7df1c13b69
linux /puppy22/vmlinuz pmedia=atahd pdrv=LABEL=rootantiX21 psubdir=/puppy22
initrd /puppy22/initrd.gz
}