From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1QbWSX-0006rB-7e for mharc-grub-devel@gnu.org; Tue, 28 Jun 2011 07:28:01 -0400 Received: from eggs.gnu.org ([140.186.70.92]:46598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbWSU-0006qW-S0 for grub-devel@gnu.org; Tue, 28 Jun 2011 07:28:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbWSS-0006sb-3e for grub-devel@gnu.org; Tue, 28 Jun 2011 07:27:58 -0400 Received: from mail-pv0-f169.google.com ([74.125.83.169]:50019) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbWSR-0006sK-Og for grub-devel@gnu.org; Tue, 28 Jun 2011 07:27:56 -0400 Received: by pvc12 with SMTP id 12so14977pvc.0 for ; Tue, 28 Jun 2011 04:27:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=x1+DgzfVYN/v8p4q6Gxo55nXfbd+03fTpQ0RXTUL94I=; b=AWJ+mVFfflKhA0X5On1pH4i2mfAtzmDIkMSutyfcakRsgfmYbnNkSqTI7Xh+Nid3cC RHikVJy6CPXDpDubOvINwmuDYORBhzPF89W615ocRugRlSaWZCebyAfTJjb+XuqG/uEI 4GgiBI7r/f0SHjzOHHfuYnleKhWy+xPEYP8fU= Received: by 10.142.151.19 with SMTP id y19mr1411532wfd.47.1309260474264; Tue, 28 Jun 2011 04:27:54 -0700 (PDT) Received: from [10.1.1.12] (d122-104-32-184.sbr6.nsw.optusnet.com.au [122.104.32.184]) by mx.google.com with ESMTPS id e13sm67074wfd.1.2011.06.28.04.27.52 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Jun 2011 04:27:53 -0700 (PDT) Message-ID: <4E09BAB5.1010406@gmail.com> Date: Tue, 28 Jun 2011 21:27:49 +1000 From: Graeme Russ User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: Grub2 can not detect usb disk References: <4E030EF9.4060907@163.com> <4E034071.9040205@gmail.com> <4E03FD0C.2060400@163.com> <4E084A56.1030908@163.com> <4E084D04.4040001@gmail.com> <4E0855C6.8060704@viatech.com.cn> <4E085945.3010408@gmail.com> <4E092C1B.70906@viatech.com.cn> <4E095F02.9050504@gmail.com> <4E0994B7.4080408@viatech.com.cn> <4E099895.4060808@gmail.com> <4E09A6C7.5090205@163.com> <4E09B613.1020904@gmail.com> In-Reply-To: <4E09B613.1020904@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 74.125.83.169 Cc: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= 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: Tue, 28 Jun 2011 11:28:00 -0000 On 28/06/11 21:08, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > On 28.06.2011 12:02, Cui Lei wrote: >> Sorry , I don't know what the meaning of the "bisect" and how to do? >> Could you tell me some message in detail ? > You take a revision which doesn't work (1.99rc2 = r3229) and a working > one (1.98 = r2249). Then you try a revision in the middle, e.g. r2749. > If it works the error is in the range 2749..3229, otherwise in > 2249..2749, then you try a revision inside this range and in 10 steps > you'll have the exact revision which causes your problem. Does bazzar have the equivalent of git-bisect where you simply provide the last known working version and the first known broken version and simply answer a series of yes/no questions as the bisection is done in the background automatically? Regards, Graeme >> Thanks a lot. >> >> BRs, >> >> Rock. >> >>> On 28.06.2011 10:45, Rock Cui wrote: >>>> I had tried to use the grub1.99rc2 as a payload of coreboot at the >>>> beginning, but it can not boot my machine, >>> Could you try to bisect? Recent bzr worked fine in qemu+coreboot. Your >>> machine may present some special aspect and bisect is probably the >>> fastest way in your case. >>>> so I changed to 1.98 >>> As I said USB support in 1.98 wasn't good enough. Basically it worked >>> only in qemu. >>>> , then booting succeed. I want to insmod the uhci.mod and usbms.mod to >>>> support USB, >>>> but they are not exit in my build folder. If I run "configure" with >>>> "--with-platform=pc", they will be there, but >>>> with "--with-platform=coreboot", I can not found them. I don't know >>>> what should I do to get them for i386-coreboot, so I use the two >>>> modules which were built with "--with-platform=pc" in my payload.elf. >>> USB modules weren't enabled in 1.98 on coreboot. >>>> Surprising, they can be insmoded and run in the grub-shell , but >>>> unfortunately, I got those logs, they can not >>>> work. >>> it's already surprising they didn't crash GRUB altogether. >>> >>> >>> >>> _______________________________________________ >>> Grub-devel mailing list >>> Grub-devel@gnu.org >>> https://lists.gnu.org/mailman/listinfo/grub-devel >> >> >> _______________________________________________ >> Grub-devel mailing list >> Grub-devel@gnu.org >> https://lists.gnu.org/mailman/listinfo/grub-devel > > > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel