From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1DNwks-0004KW-Qn for mharc-grub-devel@gnu.org; Tue, 19 Apr 2005 13:43:22 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DNwkr-0004KO-Cv for grub-devel@gnu.org; Tue, 19 Apr 2005 13:43:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DNwkp-0004KA-OL for grub-devel@gnu.org; Tue, 19 Apr 2005 13:43:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DNwkp-0003lY-KC for grub-devel@gnu.org; Tue, 19 Apr 2005 13:43:19 -0400 Received: from [145.74.66.11] (helo=mail-cn.han.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DNwgD-0007cw-GL for grub-devel@gnu.org; Tue, 19 Apr 2005 13:38:33 -0400 Received: from vscan-cn.han.nl (venus.han.nl [145.74.65.6]) by mail-cn.han.nl (Postfix) with ESMTP id 0F7338E93 for ; Tue, 19 Apr 2005 19:36:32 +0200 (CEST) Received: from mail-cn.han.nl ([145.74.66.11]) by vscan-cn.han.nl (venus.han.nl [145.74.65.6]) (amavisd-new, port 10024) with ESMTP id 05439-02 for ; Tue, 19 Apr 2005 19:36:29 +0200 (CEST) Received: from mail1.han.nl (mail1.han.nl [145.74.103.11]) by mail-cn.han.nl (Postfix) with ESMTP id B8B6995DB for ; Tue, 19 Apr 2005 19:36:29 +0200 (CEST) Received: from localhost.localdomain (mgerards.xs4all.nl [82.92.27.129]) by mail1.han.nl (Postfix) with ESMTP id 8470AC045 for ; Tue, 19 Apr 2005 19:36:29 +0200 (CEST) Mail-Copies-To: metgerards@student.han.nl To: The development of GRUB 2 References: <20050417183350.GA30191@miracle> <87r7h96vo7.fsf@student.han.nl> <1ef9095696e3f129979d08a7d385e1d2@penguinppc.org> From: Marco Gerards Date: Tue, 19 Apr 2005 19:36:30 +0200 In-Reply-To: (Hollis Blanchard's message of "Mon, 18 Apr 2005 22:59:51 -0500") Message-ID: <87is2i4qjl.fsf@student.han.nl> User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new (2.2.0) at vscan-cn.han.nl Subject: Re: [patch] set prefix on PPC - briQ results 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: Tue, 19 Apr 2005 17:43:21 -0000 Hollis Blanchard writes: > I've tested the patch on briQ. As far as I can tell, CodeGen's > "SmartFirmware" is crap, frequently suffering mysterious failures that > require unplugging and waiting (unplugging and replugging rapidly > isn't enough). It also suffers frequent ATA failures, where the disk > or controller simply stop responding. > > 1. (major) Firmware does not properly set /chosen/bootpath to include > the partition number. What happens? Is it something I could try to reproduce on the PegasosII? > 2. (major) Partition numbering *seems* to be 0-based. I had a lot of > problems booting, but I'm pretty sure it is. Same on the pegasos... :/ > 3. (minor) /chosen/bootpath is this: > /pci@FF500000/isa@6/ide@i1F0/disk@0,0 > but the "hd" devalias is this: > /pci@FF500000/isa@6/ide@i1f0/disk@0,0 > Note the differing case of "f". This prevents the devalias matching > from succeeding. I've fixed this by using strncasecmp instead of > strncmp. That seems the right way to solve this problem. > Problem 1 could be worked around by taking the yaboot approach: > iterate over all disk partitions looking for a file named > "/grub/grub.cfg" (i.e. /boot/grub/grub.cfg). This fallback can be used > if we do not find a grub.cfg in prefix. Right... > Problem 2 could be worked around by blacklisting firmwares based on > the /openprom properties. Here is the briQ's output: With blacklist you mean setting some additional flags that describe which bugs the firmware has? > ok dev /openprom > ok .properties > relative-addressing > model "BRIQ,1.0.2.60" > SmartFirmware-version "1.1" > CodeGen-copyright "SmartFirmware(tm) Copyright 1996-2000 > by CodeGen, Inc. All Rights Reserved." > name "openprom" > > Does the Pegasos have a SmartFirmware-version property? It does. It has both a CodeGen and bplan copyright property. The SmartFirmware-version is 1.2 here. The model is "Pegasos2,1.2". It seems to me that this SmartFirmware-version is not interesting because it looks like this version is not changed for every build. The most interesting property is "built-on", which we can use to detect if a specific version has the bug or not. Thanks, Marco