(old)Puppy Linux Discussion Forum

READ-ONLY Archive
https://oldforum.puppylinux.com/

Grub4DosConfig

https://oldforum.puppylinux.com/viewtopic.php?t=51697

Page 18 of 20

Posted: Thu 12 Mar 2015, 16:04
by Burn_IT
You will never be able to boot direct from any flash drive that is not detected by the BIOS.
Plop does go a little way towards helping by supplying some extra support. but even then the device must be supported by the Plop drivers and Plop itself must be located on a BIOS detectable device.

Posted: Fri 13 Mar 2015, 00:14
by don570
grub or grub4dos needs to installed somewhere.


For PLOP to work the USB flash drive must be truly bootable.
Barry Kauler uses syslinux. He's very careful about what version he uses.

I don't have any problems with April64 on a USB drive and PLOP using the script

4install-quirky-to-drive.

The details are here

Here is how plop looks when I choose the USB drive to boot the distro...

Image


__________________________________

Posted: Fri 24 Apr 2015, 16:29
by jlst
There is a grub4dos 'fork' that is being actively developed since 2010. The developer is a Chinese.

Here is a tutorial that can be used as a starting point regarding this grub4dos 'fork'
http://www.rmprepusb.com/tutorials/grub4dos

Github
https://github.com/chenall/grub4dos

Blog/News
http://grub4dos.chenall.net/

############################################################

I compiled grub4dos v0.4.5c git20150424 and a few utilities.

This pkg replaces:
/usr/lib/grub4dos/grldr
/usr/sbin/bootlace.com

And adds:
/usr/lib/grub4dos/grldr.mbr
/usr/lib/grub4dos/grub.pif
/usr/lib/grub4dos/menu.wee
/usr/lib/grub4dos/wee63start
/usr/lib/grub4dos/wee63.mbr
/usr/lib/grub4dos/wee127.mbr
/usr/sbin/bootlace64.com
/usr/sbin/weesetup

This is for TESTING purposes only, maybe the developers can find new ways to expand their horizon..

Video tutorial

Posted: Thu 23 Jul 2015, 11:44
by Pelo
Postponed as Video disappeared ! The matter was to explain by image what french does not understand in english linux language... :?
video now here, by a click on the blue.

Posted: Wed 17 Feb 2016, 01:43
by bigpup
There is a bug in Grub4dos v1.9.2

If you install to a USB hard drive

Grub4dos will find the Puppy OS on the USB hard drive and make a boot menu entry.
The entry will not boot. Will not find the Puppy_sfs.

The bug:
The pmedia entry is wrong.

The entry will have pmedia=atahd

It needs to be pmedia=usbhd

With entry changed to pmedia=usbhd it boots OK.

Posted: Wed 17 Feb 2016, 02:26
by LazY Puppy
bigpup wrote:There is a bug in Grub4dos v1.9.2

If you install to a USB hard drive

Grub4dos will find the Puppy OS on the USB hard drive and make a boot menu entry.
The entry will not boot. Will not find the Puppy_sfs.

The bug:
The pmedia entry is wrong.

The entry will have pmedia=atahd

It needs to be pmedia=usbhd

With entry changed to pmedia=usbhd it boots OK.
This is weird! :shock:

For about two years I'm now booting from USB hard disk drive using pmedia=atahd in entries of menu.lst. Boot partition is ext2.

No matter if original Puppy or remastered Versions: all Puppy do find its main .sfs.

In init script there is a code section where it is asked for ata.

Code: Select all

search_func() { #110425

 case $1 in
  ata)
   [ "$PMEDIA" = "usbflash" -o "$PMEDIA" = "usbhd" ] && return #only probe usb drives.
   LESSPARTS0="`echo "$PCPARTS0" | grep -f /tmp/ALLDRVS0`" #111003 only probe non-usb drives. need for kernels builtin usb drvr.
  ;;
This seems to switch ata to usb somehow as atahd is only to be found as a comment in init script.

However: my pmedia=atahd is going directly into /etc/rc.d/PUPSTATE.

Code: Select all

PUPMODE=5
PDEV1='sde1'
DEV1FS='ext2'
PUPSFS='sde1,ext2,/Tahr602CE/puppy_tahr_6.0.2.sfs'
PUPSAVE=''
PMEDIA='atahd'
#ATADRIVES is all internal ide/pata/sata drives, excluding optical, excluding usb...
ATADRIVES='sda sdb sdc sdd '
#ATAOPTICALDRIVES is list of non-usb optical drives...
ATAOPTICALDRIVES='sr0 sr1 '
#these directories are unionfs/aufs layers in /initrd...
SAVE_LAYER=''
PUP_LAYER='/pup_ro2'
#The partition that has the tahrsave file is mounted here...
PUP_HOME=''
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV='sde1,ext2,/Tahr602CE/zdrv_tahr_6.0.2.sfs'
ADRV=''
YDRV=''
#complete set of modules in the initrd (moved to main f.s.)...
ZDRVINIT='no'
#Partition no. override on boot drive to which session is (or will be) saved...
PSAVEMARK=''
#PLANG is written to LANG in /etc/profile by init script initrd...
PLANG=de_DE.UTF-8
OUTPUT_CHARSET=UTF-8
export OUTPUT_CHARSET
PSUBDIR='/Tahr602CE'
So it should not cause any problems at all. :?

