Puppy Linux Discussion Forum

HI ,
I am trying to get Bookworm Pup64 to boot but cant fiqure out what the correct entry to put on limine boot loader.
I put this but it gets so far then stops
Puppy Linux BookwormPup64 (partition sda11, path BookwormPup64)
PROTOCOL=linux
KERNEL_CMDLINE=root=UUID=134d593c-73b3-4c82-81b2-fe865e7f94b5 pmedia=atahd pfix=fsck
KERNEL_PATH=fslabel://Bookworm-Pup64/BookwormPup64/vmlinuz
MODULE_PATH=fslabel://Bookworm-Pup64/BookwormPup64/initrd.gz
this is the same as Fossapup and it boots ok.
thanks
Ali

Does it do anything when selected to boot?

Is it installed on the same drive partition as Fossapup64?
If no.
If that is the uuid of the partition Fossapup64 is installed on. It is wrong uuid.
It needs to be the uuid of the partition Bookworm Pup64 is on.

I assume it is installed in a directory(folder) named BookwormPup64?

Note:
names are case sensitive. Capital and lower case letters must be correct.

Thanks for the reply
it is on a seprate partion in a folder BookwormPup64
It boots as far as Finding puppy main sfs file.

0: PMEDIA=atahd PDRV= PSUBDIR= pfix=fsck
1: PDRV= P_BP_ID= P_BP_FN=
2: LOOK_PUP=yes LOOK_SAVE= PMEDIA=atahd
3: PSUBDIR= P_BP_FN= P_DEF_FN=puppy_dpup_10.0.sfs
HAVE_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
TRY_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
4: ONE_PART=sda1
4: ONE_PART=sda10
4: ONE_PART=sda11
4: ONE_PART=sda2
4: ONE_PART=sda6
4: ONE_PART=sda7
4: ONE_PART=sda8
4: ONE_PART=sda9
3: PSUBDIR= P_BP_FN= P_DEF_FN=puppy_dpup_10.0.sfs
HAVE_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
TRY_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
4: ONE_PART=sda1
4: ONE_PART=sda10
4: ONE_PART=sda11
4: ONE_PART=sda2
4: ONE_PART=sda6
4: ONE_PART=sda7
4: ONE_PART=sda8
4: ONE_PART=sda9
3: PSUBDIR= P_BP_FN= P_DEF_FN=puppy_dpup_10.0.sfs
HAVE_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
TRY_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
4: ONE_PART=sda1
4: ONE_PART=sda10
4: ONE_PART=sda11
4: ONE_PART=sda2
4: ONE_PART=sda6
4: ONE_PART=sda7
4: ONE_PART=sda8
4: ONE_PART=sda9
3: PSUBDIR= P_BP_FN= P_DEF_FN=puppy_dpup_10.0.sfs
HAVE_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
TRY_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
4: ONE_PART=sda1
4: ONE_PART=sda10
4: ONE_PART=sda11
4: ONE_PART=sda2
4: ONE_PART=sda6
4: ONE_PART=sda7
4: ONE_PART=sda8
4: ONE_PART=sda9
3: PSUBDIR= P_BP_FN= P_DEF_FN=puppy_dpup_10.0.sfs
HAVE_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
TRY_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
4: ONE_PART=sda1
4: ONE_PART=sda10
4: ONE_PART=sda11
4: ONE_PART=sda2
4: ONE_PART=sda6
4: ONE_PART=sda7
4: ONE_PART=sda8
4: ONE_PART=sda9
3: PSUBDIR= P_BP_FN= P_DEF_FN=puppy_dpup_10.0.sfs
HAVE_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
TRY_PARTS='sda1|vfat
sda10|vfat
sda11|ext4
sda2|ext4
sda6|ext4
sda7|ext4
sda8|ext4
sda9|ext4'
4: ONE_PART=sda1
4: ONE_PART=sda10
4: ONE_PART=sda11
4: ONE_PART=sda2
4: ONE_PART=sda6
4: ONE_PART=sda7
4: ONE_PART=sda8
4: ONE_PART=sda9
6: ONE_PART=sda9 ONE_TRY_FN=/puppy_dpup_10.0.sfs PDRV=

that is bootinit.log
I dont really understand what it means

the uuid is correct

Post an image of what Rox file manager shows for what is in this BookwormPup64 directory.

I want to exactly see what files are in it.

Take a Shot program can make an image you can attach to a post.

download/file.php?mode=view&id=17723

I am not seeing anything obvious.

I would try a fresh new download of the Bookworm64 ISO

Totally delete the install you have of it.

Do a fresh new install from this new ISO.

See if that changes anything.

Downloads of the ISO and installs not good do happen, sometimes.

Make sure to try booting from a completely powered off back on computer. no power for at least 1 minute.
That makes sure the RAM is clean when you start booting.
Eliminates possible RAM corruption.

Barry has a limine installer pet you can download. it will generate a puppy limine stanza
viewtopic.php?p=62566#p62566

if you do not have a running puppy or a way to run the pet, and wish to use the =label parameter, you need to have a label on the partition in question.

Is fslabel://Bookworm-Pup64/BookwormPup64/xxxxx your partition label? if not, you can assign one with gparted without having to reformat the partition

Is =fslabel://Bookworm-Pup64/BookwormPup64/xxxxx your install subfolder on that partition? If so maybe add psubdir=BookwormPup64 to the KERNEL_CMDLINE=

my partition label for the vanilla install is F1 and vanilla is the subfolder where the frugal is.

:Vanilla Dpup 9.3.24
    PROTOCOL=linux
    TEXTMODE=yes
    KERNEL_PATH=fslabel://F1/vanilla/vmlinuz
    MODULE_PATH=fslabel://F1/vanilla/initrd.gz
    KERNEL_CMDLINE=pmedia=ataflash psubdir=vanilla pfix=fsck

your root=UUID=134d593c-73b3-4c82-81b2-fe865e7f94b5
looks like something used with grub? maybe not neccesary?

thanks for all the help
I downloaded the iso and reinstalled and installed grub2 to check it booted ok
I then removed grub (dont like grub as cant figure it out, couldn't get it to boot easyos which i have been playing with)
I then ran the limine installer and it found bookworm pup, i never thought to try that, because it never saw fosapup. (i had copied the entry from grub4dos originaly )
the part i was missing from my attempt was psubdir=BookwormPup64.
Liminie made the entry neater by doing it like this;

:Puppy Linux dpup (partition sda11, path BookwormPup64)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=BookwormPup64 pmedia=atahd
KERNEL_PATH=fslabel://Bookworm-Pup64/BookwormPup64/vmlinuz
MODULE_PATH=fslabel://Bookworm-Pup64/BookwormPup64/initrd.gz

So your problem is solved?

sorry was away
yes the problem is solved
Thanks

Sorry to hijack a thread like this, but this is Limine-related: Is it possible to use Limine to boot a Linux OS directly from a USB flash drive, same as it is with Syslinux or Grub 2? Can you install Limine, and your OS files, directly to a flash drive in such a way that the pen drive then becomes self-contained, Limine is found and boots from the flash drive itself, and can then see and boot the OS files direct from the flash drive, same as Syslinux/Grub 2? After a while of searching, I've yet to discover a satisfying answer to this question and was hoping if the Puppy community would know.

directly... same as grub....

are you asking if you can boot an iso with limine without persistence? or "Live"?
viewtopic.php?p=88699#p88699

as for haveing a self contained bookworm on a usb with limine. a frugal install is certianly possible. If you have a linux booted on a machine with an open usb port. you can use limine bootloader installer

williwaw wrote: ↑Tue Aug 22, 2023 12:40 am

directly... same as grub....

are you asking if you can boot an iso with limine without persistence? or "Live"?
viewtopic.php?p=88699#p88699

as for haveing a self contained bookworm on a usb with limine. a frugal install is certianly possible. If you have a linux booted on a machine with an open usb port. you can use limine bootloader installer

No, no ISOs. Frugal install to a flash drive is the game plan. I will unpack the ISO and copy the relevant files into a folder on the flash drive. The idea, then, is to edit Limine's config file to point it to the correct Puppy files to be booted. So you're saying that, same as Syslinux and Grub 2, Limine can also see all properly formatted storage devices, including USB pen drives, and boot Puppies directly from those, no problem? Because this is what I frequently do with Windows machines. I dual boot Win and Puppy safely by using boot flash drives for Puppy Linux, rather than disturbing the Windows partition. I find Limine interesting, and would like to study it more, but only if it offers the desired functionality.

To sort of answer my own question, I have successfully created a Limine-based bootable USB flash drive after looking into this newfound bootloader more closely. I will now share what I did for those interested. This will be for systems using UEFI, but BIOS/MBR-boot doesn't need too many changes to get one going.

1. Download Limine binaries from (https://github.com/limine-bootloader/limine/releases), if you don't already have them.

2. Choose any flash drive you think you can spare for this. Format flash drive to FAT32 filesystem if it isn't already, making sure to back-up any important datas on the drive first.

3. Create the EFI-folder to the root of your USB stick, then create the BOOT-folder inside that, so that you get the standard /EFI/BOOT-directory structure used in UEFI boots. Then copy the file BOOTX64.EFI inside /EFI/BOOT, to get /EFI/BOOT/BOOTX64.EFI. BOOTX64.EFI comes from the Limine binary package you hopefully downloaded from Limine's Github page. BOOTX64.EFI, specifically, is for the 64-bit Intel/AMD systems.

4. Now create the folder "limine" to the root of your flash drive, so that you get /limine. Now we need to create the limine.cfg file here, which will contain instructions for Limine to boot our Puppy. Open any ASCII-text editor, and copy and paste this into your limine.cfg.

TIMEOUT=60
GRAPHICS=no
DEFAULT_ENTRY=1
EDITOR_ENABLED=yes
INTERFACE_BRANDING=Limine Boot Manager

:PUPPY-LINUX-BOOKWORM
    COMMENT=PuppyLinuxBookworm
    PROTOCOL=linux
    TEXTMODE=yes
    KERNEL_PATH=boot:///bookworm/vmlinuz
    MODULE_PATH=boot:///bookworm/initrd.gz
    KERNEL_CMDLINE=pmedia=usbflash psubdir=/bookworm

Then save limine.cfg inside the /limine-folder, so that you get /limine/limine.cfg to your flash drive. Remember, that some of these settings are just my personal preferences.

5. Next, mount and unpack your preferred Puppy .ISO. I will be using the latest and greatest Bookworm Pup for this example. Now you must create one more folder, called /bookworm to the root of your flash drive. With your Bookworm .ISO mounted, copy Bookworm Puppy's files inside the /bookworm folder on your flash drive. Once this is done, you should now have a functional, UEFI-bootable system, self-contained on a USB flash drive, and so you may now unmount the flash drive and test its boot capabilites.

Anyone wishing to amend these instructions to include BIOS/MBR boot capabilities as well is free to do so. If your UEFI has Secure Boot enabled, remember to turn that off first.