puppy boot from USB using YUMI

Booting, installing, newbie
Message
Author
User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

puppy boot from USB using YUMI

#1 Post by mahaju »

I have made a bootable pendrive following the instructions here
http://www.pendrivelinux.com/yumi-multi ... b-creator/
I am not quite sure about all the steps that take place during booting
However, I was able to install DSL and Puppy 511
DSL boots easily while Puppy 511 says that it can't find the lupu-511.sfs file
The puppy linux files are located at

Code: Select all

<USB_ROOT>:\multiboot\puppy
It has initrd.gz, lupu-511.sfs, vmlinuz as well as the other files

The menu in the bootloader that allows me to boot puppy can be edited by pressing the tab key. It contains the line

Code: Select all

multiboot/puppy/vmlinuz initrd=/multiboot/puppy/initrd.gz pmedia=usbflash
Pressing Enter here starts booting of puppy and after a few lines of messages it says it cannot find lupu-511.sfs then goes into some kind of command prompt (bash I think)

How can I correct this?

Thanks

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#2 Post by Béèm »

I am afraid few people use YUMI.
You might not have an answer very soon.

It seems more like a YUMI setup issue.
Isn't there a YUMI forum to address the issue?
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#3 Post by mahaju »

It boots the other distros fine (Tinycore, Slax, DSL, as well as other programs such as AVG Antivirus boot disk, freeDOS and many others) and according to it's website Puppy version 5* are directly supported by the current release of YUMI

I was thinking may be there is some kind of problem with the location of the files in their folders

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#4 Post by Béèm »

I don't know YUMI, so I can't tell if the code you reference is correct or not.
You say after a few lines....
What do the few lines say?
I suspect the boot of puppy is starting.
Did you verify the check sum of the puppy files?
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#5 Post by mahaju »

the first two lines are the loading of vmlinuz and initrd I think
Then when looking for the sfs file it says it cannot find it
rcrsn51 suggested I put the sfs file on the USB root instead of <root>\multiboot\puppy folder [which is the default location selected by YUMI]

I cannot try this right now, but later in the evening, after I try it I will update this thread with the result

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

Re: puppy boot from USB using YUMI

#6 Post by nooby »

mahaju wrote:...
The menu in the bootloader that allows me to boot puppy can be edited by pressing the tab key. It contains the line

Code: Select all

multiboot/puppy/vmlinuz initrd=/multiboot/puppy/initrd.gz pmedia=usbflash
rcrsn51 suggests ...
I trust rcrsn51, he has helped me and many others numerous times
during the three years I've been active here.

As he say. Try to edit this part multiboot/puppy/vmlinuz initrd=/multiboot/puppy/initrd.gz pmedia=usbflash

to /puppy/vmlinuz initrd=/multiboot/puppy/initrd.gz pmedia=usbflash
and you need to move the whole puppy folder with all it's files outside of the directory multiboot.

Sure I can be wrong but maybe being that many dirs sub makes the boot not being able to see them.

A termporal thing would be to create a test boot outside of it and keep it inside just for the fun of it.

You simply make a copy of the whole puppy dir outside of multiboot.

that way it is still there. Unless the USB will get too full having so many OS to boot.

So the best bet is to move it outside. You don't need the puppy iso as
long as you have the three files.

Here is how 528 usually do things in isolinux.

Code: Select all

label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd
So them even have vmlinuz and initrd.gz directly on / on the usb.

If yumi has grub or grub4dos then it more likely look like this.

title lupu-528
rootnoverify (hd0,0)
kernel /lupu-528/vmlinuz psubdir=lupu-528 puppy pfix=fsck
initrd /lupu-528/initrd.gz

so that is only one step down from / having a dir named lupu-528
and you are two step down having first the /multiboot/puppy/vwmlinuz

this part pmedia=usbflash can be important. if you have a usb external drive that is SATA then maybe it should be pmedia=usbhd or pmedia=usbSATA I am not sure.

So I would try to move puppy out on to being its own there. And then change the boot code accordingly.

Tell us if it worked.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#7 Post by mahaju »

Hello
Thank you for your suggestions
As per rcrsn51 I moved the lupu-511.sfs to the pendrive root
It is now detected, but now the computer is showing Kernel Panic and the system halts after that
And I don't think YUMI has grub
I'm not much sure about the details but I think it boots on syslinux

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#8 Post by nooby »

Yes I took the isolinux directly from the puppy iso so that code
should be the recommended.

You have to copy the yumi boot code to us so we can look at it.
It is most likely a very simple to correct thing somewhere.

Don't give up on it. Rescue is just a detail that needs to be changed.

I will go do other things now. Test ArchBang booting so I will most
likely abandon you here and hope others can help you.

if none volunteer then use the links in my signature and try to find others with kernel panic and you can compare how them set up things.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#9 Post by rcrsn51 »

mahaju wrote:It is now detected, but now the computer is showing Kernel Panic and the system halts after that.
I would recommend that you get another flash drive and do a single install of Puppy, instead of using YUMI. That will help to isolate the problem.

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#10 Post by mahaju »

I already have one so I know it is possible
I used YUMI because I could have a number of Linuxes on a single pendrive with it
In my other pen drive with only puppy, it boots normally and I even get the welcome screen, the one in which we have to press F2 within 5 seconds to enter further boot options
By the way, that screen doesn't show up in the case of my YUMI pendrive
It directly says loading initrd and vmlinuz, then reads the hard disk and then searches for the sfs file. It was at this point where it said it could not find lupu-511.sfs before. That problem is solved by copying the sfs file to the pendrive root, however, now I have the Kernel Panic error

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#11 Post by rcrsn51 »

The next thing I would check is that the files on your flash drive are identical to the ones in the ISO.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#12 Post by Burn_IT »

My thought is that you should put the files back where they were and add:
PSUBDIR=puppy after the PMEDIA=usbflash

This is roughly how I do it with Grub4dos, and I have lots of bootable bits on the same partition. Here's my menu.lst The case of the filenames must match. This has Hiren on the USB as well.

Code: Select all

color blue/green yellow/red white/magenta white/magenta
timeout 30
default /default

title Puppy Linux Lucid 528 frugal
find --set-root /lupu5000/VMLINUZ
kernel /lupu5000/VMLINUZ pmedia=idehd psubdir=lupu5000 pfix=nox
initrd /lupu5000/INITRD.GZ

title Puppy Linux 420 Frugal
find --set-root /puppy420/vmlinuz
kernel /puppy420/vmlinuz pmedia=idehd psubdir=puppy420
initrd /puppy420/initrd.gz

title Puppy Linux 420 Frugal fresh
find --set-root /puppy420/vmlinuz
kernel /puppy420/vmlinuz pmedia=idehd psubdir=puppy420 pfix=ram
initrd /puppy420/initrd.gz


title Puppy Linux Lucid 528 Frugal fresh
find --set-root /lupu5000/VMLINUZ
kernel /lupu5000/VMLINUZ pmedia=idehd psubdir=lupu5000 pfix=ram
initrd /lupu5000/INITRD.GZ
 
title Puppy Linux Lucid 529 frugal
find --set-root /luci3hd/VMLINUZ
kernel /luci3hd/VMLINUZ pmedia=idehd psubdir=luci3hd pfix=nox
initrd /luci3hd/INITRD.GZ

title Puppy Linux Lucid 529 frugal fresh
find --set-root /luci3hd/VMLINUZ
kernel /luci3hd/VMLINUZ pmedia=idehd psubdir=luci3hd pfix=ram
initrd /luci3hd/INITRD.GZ


write (md)0x220+1 !BAT\necho -n -P:0000 $[0107] Hiren's BootCD 14.1 \0 && initscript (md)0x220+1

title Boot From Hard Drive (Windows Vista/7/2008 or Xp)\n
find --set-root --ignore-floppies --ignore-cd /bootmgr || find --set-root --ignore-floppies --ignore-cd /ntldr || rootnoverify (hd0) && chainloader +1 && boot
map () (hd0) && map (hd0) () && map --rehook
find --set-root --devices=h /bootmgr || find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /bootmgr || chainloader /ntldr

title \n
root

