How to boot USB key if BIOS won't boot from USB?
How to boot USB key if BIOS won't boot from USB?
I have puppy on an old computer.
This computer can not be boot from USB key.
It is also a small computer that has no CDROM.
But I have a USB key slot and I was wondering (like maybe other newbees)...
Would it be possible to configure GRUB to set a path to boot a frugal (or full) install of puppy that would not be on the hard disk but on the one and only USB key slot so that it would be possible to run puppy from the USB key.
So grub would run from the hard disk, mount (?) the USB key, and load puppy onto the RAM.
So, like that it would be actually possible to boot from a USB key even if it is not bootable according to the bios...
I m talking crazy or is it possible ?
Thank for your answers,
Cheers,
Dam
This computer can not be boot from USB key.
It is also a small computer that has no CDROM.
But I have a USB key slot and I was wondering (like maybe other newbees)...
Would it be possible to configure GRUB to set a path to boot a frugal (or full) install of puppy that would not be on the hard disk but on the one and only USB key slot so that it would be possible to run puppy from the USB key.
So grub would run from the hard disk, mount (?) the USB key, and load puppy onto the RAM.
So, like that it would be actually possible to boot from a USB key even if it is not bootable according to the bios...
I m talking crazy or is it possible ?
Thank for your answers,
Cheers,
Dam
It's easy. You set up GRUB for a regular frugal install, except that the first two Puppy files (vmlinuz and initrd.gz) are on the hard drive and the second two files (pupxxx.sfs and zdrvxxx.sfs) are on the USB drive. [Edit] In newer versions of Puppy, the first two files must also be on the USB drive. Then change the GRUB menu argument to PMEDIA=usbflash. Once the kernel has loaded off your hard drive, Puppy's hardware detection will find itself on the USB drive. However, this old machine is probably USB1.0 and will be slow to load Puppy.
Last edited by rcrsn51 on Tue 25 Sep 2007, 19:58, edited 1 time in total.
boot from USB key without bios recognization
Thank you for your answer rcrsn51 ,
ok, so for what I understand step 1, I just copy vmlinuz and initrd.gz on the hard disk (hdaX), must be on the root I think, and the second two files on the USB keybe on the root two. I do not need to touch GRUB at this very moment, isn't it, it is just about copying files.
All right, si if I got it, step 2, I change my grub settings and it should look like that :
title Puppy Linux
root (hdX,X)
kernel /vmlinuz root=/dev/ram0 PMEDIA=usbflash
initrd /initrd.gz
I have USB 2.0 so I think it will be ok with the speed.
Now, I think that from puppy 2.16 and forthcoming puppy 2.20 I can ask the universal installer to set a frugal install and then move the two files to the USB key and rewrite GRUB menu.lst. But I have the 2.17 version and there are many issues with the installer so I will have to try to do things manually.
I will post the results later.
Thank you for your following ,
Cheers,
Dam
It's easy. You set up GRUB for a regular frugal install, except that the first two Puppy files (vmlinuz and initrd.gz) are on the hard drive and the second two files (pupxxx.sfs and zdrvxxx.sfs) are on the USB drive.
ok, so for what I understand step 1, I just copy vmlinuz and initrd.gz on the hard disk (hdaX), must be on the root I think, and the second two files on the USB keybe on the root two. I do not need to touch GRUB at this very moment, isn't it, it is just about copying files.
Then change the GRUB menu argument to PMEDIA=usbflash. Once the kernel has loaded off your hard drive, Puppy's hardware detection will find itself on the USB drive.
All right, si if I got it, step 2, I change my grub settings and it should look like that :
title Puppy Linux
root (hdX,X)
kernel /vmlinuz root=/dev/ram0 PMEDIA=usbflash
initrd /initrd.gz
I have USB 2.0 so I think it will be ok with the speed.
Now, I think that from puppy 2.16 and forthcoming puppy 2.20 I can ask the universal installer to set a frugal install and then move the two files to the USB key and rewrite GRUB menu.lst. But I have the 2.17 version and there are many issues with the installer so I will have to try to do things manually.
I will post the results later.
Thank you for your following ,
Cheers,
Dam
-
- Posts: 186
- Joined: Sun 17 Jun 2007, 18:25
Wakepup floppy
As stated in his initial post: he has no CD-ROM.
NST: Could you elaborate on how exactly the wakepup floppy can be used to boot to a USB? I have the same problem (i.e. bios cannot be set to boot from USB). It seems this might be the simplest solution.
NST: Could you elaborate on how exactly the wakepup floppy can be used to boot to a USB? I have the same problem (i.e. bios cannot be set to boot from USB). It seems this might be the simplest solution.
[i]Welcome to my weird, wild, wonderful, wired world![/i]
-
- Posts: 186
- Joined: Sun 17 Jun 2007, 18:25
Re: Wakepup floppy
Format floppy, then chkdisk it if you have dos or windows. No bad sectors allowed.macadavy wrote:NST: Could you elaborate on how exactly the wakepup floppy can be used to boot to a USB? I have the same problem (i.e. bios cannot be set to boot from USB). It seems this might be the simplest solution.
Format usb stick as FAT32
Copy Puppy onto usb stick, same as for frugal hd install.
Make wakepup floppy from within Puppy: Menu-Setup-Wakepup.
Hope that helps!
--97T--
Re: Wakepup floppy
if interested, provide feedback from this image:NinerSevenTango wrote:Make wakepup floppy from within Puppy: Menu-Setup-Wakepup.
http://www.murga-linux.com/puppy/viewto ... 593#139593
instructions are here:
http://www.murga-linux.com/puppy/viewto ... 924#122924
On the road to try
I just wanted to thanks everybody,
I can not use wake up puppy because I have only one USB port...
I will try rcrsn51 way, though I had no answer on my doubts.
Will try anyway and post my result.
Cheers,
Dam
I can not use wake up puppy because I have only one USB port...
I will try rcrsn51 way, though I had no answer on my doubts.
Will try anyway and post my result.
Cheers,
Dam
and another possible solution is to use grub to boot a wakepup floppy image that is on your hdisk, which then loads the usbkey. which is what i've done. this is the portion of my grub's menu.lst, using memdisk.bin to load wakepup2.img, which i can then use to boot usbkey:
Code: Select all
title wakepup
kernel (hd0,2)/boot/grub/memdisk.bin
initrd (hd0,0)/lib/wakepup2.img
Not that easy
OK, so it didn't work with puppy 2.17. I have :It's easy. You set up GRUB for a regular frugal install, except that the first two Puppy files (vmlinuz and initrd.gz) are on the hard drive and the second two files (pupxxx.sfs and zdrvxxx.sfs) are on the USB drive. Then change the GRUB menu argument to PMEDIA=usbflash. Once the kernel has loaded off your hard drive, Puppy's hardware detection will find itself on the USB drive. However, this old machine is probably USB1.0 and will be slow to load Puppy.
I'm no guru , I will try with 2.16 too and post,error, cannot find Puppy on 'usbflash' boot media;
PUPMOD=1 PDEV1=
Exited to initial-ramdisk (initramfs) commandline...
(the Linux-guru can now debug, 'e3' editor is available)
Cheers,
Dam
no luck
Just to follow the last post :
exact same result with 2.16
Will try muggins advice
especially, what is memdisk.bin ? It is hard to find some info on it.
Thanks
Dam
exact same result with 2.16
Will try muggins advice
but can you be more precise in the procedure, I'm a real beginner...title wakepup
kernel (hd0,2)/boot/grub/memdisk.bin
initrd (hd0,0)/lib/wakepup2.img
especially, what is memdisk.bin ? It is hard to find some info on it.
Thanks
Dam
i've attached memdisk.bin.zip. just extract memdisk.bin to the same location as your grub menu.lst file, /boot/grub. Then copy the wakepup2.img to the same location, (from /lib/wakepup2.img).
Then add these lines to menu.lst:
[N.B. I'm assuming that your /boot/grub is on hda1. if not you'll have to alter the above to reflect your actual setup...hda1=(hd0,0) etc. also]
Also, you'll probably find usb-boot a bit slower. If it doesn't work, post back where it fails. john Doe also has another thread where he's making modifications to wakepup, & using his image could also be an option if you're unsuccessful. see here:
http://www.murga-linux.com/puppy/viewtopic.php?t=19831
Then add these lines to menu.lst:
Code: Select all
title wakepup
kernel (hd0,0)/boot/grub/memdisk.bin
initrd (hd0,0)/boot/grub/wakepup2.img
Also, you'll probably find usb-boot a bit slower. If it doesn't work, post back where it fails. john Doe also has another thread where he's making modifications to wakepup, & using his image could also be an option if you're unsuccessful. see here:
http://www.murga-linux.com/puppy/viewtopic.php?t=19831
- Attachments
-
- memdisk.bin.zip
- (5.33 KiB) Downloaded 340 times
Here's an example for "a path"
# Linux bootable partition config begins
title Puppy USB216
rootnoverify (hd0,0)
kernel (hd0,0)/boot/p216/vmlinuz ramdisk_size=100000 init=/etc/init PMEDIA=usbflash
initrd (hd0,0)/boot/p216/initrd.gz
# Linux bootable partition config ends
Suggestion: Leave all files on USB. Puppy definately(!) sometimes requieres the boot files in the root folder. Migrating the p2xx subfolders from one partition to another can be the end of this kind of puppy booting. Vmlinuz and initrd.gz has to be then in the root folder!
Hope that helps!
# Linux bootable partition config begins
title Puppy USB216
rootnoverify (hd0,0)
kernel (hd0,0)/boot/p216/vmlinuz ramdisk_size=100000 init=/etc/init PMEDIA=usbflash
initrd (hd0,0)/boot/p216/initrd.gz
# Linux bootable partition config ends
Suggestion: Leave all files on USB. Puppy definately(!) sometimes requieres the boot files in the root folder. Migrating the p2xx subfolders from one partition to another can be the end of this kind of puppy booting. Vmlinuz and initrd.gz has to be then in the root folder!
Hope that helps!
question
Hello,
and what is the meaning of rootnoverify in
Thanks you ,
Dam
mayB do you mean to leave all files on USB - FAT 32 - without copying Vmlinuz and initrd.gz on the harddisk partition root ? (maybe you stated that point in your sentence but I could not understand fully).Suggestion: Leave all files on USB. Puppy definately(!) sometimes requieres the boot files in the root folder. Migrating the p2xx subfolders from one partition to another can be the end of this kind of puppy booting. Vmlinuz and initrd.gz has to be then in the root folder!
and what is the meaning of rootnoverify in
Code: Select all
rootnoverify (hd0,0)
Thanks you ,
Dam
Sum up : Procedures for USB boot without USB boot OS
Thank you everybody,
There are many informations on that threat. So I will try to sum up, and it might be enhanced for a wiki later on.
First there is the 'fifty/fifty' procedure described simply by rcrsn51 :
An enhanced fifty/fifty procedure has been presented by MayB :
Still have to test this one.
Then, there is the 'wakepup Hard Disk' procedure clearly described by Muggins :
Copy memdisk.bin (that can be found at this link http://murga-linux.com/puppy/viewtopic.php?t=21520 ) and wakepup2.img (from /lib/wakepup2.img) to the same location as your grub menu.lst file, /boot/grub.
Then add these lines to menu.lst:
[N.B. I'm assuming that your /boot/grub is on hda1. if not you'll have to alter the above to reflect your actual setup...hda1=(hd0,0) etc. also]
Will try this one tomorrow and update,
Cheers and thanks for everybody support ,
Dam
There are many informations on that threat. So I will try to sum up, and it might be enhanced for a wiki later on.
First there is the 'fifty/fifty' procedure described simply by rcrsn51 :
maybe it worked for some people, please do post. In my case it did not work (version 2.16 and version 2.17)It's easy. You set up GRUB for a regular frugal install, except that the first two Puppy files (vmlinuz and initrd.gz) are on the hard drive and the second two files (pupxxx.sfs and zdrvxxx.sfs) are on the USB drive. Then change the GRUB menu argument to PMEDIA=usbflash. Once the kernel has loaded off your hard drive, Puppy's hardware detection will find itself on the USB drive. However, this old machine is probably USB1.0 and will be slow to load Puppy.
An enhanced fifty/fifty procedure has been presented by MayB :
you also would have to add the following code line in Grub :Suggestion: Leave all files on USB. Puppy definately(!) sometimes requieres the boot files in the root folder. Migrating the p2xx subfolders from one partition to another can be the end of this kind of puppy booting. Vmlinuz and initrd.gz has to be then in the root folder!
Code: Select all
# Linux bootable partition config begins
title Puppy USB216
rootnoverify (hd0,0)
kernel (hd0,0)/boot/p216/vmlinuz ramdisk_size=100000 init=/etc/init PMEDIA=usbflash
initrd (hd0,0)/boot/p216/initrd.gz
# Linux bootable partition config ends
Then, there is the 'wakepup Hard Disk' procedure clearly described by Muggins :
Copy memdisk.bin (that can be found at this link http://murga-linux.com/puppy/viewtopic.php?t=21520 ) and wakepup2.img (from /lib/wakepup2.img) to the same location as your grub menu.lst file, /boot/grub.
Then add these lines to menu.lst:
Code: Select all
title wakepup
kernel (hd0,0)/boot/grub/memdisk.bin
initrd (hd0,0)/boot/grub/wakepup2.img
Will try this one tomorrow and update,
Cheers and thanks for everybody support ,
Dam
rootnoverify
"rootnoverify"
Grabbed it from somewhere in this forum..!
No, the bootfiles exist twice, mainly where grub is pointed to.
I encountered when an install failed but the cdrom is still inserted puppy boots fine by confusing.
And as I said after migrating (on harddisks) the root directory was -is- requiered.
Cheers
Grabbed it from somewhere in this forum..!
No, the bootfiles exist twice, mainly where grub is pointed to.
I encountered when an install failed but the cdrom is still inserted puppy boots fine by confusing.
And as I said after migrating (on harddisks) the root directory was -is- requiered.
Cheers
Booting USB (Puppy 2.17.1)
Thanks everyone who posted help here.
I just used the Puppy Universal Installer to install Puppy 2.17.1 to a 128MB(!) Transcend JetFlash USB stick and then used the Wakepup creation script to make a boot floppy. It works fine on my home computer and has since been tested on two other machines, worked on one but not the other, go figure!
I just used the Puppy Universal Installer to install Puppy 2.17.1 to a 128MB(!) Transcend JetFlash USB stick and then used the Wakepup creation script to make a boot floppy. It works fine on my home computer and has since been tested on two other machines, worked on one but not the other, go figure!
[i]Welcome to my weird, wild, wonderful, wired world![/i]