From owner-freebsd-current@freebsd.org Fri Oct 26 21:47:21 2018 Return-Path: <owner-freebsd-current@freebsd.org> 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 3B84B10C7ED2 for <freebsd-current@mailman.ysv.freebsd.org>; Fri, 26 Oct 2018 21:47:21 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc41.google.com (mail-yw1-xc41.google.com [IPv6:2607:f8b0:4864:20::c41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9B216BFFA for <freebsd-current@freebsd.org>; Fri, 26 Oct 2018 21:47:20 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc41.google.com with SMTP id t78-v6so1048299ywg.11 for <freebsd-current@freebsd.org>; Fri, 26 Oct 2018 14:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FotkN9dCxgX3eWChTVgn0lC5f7UbHl60YtGorWK8woY=; b=OASvfaCBmXT2rZbXPb0t/9yyra/pD7F352gmbIrXPJy4FQ1/B2PBET7qVMV3WzBTNC nnXKttEuIfbw3Xi3VHH6kJ8ERvT967OiAPqhBp2eYnOx6jE24jgG8YJA6F1MHzVQFzLh 7HbYbj1kDgSMWtxG94UFFaY/N61Zy/1vbXIR3mN33SQtp71L2yBYuft9O0X6+o4T7LEp bxIqABxmpeZ8VKoaJeqtVPzFH/K41i67IpUR1x78fGZujE6J/cC/3m9Z73/2DbGul0u2 N/HCyauCatPta7JG+ek0HaOts2ZZzAoWdvM/gZhJOT9QNYEhatecrmbIBKYpdtaw+Jty aK4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=FotkN9dCxgX3eWChTVgn0lC5f7UbHl60YtGorWK8woY=; b=qqIR4zfSPzLq0TzINh5JBkDIiZfuB/S7oEOvMqJ+7tC+0WtzECGDbgYaKMfdeT/Zpl 8TbUW2btPPQJPkeBthyrJTn1y8BKSY8inIAnMw4rsZH18n1njgQSVUI3zWythXtUm5h3 hEymDmfE3I1L80goRFIuYBJ3KruQw5nFqqC5BsBVGjzIhv8Y6mimcRzs7zHgjsdnXrPI wmDS9XPk7XJZK/YOBbvtmW1rP7KUP+S3nZ7DvwTQBgNjiOtaMd9vtOP2cavKYYmxzN0X m0n+Xzbq98E3jHXHB1Cy0SDEr2jkkbs5GrCqso78jggg3ZyuMB7wgVc5u5s5fXF5ux7f O0FQ== X-Gm-Message-State: AGRZ1gIiG99xLKm486kAjp2zWGu/jYTQ1e/P2KxVeeaJaq1cNuckP7Oq PPBx6QuLWRh3GL5tCqNnPfF+xxVIZdko1rhSO+FUYQ== X-Google-Smtp-Source: AJdET5fBjPMd2V4Pi8g773iql7WbM2zViP1ZX2fgGCH2s0WGdc9JA4MCFXN0pmvz0mw65JPj7FuAJjenxexpOhy9L5k= X-Received: by 2002:a81:5214:: with SMTP id g20-v6mr5454524ywb.252.1540590439937; Fri, 26 Oct 2018 14:47:19 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:807:0:0:0:0:0 with HTTP; Fri, 26 Oct 2018 14:47:19 -0700 (PDT) In-Reply-To: <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> References: <CAKAm69Fw+X3Xik6rUcEOrr0TtxypEc2D05+5g9JGh=N2VxZGpA@mail.gmail.com> <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <CAKAm69EMraV0KaPEbsxTcEpwFjpNZtW-sc42mmSq=9vv+iyGzQ@mail.gmail.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <CAKAm69Gd1yq0Lss2nByjkkfiTPCAW6wvaKPF8LVqbw+vbEnxUQ@mail.gmail.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <CAKAm69EF98FZnh0KHkArPGX=_7OZT369kQr3J5YigE-0mOsgqA@mail.gmail.com> <B5749B46-02E5-4B48-858B-EE2743281154@me.com> <CAKAm69HrTh+ibMi8GHV9CpUa2=2jsof2AXk5LeOE0TwRxTWc3w@mail.gmail.com> <CAKAm69FEOCWwEPr3ZLVOYHuVyZYNACbXhzhwH_4VgC0DV9B7jw@mail.gmail.com> <CACNAnaGrk9tN0Pg0HeODRuSnqGCaSZSBQtvV6JscVh+7hBCN+Q@mail.gmail.com> <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> From: Harry Newton <hn@yewbarrow.net> Date: Fri, 26 Oct 2018 22:47:19 +0100 X-Google-Sender-Auth: kAS60LKsv_LZVwbJKFTiNaTdTn8 Message-ID: <CAKAm69GSF9o6XAFMdiChXKs5eSsUs7H7W+t5DRDSNMbPWAPaXA@mail.gmail.com> Subject: Re: UEFI boot hangs after loader To: Toomas Soome <tsoome@me.com>, imp@bsdimp.com Cc: FreeBSD Current <freebsd-current@freebsd.org>, Kyle Evans <kevans@freebsd.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/> List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 26 Oct 2018 21:47:21 -0000 So patching out find_currdev() in efi/loader/main.c allows the machine to boot. The hang occurs in the call to efi_devpath_name() in match_boot_info() because the (last) call to ConvertDevicePathToText() call does not return. /H On 24 October 2018 at 07:32, Toomas Soome <tsoome@me.com> wrote: > > > > On 24 Oct 2018, at 00:51, Kyle Evans <kevans@freebsd.org> wrote: > > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for booting? If that works, we can explore UEFI > > variables from there. > > > > > Yes, thats my guess too, my guess is that since in general the uefi boot > is working, in this case it has to be some corner case, and I would start > checking with boot variable related code; specifically, I=E2=80=99d sugge= st to > patch (temporarily) the find_currdev() in efi/loader/main.c to set > do_bootmgr =3D false and see if that will fix the boot. Then we can explo= re > what is happening in match_boot_info() > > rgds, > toomas > > > efibootmgr will only work on a successful UEFI boot, unfortunately- if > > we didn't make uefi loader -> kernel transition, then we don't have > > access to runtime services. > > > > Thanks, > > > > Kyle Evans > > > > [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO- > IMAGES/12.0/ > > > > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton <hn@yewbarrow.net> wrote: > >> > >> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-ma= de > the > >> binaries in /boot but this doesn't solve the problem. It did copy > >> /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8= ) > >> which is what is called from /boot/boot1.efi and which contains the > strings > >> I see on the console before the hang. But it must then call / read > >> something else and I don't think it can find it. Not sure why it > doesn't > >> produce an error message. I *think* it may be something to do with EF= I > >> variables, but as efibootmgr doesn't work I can't explore this, despit= e > >> efirt being in the kernel. > >> > >> Suggestions received welcomed, and new suggestions / leads to follow > also > >> very much welcomed. > >> > >> /H > >> > >> > >> On 23 October 2018 at 21:33, Harry Newton <hn@yewbarrow.net> wrote: > >> > >>> Right ... I've the binaries in /boot, freshly made. This might be a > silly > >>> question ... do I not need to copy them (or dd the boot1.efifat image= ) > to > >>> the EFI partition ? > >>> > >>> /H > >>> > >>> On 23 October 2018 at 21:30, Toomas Soome <tsoome@me.com> wrote: > >>> > >>>> you should have the binaries in boot - just ln (or copy) one to > loader.efi > >>>> > >>>> rgds, > >>>> toomas > >>>> > >>>> > >>>> On 23 Oct 2018, at 23:22, Harry Newton <hn@yewbarrow.net> wrote: > >>>> > >>>> Yes ... so as everything is built, can I just alter > LOADER_DEFAULT_INTERP > >>>> in /etc/make.conf and then reinstall just the loader and boot parts > onto > >>>> the UEFI partition ? If so, how ? > >>>> > >>>> > >>>> On 23 October 2018 at 21:17, Toomas Soome <tsoome@me.com> wrote: > >>>> > >>>>> ok, in that case I=E2=80=99d suggest to test out if forth based one= is still > >>>>> working - at least you can get the bootable system. And then there > is a > >>>>> chance to debug the lua version too (note it should be possible to > chain > >>>>> /boot/loader_lua.efi). > >>>>> > >>>>> rgds, > >>>>> toomas > >>>>> > >>>>>> On 23 Oct 2018, at 23:08, Harry Newton <hn@yewbarrow.net> wrote: > >>>>>> > >>>>>> So it's got FORTH in it, but my loader is lua based, and also > doesn't > >>>>>> appear to read loader.rc. > >>>>>> > >>>>>> /H > >>>>>> > >>>>>> On 23 October 2018 at 21:03, Toomas Soome <tsoome@me.com> wrote: > >>>>>> > >>>>>>> hm. in that case, whats the content of /boot/loader.rc ? > >>>>>>> > >>>>>>> rgds, > >>>>>>> toomas > >>>>>>> > >>>>>>> > >>>>>>> On 23 Oct 2018, at 23:01, Harry Newton <hn@yewbarrow.net> wrote: > >>>>>>> > >>>>>>> If boot menu is the screen where you get the options for various > >>>>> kernels > >>>>>>> and the picture of the daemon head, no. It stops at the point in > my > >>>>> email > >>>>>>> =E2=80=94 though not as I said just before the kernel is loaded b= ut in > point > >>>>> of > >>>>>>> fact before the menu. > >>>>>>> > >>>>>>> I've also rebuilt the kernel and still can't use efibootmgr which > is > >>>>>>> puzzling me. > >>>>>>> > >>>>>>> /H > >>>>>>> > >>>>>>> > >>>>>>> On 23 October 2018 at 20:56, Toomas Soome <tsoome@me.com> wrote: > >>>>>>> > >>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, then > type > >>>>>>>> start - if its bootfort based loader, it will load the kernel an= d > >>>>> modules. > >>>>>>>> lsmod will then list the loaded files. > >>>>>>>> > >>>>>>>> If the loader prompt is still usable, then next command would be= : > >>>>> boot > >>>>>>>> > >>>>>>>> rgds, > >>>>>>>> toomas > >>>>>>>> > >>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton <hn@yewbarrow.net> wrote= : > >>>>>>>>> > >>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BET= A1 > >>>>>>>> r339529 > >>>>>>>>> by source. Have a problem with booting which hangs after: > >>>>>>>>> > >>>>>>>>>>> FreeBSD EFI boot block > >>>>>>>>> Loader path: /boot/loader.efi > >>>>>>>>> > >>>>>>>>> Initializing modules: ZFS UFS > >>>>>>>>> Probing 5 block devices ... done > >>>>>>>>> ZFS found the following pools: zroot > >>>>>>>>> UFS found no partitions > >>>>>>>>> Consoles: EFI console > >>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>>>>>>>> > >>>>>>>>> Command line arguments: loader.efi > >>>>>>>>> EFI version 2.31 > >>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) > >>>>>>>>> Console: efi(0) > >>>>>>>>> Load Path: HD(4, GPT [ ... ] > >>>>>>>>> Load Device: Pci Root [ ... ] > >>>>>>>>> Boot Current: 0001 > >>>>>>>>> Boot Order: 0001 [x] > >>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > >>>>>>>>> - > >>>>>>>>> > >>>>>>>>> So it gets into loader.efi which runs but stops I think just > before > >>>>>>>> loading > >>>>>>>>> the kernel. Partitions: > >>>>>>>>> > >>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) > >>>>>>>>> 40 1600 1 efi (800K) > >>>>>>>>> 1640 1024 2 freebsd-boot (512K) > >>>>>>>>> 2664 1432 - free - (716K) > >>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) > >>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) > >>>>>>>>> 250068992 648 - free - (324K) > >>>>>>>>> > >>>>>>>>> and the EFI partition is FAT 12. > >>>>>>>>> > >>>>>>>>> I can't provide (at the moment) any output from efibootmgr: > >>>>>>>>> > >>>>>>>>> root@gryphon:~ # efibootmgr -v > >>>>>>>>> efibootmgr: efi variables not supported on this system. root? > >>>>> kldload > >>>>>>>> efirt? > >>>>>>>>> root@gryphon:~ # kldload efirt > >>>>>>>>> kldload: can't load efirt: module already loaded or in kernel > >>>>>>>>> > >>>>>>>>> which I don't understand. > >>>>>>>>> > >>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see if > that > >>>>>>>> allows > >>>>>>>>> me to load efirt / use efibootmgr. > >>>>>>>>> > >>>>>>>>> In the meantime, I should be very grateful for any advice. > >>>>>>>>> > >>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and > dropping > >>>>> into > >>>>>>>> its > >>>>>>>>> loader to get to the installed 12-STABLE ). > >>>>>>>>> > >>>>>>>>> /Harry > >>>>>>>>> _______________________________________________ > >>>>>>>>> freebsd-current@freebsd.org mailing list > >>>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>>>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>>>>>>> reebsd.org" > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Harry Newton > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Harry Newton > >>>>>> _______________________________________________ > >>>>>> freebsd-current@freebsd.org mailing list > >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>>>> reebsd.org" > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Harry Newton > >>>> > >>>> > >>>> > >>> > >>> > >>> -- > >>> Harry Newton > >>> > >> > >> > >> > >> -- > >> Harry Newton > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@ > freebsd.org" > > --=20 Harry Newton