Kernel can't find main sfs on USB install (solved)

[mkngo87]

I installed fossapup with frugalpup to my USB flash drive. It boots fine when I just have the flash drive as my only USB device. It seems that the boot process can't find the main sfs when I have other usb devices connected. Would someone help me? I guess I could just disconnect all my USB devices as a workaround, but it's annoying of course.

This is my boot entry in grub.cfg:

Code: Select all

menuentry "Puppy fossapup64 9.5" {
    insmod fat
    search --no-floppy --fs-uuid --set  6C37-4F73
    echo "Loading vmlinuz"
    linux /puppy/vmlinuz pmedia=usbflash pdrv=6C37-4F73 psubdir=/puppy pfix=fsck,fsckp TZ=XXX-8
    echo "Loading initrd.gz"
    initrd /puppy/initrd.gz
}

IMG_20220807_130752940_resize.jpg (127.61 KiB) Viewed 692 times

[bigpup]

This is a known bug in Fossapup64 9.5 boot process.

As long as the Fossapup64 USB is the only USB drive plugged in, it boots OK.

I only see this if I have another USB drive plugged in.

Are you having the issue with a USB mouse, keyboard, etc.... plugged in?

[bigpup]

Here is the old topic about this issue.
May be a solution in it someplace.
https://forum.puppylinux.com/viewtopic.php?t=966

[mkngo87]

Here is the old topic about this issue.
May be a solution in it someplace.
https://forum.puppylinux.com/viewtopic.php?t=966

Thanks for the link. It seems that the solution lies in fixing the init script. I think this is beyond my understanding so I'll just have to live with it.

This is a known bug in Fossapup64 9.5 boot process.

As long as the Fossapup64 USB is the only USB drive plugged in, it boots OK.

I only see this if I have another USB drive plugged in.

Are you having the issue with a USB mouse, keyboard, etc.... plugged in?

The issue occurs when I plug in one of my USB to SATA drives.

[ozsouth]

I use gparted to label the main puppy partition (must be ext3 or ext4 or ntfs) with the date & a letter, i.e. 080822a & then use pdrv=080822a in boot cfg.

[mikeslr]

Have you tried something like the boot arguments bigpup suggested in this post, https://oldforum.puppylinux.com/viewtop ... 88#p553688

"find --set-root --ignore-floppies --ignore-cd /luci268/initrd.gz
or
find --set-root --ignore-floppies --ignore-cd /lupu_527.sfs"

e.g.
find --set-root --ignore-floppies --ignore-cd /puppy/initrd.gz
or
find --set-root --ignore-floppies --ignore-cd /fossapup64_9.5.sfs

or create a text file in the puppy folder named 'my-fossapup64.txt' and edit the boot code to read:
find --set-root --ignore-floppies --ignore-cd /puppy/my-fossapup64.txt

[mikewalsh]

Are you having the issue with a USB mouse, keyboard, etc.... plugged in?

AFAIK, mice,dongles, keyboards, etc, are NOT seen the same as mass storage devices. You should be able to leave stuff like that plugged-in....

Mike.

[mkngo87]

I re-read the old topic and used the solution provided by gyrog. My new boot entry now looks like this:

Code: Select all

menuentry "Puppy fossapup64 9.5" {
    insmod fat
    search --no-floppy --fs-uuid --set  6C37-4F73
    echo "Loading vmlinuz"
    linux /puppy/vmlinuz pmedia=usbflash pdrv=6C37-4F73 psubdir=/puppy pfix=fsck,fsckp TZ=XXX-8
    echo "Loading initrd.gz"
	initrd /puppy/fossa64-withwait4usb-initrd.gz
	# Puppy Linux will not boot correctly if there are more than one USB drive.
    # initrd /puppy/initrd.gz
}

Thank you @bigpup

[ozsouth]

@mkngo87 - glad this is resolved, but since timing is the issue, you could possibly append the 'linux' line with rootwait , rather than use a special initrd.gz.

[Clarity]

HI @mkngo87

On your drive, you should have a SAVESPEC file. Would you locate and share its 3 line contents, please?

Thanks in advance.

[williwaw]

try plugging your boot usb into the best port on your computer (some machines have usb ports of different specs)
relegate other devices to the Anker hub