From owner-freebsd-current@FreeBSD.ORG Tue Mar 31 01:17:47 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3E871065670 for ; Tue, 31 Mar 2009 01:17:47 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 8D4368FC16 for ; Tue, 31 Mar 2009 01:17:47 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n2V0ov9e017474; Mon, 30 Mar 2009 18:50:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n2V0ouTh017471; Mon, 30 Mar 2009 18:50:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 30 Mar 2009 18:50:56 -0600 (MDT) From: User Wblock To: Andriy Gapon In-Reply-To: <49D1001E.2050405@icyb.net.ua> Message-ID: References: <4451ccf20903300123p4df9c1d7k4c4138ad25d2d4af@mail.gmail.com> <49D0E44C.60103@phat.za.net> <49D1001E.2050405@icyb.net.ua> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (wonkity.com [127.0.0.1]); Mon, 30 Mar 2009 18:50:57 -0600 (MDT) Cc: Aragon Gouveia , ccuiyyan@gmail.com, freebsd-current@freebsd.org Subject: Re: loader prompt doesn't work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 01:17:48 -0000 On Mon, 30 Mar 2009, Andriy Gapon wrote: > on 30/03/2009 18:25 Aragon Gouveia said the following: >> ??ccuiyyan@sina.com wrote: >>> However, problem happens. When i select the "escape to a loader >>> prompt" >>> option, i can input >>> >>> in about just 3 sec. After that, the system cannot go on whatever >>> key i >>> hit. >> >> Same problem here and it's not USB/keyboard related in my case. What >> motherboard are you using? I'm on an Intel DG33BU. > > There was a significant fix to boot code made recently by jhb. > It is now in head, stable/7 and stable/6. > So you need to update to the recent resources. > What you also need (and what was not emphasized enough, IMO) is to actually > install new boot code (/boot/boot) to your active slices after installworld completes. > > E.g.: > $ gpart bootcode -b /boot/boot adXsY The gpart manpage just makes me more confused about this. I don't know what a "protective" MBR is, or if I've got one. Can you expand on this a little? For instance: * When did it happen? * Who needs to do this--everyone who has updated to a recent -CURRENT or -STABLE? Or just those using certain partitioning features? * There's no mention in /usr/src/UPDATING. Was it mentioned anywhere? -Warren Block * Rapid City, South Dakota USA