Posted: Wed 17 Feb 2016, 03:12
by gcmartin
Hello @LazY Puppy

Actually the post is only partially true:
LazY Puppy wrote:... No matter if original Puppy or remastered Versions: all Puppy do find its main .sfs. ...
Not only does what @BigPUP report, there are a few other similar issues.

Here's one reported by @CatDude. MultiPUP is a Puppy Utility which uses GRUB4DOS as its bootmanager.

And, to this day, I have not been able to boot couple of recent PUP distros after burning distro's ISO to a DVD; as I get the "... PUP.sfs not found" boot crash. (This problem has not gotten much attention of what is occurring or why in those PUP distros.)

Hope this is helpful

Posted: Wed 17 Feb 2016, 04:12
by bigpup
Let me add.
This was for Slacko 6.3.0 and Tahrpup 6.0.5 installs.
Not sure if it also affects other Puppies.
bigpup wrote:There is a bug in Grub4dos v1.9.2

If you install to a USB hard drive

Grub4dos will find the Puppy OS on the USB hard drive and make a boot menu entry.
The entry will not boot. Will not find the Puppy_sfs.

The bug:
The pmedia entry is wrong.

The entry will have pmedia=atahd

It needs to be pmedia=usbhd

With entry changed to pmedia=usbhd it boots OK.

Posted: Wed 17 Feb 2016, 05:01
by LazY Puppy
Let me add the Puppies I'm booting from USB HD using pmedia=atahd in menu.lst:

Sulu 004, Precise 5.7.1, Slacko 5.9.3, Slacko 64 5.9.1, Slacko 64 6.3.0, Tahr 6.0.2 CE, Tahr 6.0.5 CE, Tahr 64 6.0.2 CE, Tahr 64 6.0.4 CE, Tahr 64 6.0.5 CE, Unicorn 6.0, Vivid beta2

Plus five Puppies more which are remastered and based on Lucid 5.2.8-4, Three Headed Dog, Precise 5.7.1, Tahr 6.0 and Unicorn 6.0.

Posted: Wed 17 Feb 2016, 07:29
by gcmartin
All of this leads to one question (maybe several related, but...)
  • Under what circumstances and under what conditions are the options for pmedia to be used?
Is there clear documentation on the parm for developers/users, beyond its listing the pmedia options. For example, is there a design difference between the usb vs the ata option?

Posted: Wed 17 Feb 2016, 11:56
by Burn_IT
I just looked at mine and it is set to IDEHD and works fine for both internal and USB drives.

Posted: Thu 18 Feb 2016, 11:11
by gyro
There is an advantage to using "usbflash" or "usbhd" when booting puppy from a usb device;
The 'init' script will not look on any of your ata devices, when searching for puppy files.
gyro

Posted: Fri 19 Feb 2016, 13:12
by mavrothal
Grub4dosconfig fails when run from a full install as reported, because can not get the "MY*" info from PUPSTATE
The patch below (for v1.9.1) fixes it for me.

Code: Select all

--- a/usr/sbin/grub4dosconfig
+++ b/usr/sbin/grub4dosconfig
@@ -587,13 +587,22 @@
 fi
 # 14jan10 v.1.5.2 again which sfs as PUPSFS
 [ -f /etc/rc.d/PUPSTATE ] && . /etc/rc.d/PUPSTATE
-MYSFSFILE=$(echo $PUPSFS|cut -d',' -f3)
-MYSFSBASE=$(basename "$MYSFSFILE")
-PUPPYPREFIX=$(echo $MYSFSBASE|sed -e 's/[0-9].*$//')
-MYPART=$(echo $PUPSFS|cut -d',' -f1)
-MYDRIVE=$(echo $MYPART| part2drive) # v1.7.2
-MYPUPPY=$MYPART$MYSFSFILE
-
+if [ "$PUPMODE" = "2" ];then
+ . /etc/DISTRO_SPECS
+ MYSFSFILE="${PDEV1},${DEV1FS},/"
+ MYSFSBASE="$DISTRO_PUPPYSFS"
+ PUPPYPREFIX=$(echo $MYSFSBASE|sed -e 's/[0-9].*$//')
+ MYPART="$PDEV1"
+ MYDRIVE=$(echo $MYPART| part2drive)
+ MYPUPPY=$MYPART$MYSFSFILE
+else
+ MYSFSFILE=$(echo $PUPSFS|cut -d',' -f3)
+ MYSFSBASE=$(basename "$MYSFSFILE")
+ PUPPYPREFIX=$(echo $MYSFSBASE|sed -e 's/[0-9].*$//')
+ MYPART=$(echo $PUPSFS|cut -d',' -f1)
+ MYDRIVE=$(echo $MYPART| part2drive) # v1.7.2
+ MYPUPPY=$MYPART$MYSFSFILE
+fi
 # where to install
 DISKS=$(probedisk2)
 [ "$DISKS" = "" ] && DISKS=$(probedisk)
