From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1TlR6g-00057z-MQ for mharc-grub-devel@gnu.org; Wed, 19 Dec 2012 16:23:14 -0500 Received: from eggs.gnu.org ([208.118.235.92]:51080) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TlR6e-000571-Ax for grub-devel@gnu.org; Wed, 19 Dec 2012 16:23:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TlR6d-0001cs-7f for grub-devel@gnu.org; Wed, 19 Dec 2012 16:23:12 -0500 Received: from smtp.volny.cz ([62.44.29.27]:41017) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TlR6d-0001cb-0w for grub-devel@gnu.org; Wed, 19 Dec 2012 16:23:11 -0500 Received: from [192.168.6.161] (unknown [193.86.90.90]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: starous) by smtp.volny.cz (Postfix) with ESMTPSA id 07628260AF6 for ; Wed, 19 Dec 2012 22:23:08 +0100 (CET) Subject: Re: Boot GRUB from USB - potential problem From: =?UTF-8?Q?Ale=C5=A1?= Nesrsta To: The development of GNU GRUB In-Reply-To: <50D1D814.2010407@ubuntu.com> References: <1355676885.3291.52.camel@pracovna> <50D0D381.4030508@ubuntu.com> <1355868560.2783.62.camel@pracovna> <50D1D814.2010407@ubuntu.com> Content-Type: text/plain; charset="ISO-8859-2" Date: Wed, 19 Dec 2012 22:23:02 +0100 Message-ID: <1355952182.2871.30.camel@pracovna> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 62.44.29.27 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2012 21:23:13 -0000 > On 12/18/2012 5:09 PM, Ale=B9 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. >=20 > You can also put the modules into a ramdisk and load that. >=20 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