01 2a 00 01 00 00 00 28 00
>> 0020: 00 00 00 00 00 00 00 40 06 00 00 00 00 00 f1 84
>> 0030: d7 13 ca da e8 11 94 1d 30 85 a9 40 0a 5c 02 02
>> 0040: 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00
>> 0050: 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00
>>
nfortunately- 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/1
Thanks — please let me if there's anything I can do to help.
On 24 October 2018 at 18:25, Warner Losh wrote:
>
>
> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote:
>
>> gryphon# efivar -N --hex $(efivar | grep Boot0002)
>> : 01 00 00 00 98 00 55 00 45 00
:
>
>
> On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote:
>
>> Booted with the installer image makes efibootmgr to work as you said:
>>
>> gryphon# efibootmgr -v
>> BootCurrent: 0002
>> Timeout : 2 seconds
>> BootOrder : 0001, 0002
>>
24 October 2018 at 08:13, Harry Newton wrote:
> Booted with the installer image makes efibootmgr to work as you said:
>
> gryphon# efibootmgr -v
> BootCurrent: 0002
> Timeout : 2 seconds
> BootOrder : 0001, 0002
> Boot0001* UEFI OS HD(1,GPT,b19ccd5d-7c6a-11e7-
> ae3e-28b2b
t; 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 wrote:
> >
> > I set LOADER_D
espite
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 wrote:
> Right ... I've the binaries in /boot, freshly made. This might be a silly
> question ... do I not need
) one to loader.efi
>
> 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, h
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 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, H
> If the loader prompt is still usable, then next command would be: boot
>
> 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 wit
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
12 matches
Mail list logo
