From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1P0ge0-00058N-21 for mharc-grub-devel@gnu.org; Tue, 28 Sep 2010 16:19:20 -0400 Received: from [140.186.70.92] (port=36573 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0gdr-00053H-9d for grub-devel@gnu.org; Tue, 28 Sep 2010 16:19:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P0gdn-0003qe-Hb for grub-devel@gnu.org; Tue, 28 Sep 2010 16:19:11 -0400 Received: from mail-bw0-f41.google.com ([209.85.214.41]:42471) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P0gdn-0003qM-6U for grub-devel@gnu.org; Tue, 28 Sep 2010 16:19:07 -0400 Received: by bwz10 with SMTP id 10so92326bwz.0 for ; Tue, 28 Sep 2010 13:19:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=oTJtWWveaveMC5h3eRr6sveRDDtF+jngbp4ZJYFLu6o=; b=iR+ofuQ/0hxctYO9hJUsRJZH6fd/HVmeKFCz/FulLKKlpDhiCdhwTRbH4/3VNhy8ii eLrg+RrfMmUIPT16LDZO4gKsI4B/XFfI5FuAb/0Rv1SO5Zu2UlABVEClwKD2gaRz7jEN AHw7hDOxxKLk57riJb1mv3XyvTpaez7pymCko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=lf2VE85/C4VVWuK1vfVcGdGofL7UocPqm2+VhrbEPu7YysVAK9p9Xp4YESQsMjrOZR FF5N02EBhC0tCicyN1EPdvx1N3IZKfcv5+6j4vciv+ZrNnRZ3Yo7xCr2UG0x6eb3EttK rj8u5SRluP1CTb40rhwHZUsIKUfhnYHHUlEAM= Received: by 10.204.146.153 with SMTP id h25mr460998bkv.86.1285705145134; Tue, 28 Sep 2010 13:19:05 -0700 (PDT) Received: from [192.168.178.55] (p5B0CF35C.dip.t-dialin.net [91.12.243.92]) by mx.google.com with ESMTPS id y19sm5983785bkw.18.2010.09.28.13.19.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 28 Sep 2010 13:19:03 -0700 (PDT) Message-ID: <4CA24DB4.9050202@googlemail.com> Date: Tue, 28 Sep 2010 22:19:00 +0200 From: Andreas Born User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100917 Lightning/1.0b1 Thunderbird/3.0.8 MIME-Version: 1.0 To: GRUB2 Devel References: <20100907234220.54cf8040@gmail.com> <4C87AB87.2070508@googlemail.com> <20100908154603.GN21862@riva.ucam.org> <4C87BA4D.4070807@googlemail.com> <4C9FAB74.8020804@googlemail.com> <4CA0B59A.8030404@cfl.rr.com> <4CA1FEF0.4000209@googlemail.com> <4CA215C9.9060000@cfl.rr.com> <4CA219B9.3020209@googlemail.com> <4CA22FC6.9000701@cfl.rr.com> In-Reply-To: <4CA22FC6.9000701@cfl.rr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) Cc: Phillip Susi Subject: Re: GRUB2 fails when booting from CD X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 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: Tue, 28 Sep 2010 20:19:17 -0000 Am 28.09.2010 20:11, schrieb Phillip Susi: > On 9/28/2010 12:37 PM, Andreas Born wrote: > >> If I understood that part about hd emulation right, that would mean the >> image wouldn't work on any machine? Or is it possible to switch >> dynamically with one single image between hd emulation and native >> el-torito? >> > That's true, if that were the problem the image would not work on any > machine. If it works on other machines, then it seems to be a problem > with the bios. > > >> Output: >> grub rescue> set >> prefix=(hd111)/boot/grub/i386-pc/ >> root=hd111 >> > The odd ( 111 ) hd number is a hint that the bios is broken. Does ls > report any available drives? Maybe it is there, but the bios did not > pass the correct number. > Yes, as I wrote in my first mail: grub rescue> ls (hd0) grub rescue> ls (hd0) error: unknown filesystem Is there any way to clearly identify the BIOS as the culprit? Or maybe even a chance to implement a workardound at some point if it really is a problem with the BIOS? I guess the fact that I don't have such problems with isolinux can be explained with different use of BIOS functionality? I'm not asking because it were a serious problem for me. I'd just like to lower the probability that other users face unlike me a real problem. At least if it's possible with considerable effort.