From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MtLLl-0006KI-MY for mharc-grub-devel@gnu.org; Thu, 01 Oct 2009 09:05:37 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtLLi-0006Ip-P2 for grub-devel@gnu.org; Thu, 01 Oct 2009 09:05:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtLLi-0006Hs-3G for grub-devel@gnu.org; Thu, 01 Oct 2009 09:05:34 -0400 Received: from [199.232.76.173] (port=33960 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtLLh-0006Hn-Ok for grub-devel@gnu.org; Thu, 01 Oct 2009 09:05:33 -0400 Received: from eta-ori.net ([91.121.142.51]:42112 helo=orion.eta-ori.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtLLh-00021T-HC for grub-devel@gnu.org; Thu, 01 Oct 2009 09:05:33 -0400 Received: from [10.0.0.151] (p4FEDF5E0.dip.t-dialin.net [79.237.245.224]) by orion.eta-ori.net (Postfix) with ESMTPSA id 95F0A60CCEB for ; Thu, 1 Oct 2009 15:05:32 +0200 (CEST) Message-ID: <4AC4A917.10805@impulze.org> Date: Thu, 01 Oct 2009 15:05:27 +0200 From: Daniel Mierswa User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20090930 Thunderbird/3.0pre MIME-Version: 1.0 To: grub-devel@gnu.org References: <4AC2B06F.5020302@impulze.org> <4AC2F8C4.3000909@gmail.com> <4AC3AD67.2020401@impulze.org> <4AC466A9.8030805@gmail.com> In-Reply-To: <4AC466A9.8030805@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: Faulty BIOS or GRUB issue (USB Stick won't boot) 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, 01 Oct 2009 13:05:35 -0000 On 01.10.2009 10:22, Vladimir 'phcoder' Serbinenko wrote: > To simulate brain damage of your BIOS *shrug* I wonder how you can manage to simulate _that_ severe damage. > echo '(hd0) /dev/loop0'> /boot/grub/device.map D'oh, didn't think of hardcoding it, I thought GRUB detects it properly. However, phcoder, there were some crackheads back in January taking some time with that matter and I tried almost every hack discussed on the net. And out of nothing comes you, applying yet another hack and it just seems to work. You're a true hero. :D However when doing "ls (hd0)" in the GRUB rescue shell that fires up, I'm getting "Partition table". I guess this is part of the hack? Is it possible to apply this workaround in the codebase so that others with that broken BIOS (remember I have another MBR file of a guy who reported identical behaviour) or is this something that should be left to people with broken BIOS? All in all, thank you very much, now that I have a rescue shell, I can start playing. -- Mierswa, Daniel If you still don't like it, that's ok: that's why I'm boss. I simply know better than you do. --- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22