From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KTfsW-0004yi-7Y for mharc-grub-devel@gnu.org; Thu, 14 Aug 2008 12:40:48 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KTfsV-0004y9-0x for grub-devel@gnu.org; Thu, 14 Aug 2008 12:40:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KTfsT-0004xI-4f for grub-devel@gnu.org; Thu, 14 Aug 2008 12:40:46 -0400 Received: from [199.232.76.173] (port=39225 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KTfsS-0004xD-Vm for grub-devel@gnu.org; Thu, 14 Aug 2008 12:40:45 -0400 Received: from moutng.kundenserver.de ([212.227.126.177]:51955) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KTfsP-0005sC-Jo for grub-devel@gnu.org; Thu, 14 Aug 2008 12:40:44 -0400 Received: from [85.180.28.246] (e180028246.adsl.alicedsl.de [85.180.28.246]) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis) id 0ML29c-1KTfsN1Zji-0001gg; Thu, 14 Aug 2008 18:40:39 +0200 From: Felix Zielcke To: The development of GRUB 2 Content-Type: text/plain Date: Thu, 14 Aug 2008 18:40:44 +0200 Message-Id: <1218732044.8610.2.camel@fz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1//A1uYDl0XRl7bCS+Q8QvjVttVC/ccGpQHWGx qatqgQtwmdzf01jFOOQSpbXSjkHaUizmZIZhoTdzHWJ4Cwca3F Uke6onqMgzc4Xmp7g6b0TbI9gBPYW86 X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) Subject: [Fwd: Re: Bug#495049: grub-pc: does not boot because module "normal" is not loaded] X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2008 16:40:47 -0000 Hello, anyone has an idea why grub itself fails to switch from rescue to normal mode, but just `insmod normal; normal' does work? For me this doestn't make any sense at all. If you want to see the initial report: http://bugs.debian.org/495049 -------- Weitergeleitete Nachricht -------- > Von: ian_bruce@fastmail.fm > An: Felix Zielcke > Kopie: 495049@bugs.debian.org > Betreff: Re: Bug#495049: grub-pc: does not boot because module > "normal" is not loaded > Datum: Thu, 14 Aug 2008 05:13:15 -0700 > > On Thu, 14 Aug 2008 13:20:53 +0200 > Felix Zielcke wrote: > > > > After running "grub-install" and rebooting, grub drops into the > > > "grub rescue>" prompt. The "pc", "lvm", and "ext2" modules are loaded, > > > "ls" finds the root volume, and the variable "root" is set > > > appropriately. > > > > Only the variable root or the prefix too? > > Both. > > > Are sure that if you boot you only type > > > > insmod normal > > normal > > > > and then the menu shows? i.e. nothing before like set prefix or set > > root? > > Only those two commands. Nothing else. > > > That would be very weird if GRUB set it's variables right, but still > > fails to load grub.cfg by it's own. > > > > fz@fz:~$ strings /boot/grub/core.img|grep normal > > fz@fz:~$ > > # strings /boot/grub/normal.mod | grep grub.cfg > %s/grub.cfg > # > > The reason it doesn't load grub.cfg is because that filename is only found > in the "normal" module, which as I said, doesn't get loaded automatically, > but is located without problem with the "insmod" command. > > > I think that core.img doestn't contain the string `normal' is just well > > normal, grub2 works fine for me, but I don't have LVM or RAID ;) > > I don't know how the "normal" module is supposed to get loaded, but it's > clear that it IS supposed to, and that it isn't happening here. > > I don't know if the problem is related to lvm, or if it's specific to AMD64, > or what.