Date: Wed, 21 Feb 2018 07:58:24 -0600 From: Kyle Evans <kevans@freebsd.org> To: =?UTF-8?Q?Juan_Ram=C3=B3n_Molina_Menor?= <listjm@club.fr> Cc: rgrimes@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, imp@freebsd.org Subject: Re: ACPI panic on boot with new Lua loader and other minor issues Message-ID: <CACNAnaFubiW1guSkNfy6vOTvgpV%2BfhACM6ceoiz0VXSG5VXpdQ@mail.gmail.com> In-Reply-To: <b2607cde-fdb8-495b-d221-3b23a775b4de@club.fr> References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> <CACNAnaH-WQCLix6Jq_HXGz9tJMXPzxWkoQUwg7RrHatmUdFsEw@mail.gmail.com> <b2607cde-fdb8-495b-d221-3b23a775b4de@club.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 21, 2018 at 4:43 AM, Juan Ram=C3=B3n Molina Menor <listjm@club.= fr> 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 <listjm@cl= ub.fr> >> 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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaFubiW1guSkNfy6vOTvgpV%2BfhACM6ceoiz0VXSG5VXpdQ>