From owner-freebsd-current@freebsd.org Wed Feb 21 13:58:56 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 DE07EF03DA5 for ; Wed, 21 Feb 2018 13:58:55 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 517C87BB9C; Wed, 21 Feb 2018 13:58:55 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f46.google.com with SMTP id g72so2481393lfg.5; Wed, 21 Feb 2018 05:58:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=MLb5SKa32krWl5fQNm8rtlvRyzh4G5OWWCf6v0A7A90=; b=AVM8rEbhglKFUf1EcYdPgy+5til365Q23bkEJkQZ2CLv5F4O35ietYM2PAPwnsEQob Vj0iGgV9D986wOjtv25WtDo+i4NDvjAa9gCG738wwFOtNvZ1wNVCXqPuRFgXh7myOmuv Ssv38LZzg4Qr0rdb9/I8Cp5PLUFzCyHKPtX3cfdYANF8mBXsCZ/QEjJ39V9KgWREXPEd hkvnSlujg6eBq1EtarC3mdN0ptCkK6xOpzQYqabqVT4KIisOdabKN/jZtfz7IxpKsetw gW/MagEvMymwd2uW8xGyoxgumtPah+GHUPdD8/gf1lVFDcx9WwBKt50UILCcPZGj8uDY XpBQ== X-Gm-Message-State: APf1xPAZE6rPMMOPNSL32VKSHZ6BGKbTsnnXvoX5OlDsBheIkL91VYSi Rt4kAWSc9bHxr3vAnbnLFIxcMqnb X-Google-Smtp-Source: AH8x2249kQqlb4+5g3FKr/yLPTssxSI9EX8K1awptlucI42YPY+ky2wUiL6VhHwfIaadPUxvl3DdUg== X-Received: by 10.46.29.147 with SMTP id w19mr2370050lje.70.1519221527208; Wed, 21 Feb 2018 05:58:47 -0800 (PST) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com. [209.85.215.47]) by smtp.gmail.com with ESMTPSA id k8sm165148ljk.63.2018.02.21.05.58.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Feb 2018 05:58:47 -0800 (PST) Received: by mail-lf0-f47.google.com with SMTP id t79so2492587lfe.3; Wed, 21 Feb 2018 05:58:47 -0800 (PST) X-Received: by 10.46.64.203 with SMTP id r72mr2654570lje.38.1519221526708; Wed, 21 Feb 2018 05:58:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.106.8 with HTTP; Wed, 21 Feb 2018 05:58:24 -0800 (PST) In-Reply-To: References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> From: Kyle Evans Date: Wed, 21 Feb 2018 07:58:24 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: ACPI panic on boot with new Lua loader and other minor issues To: =?UTF-8?Q?Juan_Ram=C3=B3n_Molina_Menor?= Cc: rgrimes@freebsd.org, FreeBSD Current , imp@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 13:58:56 -0000 On Wed, Feb 21, 2018 at 4:43 AM, Juan Ram=C3=B3n Molina Menor wrote: > Le 20/02/2018 =C3=A0 22:45, Kyle Evans a =C3=A9crit : >> >> On Mon, Feb 19, 2018 at 8:21 AM, Juan Ram=C3=B3n 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 =E2=80=99fake=E2=80=99 > Failed to load any kernel > can=E2=80=99t load =E2=80=99kernel=E2=80=99 > > The two last lines are odd: Did the loader try to load a fallback kernel = and > failed? That would explain the =E2=80=99kernel=E2=80=99 name in quotes, b= ut I have such a > kernel=E2=80=A6 Also, just nitpicking, but "can=E2=80=99t" should be capi= talized. (CC'ing Rod, since he also commented on this) I'm only directly responsible for the first two messages. =3D) I've removed the second one, though, since it was a carry-over from when it would try to load the selected kernel and then some default kernel that might be in your module_path. We can look at changing "can't load 'kernel'" to capitalize and remove the contraction, but that's common loader stuff and should've also been displayed for the same Forth scenario. > 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 chan= ge > the gop mode in the loader with 'gop set [0-3]'. > Oy. This is actually a Forth file, so we can't really maintain all of the functionality that would have been allowed there. Technically, things like this should probably either appear in your loader.conf(5) in the form of 'exec=3D"gop set 3"' to be applied when loader.conf(5) is read, or we should provide some other means of running pure loader command scripts at different points in the loader sequence. (CC Warner, because he probably has thoughts about this latter idea)