It can obviously be simplified and use for all cases more of the info in DISTRO_SPECS

Posted: Fri 19 Feb 2016, 16:23
by CatDude
Hi

@ gcmartin
gcmartin wrote:...Here's one reported by @CatDude. MultiPUP is a Puppy Utility which uses GRUB4DOS as its bootmanager.
If i recall correctly MultiPup is using the old legacy grub (0.97) not Grub4Dos

Just trying to clarify things, so as not to muddy the waters (so to speak).

CatDude
.

Posted: Thu 25 Feb 2016, 18:06
by 666philb
mavrothal wrote:Grub4dosconfig fails when run from a full install as reported, because can not get the "MY*" info from PUPSTATE
The patch below (for v1.9.1) fixes it for me.

Code: Select all

--- a/usr/sbin/grub4dosconfig
+++ b/usr/sbin/grub4dosconfig
@@ -587,13 +587,22 @@
 fi
 # 14jan10 v.1.5.2 again which sfs as PUPSFS
 [ -f /etc/rc.d/PUPSTATE ] && . /etc/rc.d/PUPSTATE
-MYSFSFILE=$(echo $PUPSFS|cut -d',' -f3)
-MYSFSBASE=$(basename "$MYSFSFILE")
-PUPPYPREFIX=$(echo $MYSFSBASE|sed -e 's/[0-9].*$//')
-MYPART=$(echo $PUPSFS|cut -d',' -f1)
-MYDRIVE=$(echo $MYPART| part2drive) # v1.7.2
-MYPUPPY=$MYPART$MYSFSFILE
-
+if [ "$PUPMODE" = "2" ];then
+ . /etc/DISTRO_SPECS
+ MYSFSFILE="${PDEV1},${DEV1FS},/"
+ MYSFSBASE="$DISTRO_PUPPYSFS"
+ PUPPYPREFIX=$(echo $MYSFSBASE|sed -e 's/[0-9].*$//')
+ MYPART="$PDEV1"
+ MYDRIVE=$(echo $MYPART| part2drive)
+ MYPUPPY=$MYPART$MYSFSFILE
+else
+ MYSFSFILE=$(echo $PUPSFS|cut -d',' -f3)
+ MYSFSBASE=$(basename "$MYSFSFILE")
+ PUPPYPREFIX=$(echo $MYSFSBASE|sed -e 's/[0-9].*$//')
+ MYPART=$(echo $PUPSFS|cut -d',' -f1)
+ MYDRIVE=$(echo $MYPART| part2drive) # v1.7.2
+ MYPUPPY=$MYPART$MYSFSFILE
+fi
 # where to install
 DISKS=$(probedisk2)
 [ "$DISKS" = "" ] && DISKS=$(probedisk)
It can obviously be simplified and use for all cases more of the info in DISTRO_SPECS
hi mavrothal,

will this patch also work with grub4dos 1.9.2?

Posted: Thu 25 Feb 2016, 19:08
by mavrothal
666philb wrote:will this patch also work with grub4dos 1.9.2?
It should but I never tested it. I do not think the code has been changed in that part.
Try to patch it and if it does not fail, should be OK.

Posted: Sat 26 Mar 2016, 00:24
by recobayu
I have linuxmint and ubuntu installed in my laptop.
Can we set grub4dos so that we can see splash screen of ubuntu or linuxmint on boot?

Posted: Sun 17 Apr 2016, 05:25
by april
How to use Grub4Dos for USB drives
A video tutorial
Can we just have something written that does not use a whole lot of download data.!

Posted: Fri 29 Apr 2016, 00:58
by starhawk
grub4dos appears to have problems booting from SD cards, at least in an SD-to-IDE adapter. I have booted Puppy from that media successfully with extlinux/syslinux -- but grub4dos consistently fails.

This is in reference to this post and thread.

Posted: Sun 01 May 2016, 23:55
by jlst
The official grub4dos is long dead, however you might want to use the grldr from this file:

http://dl.grub4dos.chenall.net/grub4dos ... 6-04-26.7z

Which has many enhacenments in every possible way. If it doesnt work, you can report this issue in the chenall github repo
All times are UTC
Page 18 of 20

Powered by phpBB® Forum Software © phpBB Limited