Puppy Linux Discussion Forum

I found how to fix some of the boot issues with F96-CE_1

Booting from an install to a USB stick and it not booting.
USB stick has one partition and formatted fat32.

The problem is caused by not having the grub.cfg file in the top layer of the install on a USB drive.
It needs to be in the same place as the other SFS, initrd.gz, vmlinuz, etc.... files.

What I did was copy the grub.cfg file from the /boot/grub/ directory in the F96-CE_1 ISO.
Put this copy of the grub.cfg file in the same place as the other SFS, initrd.gz, vmlinuz, etc.... files.
So when it boots, the grub.cfg file is there with the other files and does not have to be found inside the boot directory.
The original grub.cfg file is still in the /boot/grub/ directory. Best to keep one there.

Two example installs that this fixed:
1. I tried doing a manual install of all the stuff in the ISO to the top layer of a USB stick.
Would not boot.
Copied the grub.cfg file to the top layer with the other files.
It booted OK to a working desktop.

2. Did an install using Unetbootin installer v702.
It would not boot.
Copied the grub.cfg file to the top layer with the other files.
It now boots to working desktop.

Note:
Unetbootin installs a bunch of extra stuff that is suppose to be it's boot loader, but they do not seem to really get used. (well, maybe)

Just to show what the modified Unetbootin install looks like that is working.
.

.
.

One other bug in the boot process, if the install is a live install, using the boot files provided by the ISO.

It boots to a point of waiting for an iso9660 partition.
Shows some messages about accessing files.
Stops booting with a message waiting for 60 seconds.

After 60 seconds.
It proceeds to what is a normal boot to a working desktop.

Both installs shown in above post do this.

Not sure what is causing this.

Note:
If I do a frugal install using the Frugalpup Installer.
The frugal install has no boot loader files from the ISO in it.
It uses the boot loader Frugalpup Installer installs.
The boot process is straight to a normal boot to desktop.

Found a fix for this.

Edited the grub.cfg file.

Changed pmedia=cd to pmedia=usbflash.

Now it boots straight to a normal boot only looking for stuff on the USB stick.
Also only finds the save that is on the USB stick.
Does not search all drives for the save.

@bigpup this 60 second boot delay has to do with the pmedia=cd in the /boot/grub/menu.lst

@wizard has been working on it and found this fix.

I added to my above post what I did to fix this 60 sec. delay.

This is kind of a catch 22 thing.

If someone does a ISO burn to a CD.

It probably needs the pmedia=cd in the boot menu entry.

Wonder if it shows if the USB stick is formatted iso9660.

Would need to modify the ISO to have the grub.cfg location change to test this idea.
dd command install would make the format iso9660.

@rockedge @bigpup

I pass credit for the 60 second fix, pmedia=usbflash to bigpup. He has posted it multiple times on the forum and I took my que from him to apply it to F96-CE_1.

Thanks
wizard

@bigpup we'll be applying these fixes very soon. Good work!

Getting the boot stanza's and boot components structure fine tuned is a process,

Look at my above post.

I think we typed and posted at the same time.

I think it is time to have the boot loader setup correctly for installs to a USB stick or SD card.
But then there will still be someone that wants to do it to a CD.
pmedia=cd is probably needed for that.

It kind of points to why barryK is all about releases in the form of a USB image.
Stopped using ISO.

@bigpup

If someone does a ISO burn to a CD.

It probably needs the pmedia=cd in the boot menu entry.

\\

Yes, tested today, the CD will boot and run without it, but cannot find a save file/folder on reboot.

Been working on the boot issues all this week, you have found the same issue of needing grub.cfg in / as I did. I have a working solution for the CD/USB boot issue too. Unetbootin and Rufus are the main installers. Goal is to have an ISO for the following:
-USB MBR
-USB UEFI
-CD MBR
-CD UEFI
So far I've turned 2 USB drives and 2 CD-RW disk into trash

It's kind of a game of "Whack-a-Mole" getting them all to play nicely. Will keep you updated when something good happens.

