All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Chainloadig from grub2 to isolinux
Date: Wed, 09 Jul 2014 00:22:41 +0200	[thread overview]
Message-ID: <53BC6F31.2020302@gmail.com> (raw)
In-Reply-To: <20140708163941.1ae7c9ce@rsbsd.rsb>

[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]

On 08.07.2014 15:39, Raif S. Berent wrote:
> Not to beat a dead horse, but I'd like to clarify a few issues that
> seem to be not working.
> 
You're confused as to what GRUB's responsibility is.
> 1. I compiled and installed Grub_trunk on an old laptop, then copied
> the debian.iso to a folder under (hd0,gpt*). Modified the grub.cfg and
> tried to use "syslinux_configfile -i (loop)/isolinux/isolinux.cfg -r
> (loop)" I got the exact same result as PXE booting (No CD-ROM). From
> what I can tell, debian needs the loopback module from the iso loaded
> and the iso to be loop-mounted as a second device in order to get this
> working (have not asked the debian folk).
Debian can't access GRUB's loopback. It has to find iso itself using
special parameters. Use /boot/grub/loopback.cfg for those. Don't forget
to set and export iso_path.
> 
> 2. Most Debian-based iso's fail to properly boot with loopback over
> PXE, including the likes of GParted and Inquisitor. They mostly fail
> with kernel panic: can't mount root.
> 
Ditto.

> 3. MEMDISK: There were several programs I can boot from my USB setup by
> including syslinux memdisk. These now fail due to memdisk error - for
> example (<...> means options I have tried): menuentry "HDT: hardware
> diagnostics tool" { set root="http,192.168.2.100" set
> memfile="/pub/tftp/rescue/rscd/memdisk" set
> isofile="/pub/tftp/rescue/rscd/hdt.img" linux16  ($root)$memfile
> <keeppxe floppy raw safeint> initrd16 ($root)$isofile	}
> With PXE, memdisk may need to be replaced with gpxelinux.0, but that
> will require using Grub's broken pxechain. Is there a better way to do
> this? syslinux apparently can also use memdisk for iso booting KERNEL
> memdisk  \  APPEND iso initrd=http://192.168.2.100/path/isofile.iso
> 
memdisk isn't good idea for anything over few MiB or anything that uses
own drivers. Again Linux will not be able to access this memdisk.
> 4. I think it would be a great idea if known grub.cfg entries could be
> listed in the official Grub-wiki. 
Nobody volunteered to host an "official wiki".



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]

  parent reply	other threads:[~2014-07-11  1:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  9:46 Chainloadig from grub2 to isolinux Beeblebrox
2014-07-02  9:48 ` Vladimir 'phcoder' Serbinenko
2014-07-02 13:37 ` Beeblebrox
2014-07-02 13:46   ` Vladimir 'phcoder' Serbinenko
2014-07-02 14:52   ` Beeblebrox
2014-07-02 15:00     ` Vladimir 'phcoder' Serbinenko
2014-07-08 13:39     ` Raif S. Berent
2014-07-08 15:47       ` Andrey Borzenkov
2014-07-08 22:22       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-07-21 19:18     ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 21:37       ` Ben Hildred
2014-07-21 21:41         ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 21:55         ` Raif S. Berent
2014-07-21 22:22           ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-22  4:24           ` Ben Hildred
2014-07-22 10:37             ` tuxracer
2014-07-22 11:04               ` Vladimir 'phcoder' Serbinenko
2014-07-22 12:44                 ` tuxracer
2014-08-07 14:52             ` Beeblebrox
2014-08-07 17:59               ` adrian15
2014-09-21 17:05                 ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53BC6F31.2020302@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.