From owner-freebsd-current@freebsd.org Wed Feb 21 10:43:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 103BAF1C69C for ; Wed, 21 Feb 2018 10:43:29 +0000 (UTC) (envelope-from listjm@club.fr) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B9B672102 for ; Wed, 21 Feb 2018 10:43:28 +0000 (UTC) (envelope-from listjm@club.fr) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) by msfrf2629.sfr.fr (SMTP Server) with ESMTP id 849541C030C16 for ; Wed, 21 Feb 2018 11:43:27 +0100 (CET) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juanmolina@sfr.fr) by msfrf2629.sfr.fr (SMTP Server) with ESMTPSA; Wed, 21 Feb 2018 11:43:27 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=juanmolina@sfr.fr Subject: Re: ACPI panic on boot with new Lua loader and other minor issues To: Kyle Evans Cc: FreeBSD Current References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor Message-ID: Date: Wed, 21 Feb 2018 11:43:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: X-sfr-mailing: LEGIT Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Wed, 21 Feb 2018 10:43:29 -0000 Le 20/02/2018 à 22:45, Kyle Evans a écrit : > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: >> [... snip ...] >> >> Moreover, the "boot [kernel]" loader command does not work: >> >> OK ls /boot/kernel.old/kernel >> /boot/kernel.old/kernel >> OK boot kernel.old >> Command failed >> OK boot /boot/kernel.old/kernel >> Command failed >> OK boot kernel >> Command failed >> >> On the other hand, just "boot" works. >> > > This part should work as expected as of r329674, so please give that a > shot. I'm still trying to see if I can reproduce your box drawing > problem. > > Thanks, > > Kyle Evans > Thanks Kyle. boot command works now. There is though a somewhat strangely formulated messages when trying to load an non-existent kernel: OK boot fake Failed to load kernel ’fake’ Failed to load any kernel can’t load ’kernel’ The two last lines are odd: Did the loader try to load a fallback kernel and failed? That would explain the ’kernel’ name in quotes, but I have such a kernel… Also, just nitpicking, but "can’t" should be capitalized. Then, I have just remembered why I was seeing a higher resolution menu before: I had set 'gop set 0' in /boot/loader.rc.local. It seems the new loader is not implementing the inclusion of this file, because I can change the gop mode in the loader with 'gop set [0-3]'. This has thus nothing to do with the drawing lines, I guess. Best regards.