Frugal Puppy won't boot, Error 15: file not found (Solved)

[tikbalang]

something is messing up the LFN. since you have winxp, use it to copy files from the CD/iso. if iso, extract first with 7zip. if you are working from DOS, load a suitable lfn driver first before copying from cd.

http://sta.c64.org/lfnemu.html

i tried to do what you're trying to do now but 8.3 filenames are not a priority for puppy devs.

[tikbalang]

again, since you have winxp, add grub4dos to boot.ini with this line at the bottom:

Code: Select all

c:\grldr="Grub4DOS"

then copy GRLDR and your menu.lst to where boot.ini exists, usually c:\. i recommend grub4dos because it can "search". you can use the .LST file i posted in the previous page.

if you want you can boot any puppy os from DOS using linld.com:

http://busybox.net/~vda/linld/

LUPU.BAT

Code: Select all

:: LUPU.BAT
@echo off
linld.com image=/lupu/vmlinuz initrd=/lupu/initrd.gz cl=@lupu.cl %1 %2 %3

LUPU.CL

Code: Select all

psubdir=lupu
acpi=force

[Béèm]

still not working. :/ However, I think I know where the problem is.

Puppy boots, but the loading screens don't say anything about preferences file.

With the CD, it does find it, however, I notice it only does it after it does a "deeper search," which comes up after "Searching for Puppy files in disk drives."

I think that's the problem. The LiveCD is searching 2 levels down, but the HDD boot is only searching the main sda3 level.

Can I add that deep search into the grub code? I tried looking but can't find anything.

Does this mean you don't have the file not found error 15 anymore?

What do you mean by preferences file?
This is a new concept not known to me in puppy. Please be precise or we are getting nowhere.

There is no need to change to change grub code or whatever is in your mind.

All is done and defined in menu.lst.

Try to add the simplest entries in menu.lst:

Code: Select all

title Lucid Puppy 5.2.5 Frugal (on /dev/sda3) test
kernel (hd0,2)/LuPu525/vmlinuz
initrd (hd0,2)/LuPu525/initrd.gz
boot 

Also if I understand you well your puppy files are in LuPu525.

boot from the CD
mount sda3
enter command cd /mnt/sda3/LuPu525
enter command ls -l
copy/paste the result here

[ICPUG]

I don't think we have the full information here.

I wonder if you are storing your puppy sfs file and preference file (the pupsave file?) in different places. Please tell us where they are!

I would prefer they should be in the same place (with vmlinuz and initrd.gz)

With this info we can better tell you what the menu.lst should read.

grub is only booting the vmlinuz and initrd.gz and it is working. Puppy boots the rest and it will boot from deeper levels whether from CD or HD. However, we have to tell it by means of the pmedia, pdev1, psubdir codes.

It seems the only people writing here who understand these codes properly are rcrsn51, Beem and myself!

Yes, you can leave them out (and the CD does except for pmedia), which is why it appears to find deeper levels at the moment. However leaving them out slows the boot process because it goes searching everywhere.

If you stick the sfs file, save file, vmlinuz and initrd.gz all in:
sda3/lupu525 (note I use single case as a preference - the KISS principle)

then the use of:
pmedia=atahd or pmedia=idehd
pdev1=sda3
psubdir=lupu525

should boot properly and the quickest you are going to get.

If you really want to go to deeper levels then it is possible but please tell us where everything is and we can advise better.

There is an advantage to keeping all the files associated with a particular Puppy in one folder. Namely that you can have multiple Puppies on your machine and with menu.lst set up correctly they will boot quickly and not interfere with each other.

[Sp3ctre18]

SOLVED!

I wonder if you are storing your puppy sfs file and preference file (the pupsave file?) in different places. Please tell us where they are!

I would prefer they should be in the same place (with vmlinuz and initrd.gz)

Thank you!! This along with your explanation of how it should work (along with a bit I read on a page called "how Puppy works" or something like that) gave me enough to figure it out.

You were correct, the problem was that the sfs and 3fs files were NOT in the same place. (I had removed the psubsir command in grub and it didn't help.)

I'm sorry if I had not given enough info. I appreciate everyone's patience and hope you can understand as a totally new Linux user, I didn't know what all the relevant info was from all those steps in the installation process. File placements should be just like what the instructions say because that's what I followed. Still, if I hadn't figured it out now, I was was going to post my whole directory and file structure of sda3.

So, on sda3, I had the 3fs preferences/pupsave file, the boot folder, and the LuPu525 folder, along with a couple of other things such as swap. Once I put the 3fs file into the LuPu525 folder (where vmlinuz, initrd.gz, lupu_525.sfs, and menu.lst are), it booted just fine. All files were discovered in boot, wireless is set up, my non-default wallpaper is there, so all looks good!

Now that you know where those main files were, I have to ask: was there a mistake somewhere? I know the installation instructions I followed used Puppy 4.00 as an example, so could it be that things work a little differently in 5.2.5? For my own education in GRUB, would it have been possible to keep the .3fs file on /dev/sda3 by adding a command in GRUB, or MUST it be (in my case) inside /dev/sda3/LuPu525 as I have it now?

btw, Béèm:
Yes, I no longer had error 15; it was booting but into a clean boot like from a first-time or pfix=ram boot.
Preferences file is the save file, with extension .3fs.

Thanks again very much to everyone.

For any future readers, my current menu.lst is the same as the one I posted before, but with all uuid lines removed, with pdev1=sda3 at the end of the kernel line, and with "psubdir" part removed...changes that probably didn't make a difference (?), imo, seeing how it was the actual placement of the .3fs file that was the problem. My Windows boot doesn't work but I expect I can fix that easily.

[ICPUG]

Great - we have a solution!

Whether there was a mistake in the original instructions? I don't know - I didn't read them! I don't think Puppy 5.2.5 is much different from 4.0, except I don't think Puppy 4.0 allowed to place the files at levels deeper than 1 folder.

Yes - it IS possible to keep the 3fs file separate. Indeed, you might be able to do it now if you have removed psubdir. If you remove the psubdir it should look all over the sda3 partition.

With all the files together the removal of the psubdir might slow the bootup slightly - as it will search all over the sda3 partition.

It has another effect if you later have multiple Puppy installations on sda3. It will find the 3fs files for the other puppies on the sda3 partition and you will have to select which one you need. What is more likely is you will run the next Puppy WITHOUT a 3fs file initially and it will pick up the one for Puppy 5.2.5 automatically and try to update it - potentially messing it up. I know - I've done that! In a multipup environment the use of psubdir is essential.

I think it worth mentioning that if you run a Live Puppy CD now it might find that 3fs file and try to change it. Run a Live puppy CD with pfix=ram or backup your 3fs file before running the Live CD and restore it afterwards if necessary.

[Béèm]

Sp3ctre18,
For the sake of fellow posters, can you edit the subject of initial post and add [SOLVED] at the end of it.

[Sp3ctre18]

Thanks for the info, ICPUG. Someday I feel like fiddling around I'll see if it works that way.

[mimmo]

when booting I have a message "inird.gz file not found"

I think that the problem is due to a corrupted directory
I have a "nouveu dossier" under my /mnt/home/puppy525
and I am not able to remove it

under windows the puppy525 directory is given as corupted

the problem is that I'm not able to erase or reformat this directory

any idea
/----------------------------------------------

OK I finaly whas able to see it under windows (I don't know what changed?) and removed the "new folder" ("nouveau dossier" in french) and then restarted puppy with out pb