Thanks
wizard

I also went around in circles when I tried to create a new USB install to try out F96. I'm not as technical as some, but I have been using different puppies for quite some years, and got very frustrated not being able to create a bootable USB in the manner I (thought) I have done previously. Anyway, this time around I made myself some notes to avoid the frustration in the future. Not sure if it would be of use to anyone else.
https://www.mediafire.com/file/715mgmxu ... B.pdf/file

I am getting this feeling that the initrd.gz code needs to be revisited and looked over. Perhaps to cover more of the possible boot media types and the styles of Puppy Linux installations. Unless there can be fixes found in the boot stanza syntax, the solution may lay in a initrd modification.

A closer look at the loop.cfg by fresh eyes may also be helpful to develop the best version of stanza syntax.

You are probably correct that the initrd.gz needs some tweaking .

----------------------------------------------------------------------------------------------------------------------------------
This is an idea.
I tried this with the USB install I am using that works.

I made two normal boot entries in the grub.cfg file.

They read like this:

1. fossapup64 9.6 normal boot from USB drive
This has the pmedia=usbflash
It boots normally for an install to a USB drive. USB stick or SD card.

2. fossapup64 9.6 normal boot from CD/DVD drive
This has the pmedia=cd
It seems to boot normally for an install to a CD/DVD

I only did this for the normal boot entries in the grub.cfg file.
All the other entries still have pmedia=cd
Installed on a USB.
These other entries will work, but it is trying to boot as if installed on a CD/DVD.

Maybe all entries would need to have two versions.
One for USB install and one for CD/DVD install.

One thing I noticed.
When booting from a USB and save is on the USB.
pmedia= has to be pmedia=usbflash for the boot process to find the save on the USB.
Actually it only seems to look for the save on the USB.

Installed on a USB and pmedia= is pmedia=cd
It only looks on all other drives for a save.
Never looks on the USB drive.
.
.

@bigpup

Check your PM for an update.

Thanks
wizard

I am going to get to applying your changes later today.

Should be easy to modify the USB install with them.

Not exactly sure how to do it for a CD install.

I guess I will have to add them to a new ISO for F96-CE_1

I was thinking I could open the ISO
Run Pburn.
Select all the files from the ISO.
Select the added files you provided in your PM
Now with Pburn having all the files to write to a CD.
Make a new CD burn with all the files in it.

Or would it all need to be made into a new ISO and then do a ISO burn to make a working boot-able CD?

@bigpup

Should be easy to modify the USB install with them.

Yes, just follow the steps I gave.

was thinking I could open the ISO
Run Pburn.
Select all the files from the ISO.
Select the added files you provided in your PM
Now with Pburn having all the files to write to a CD.
Make a new CD burn with all the files in it.

No, that won't work. Pburn can burn a CD from an ISO, but cannot build an ISO. Your USB has files put on it by the installer that may cause problems. You need to extract the files from F96-CE_1.iso and add the menu files to them. then make a new ISO.

Or would it all need to be made into a new ISO and then do a ISO burn to make a working boot-able CD?

yes
Sent you this in a PM on Friday.

You have to rebuild the ISO, then use that to burn the CD. Puppy's ISOmaster can do the rebuild, but it won't be a UEFI CD. Keep in mind that the original F96-CE_1 ISO will not make a UEFI CD.

I have a script that you can run that will make the ISO for a UEFI CD. Let me know if you want to give it a try.

wizard

@wizard quick link to the script please! I am experimenting with VirtualBox UEFI and QEMU UEFI booting.

@rockedge

Check your PM's from last Wed. "F96 UEFI/hybrid with 60 second fix", it's in the attachment.

wizard

Well I use Ventoy these days but an older version.

Tried a few fixes. Thought it was just me.

"""""""
"Stops booting with a message waiting for 60 seconds.

After 60 seconds.
It proceeds to what is a normal boot to a working desktop."

No mine dies. with a message.

Anyway I will wait for a fix....Chris