Author |
Message |
mavrothal

Joined: 24 Aug 2009 Posts: 3088
|
Posted: Thu 25 Feb 2016, 15:08 Post subject:
|
|
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.
_________________ == Here is how to solve your Linux problems fast ==
|
Back to top
|
|
 |
recobayu

Joined: 15 Sep 2010 Posts: 374 Location: indonesia
|
Posted: Fri 25 Mar 2016, 20:24 Post subject:
|
|
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?
|
Back to top
|
|
 |
april
Joined: 14 Sep 2013 Posts: 1241 Location: Green Island baby!
|
Posted: Sun 17 Apr 2016, 01:25 Post subject:
|
|
Quote: |
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.!
|
Back to top
|
|
 |
starhawk
Joined: 22 Nov 2010 Posts: 5056 Location: Everybody knows this is nowhere...
|
Posted: Thu 28 Apr 2016, 20:58 Post subject:
|
|
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.
_________________

|
Back to top
|
|
 |
jlst
Joined: 23 Nov 2012 Posts: 571
|
Posted: Sun 01 May 2016, 19:55 Post subject:
|
|
The official grub4dos is long dead, however you might want to use the grldr from this file:
http://dl.grub4dos.chenall.net/grub4dos-0.4.6a-2016-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
|
Back to top
|
|
 |
nic007

Joined: 13 Nov 2011 Posts: 3176 Location: Cradle of Humankind
|
Posted: Mon 02 May 2016, 04:32 Post subject:
|
|
starhawk wrote: | 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. |
I don't have that problem, multi-booting from sd card with grub4dos no problems. My SD card is FAT formatted.
|
Back to top
|
|
 |
starhawk
Joined: 22 Nov 2010 Posts: 5056 Location: Everybody knows this is nowhere...
|
Posted: Mon 02 May 2016, 11:17 Post subject:
|
|
@jlst -- I'll check that later.
@nic -- mine is ext4.
_________________

|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 12799 Location: Stratford, Ontario
|
Posted: Mon 02 May 2016, 11:37 Post subject:
|
|
It's been my experience that some BIOSes only boot USB devices off a FAT partition. I'm guessing that their USB drivers were not built to recognize anything else.
But that might not apply here.
|
Back to top
|
|
 |
starhawk
Joined: 22 Nov 2010 Posts: 5056 Location: Everybody knows this is nowhere...
|
Posted: Tue 03 May 2016, 18:48 Post subject:
|
|
Sorry for slow reply. The SD card is in an adapter that presents an IDE interface, so USB indeed does not apply. Although, my "Puppy testing" drive is an ext3-formatted USB flash stick, and the system in question boots just fine from that.
Hmm. Maybe it's the use of ext4 instead of ext3. I've got to recompile an Xorg driver module for XenialPup, so I may try reformatting the card when I go to do that...
_________________

|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1680 Location: Brisbane, Australia
|
Posted: Fri 06 Jan 2017, 06:52 Post subject:
Patched ""/usr/sbin/grub4dosconfig" provides uuid to "init" |
|
Attached "grub4dosconfig_uuid-1.9.2.pet" contains a patched version of the "/usr/sbin/grub4dosconfig" file.
It now supports the recent "init" boot parameter support for specifying partitions with a uuid.
It does this by adding a "pdrv=<uuid>" boot param if the entry contains a "uuid <uuid>" line.
So instead of producing an entry like this: Code: | title Puppy tahr 6.0.5.3 (sdc2/tahr)
uuid 2b4a3075-e41d-4ee4-ab92-7e7d73843a3a
kernel /tahr/vmlinuz psubdir=tahr pmedia=atahd pfix=fsck
initrd /tahr/initrd.gz | it produces an entry like this: Code: | title Puppy tahr 6.0.5.3 (sdc2/tahr)
uuid 2b4a3075-e41d-4ee4-ab92-7e7d73843a3a
kernel /tahr/vmlinuz pdrv=2b4a3075-e41d-4ee4-ab92-7e7d73843a3a psubdir=tahr pmedia=atahd pfix=fsck
initrd /tahr/initrd.gz | A "pdrv=" boot parameter is used because only recent "init"s that support uuid's also support "pdrv=".
Since we are specifying the partition to "grldr" why not provide the same curtesy to "init"?
Note: To use this pet, grub4dosconfig must already be installed.
gyro
Description |
clicck on file to install
|

Download |
Filename |
grub4dosconfig_uuid-1.9.2.pet |
Filesize |
20.19 KB |
Downloaded |
253 Time(s) |
|
Back to top
|
|
 |
