From owner-freebsd-ppc@freebsd.org Wed Dec 13 12:22:32 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DB7AE9CB25 for ; Wed, 13 Dec 2017 12:22:32 +0000 (UTC) (envelope-from brenohl@br.ibm.com) Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.pphosted.com", Issuer "thawte SHA256 SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41AEB6ECEC for ; Wed, 13 Dec 2017 12:22:30 +0000 (UTC) (envelope-from brenohl@br.ibm.com) Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vBDCJ9iJ072787 for ; Wed, 13 Dec 2017 07:22:23 -0500 Received: from e15.ny.us.ibm.com (e15.ny.us.ibm.com [129.33.205.205]) by mx0a-001b2d01.pphosted.com with ESMTP id 2eu2cnn0s7-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Wed, 13 Dec 2017 07:22:22 -0500 Received: from localhost by e15.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 13 Dec 2017 07:22:22 -0500 Received: from b01cxnp22034.gho.pok.ibm.com (9.57.198.24) by e15.ny.us.ibm.com (146.89.104.202) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 13 Dec 2017 07:22:20 -0500 Received: from b01ledav003.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp22034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id vBDCMKZL52756730; Wed, 13 Dec 2017 12:22:20 GMT Received: from b01ledav003.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 45524B2054; Wed, 13 Dec 2017 07:19:26 -0500 (EST) Received: from [9.80.205.137] (unknown [9.80.205.137]) by b01ledav003.gho.pok.ibm.com (Postfix) with ESMTP id BA98CB2050; Wed, 13 Dec 2017 07:19:25 -0500 (EST) To: freebsd-ppc@freebsd.org Subject: FreeBSD bootloader From: Breno Leitao Date: Wed, 13 Dec 2017 10:22:18 -0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en_US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 17121312-0036-0000-0000-0000029A7D4A X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00008198; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000244; SDB=6.00959599; UDB=6.00485321; IPR=6.00739621; BA=6.00005740; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00018517; XFM=3.00000015; UTC=2017-12-13 12:22:21 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17121312-0037-0000-0000-000042A783FD Message-Id: <4634e419-a0cd-45cb-b999-0ffe42ab911c@br.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-12-13_06:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1712130175 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 12:22:32 -0000 Hi, I am booting a new kernel, and I am getting the following problem: Loader variables: Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input Looking at the UPDATING file (commit #095d277cd8b), it says that I need to update the loader, since the protocol changed. I was able to build a new loader and install it inside /boot/loader, but it seems that my loader is not running on the machine boot. Is there a procedure I should use in order load this loader in the machine boot?