Puppy Linux Discussion Forum

I have one laptop that has not been able to boot from a Puppy installed to the internal emmc. Always get the error message not being able to find the Puppy files. Installed eslacko64, using frugalpup installer, on the internal emmc. eslacko64 can boot with no problem. Boots to working desktop. Exce...

Yes, I do see that "Waiting for partition [<partition-id>]" message. Good, the different "Waiting" message is the indication that the experimental 'init' script is actually in use. Thanks for testing. Edit: Of course it is very good news that it seems to be fixing the multiple u...

Now we have some iso files to use for testing,
could some folk who do direct iso booting, please try 1 of them.

eSlacko64 is released from init-experiment Thanks 01micko, Installed this on a usb HD, booted fine with a "Waiting for partition [t2Lin]" message as expected. Burnt the iso to a CD-RW, and boot fine, but no "Waiting" message at all. Installed to an internal HD, booted fine with ...

Tried it as a frugal install (setup by Frugalpup installer), on a USB flash drive, with more than one USB drives plugged into computer. This seems to work and boots with no problem. Did you notice a "Waiting for partition [<partition-id>]" message flash by on the console early in the boot?

UPupGG+D-Alpha+4 has been built using init-experiment ...... BUILD_FROM_WOOF='init-experiment;8f4c1e337;2020-10-12 19:10:19 +1000' https://sourceforge.net/projects/zestypup/files/Upup-Groovy%2B/alpha/ Thanks peebee. Later edit: I tried it, and here's what happened on my mahine: I installed it to an...

Probably binary changes caused issues in Bionic. Since then all the bins have been updated and they are probably overdue for another update. i'm not going to bother working out why the bionicpup's are incompatible with the current woof-ce 'init' script. I'll just accept that they are, so using them...

On reflection, it is quite possible that folk could be generating false negatives by testing 'init_wait-1.sfs' on their favourite Puppy, because the Puppy is incompatible with the un-patched current standard 'init' from woof-ce. So I've uploaded 'init_woof-1.sfs' to https://www.mediafire.com/folder/...

While a simple workaround is available, in some situations, there exists an underlying deficiency in Puppy, it should not matter to Puppy how many usb devices are connected. For a simpler and more general method of testing the "test" 'int' script, see https://forum.puppylinux.com/viewtopic...

The script 'wait4usb', which is called by the 'init' script to do any needed waiting, has a couple of limitations. 1. It only waits for the first USB drive. If the partition is on a device that is not a usb device, and the device needs waiting, no waiting is done. 2. It only waits for the FIRST usb ...

Unfortunately I have an "improved" 'init' script, that includes a 'wait_for_blkid' function that can be used by things other than just the 'decode_id' function. As an example, this 'init' includes code that calls 'wait_for_blkid' to get a list of "iso96660" partitions when "...

Every time you run the "FrugalPup->Boot" facility, it re-installs the boot loader files. So it you do this to simply update the 'grub.cfg' it works, but it's rather inefficient. (One of the things I'm looking at for the next version.) For now, I use the CLI utility 'bootentry', which is pa...

peebee I have a pet 'grub2_frugalpup-20.pet' that puts Grub2 files in '/usr/share/grub2/'. The version 20 relates to the version of FrugalPup they are taken from. I couldn't attach it, since it's too large, I'll upload it fo "MediaFire" and get back to you. Edit: It's at https://www.media...

I have uploaded a new version of the patched 'init' that works when the install partition is specified, and when the 'init' script has to resort to searchig for the Puppy install, (thanks jamesbond). You can download 'fossa64-initrd.gz' from https://www.mediafire.com/folder/hkwe9ykjbmvwb/init-wait ....

Getting back to the original issue. I have attached a parched version of 'init' for fossapup64. ( I tried to attach a replacement 'initrd.gz', but it is too big.) This 'init' waits for the needed partition to be "seen" by the kernel, (as in present in '/proc/partitions' or reported by 'blk...

This is just meant to provide extra information. 1. "pupsfs=" is an alias for "pdrv=", it doesn't matter which one you use. "pupsfs=" is the older one, "pdrv=" is an attempt to make it consistent with "adrv=", "fdrv=" etc... 2. Assuming 'pu...

Could it not continue after the error, going back to continue the search? Yes, it could, but there would need to be some delay, probably "Sleep" for some arbitary number of seconds, 'wait4usb' would simply return immediately. Also, could pdev not be used? Specifying the partition with a &...

The problem with Puppy not booting when there are multiple usb drives is in the' wait4usb' routine used by the 'init' script. It returns as soon as a single usb drive becomes "seen", unfortunately this might not be the required one. Unfortunately the real solution is not simple, the 'init'...

@gyrog All of my builds include: http://distro.ibiblio.org/puppylinux/pet_packages-noarch/grub2_efi-2.02.2018.08-fd64.pet which puts /usr/share/grub2-efi/grubia32.efi /usr/share/grub2-efi/grubx64.efi into the builds. Are these compatible with what frugalpup expects? Should the noarch pet be updated...

:idea: Which is why, after I use gparted to format the 2 or 3 partitions on the USB-Key, on the partition which will house the Puppy, I create the folder which will house it. Then, when frugalpup is running, all I have to do is select the folder. Great way to go, nicely avoids any confusion in the ...

Some comments: 1. FrugalPup assumes that Puppy is booting from an ALTERNATE boot device, not the main Windows "esp". 2. A facility to detect a Windows install and include an appropriate entry in the generated 'grub.cfg' would ne nice, maybe in a future version. 3. While a splash screen fac...

Am I correct in thinking that the frugalpup-20.sfs contains both 32-bit and 64-bit "components"? Is this so 32-bit systems can be installed from 64-bit systems and vice-versa? The 32bit and 64bit components have nothing to do with running FrugalPup or the Puppy it is running under, Frugal...

------------ About FrugalPup ------------ The current release of FrugalPup v41, DiskPup v41, StickPup v41 and f2StickPup v41 - Puppy frugal installer, along with e3StickPup v41 and e4StickPup v41, is announced here, https://forum.puppylinux.com/viewtopic.php?p=98498#p98498 . It can be downloaded fro...