Pelo
Joined: 10 Sep 2011 Posts: 12591 Location: Mer méditerrannée (1 kms°)
|
Posted: Fri 06 Jan 2017, 07:55 Post subject:
bookmarked for translation to fr |
|
traduction à faire pour les francophones forum francophone
Being translated to french for help to some users.
_________________ Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1707
|
Posted: Sat 07 Jan 2017, 16:53 Post subject:
Re: Patched ""/usr/sbin/grub4dosconfig" provides uuid to "init" |
|
gyro wrote: | Attached "grub4dosconfig_uuid-1.9.2.pet" contains a patched version of the "/usr/sbin/grub4dosconfig" file.
It now supports the recent "init" boot parameter support for specifying partitions with a uuid.
It does this by adding a "pdrv=<uuid>" boot param if the entry contains a "uuid <uuid>" line.
So instead of producing an entry like this: Code: | title Puppy tahr 6.0.5.3 (sdc2/tahr)
uuid 2b4a3075-e41d-4ee4-ab92-7e7d73843a3a
kernel /tahr/vmlinuz psubdir=tahr pmedia=atahd pfix=fsck
initrd /tahr/initrd.gz | it produces an entry like this: Code: | title Puppy tahr 6.0.5.3 (sdc2/tahr)
uuid 2b4a3075-e41d-4ee4-ab92-7e7d73843a3a
kernel /tahr/vmlinuz pdrv=2b4a3075-e41d-4ee4-ab92-7e7d73843a3a psubdir=tahr pmedia=atahd pfix=fsck
initrd /tahr/initrd.gz | A "pdrv=" boot parameter is used because only recent "init"s that support uuid's also support "pdrv=".
Since we are specifying the partition to "grldr" why not provide the same curtesy to "init"?
Note: To use this pet, grub4dosconfig must already be installed.
gyro |
Hi Gyro,
I've been using grub4dos for a few years, and I am wondering why anyone would want to add this ability with "pdrv=" parameter? Since you already have to enter the UUID once, what reason and/or attraction is there for doing it again? Are you saying these new init's that can recognize UUID for partitions are not going to boot if this pdrv is not on the kernel line? Sorry if this all sounds stupid, I am struggling hard here to see the or any benefit of this pdrv parameter. Doing things the simple, old way (the first entry method in your example) is not the init forced, as grub4dos goes through its motions, to be assigned to that partition? Why complicate things with a "pdrv=" entry that only repeats what init is actually forced to do as grub4dos boots? Or am I not correctly understanding how grub4dos works??? Thanks for any clarity and/or understanding on this.
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1680 Location: Brisbane, Australia
|
Posted: Sun 08 Jan 2017, 02:30 Post subject:
Re: Patched ""/usr/sbin/grub4dosconfig" provides uuid to "init" |
|
belham2 wrote: |
Hi Gyro,
I've been using grub4dos for a few years, and I am wondering why anyone would want to add this ability with "pdrv=" parameter? Since you already have to enter the UUID once, what reason and/or attraction is there for doing it again? Are you saying these new init's that can recognize UUID for partitions are not going to boot if this pdrv is not on the kernel line? Sorry if this all sounds stupid, I am struggling hard here to see the or any benefit of this pdrv parameter. Doing things the simple, old way (the first entry method in your example) is not the init forced, as grub4dos goes through its motions, to be assigned to that partition? Why complicate things with a "pdrv=" entry that only repeats what init is actually forced to do as grub4dos boots? Or am I not correctly understanding how grub4dos works??? Thanks for any clarity and/or understanding on this. | The point is that the information in the "uuid" line is not passed on to "init", hence the "pdrv=" parameter so that "init" does get this information.
When "init" starts everything is in RAM, there is nothing to indicate where it booted from.
That's why the old "init" went searching through all partitions for the appropriate "vmlinuz'.
And why the new "init" will search through all partitios for the appropriate puppy...sfs.
Unless of course the boot partition is defined to puppy with a "pdev1=","pupsfs=", or "pdrv=" boot parameter.
gyro
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1707
|
Posted: Sun 08 Jan 2017, 12:38 Post subject:
Re: Patched ""/usr/sbin/grub4dosconfig" provides uuid to "init" |
|
gyro wrote: | belham2 wrote: |
Hi Gyro,
I've been using grub4dos for a few years, and I am wondering why anyone would want to add this ability with "pdrv=" parameter? Since you already have to enter the UUID once, what reason and/or attraction is there for doing it again? Are you saying these new init's that can recognize UUID for partitions are not going to boot if this pdrv is not on the kernel line? Sorry if this all sounds stupid, I am struggling hard here to see the or any benefit of this pdrv parameter. Doing things the simple, old way (the first entry method in your example) is not the init forced, as grub4dos goes through its motions, to be assigned to that partition? Why complicate things with a "pdrv=" entry that only repeats what init is actually forced to do as grub4dos boots? Or am I not correctly understanding how grub4dos works??? Thanks for any clarity and/or understanding on this. | The point is that the information in the "uuid" line is not passed on to "init", hence the "pdrv=" parameter so that "init" does get this information.
When "init" starts everything is in RAM, there is nothing to indicate where it booted from.
That's why the old "init" went searching through all partitions for the appropriate "vmlinuz'.
And why the new "init" will search through all partitios for the appropriate puppy...sfs.
Unless of course the boot partition is defined to puppy with a "pdev1=","pupsfs=", or "pdrv=" boot parameter.
gyro |
Thank you, gyro....I usually can see the trees, but rarely the forest Thanks for clearing it up so my mind could see it.
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1680 Location: Brisbane, Australia
|
Posted: Mon 09 Jan 2017, 12:28 Post subject:
Patched "/usr/sbin/grub4dosconfig" provides uuid to "init" |
|
Attached is an updated verrsion, "grub4dosconfig_uuid-1.9.2.2.pet".
Changes:
1. Adds "pdrv=" boot parameter to frugal entries in "menu-advanced.lst". The previous version only worked for frugal entries in "menu.lst".
2. Very minor change, add "/" to front of "psubdir=" value.
gyro
Description |
click to install
|

Download |
Filename |
grub4dosconfig_uuid-1.9.2.2.pet |
Filesize |
20.2 KB |
Downloaded |
282 Time(s) |
|
Back to top
|
|
 |
|