How to Prevent BookwormPup Boot Up Error?

[JusGellin]

I get the attached same errors on boot up for two laptops of different brands:
HP Pavilion x360 Convertible 11m-ap0xxx - dual boot with Alpine Linux
Dell Inspiron 15-7569 - Standalone system

On a fresh frugal install of BookwormPup64_10.0.6 there are no errors.
But once a Save occurs, this occurs on each boot up.

How can I get rid of this error that comes up? Everything seems to work ok except for this coming up on boot up.

Thanks

[esos]

Maybe you put the wrong boot parameter(s)

[JusGellin]

Maybe you put the wrong boot parameter(s)

I allowed the puppy install to make the boot for the Dell laptop.
The dual boot HP was more manual with the help of many good people here.

It is just strange that on both computers it starts doing exactly the same error only after the first save occurs.
Do you think the error indicates anything for what boot parameter could be wrong?

Thanks

[williwaw]

Do you think the error indicates anything for what boot parameter could be wrong?

Its hard to tell, but if you post the boot menu in question, some might spot a discrepancy

[JusGellin]

Here you are. Thanks
This is the part of the grub.cfg for the puppy part for the dual boot HP laptop

menuentry 'BookwormPup64_10.0.6'{
# search --no-floppy --set=root --fs-UUID=bf498d22-5de5-49a5-951e-5ac6b01e4489
search --no-floppy --fs-uuid --set=root bf498d22-5de5-49a5-951e-5ac6b01e4489
# search --no-floppy --fs-uuid --set bf498d22-5de5-49a5-951e-5ac6b01e4489
linux /puppy/vmlinuz psubdir=/puppy pmedia=ataflash pfix=fsck
initrd /puppy/initrd.gz
}

This is the grub.cfg for the Dell laptop

#
set default=0
set timeout=5

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

loadfont /boot/grub/fonts/DejaVuSansMono18.pf2
set gfxmode=auto
terminal_output gfxterm

menuentry "Puppy dpupbw64 10.0.6" {
insmod ext2
search --no-floppy --fs-uuid --set=root 849ce5f0-7326-40e0-8ab2-1c31aa41f023
echo "Loading vmlinuz"
linux /BookwormPup64_10.0.6/vmlinuz pmedia=usbflash pdrv=boot psubdir=/BookwormPup64_10.0.6 pfix=fsck,fsckp,trim TZ=GMT0
if [ -e /BookwormPup64_10.0.6/local-initrd.gz ]; then
set local_rd=/BookwormPup64_10.0.6/local-initrd.gz
else
set local_rd=
fi
if [ -e /BookwormPup64_10.0.6/ucode.cpio ]; then
set ucode_rd=/BookwormPup64_10.0.6/ucode.cpio
echo "Loading ucode.cpio and initrd.gz"
else
set ucode_rd=
echo "Loading initrd.gz"
fi
initrd $ucode_rd /BookwormPup64_10.0.6/initrd.gz $local_rd
}
if [ $grub_platform = 'efi' ]; then
menuentry "System BIOS setup" {
fwsetup
}
fi
menuentry "Shutdown computer" {
halt
}
menuentry "Reboot computer" {
reboot
}

[williwaw]

thats more to work with.

it is unusual to get the same error with two different computers unless the error is very basic, which is not apparent from what you have posted.

can you verify the errors are exactly the same with both machines and if not, post the other error?

[JusGellin]

This one is from the Dell computer.

Wow, it is exactly the same error information! I had to really look to make sure that these were pictures from each, and they are. Everything is identical.
Both used the same BookwormPup installation.
Both didn't have the error until the first save.

[JusGellin]

I just saw another topic with the same error:
Adapting F-96-CE Puppy Linux for a Very Recent Laptop (3/2024)
viewtopic.php?t=11142

I don't fully understand if it finally got resolve or not, but it really went through a lot (49 posts)

[BologneChe]

I had the same type of error under Triton 9 (viewtopic.php?t=11195) which is based on BookwormPup 10.0.4

There was a correction but I cannot tell you its nature. I had no problems afterward.

[williwaw]

I just saw another topic with the same error:
Adapting F-96-CE Puppy Linux for a Very Recent Laptop (3/2024)
viewtopic.php?t=11142

I don't fully understand if it finally got resolve or not, but it really went through a lot (49 posts)

I think @ozsouth provided a solution in the next post after the one you linked
@vtpup had some additional issues, but they may have been related to his too new to be supported yet hardware, and I recall another thread where the user could boot the first time but not with a savefile.
maybe this is something that only affects certian machines and an older version will work better?

[JusGellin]

I believe this is the fix you are referring to:

@vtpup - you need to edit the ... initmodules.txt file, commenting out (or removing) module lines causing problem (any 'not found' module). If changing kernels, one must remove this file & it will be recreated next boot, hopefully more appropriately. I only noticed this behaviour late last year.

fixboot.jpg

Mine (from the attached images and my save folder is called puppy) has this error:
Adding module intel_ishtp_hidmodprobe: can't load module intel_ishtp_hid (kernel/drivvers/hid/intel-ish-hid/intel-ishtp-hid.ko): No such device.
failed
So intel-ishtp-hid.ko is the bad device.

Then the file he referred to that needs to be edited is from the line that says:
Using /mnt/dev_save/puppy/dpupbw64initmodules.txt

I can see this file using the terminal.
/initrd/mnt/dev_save/puppydpupbw64initmodules.txt
That file contains something similar to the problem device intel-ishtp-hid.ko but instead is intel_ishtp_hid

It looks like that folder is the same as /mnt/home/puppy

But those locations don't see that file using the rox filer. All I see are the save files,5 sfs files, AUTOSAVE, intrd.gz, SAVESPEC,vmlinuz, which is the puppy save folder

I'm guessing that file is in one of the sfs files.

So I couldn't get to that file using rox. I, instead, ran Geany from the command line (a new thing I learned) and removed that device and saved it.
I then rebooted without getting the error. Yea!!
I think I just got more education for changing a file in one of sfs files and saving it to the save folder. -- Wow!

I wanted to show my thinking process for figuring this out and if I'm thinking wrong, I would appreciate any corrections or advice.
Whew!