title Mini Windows Xp\nRun Antivirus and other windows programs
# example password: test 
# password --md5 $1$gNe0$KZPOE8wNbTNSKOzrajuoB0
find --set-root /HBCD/XP/XP.BIN
chainloader /HBCD/XP/XP.BIN

title Dos Programs\nRun Dos Programs
find --set-root /HBCD/Dos/dos.gz
map --mem /HBCD/Dos/dos.gz (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
map --floppies=1

title Linux based rescue environment (Parted Magic 6.6)\nTo manage partitions, backup and recovery
set pm=/HBCD/Boot/pmagic.lst
find --set-root %pm%
set lang=us
set opt=
configfile %pm%

title \n
root

title Windows Memory Diagnostic\n
find --set-root /HBCD/Boot/wmemtest.gz
kernel /HBCD/Boot/memdisk
initrd /HBCD/Boot/wmemtest.gz

title MemTest86+\n
find --set-root /HBCD/Boot/memtest.gz
map --mem /HBCD/Boot/memtest.gz (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
map --floppies=1

title Offline NT/2000/XP/Vista/7 Password Changer\nWindows Password Reset 2011-05-11
find --set-root /HBCD/Boot/chntpw
set opt=vga=1
clear
echo Press ENTER to boot, or give linux kernel boot options first if needed.
echo Some that I have to use once in a while:
echo boot: nousb     - to turn off USB if not used and it causes problems
echo boot: irqpoll   - if some drivers hang with irq problem messages
echo boot: vga=ask   - if you have problems with the videomode
echo boot: nodrivers - skip automatic disk driver loading
echo
set /p opt=boot: 
kernel /HBCD/Boot/chntpw %opt%
initrd /HBCD/Boot/chntpw.gz
"Just think of it as leaving early to avoid the rush" - T Pratchett

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#13 Post by Béèm »

@Burn_IT: This YUMI thing doesn't have a menu.lst.

@ALL
Intrigued by it I executed YUMI in wine.
I was only allowed in step 2 to select warry pupp5.X
In step 3 I pointed to the Wary puppy 5.1.1 ISO.

The USB partition now contains YUMI and the waryuppy files.
I can boot from the USB partition and I am working in it now.

I see that in the warrypuppy.cfg file pmedia=usb is used and not usbflash.

mahaju, can you post the copy of the cfg file corresponding to the puppy version you installed.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
Béèm
Posts: 513
Joined: Sun 16 Apr 2006, 16:18
Location: Brussels

#14 Post by Béèm »

Béèm wrote:@Burn_IT: This YUMI thing doesn't have a menu.lst.

@ALL
Intrigued by it I executed YUMI in wine.
I was only allowed in step 2 to select warry pupp5.X
In step 3 I pointed to the Wary puppy 5.1.1 ISO.

The USB partition now contains YUMI and the waryuppy files.
I can boot from the USB partition and I am working in it now.

I see that in the warrypuppy.cfg file pmedia=usb is used and not usbflash.

mahaju, can you post the copy of the cfg file corresponding to the puppy version you installed.
I tried YUMI again and found another entry in step 2 to choose another puppy linux.
It allowed only to choose a lucid/lup ISO.
I choosed the 5.2.7 and creation of this second puppy linux was ok.
I can now choose to boot from wary or from lucid/lupu 5.2.7
Strangely the corresponding cfg file now contains pmedia= usbflash.

So two puppy's installed without an issue.

mahaju, I don't know why it don't work for you.
Puppy Linux 2.02 SMkey, KDE354mini, wine0.9.20, devx-qt-renamed.
Puppy Linux 2.10r1 SMkey, JWM, devx_qt_renamed_210, KDE355mini

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#15 Post by Burn_IT »

@Burn_IT: This YUMI thing doesn't have a menu.lst.
Iwas aware of that. I was illustrating the use of PSUBDIR with multiple directories ( and the fact that he could have used Grub4Dos)
"Just think of it as leaving early to avoid the rush" - T Pratchett

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#16 Post by Béèm »

Burn_IT wrote:
@Burn_IT: This YUMI thing doesn't have a menu.lst.
Iwas aware of that. I was illustrating the use of PSUBDIR with multiple directories ( and the fact that he could have used Grub4Dos)
I have experimented a bit more with YUMI and added PCLOS to the USB drive.

I feel that YUMI doesn't permit another way of working like using Grub4Dos.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#17 Post by mahaju »

It seems even the veterans are stumped by this
This is the cfg file for booting puppy

Code: Select all

# Simple Menu Created by Lance http://www.pendrivelinux.com for YUMI - (Your USB Multiboot Installer)
menu title Puppy Boot Menu
menu background yumi.png
MENU TABMSG  http://www.pendrivelinux.com
MENU WIDTH 72
MENU MARGIN 10
MENU VSHIFT 3
MENU HSHIFT 6
MENU ROWS 15
MENU TABMSGROW 20
MENU TIMEOUTROW 22
menu color title 1;36;44 #66A0FF #00000000 none
menu color hotsel 30;47 #C00000 #DDDDDDDD
menu color sel 30;47 #000000 #FFFFFFFF
menu color border 30;44	#D00000 #00000000 std
menu color scrollbar 30;44 #DDDDDDDD #00000000 none

default live

label live
 menu label ^Run Puppy Linux from this USB
 kernel /multiboot/puppy/vmlinuz
 append initrd=/multiboot/puppy/initrd.gz pmedia=usbflash
  
MENU SEPARATOR 
label <-- Back to Main Menu
 kernel vesamenu.c32
 append /multiboot/syslinux.cfg 
And like I said this is not grub. I am not sure but I think the bootloader here is called syslinux or something
I am attaching a screenshot of the files installed by Yumi in the folder containing the multiboot system files

From here, the files for the individual operating systems are in their respective folders, like puppy, tinycore and dsl. The folder menu contains the .cfg files for all the distros and other utility programs like the AVG boot CD, freeDOS, etc

And by all the code that is present in the puppy.cfg file, all that shows up in the YUMI boot screen for puppy, that can be edited at the command line, is

Code: Select all

multiboot/puppy/vmlinuz initrd=/multiboot/puppy/initrd.gz pmedia=usbflash
The other code is for formating the display, such as displaying the window borders etc I think

(by the way, the pendrive root contains a folder called multiboot and the files shown in this screenshot are INSIDE the multiboot directory)
Attachments
multiboot_root.jpg
(89.15 KiB) Downloaded 645 times
Last edited by mahaju on Tue 15 Nov 2011, 14:36, edited 2 times in total.

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#18 Post by mahaju »

UPDATE:

OK I copied everything related to puppy to the pendrive root as well as keeping a copy in the default location as installed by YUMI

It boots fine with the usbflash option, at least in VMWare player
Now I just have to go home and test it in my computer in the evening (but I am hoping it should work)

Could anyone please tell me which of the puppy files I may delete from the root of my pendrive, so that I can save up some space on it? I suppose I could find out by check deleting each and every file, but I'm too lazy :P (OR maybe perhaps edit the cfg file somewhere so that it will look for all the necessary files in the puppy directory created by YUMI only; I should also point out that this problem starts after the booting process of puppy begins, so I don't know if editing the configuration files of the bootloader will do anything or not)

I would also like to install firefox as well as flash (and may be perhaps some other utilities as well) for this puppy (lupu511) and have them saved to the pen drive so that I can have firefox and other utilities wherever I go, but I don't want other settings such as ethernet, graphics, touch pad settings (if using a laptop), etc to be saved in the USB. Is there any way to do this?

Thank you very much
Last edited by mahaju on Mon 31 Oct 2011, 01:48, edited 1 time in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#19 Post by rcrsn51 »

mahaju wrote:It seems even the veterans are stumped by this
In Windows, I used YUMI to set up a Lupu 511 flash drive. I moved JUST the sfs file to the root of the drive. It booted and ran fine.

User avatar
mahaju
Posts: 487
Joined: Mon 11 Oct 2010, 07:11
Location: between the keyboard and the chair

#20 Post by mahaju »

In my case lupu511 is detected after I did as you told, however, as I mentioned it shows kernel panic after loading the sfs file

but I now copied all the puppy files to root and kept a copy in the directories as installed by YUMI and it boots fine, at least in my virtual machine

Please see this
http://www.murga-linux.com/puppy/viewto ... 109#578109 (my previous post in this thread)

Post Reply