All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aleš Nesrsta" <starous@volny.cz>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Boot GRUB from USB - potential problem
Date: Wed, 19 Dec 2012 22:23:02 +0100	[thread overview]
Message-ID: <1355952182.2871.30.camel@pracovna> (raw)
In-Reply-To: <50D1D814.2010407@ubuntu.com>

> On 12/18/2012 5:09 PM, Aleš Nesrsta wrote:
> > Probably the only one possibility is to load all necessary USB
> > GRUB modules manually before issuing "insmod ehci" as You
> > recommend. I will try if it is working in this way, it could be
> > usable.
> 
> You can also put the modules into a ramdisk and load that.
> 
Thanks for advice, I will try ramdisk also.

Today I tried pre-loading of all necessary USB modules followed by
loading of ehci module. It works with some exceptions - I cannot issue
some commands like e.g. "ls" after loading ehci module.
It is probably because such commands lists or try access to all disks -
and GRUB freezes when it tries to access BIOS boot disk (even if I have
correctly set new values in root, prefix and locale_dir to USB disk
newly created by USB modules).

I tried to do "rmmod biosdisk" - it helps, GRUB does not freeze with
"ls" command after that. But GRUB looks little bit unstable since then -
it does sometimes something wrong...

But, generally, it works. It is fine that I found there exists some
way(s) how to solve booting from USB devices together with use of GRUB
USB driver when it will be necessary - that is all what I wanted to
know.

BR,
Ales



      reply	other threads:[~2012-12-19 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16 16:54 Boot GRUB from USB - potential problem Aleš Nesrsta
2012-12-18 20:35 ` Phillip Susi
2012-12-18 22:09   ` Aleš Nesrsta
2012-12-19 15:07     ` Phillip Susi
2012-12-19 21:23       ` Aleš Nesrsta [this message]

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=1355952182.2871.30.camel@pracovna \
    --to=starous@volny.cz \
    --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.