From owner-freebsd-current@freebsd.org Tue Oct 23 20:33:58 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 D71CDFFC062 for ; Tue, 23 Oct 2018 20:33:57 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc2b.google.com (mail-yw1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) (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 690388F613 for ; Tue, 23 Oct 2018 20:33:57 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc2b.google.com with SMTP id i185-v6so1116385ywa.12 for ; Tue, 23 Oct 2018 13:33:57 -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=g7MlBMyQT48v6rL6p0xIWN+ttIDqaccClv2WuCQNR7Q=; b=bVKhjJUZ4VZ9EZgRpqd3iXn0sXNx63iYBDYqsilUDzYOAod7w+lYhOV4/Yx8DLJ0Jl Mmo66JJIitYL5ojwTvqtKos4GZR2FvFw3eumCQVqkBQdaZ6eRNUOOqjatTZCuzRQddBF 7NIDAy7MnottDM9p+6conIEh/5qn2GFinUte2aJdNhOm1jBA4VXn0/NfF6Qe+UxhgOct satvsenfzBPsc8o9XErYMg0m6TLF0i9dKoul/qVTEhwv8yWeS0M8Drw1R0As8mU2Iyzc 0wVRsqvQrQzScFV2QtTgbZS2MujJZXv5mrqz18ssZAsrvu9hu0oxzxdG0vgzH/J84jIQ O0BA== 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=g7MlBMyQT48v6rL6p0xIWN+ttIDqaccClv2WuCQNR7Q=; b=cnl7cfQIw8m9iulenZlFVsvGZ08ZkV9XySpVcqiTUb0A0i9KZfFWaRlw+kVAsgBPD3 O1iX4SOIbodAIvUNFrYyfeMPJ8qd5GETkoYgdce5llVqYWOeW2zijGR4h6axMH554WDb y6denCqFIqrHMwCPESwjD9cunrj6WbNkE06ZuKtx1ZrDxOBPXgWrXe9IL/T32UUH38RZ raLdCqJq6k40aiIRTqrO5CmJ04S1S8oHbV+VU7mmwT2hCg1cZrOlTkaeIPEnAk27O1jT JptgsnI5fFgGi3pQ/QsDOcsZCgWbtjgTK1vLaSskMqaiFDy9hgOvd6ASDhGziLTQ0N+W zrZQ== X-Gm-Message-State: ABuFfojGMYC8RHV7NLjfl+VNAct2MoVCG2tOba9xauuVDgxylTp2Y9s6 OU52NClKCmGgtp7L49bvMQoR34A9PlJ7dLUKjmRCig== X-Google-Smtp-Source: ACcGV63iqdrbyFiYosUbmQ7EhrCOpUhUCp7pB4nRMhGZTydGHvnRkqviRfO6NiDDfTEpaUazsSi1kr8Db8gMVRbQ3uo= X-Received: by 2002:a0d:f144:: with SMTP id a65-v6mr37115066ywf.330.1540326836805; Tue, 23 Oct 2018 13:33:56 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 13:33:55 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Tue, 23 Oct 2018 21:33:55 +0100 X-Google-Sender-Auth: aVpBpjBSY4aUYoV7YcAqXI833Hs Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: FreeBSD Current 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2018 20:33:58 -0000 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 wrote: > you should have the binaries in boot - just ln (or copy) one to loader.ef= i > > rgds, > toomas > > > On 23 Oct 2018, at 23:22, Harry Newton 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 wrote: > >> ok, in that case I=E2=80=99d suggest to test out if forth based one is s= till >> 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 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 wrote: >> > >> >> hm. in that case, whats the content of /boot/loader.rc ? >> >> >> >> rgds, >> >> toomas >> >> >> >> >> >> On 23 Oct 2018, at 23:01, Harry Newton 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 but i= n 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 wrote: >> >> >> >>> Do you get boot menu? if so, press esc to get to ok prompt, then typ= e >> >>> start - if its bootfort based loader, it will load the kernel and >> modules. >> >>> lsmod will then list the loaded files. >> >>> >> >>> If the loader prompt is still usable, then next command would be: bo= ot >> >>> >> >>> rgds, >> >>> toomas >> >>> >> >>>> On 23 Oct 2018, at 20:45, Harry Newton wrote: >> >>>> >> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 >> >>> 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? kldlo= ad >> >>> 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 > > > --=20 Harry Newton