puppy boot from USB using YUMI

Message

#16 Post by **BÃ©Ã¨m** » Sun 30 Oct 2011, 23:48

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.

mahaju · #17 Post by **mahaju** » Mon 31 Oct 2011, 01:06

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)

mahaju · #18 Post by **mahaju** » Mon 31 Oct 2011, 01:44

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

(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

rcrsn51 · #19 Post by **rcrsn51** » Mon 31 Oct 2011, 01:46

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.

mahaju · #20 Post by **mahaju** » Mon 31 Oct 2011, 01:50

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)

#21 Post by **BÃ©Ã¨m** » Mon 31 Oct 2011, 08:34

mahaju,
As I told you in my first reply it will be difficult to find YUMI knowledge here.
Please realize YUMI is not part of puppy.
Therefor I advised to look for help in the YUMI support structure.

As you see from a previous post, I have lupu/lucid 5.2.7, warypuppy 5 and PCLinuxOS set up and working as advertised. No need to copy whatever file to root.
My puppy.cfg is

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

Looks pretty like yours.

As for files to delete, they are so tiny that it is a waste of time to delete those not needed. I always leave every file, which in total may take only 1MB of space.

Again your problem is not a puppy issue, but a YUMI one.
Unless you have corrupted files. So do a checksum on them.

Or you can try another puppy version then 5.1.1 as I did.

mahaju · #22 Post by **mahaju** » Mon 31 Oct 2011, 08:39

I guess it is true this is not a specific puppy problem
Also I don't think there is any forum dedicated to YUMI
In the Yumi website it says says puppy is one of the supported distros but I think they may be wrong
However, copying all the puppy files to root of the pendrive has solved the kernel panic problem

#23 Post by **BÃ©Ã¨m** » Mon 31 Oct 2011, 08:55

There is a contact entry on the YUMI website to ask for help.

In step 2 there are 2 puppy's referenced. The warypuppy and just puppy.
I used them both to create a 5.2.7 and a wary 5.

The strange thing in your situation is that your cfg file points to multiboot/puppy and yet when you copy the files to root you got it working.
I didn't have to do that.
So that is the question you have to ask through contact on the YUMI website.

As for me puppy boot from USB using YUMI works as advertised.

mahaju · #24 Post by **mahaju** » Mon 31 Oct 2011, 08:59

Oh ok I will recheck everything I did to see if there is any mistake
Thank you for your time and effort
By the way, the same problem is seen when I boot the pendrive in VMWare as well, but after I copied everything to root it is working in VMWare as well as my desktop
Still I will recheck everything to see what else can be done
Thank you very much

#25 Post by **BÃ©Ã¨m** » Mon 31 Oct 2011, 09:02

It was interesting to try out YUMI.
I post with FireFox which came with PCLinuxOS-KDE which I booted from the USBflash with YUMI.

Burn_IT · #26 Post by **Burn_IT** » Mon 31 Oct 2011, 09:06

I still think adding the PSUBDIR parameter after the pmedia in YUMI may work.

It won't hurt to try it.

mahaju · #27 Post by **mahaju** » Mon 31 Oct 2011, 09:19

Thanks I will try it
I will update the thread when I get a chance

rcrsn51 · #28 Post by **rcrsn51** » Mon 31 Oct 2011, 11:47

Burn_IT wrote:I still think adding the PSUBDIR parameter after the pmedia in YUMI may work.

I tried that and it failed. Apparently, on a flash drive install, Puppy won't search that far down for the sfs file.

#29 Post by **BÃ©Ã¨m** » Mon 31 Oct 2011, 12:16

Strange.
I still am not convinced that YUMI follows some kind of grub logic.
There is no menu.lst.

My puppy files are 2 deep.
I had no need to duplicate the puppy files in root.

Code: Select all

# ls -l
total 162868
-rwxr-xr-x 1 root root      2048 2011-08-08 06:42 boot.cat
-rwxr-xr-x 1 root root       126 2011-08-08 06:42 boot.msg
-rwxr-xr-x 1 root root      1200 2011-08-08 06:42 help2.msg
-rwxr-xr-x 1 root root      1235 2011-08-08 06:42 help.msg
-rwxr-xr-x 1 root root   1902305 2011-08-08 06:35 initrd.gz
-rwxr-xr-x 1 root root     24576 2010-10-22 23:07 isolinux.bin
-rwxr-xr-x 1 root root       151 2011-08-08 06:42 isolinux.cfg
-rwxr-xr-x 1 root root     19790 2011-08-08 06:42 logo.16
-rwxr-xr-x 1 root root 129015824 2011-08-08 06:42 lupu_527.sfs
-rwxr-xr-x 1 root root  33554432 2011-10-30 22:43 lupusave-R40_lucid_527.3fs
-rwxr-xr-x 1 root root   2228816 2011-08-08 06:33 vmlinuz
# pwd
/mnt/sdc1/multiboot/puppy
#

rcrsn51 · #30 Post by **rcrsn51** » Mon 31 Oct 2011, 12:19

@Béèm: It may be that the Puppies you installed have improved logic that searches deeper for the sfs file. BK has been modifying this procedure.

#31 Post by **BÃ©Ã¨m** » Mon 31 Oct 2011, 12:22

That could be.
When having a bit more time, I'll try he 5.1.1
But if I remember well, 5.1.1 has always been kinda troublesome.

Burn_IT · #32 Post by **Burn_IT** » Mon 31 Oct 2011, 12:38

@Béèm: PSUBDIR is a Puppy parameter not Grub4Dos.

My directories are only one level deep. I will try it in a minute (with Grub4Dos) when I've got 5.3 to try. Unfortunately I have to work with Windows so reboots only take place in slack periods and at home.

#33 Post by **BÃ©Ã¨m** » Mon 31 Oct 2011, 12:48

Burn_IT wrote:@Béèm: PSUBDIR is a Puppy parameter not Grub4Dos.

My directories are only one level deep. I will try it in a minute (with Grub4Dos) when I've got 5.3 to try. Unfortunately I have to work with Windows so reboots only take place in slack periods and at home.

Yes you're right, but I never use it.
But what I wanted to say, there is no menu.lst, but maybe the puppy.cfg file of YUMI do act the same way.

Burn_IT · #34 Post by **Burn_IT** » Mon 31 Oct 2011, 13:25

But what I wanted to say, there is no menu.lst, but maybe the puppy.cfg file of YUMI do act the same way.

A Rose by any other name.... etc.

I've got so used to switching between different bits of software over the years that I tend to think of script and program languages in terms of what they do, rather than what particular dialect they are written in.

umair · #35 Post by **umair** » Wed 20 Nov 2013, 13:00

Hello Everyone:
I was looking for the solution of the problem as mahaju have. find this thread. By using YUMI, it usually fails to boot the ISO of Puppy versions with the error that "no xxx.sfs" file found. The solution which I used and will work 100 % is that.

1 . make a folder e.g puppy in your multiboot/isos folder. Extract all the files of puppy linux in this folder , which ever version you want.
2. make the changes of your menu.lst which you will find in menu folder and add the following entry:

title Linux Puppy (USB Boot)
root=(hd0,0)
kernel /multiboot/isos/puppy/vmlinuz PMEDIA=usbflash PDEV1=sdb1 psubdir=multiboot/isos/puppy pfix=fsck
initrd /multiboot/isos/xprecise/initrd.gz

Thats it: By adding the above entry you can boot your puppy linux from usb drive as well as you can place all your puppy files in separate folder.

Hope that this will help someone:
(UMAIR)

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

puppy boot from USB using YUMI