Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Chris 

On Fri, 8 Nov 2019 20:43:33 +0200 Toomas Soome tso...@me.com said


> On 8. Nov 2019, at 20:34, Chris  wrote:
> 
> On Fri, 8 Nov 2019 10:32:25 +0100 gljennj...@gmail.com

>  said
> 
>> On Thu, 07 Nov 2019 09:41:01 -0800

>> Chris  wrote:
>> > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
>> > > > > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote: 
> > > > > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said  > > >>

> I chose GPT.  > > > > > Maybe whoever wrote the EFI/BIOS code in your machine
> went all-in on > > > > "Legacy", and it only handles MBR disks (or disks <
> 2.2TB)?
>> > > > After all, it seems like "not booting" would be a standards-compliant
>> > > > way for a classic BIOS to handle a GPT disk.  > > > >  > > if your
> system is not booting from GPT disk, it means it is not standards
>> > > compliant.  > Interesting. So then RELENG-12 is not "Standards"
> compliant. While 13-CURRE
>> > NT is?
>> > IOW I attempted in early October to install each of the (13-CURRENT)
> instal
>> > l
>> > images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success.
> In
>> > desperation, I settled for the then (most recent) RELENG-12. 12 installed
>> > as all previous FreeBSD installs have done successfully.
>> > So something in (recent) 13' boot layout has changed. I can boot
> Legacy/UEF
>> > I/GPT
>> > on 12. But cannot boot at all in recent 13.
>> >
>> I noticed that your 12 disk has Stripesize: 0 on all partitions
>> but 13 has Stripesize: 4096 on all partitions.
>> My bootable 13 disk has Stripesize: 0 on all partitions.
>> Whether that is the cause of your problem I can't say.
> 
> Thanks for the reply, Gary.

> Toomas also had some valuable input on my problem booting 13.
> In any case. I used the installer to create the disk layout. I didn't
> do anything different than I have for many years installing FreeBSD from
> the install sources. What puzzles me, is that RELENG-12 creates a
> bootable install, whereas 13-CURRENT won't.
> I've manually setup disks innumerable times in the past. I'll see
> if doing so produces bootable media doing it from a 13-CURRENT live
> DVD, or MEMSTICK, and report my findings.
> 
> Thanks again for taking the time to reply, Gary.
>> 


Did you manage to check what is in your efi (ESP) partition? Also, can you
confirm if your system is set to boot in BIOS or UEFI mode? Note this may be
tricky to figure, for example my AMI bios depends on which device is set for
boot device. Also for UEFI boot, we do not support secure boot.


Thanks for the reminder.

It appears that the installer didn't *format* the ESP/EFI partition. Following
are the results of my investigation -- I'm also attaching a copy of the session,
should it be easier to read.

Script started on Fri Nov  8 11:04:11 2019
root@thirteen:~ # 


root@thirteen:~ # ls -la /dev/gpt/

total 1
dr-xr-xr-x   2 root  wheel  512 Nov  7 00:54 .
dr-xr-xr-x  15 root  wheel  512 Nov  6 16:54 ..
crw-r-   1 root  operator  0x8e Nov  7 00:54 throot
crw-r-   1 root  operator  0x91 Nov  7 00:54 thswap
crw-r-   1 root  operator  0x96 Nov  7 00:54 thusr
crw-r-   1 root  operator  0x93 Nov  7 00:54 thvar
crw-r-   1 root  operator  0x99 Nov  7 00:54 thxtra
crw-r-   1 root  operator  0x72 Nov  6 16:54 troot
crw-r-   1 root  operator  0x75 Nov  7 00:54 tswap
crw-r-   1 root  operator  0x7a Nov  6 16:54 tusr
crw-r-   1 root  operator  0x77 Nov  6 16:54 tvar
crw-r-   1 root  operator  0x7d Nov  6 16:54 txtra
root@thirteen:~ # mount -t msdosfs /dev/ada0p1 /mnt

root@thirteen:~ # ls -la /mnt/

total 21
drwxr-xr-x   1 root  wheel  16384 Jan  1  1980 .
drwxr-xr-x  22 root  wheel   1024 Nov  7 00:54 ..
drwxr-xr-x   1 root  wheel512 Apr 12  2016 EFI
root@thirteen:~ # ls -la /mnt/EFI/

total 17
drwxr-xr-x  1 root  wheel512 Apr 12  2016 .
drwxr-xr-x  1 root  wheel  16384 Jan  1  1980 ..
drwxr-xr-x  1 root  wheel512 Apr 12  2016 BOOT
root@thirteen:~ # ls -la /mnt/EFI/BOOT/

total 130
drwxr-xr-x  1 root  wheel 512 Apr 12  2016 .
drwxr-xr-x  1 root  wheel 512 Apr 12  2016 ..
-rwxr-xr-x  1 root  wheel  131072 Apr 12  2016 BOOTX64.EFI
-rwxr-xr-x  1 root  wheel  12 Apr 12  2016 STARTUP.NSH
root@thirteen:~ # umount /mnt/

root@thirteen:~ # mount -t msdosfs /dev/ada1p1 /mnt

mount_msdosfs: /dev/ada1p1: Invalid argument
root@thirteen:~ # ls /dev/ada*

/dev/ada0   /dev/ada0p2 /dev/ada0p4 /dev/ada0p6 /dev/ada1p1 /dev/ada1p3 
/dev/ada1p5
/dev/ada0p1 /dev/ada0p3 /dev/ada0p5 /dev/ada1   /dev/ada1p2 /dev/ada1p4 
/dev/ada1p6
root@thirteen:~ # mount /dev/ada1p1 /mnt/

mount: /dev/ada1p1: No such file or directory
root@thirteen:~ # exit

exit

Script done on Fri Nov  8 11:09:35 2019


Thanks again!

--Chris


rgds,
toomas


DISKCHECK
Description: DISKCHECK
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any

Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Chris 

On Fri, 8 Nov 2019 07:53:49 -0500 Ed Maste ema...@freebsd.org said


On Thu, 7 Nov 2019 at 03:38, Chris  wrote:
>
> I'm wondering what happened between RELENG-12, and 13 that made the change?

What is the latest 12.x you tried that worked in this configuration?


Thanks for the reply, Ed.

FreeBSD 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 #0 r353409:
Thu Oct 10 15:57:48 PDT 2019 amd64

Thanks again!

--Chris


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Toomas Soome 



> On 8. Nov 2019, at 20:34, Chris  wrote:
> 
> On Fri, 8 Nov 2019 10:32:25 +0100 gljennj...@gmail.com 
>  said
> 
>> On Thu, 07 Nov 2019 09:41:01 -0800
>> Chris  wrote:
>> > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
>> > > > > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:  
>> > > > > > > > > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com 
>> > > > > said  > > >> I chose GPT.  > > > > > Maybe whoever wrote the 
>> > > > > EFI/BIOS code in your machine went all-in on > > > > "Legacy", and 
>> > > > > it only handles MBR disks (or disks < 2.2TB)?
>> > > > After all, it seems like "not booting" would be a standards-compliant
>> > > > way for a classic BIOS to handle a GPT disk.  > > > >   > > if your 
>> > > > system is not booting from GPT disk, it means it is not standards
>> > > compliant.  > Interesting. So then RELENG-12 is not "Standards" 
>> > > compliant. While 13-CURRE
>> > NT is?
>> > IOW I attempted in early October to install each of the (13-CURRENT) instal
>> > l
>> > images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success. In
>> > desperation, I settled for the then (most recent) RELENG-12. 12 installed
>> > as all previous FreeBSD installs have done successfully.
>> > So something in (recent) 13' boot layout has changed. I can boot Legacy/UEF
>> > I/GPT
>> > on 12. But cannot boot at all in recent 13.
>> >
>> I noticed that your 12 disk has Stripesize: 0 on all partitions
>> but 13 has Stripesize: 4096 on all partitions.
>> My bootable 13 disk has Stripesize: 0 on all partitions.
>> Whether that is the cause of your problem I can't say.
> 
> Thanks for the reply, Gary.
> Toomas also had some valuable input on my problem booting 13.
> In any case. I used the installer to create the disk layout. I didn't
> do anything different than I have for many years installing FreeBSD from
> the install sources. What puzzles me, is that RELENG-12 creates a
> bootable install, whereas 13-CURRENT won't.
> I've manually setup disks innumerable times in the past. I'll see
> if doing so produces bootable media doing it from a 13-CURRENT live
> DVD, or MEMSTICK, and report my findings.
> 
> Thanks again for taking the time to reply, Gary.
>> 

Did you manage to check what is in your efi (ESP) partition? Also, can you 
confirm if your system is set to boot in BIOS or UEFI mode? Note this may be 
tricky to figure, for example my AMI bios depends on which device is set for 
boot device. Also for UEFI boot, we do not support secure boot.

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Chris 

On Fri, 8 Nov 2019 10:32:25 +0100 gljennj...@gmail.com said


On Thu, 07 Nov 2019 09:41:01 -0800
Chris  wrote:

> On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
> 
> > > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:  
> > > > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said  
> > >> I chose GPT.  
> > > > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on 
> 
> > > "Legacy", and it only handles MBR disks (or disks < 2.2TB)?

> > > After all, it seems like "not booting" would be a standards-compliant
> > > way for a classic BIOS to handle a GPT disk.  
> > > >   
> > if your system is not booting from GPT disk, it means it is not standards
> > compliant.  
> Interesting. So then RELENG-12 is not "Standards" compliant. While 13-CURRE

> NT is?
> IOW I attempted in early October to install each of the (13-CURRENT) instal
> l
> images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success. In
> desperation, I settled for the then (most recent) RELENG-12. 12 installed
> as all previous FreeBSD installs have done successfully.
> So something in (recent) 13' boot layout has changed. I can boot Legacy/UEF
> I/GPT
> on 12. But cannot boot at all in recent 13.
>

I noticed that your 12 disk has Stripesize: 0 on all partitions
but 13 has Stripesize: 4096 on all partitions.

My bootable 13 disk has Stripesize: 0 on all partitions.

Whether that is the cause of your problem I can't say.


Thanks for the reply, Gary.
Toomas also had some valuable input on my problem booting 13.
In any case. I used the installer to create the disk layout. I didn't
do anything different than I have for many years installing FreeBSD from
the install sources. What puzzles me, is that RELENG-12 creates a
bootable install, whereas 13-CURRENT won't.
I've manually setup disks innumerable times in the past. I'll see
if doing so produces bootable media doing it from a 13-CURRENT live
DVD, or MEMSTICK, and report my findings.

Thanks again for taking the time to reply, Gary.


[snip gpart output]

--
Gary Jennejohn


--Chris


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Ed Maste 
On Thu, 7 Nov 2019 at 03:38, Chris  wrote:
>
> I'm wondering what happened between RELENG-12, and 13 that made the change?

What is the latest 12.x you tried that worked in this configuration?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Gary Jennejohn 
On Thu, 07 Nov 2019 09:41:01 -0800
Chris  wrote:

> On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
> 
> > > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:  
> > > > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said  
> > >> I chose GPT.  
> > > > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on  
> > > "Legacy", and it only handles MBR disks (or disks < 2.2TB)?
> > > After all, it seems like "not booting" would be a standards-compliant
> > > way for a classic BIOS to handle a GPT disk.  
> > > >   
> > if your system is not booting from GPT disk, it means it is not standards
> > compliant.  
> Interesting. So then RELENG-12 is not "Standards" compliant. While 13-CURRE
> NT is?
> IOW I attempted in early October to install each of the (13-CURRENT) instal
> l
> images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success. In
> desperation, I settled for the then (most recent) RELENG-12. 12 installed
> as all previous FreeBSD installs have done successfully.
> So something in (recent) 13' boot layout has changed. I can boot Legacy/UEF
> I/GPT
> on 12. But cannot boot at all in recent 13.
>

I noticed that your 12 disk has Stripesize: 0 on all partitions
but 13 has Stripesize: 4096 on all partitions.

My bootable 13 disk has Stripesize: 0 on all partitions.

Whether that is the cause of your problem I can't say.

[snip gpart output]

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome 


> On 7. Nov 2019, at 21:07, Chris  wrote:
> 
> On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tso...@me.com 
>  said
> 
>> > On 7. Nov 2019, at 19:37, Chris.H  wrote:
>> > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
>> > >> > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:
>> >> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said
>> >> >> I chose GPT.
>> >> > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on
>> >> > "Legacy", and it only handles MBR disks (or disks < 2.2TB)?
>> >> > After all, it seems like "not booting" would be a standards-compliant
>> >> > way for a classic BIOS to handle a GPT disk.
>> >> > if your system is not booting from GPT disk, it means it is not 
>> >> > standards
>> >> compliant.
>> > Interesting. So then RELENG-12 is not "Standards" compliant. While 
>> > 13-CURRENT
>> > is?
>> Can not tell if you do not provide actual information, we can not really tell
>> too much. However, based on the partition tables below, I can tell a bit.
>> Those disks are using GPT, there is EFI partition, which does suggest UEFI
>> boot and not BIOS boot. There is no freebsd-boot partition, meaning the
>> standard pmbr boot block does not work (if installed) — pmbr does search
>> for freebsd-boot and will load its content and jumps on it. Without seeing
>> your sector 0, I can not tell what code is there (if any), and based on
>> partitions on that system, it is possible the BIOS boot is not installed at
>> all. In a similar way, without seeing EFI partition content, we can not tell
>> if UEFI boot is actually installed - EFI partition should have FAT file
>> system with specific directory tree.
>> To make things better, the exact description would be helpful, so the devs
>> taking care of installer could review the information and make fixes.
> 
> Right. Sorry. I forgot you had asked for the output of dd(1).
> 
> I've done so, and will send you the output directly (off list).
> 

neither of disks had boot code in MBR block, so BIOS boot was definitely not 
going to happen there (the regular pmbr there would not help because there is 
no freebsd-boot partition). Therefore the question is if the ESP was set up 
properly.

My personal suggestion for x86 setups would be to set up both bios and efi boot.

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Chris 

On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tso...@me.com said


> On 7. Nov 2019, at 19:37, Chris.H  wrote:
> 
> On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
> 
>> > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:

>> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said
>> >> I chose GPT.
>> > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on
>> > "Legacy", and it only handles MBR disks (or disks < 2.2TB)?
>> > After all, it seems like "not booting" would be a standards-compliant
>> > way for a classic BIOS to handle a GPT disk.
>> > if your system is not booting from GPT disk, it means it is not standards
>> compliant.
> Interesting. So then RELENG-12 is not "Standards" compliant. While 13-CURRENT
> is?


Can not tell if you do not provide actual information, we can not really tell
too much. However, based on the partition tables below, I can tell a bit.

Those disks are using GPT, there is EFI partition, which does suggest UEFI
boot and not BIOS boot. There is no freebsd-boot partition, meaning the
standard pmbr boot block does not work (if installed) — pmbr does search
for freebsd-boot and will load its content and jumps on it. Without seeing
your sector 0, I can not tell what code is there (if any), and based on
partitions on that system, it is possible the BIOS boot is not installed at
all. In a similar way, without seeing EFI partition content, we can not tell
if UEFI boot is actually installed - EFI partition should have FAT file
system with specific directory tree.

To make things better, the exact description would be helpful, so the devs
taking care of installer could review the information and make fixes.


Right. Sorry. I forgot you had asked for the output of dd(1).

I've done so, and will send you the output directly (off list).

Thank you!


rgds,
toomas



[snip]

--Chris


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome 


> On 7. Nov 2019, at 19:37, Chris.H  wrote:
> 
> On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
> 
>> > On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:
>> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said
>> >> I chose GPT.
>> > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on
>> > "Legacy", and it only handles MBR disks (or disks < 2.2TB)?
>> > After all, it seems like "not booting" would be a standards-compliant
>> > way for a classic BIOS to handle a GPT disk.
>> > if your system is not booting from GPT disk, it means it is not standards
>> compliant.
> Interesting. So then RELENG-12 is not "Standards" compliant. While 13-CURRENT 
> is?


Can not tell if you do not provide actual information, we can not really tell 
too much. However, based on the partition tables below, I can tell a bit.

Those disks are using GPT, there is EFI partition, which does suggest UEFI boot 
and not BIOS boot. There is no freebsd-boot partition, meaning the standard 
pmbr boot block does not work (if installed) — pmbr does search for 
freebsd-boot and will load its content and jumps on it. Without seeing your 
sector 0, I can not tell what code is there (if any), and based on partitions 
on that system, it is possible the BIOS boot is not installed at all. In a 
similar way, without seeing EFI partition content, we can not tell if UEFI boot 
is actually installed - EFI partition should have FAT file system with specific 
directory tree.

To make things better, the exact description would be helpful, so the devs 
taking care of installer could review the information and make fixes.

rgds,
toomas


> IOW I attempted in early October to install each of the (13-CURRENT) install
> images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success. In
> desperation, I settled for the then (most recent) RELENG-12. 12 installed
> as all previous FreeBSD installs have done successfully.
> So something in (recent) 13' boot layout has changed. I can boot 
> Legacy/UEFI/GPT
> on 12. But cannot boot at all in recent 13.
> Following is the output of the RELENG-12 disk, as well as 13-CURRENT:
> 
> LIVE BOOTED DISK @FreeBSD 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 #0 
> r353409:
> Thu Oct 10 15:57:48 PDT 2019 amd64
> 
> Geom name: ada0
> modified: false
> state: OK
> fwheads: 16
> fwsectors: 63
> last: 976773127
> first: 40
> entries: 152
> scheme: GPT
> Providers:
> 1. Name: ada0p1
>  Mediasize: 209715200 (200M)
>  Sectorsize: 512
>  Stripesize: 0
>  Stripeoffset: 20480
>  Mode: r0w0e0
>  efimedia: HD(1,GPT,280cea32-eae6-11e9-ae21-4c72b9f5e07f,0x28,0x64000)
>  rawuuid: 280cea32-eae6-11e9-ae21-4c72b9f5e07f
>  rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
>  label: (null)
>  length: 209715200
>  offset: 20480
>  type: efi
>  index: 1
>  end: 409639
>  start: 40
> 2. Name: ada0p2
>  Mediasize: 27707572224 (26G)
>  Sectorsize: 512
>  Stripesize: 0
>  Stripeoffset: 209735680
>  Mode: r1w1e2
>  efimedia: HD(2,GPT,2856af2c-eae6-11e9-ae21-4c72b9f5e07f,0x64028,0x339c000)
>  rawuuid: 2856af2c-eae6-11e9-ae21-4c72b9f5e07f
>  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
>  label: troot
>  length: 27707572224
>  offset: 209735680
>  type: freebsd-ufs
>  index: 2
>  end: 54525991
>  start: 409640
> 3. Name: ada0p3
>  Mediasize: 3984588800 (3.7G)
>  Sectorsize: 512
>  Stripesize: 0
>  Stripeoffset: 2147504128
>  Mode: r1w1e1
>  efimedia: HD(3,GPT,3c01ab9d-eae6-11e9-ae21-4c72b9f5e07f,0x3400028,0x76c000)
>  rawuuid: 3c01ab9d-eae6-11e9-ae21-4c72b9f5e07f
>  rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
>  label: tswap
>  length: 3984588800
>  offset: 27917307904
>  type: freebsd-swap
>  index: 3
>  end: 62308391
>  start: 54525992
> 4. Name: ada0p4
>  Mediasize: 68719476736 (64G)
>  Sectorsize: 512
>  Stripesize: 0
>  Stripeoffset: 1837125632
>  Mode: r1w1e2
>  efimedia: HD(4,GPT,4abf5d7c-eae6-11e9-ae21-4c72b9f5e07f,0x3b6c028,0x800)
>  rawuuid: 4abf5d7c-eae6-11e9-ae21-4c72b9f5e07f
>  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
>  label: tvar
>  length: 68719476736
>  offset: 31901896704
>  type: freebsd-ufs
>  index: 4
>  end: 196526119
>  start: 62308392
> 5. Name: ada0p5
>  Mediasize: 289910292480 (270G)
>  Sectorsize: 512
>  Stripesize: 0
>  Stripeoffset: 1837125632
>  Mode: r1w1e2
>  efimedia: HD(5,GPT,58f639dd-eae6-11e9-ae21-4c72b9f5e07f,0xbb6c028,0x21c0)
>  rawuuid: 58f639dd-eae6-11e9-ae21-4c72b9f5e07f
>  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
>  label: tusr
>  length: 289910292480
>  offset: 100621373440
>  type: freebsd-ufs
>  index: 5
>  end: 762757159
>  start: 196526120
> 6. Name: ada0p6
>  Mediasize: 109521666048 (102G)
>  Sectorsize: 512
>  Stripesize: 0
>  Stripeoffset: 3984609280
>  Mode: r0w0e0
>  efimedia: HD(6,GPT,650e64bd-eae6-11e9-ae21-4c72b9f5e07f,0x2d76c028,0xcc0)
>  rawuuid: 650e64bd-eae6-11e9-ae21-4c72b9f5e07f
>  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
>  label: txtra
>  length: 109521666048
>  offset: 390531665920
>  type: freebsd-ufs
>  index:

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Chris 

On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said


> On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:
> 
>> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said

>> I chose GPT.
> 
> Maybe whoever wrote the EFI/BIOS code in your machine went all-in on

> "Legacy", and it only handles MBR disks (or disks < 2.2TB)?
> After all, it seems like "not booting" would be a standards-compliant
> way for a classic BIOS to handle a GPT disk.
> 


if your system is not booting from GPT disk, it means it is not standards
compliant.

Interesting. So then RELENG-12 is not "Standards" compliant. While 13-CURRENT 
is?
IOW I attempted in early October to install each of the (13-CURRENT) install
images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success. In
desperation, I settled for the then (most recent) RELENG-12. 12 installed
as all previous FreeBSD installs have done successfully.
So something in (recent) 13' boot layout has changed. I can boot Legacy/UEFI/GPT
on 12. But cannot boot at all in recent 13.
Following is the output of the RELENG-12 disk, as well as 13-CURRENT:

LIVE BOOTED DISK @FreeBSD 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 #0 r353409:
Thu Oct 10 15:57:48 PDT 2019 amd64

Geom name: ada0
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 976773127
first: 40
entries: 152
scheme: GPT
Providers:
1. Name: ada0p1
  Mediasize: 209715200 (200M)
  Sectorsize: 512
  Stripesize: 0
  Stripeoffset: 20480
  Mode: r0w0e0
  efimedia: HD(1,GPT,280cea32-eae6-11e9-ae21-4c72b9f5e07f,0x28,0x64000)
  rawuuid: 280cea32-eae6-11e9-ae21-4c72b9f5e07f
  rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
  label: (null)
  length: 209715200
  offset: 20480
  type: efi
  index: 1
  end: 409639
  start: 40
2. Name: ada0p2
  Mediasize: 27707572224 (26G)
  Sectorsize: 512
  Stripesize: 0
  Stripeoffset: 209735680
  Mode: r1w1e2
  efimedia: HD(2,GPT,2856af2c-eae6-11e9-ae21-4c72b9f5e07f,0x64028,0x339c000)
  rawuuid: 2856af2c-eae6-11e9-ae21-4c72b9f5e07f
  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
  label: troot
  length: 27707572224
  offset: 209735680
  type: freebsd-ufs
  index: 2
  end: 54525991
  start: 409640
3. Name: ada0p3
  Mediasize: 3984588800 (3.7G)
  Sectorsize: 512
  Stripesize: 0
  Stripeoffset: 2147504128
  Mode: r1w1e1
  efimedia: HD(3,GPT,3c01ab9d-eae6-11e9-ae21-4c72b9f5e07f,0x3400028,0x76c000)
  rawuuid: 3c01ab9d-eae6-11e9-ae21-4c72b9f5e07f
  rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
  label: tswap
  length: 3984588800
  offset: 27917307904
  type: freebsd-swap
  index: 3
  end: 62308391
  start: 54525992
4. Name: ada0p4
  Mediasize: 68719476736 (64G)
  Sectorsize: 512
  Stripesize: 0
  Stripeoffset: 1837125632
  Mode: r1w1e2
  efimedia: HD(4,GPT,4abf5d7c-eae6-11e9-ae21-4c72b9f5e07f,0x3b6c028,0x800)
  rawuuid: 4abf5d7c-eae6-11e9-ae21-4c72b9f5e07f
  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
  label: tvar
  length: 68719476736
  offset: 31901896704
  type: freebsd-ufs
  index: 4
  end: 196526119
  start: 62308392
5. Name: ada0p5
  Mediasize: 289910292480 (270G)
  Sectorsize: 512
  Stripesize: 0
  Stripeoffset: 1837125632
  Mode: r1w1e2
  efimedia: HD(5,GPT,58f639dd-eae6-11e9-ae21-4c72b9f5e07f,0xbb6c028,0x21c0)
  rawuuid: 58f639dd-eae6-11e9-ae21-4c72b9f5e07f
  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
  label: tusr
  length: 289910292480
  offset: 100621373440
  type: freebsd-ufs
  index: 5
  end: 762757159
  start: 196526120
6. Name: ada0p6
  Mediasize: 109521666048 (102G)
  Sectorsize: 512
  Stripesize: 0
  Stripeoffset: 3984609280
  Mode: r0w0e0
  efimedia: HD(6,GPT,650e64bd-eae6-11e9-ae21-4c72b9f5e07f,0x2d76c028,0xcc0)
  rawuuid: 650e64bd-eae6-11e9-ae21-4c72b9f5e07f
  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
  label: txtra
  length: 109521666048
  offset: 390531665920
  type: freebsd-ufs
  index: 6
  end: 97663
  start: 762757160
Consumers:
1. Name: ada0
  Mediasize: 500107862016 (466G)
  Sectorsize: 512
  Mode: r4w4e11
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
FRESH 13-CURRENT INSTALL

Geom name: ada1
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 1953525127
first: 40
entries: 152
scheme: GPT
Providers:
1. Name: ada1p1
  Mediasize: 272629760 (260M)
  Sectorsize: 512
  Stripesize: 4096
  Stripeoffset: 0
  Mode: r0w0e0
  efimedia: HD(1,GPT,8dace702-fbde-11e9-9be1-4c72b9f5e07f,0x28,0x82000)
  rawuuid: 8dace702-fbde-11e9-9be1-4c72b9f5e07f
  rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
  label: (null)
  length: 272629760
  offset: 20480
  type: efi
  index: 1
  end: 532519
  start: 40
2. Name: ada1p2
  Mediasize: 34087104512 (32G)
  Sectorsize: 512
  Stripesize: 4096
  Stripeoffset: 0
  Mode: r0w0e0
  efimedia: HD(2,GPT,8df547ab-fbde-11e9-9be1-4c72b9f5e07f,0x82028,0x3f7dff8)
  rawuuid: 8df547ab-fbde-11e9-9be1-4c72b9f5e07f
  rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
  label: throot
  length: 34087104512
  offset: 272650240
  type: freebsd-ufs
  index: 2
  end: 67108895
  start: 532520
3. Name: ada1p3
  Mediasize:

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome 



> On 7. Nov 2019, at 17:23, Daniel Nebdal  wrote:
> 
>> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said
>> I chose GPT.
> 
> Maybe whoever wrote the EFI/BIOS code in your machine went all-in on
> "Legacy", and it only handles MBR disks (or disks < 2.2TB)?
> After all, it seems like "not booting" would be a standards-compliant
> way for a classic BIOS to handle a GPT disk.
> 

if your system is not booting from GPT disk, it means it is not standards 
compliant.

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Daniel Nebdal 
> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said
> I chose GPT.

Maybe whoever wrote the EFI/BIOS code in your machine went all-in on
"Legacy", and it only handles MBR disks (or disks < 2.2TB)?
After all, it seems like "not booting" would be a standards-compliant
way for a classic BIOS to handle a GPT disk.

-- 
Daniel Nebdal
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Chris 

On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said


On Thu, 07 Nov 2019 00:38:29 -0800
Chris  wrote:

> On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said
> 
> > > On 7. Nov 2019, at 10:05, Chris  wrote:  
> > > > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said  
> > > > >> On Wed, 06 Nov 2019 17:23:08 -0800  
> > >> Chris  wrote:  
> > >> > I put a box together to test 13 about a mos ago.

> > >> > It's a second gen core i3. But whether choosing automatic
> > >> > disk layout, or choosing manual. When the install finishes, and
> > >> > boots to the drive. The BIOS reports no bootable media.
> > >> > I finally gave up, and grabbed the most recent RELENG-12. Which
> > >> > worked as expected.
> > >> > While I have no troubles booting (U)EFI. Isn't the so-called
> > >> > LEGACY boot option still supported?  
> > >> > > Thank you for all your time, and consideration.  
> > >> > > > > > Thanks for taking the time to respond, Gary.  
> > > > >> I installed the latest FreeBSD 13 memstick image (UEFI) yesterday  
> > >> and had no problem booting it.  I used manual disk partitioning. In
> fact,  
> > > when I added the / partition the installer automatically  
> > >> created and populated the EFI boot partition for me.  
> > > > > Same here. But in spite of it. The reboot proved to be unsuccessful.
> :(  
> > >> I used UEFI because that was already set in the BIOS and the

> > >> computer doesn't belong to me.
> > >> LEGACY mode should still work as long as the BIOS offers that. My main 
> 
> > > FreeBSD 13 box uses LEGACY booting.  
> > > > > My BIOS offers both. Yet neither option proved fruitful. :(  
> > >> -- > >> Gary Jennejohn  
> > > > > Thanks again, Gary! :)  
> > > >   
> > Do you have more detailed information? any error messages, screenshots?  
> 
> Thanks for the reply, toomas.
> 
> It's just the standard BIOS report about non-bootable device, please inset

> bootable medium...
> 
> IOW it doesn't recognize the freshly installed 13-CURRENT on the hard drive

> as being a bootable OS.
> 
> I'm wondering what happened between RELENG-12, and 13 that made the change?
> 
> Thanks again!
> 


Did you use MBR (which seems to be the default) or GPT?  I forced the
installer to use GPT.


I chose GPT.

Thanks for asking.


--
Gary Jennejohn


--Chris


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome 



> On 7. Nov 2019, at 10:38, Chris  wrote:
> 
> On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com 
>  said
> 
>> > On 7. Nov 2019, at 10:05, Chris  wrote:
>> > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said
>> > >> On Wed, 06 Nov 2019 17:23:08 -0800
>> >> Chris  wrote:
>> >> > I put a box together to test 13 about a mos ago.
>> >> > It's a second gen core i3. But whether choosing automatic
>> >> > disk layout, or choosing manual. When the install finishes, and
>> >> > boots to the drive. The BIOS reports no bootable media.
>> >> > I finally gave up, and grabbed the most recent RELENG-12. Which
>> >> > worked as expected.
>> >> > While I have no troubles booting (U)EFI. Isn't the so-called
>> >> > LEGACY boot option still supported?
>> >> > > Thank you for all your time, and consideration.
>> >> > > > Thanks for taking the time to respond, Gary.
>> > >> I installed the latest FreeBSD 13 memstick image (UEFI) yesterday
>> >> and had no problem booting it.  I used manual disk partitioning. In fact,
>> > when I added the / partition the installer automatically
>> >> created and populated the EFI boot partition for me.
>> > > Same here. But in spite of it. The reboot proved to be unsuccessful. :(
>> >> I used UEFI because that was already set in the BIOS and the
>> >> computer doesn't belong to me.
>> >> LEGACY mode should still work as long as the BIOS offers that. My main
>> > FreeBSD 13 box uses LEGACY booting.
>> > > My BIOS offers both. Yet neither option proved fruitful. :(
>> >> -- >> Gary Jennejohn
>> > > Thanks again, Gary! :)
>> > Do you have more detailed information? any error messages, screenshots?
> 
> Thanks for the reply, toomas.
> 
> It's just the standard BIOS report about non-bootable device, please inset
> bootable medium...
> 
> IOW it doesn't recognize the freshly installed 13-CURRENT on the hard drive
> as being a bootable OS.
> 
> I'm wondering what happened between RELENG-12, and 13 that made the change?
> 

If the BIOS does not find bootable disk, it likely does check the MBR, please 
use dd to read out sector 0 from your boot disk (something like dd if=/dev/da0 
of=mbr.dd count=1) and mail it to me directly so I can check what is there.

rgds,
toomas


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Gary Jennejohn 
On Thu, 07 Nov 2019 00:38:29 -0800
Chris  wrote:

> On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said
> 
> > > On 7. Nov 2019, at 10:05, Chris  wrote:  
> > > > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said  
> > > > >> On Wed, 06 Nov 2019 17:23:08 -0800  
> > >> Chris  wrote:  
> > >> > I put a box together to test 13 about a mos ago.
> > >> > It's a second gen core i3. But whether choosing automatic
> > >> > disk layout, or choosing manual. When the install finishes, and
> > >> > boots to the drive. The BIOS reports no bootable media.
> > >> > I finally gave up, and grabbed the most recent RELENG-12. Which
> > >> > worked as expected.
> > >> > While I have no troubles booting (U)EFI. Isn't the so-called
> > >> > LEGACY boot option still supported?  
> > >> > > Thank you for all your time, and consideration.  
> > >> > > > > > Thanks for taking the time to respond, Gary.  
> > > > >> I installed the latest FreeBSD 13 memstick image (UEFI) yesterday  
> > >> and had no problem booting it.  I used manual disk partitioning. In 
> > >> fact,  
> > > when I added the / partition the installer automatically  
> > >> created and populated the EFI boot partition for me.  
> > > > > Same here. But in spite of it. The reboot proved to be unsuccessful. 
> > > > > :(  
> > >> I used UEFI because that was already set in the BIOS and the
> > >> computer doesn't belong to me.
> > >> LEGACY mode should still work as long as the BIOS offers that. My main  
> > > FreeBSD 13 box uses LEGACY booting.  
> > > > > My BIOS offers both. Yet neither option proved fruitful. :(  
> > >> -- > >> Gary Jennejohn  
> > > > > Thanks again, Gary! :)  
> > > >   
> > Do you have more detailed information? any error messages, screenshots?  
> 
> Thanks for the reply, toomas.
> 
> It's just the standard BIOS report about non-bootable device, please inset
> bootable medium...
> 
> IOW it doesn't recognize the freshly installed 13-CURRENT on the hard drive
> as being a bootable OS.
> 
> I'm wondering what happened between RELENG-12, and 13 that made the change?
> 
> Thanks again!
> 

Did you use MBR (which seems to be the default) or GPT?  I forced the
installer to use GPT.

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Chris 

On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said


> On 7. Nov 2019, at 10:05, Chris  wrote:
> 
> On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said
> 
>> On Wed, 06 Nov 2019 17:23:08 -0800

>> Chris  wrote:
>> > I put a box together to test 13 about a mos ago.
>> > It's a second gen core i3. But whether choosing automatic
>> > disk layout, or choosing manual. When the install finishes, and
>> > boots to the drive. The BIOS reports no bootable media.
>> > I finally gave up, and grabbed the most recent RELENG-12. Which
>> > worked as expected.
>> > While I have no troubles booting (U)EFI. Isn't the so-called
>> > LEGACY boot option still supported?
>> > > Thank you for all your time, and consideration.
>> > 
> 
> Thanks for taking the time to respond, Gary.
> 
>> I installed the latest FreeBSD 13 memstick image (UEFI) yesterday

>> and had no problem booting it.  I used manual disk partitioning. In fact,
> when I added the / partition the installer automatically
>> created and populated the EFI boot partition for me.
> 
> Same here. But in spite of it. The reboot proved to be unsuccessful. :(

>> I used UEFI because that was already set in the BIOS and the
>> computer doesn't belong to me.
>> LEGACY mode should still work as long as the BIOS offers that. My main
> FreeBSD 13 box uses LEGACY booting.
> 
> My BIOS offers both. Yet neither option proved fruitful. :(
>> -- 
>> Gary Jennejohn
> 
> Thanks again, Gary! :)
> 


Do you have more detailed information? any error messages, screenshots?


Thanks for the reply, toomas.

It's just the standard BIOS report about non-bootable device, please inset
bootable medium...

IOW it doesn't recognize the freshly installed 13-CURRENT on the hard drive
as being a bootable OS.

I'm wondering what happened between RELENG-12, and 13 that made the change?

Thanks again!

--Chris


rgds,
toomas



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome 



> On 7. Nov 2019, at 10:05, Chris  wrote:
> 
> On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said
> 
>> On Wed, 06 Nov 2019 17:23:08 -0800
>> Chris  wrote:
>> > I put a box together to test 13 about a mos ago.
>> > It's a second gen core i3. But whether choosing automatic
>> > disk layout, or choosing manual. When the install finishes, and
>> > boots to the drive. The BIOS reports no bootable media.
>> > I finally gave up, and grabbed the most recent RELENG-12. Which
>> > worked as expected.
>> > While I have no troubles booting (U)EFI. Isn't the so-called
>> > LEGACY boot option still supported?
>> > > Thank you for all your time, and consideration.
>> > 
> 
> Thanks for taking the time to respond, Gary.
> 
>> I installed the latest FreeBSD 13 memstick image (UEFI) yesterday
>> and had no problem booting it.  I used manual disk partitioning. In fact, 
>> when I added the / partition the installer automatically
>> created and populated the EFI boot partition for me.
> 
> Same here. But in spite of it. The reboot proved to be unsuccessful. :(
>> I used UEFI because that was already set in the BIOS and the
>> computer doesn't belong to me.
>> LEGACY mode should still work as long as the BIOS offers that. My main 
>> FreeBSD 13 box uses LEGACY booting.
> 
> My BIOS offers both. Yet neither option proved fruitful. :(
>> -- 
>> Gary Jennejohn
> 
> Thanks again, Gary! :)
> 

Do you have more detailed information? any error messages, screenshots?

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Chris 

On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said


On Wed, 06 Nov 2019 17:23:08 -0800
Chris  wrote:

> I put a box together to test 13 about a mos ago.
> It's a second gen core i3. But whether choosing automatic
> disk layout, or choosing manual. When the install finishes, and
> boots to the drive. The BIOS reports no bootable media.
> I finally gave up, and grabbed the most recent RELENG-12. Which
> worked as expected.
> While I have no troubles booting (U)EFI. Isn't the so-called
> LEGACY boot option still supported?
> 
> Thank you for all your time, and consideration.
> 


Thanks for taking the time to respond, Gary.



I installed the latest FreeBSD 13 memstick image (UEFI) yesterday
and had no problem booting it.  I used manual disk partitioning. 
In fact, when I added the / partition the installer automatically

created and populated the EFI boot partition for me.


Same here. But in spite of it. The reboot proved to be unsuccessful. :(


I used UEFI because that was already set in the BIOS and the
computer doesn't belong to me.

LEGACY mode should still work as long as the BIOS offers that. 
My main FreeBSD 13 box uses LEGACY booting.


My BIOS offers both. Yet neither option proved fruitful. :(


--
Gary Jennejohn


Thanks again, Gary! :)


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT October images do not create a bootable install

2019-11-06 Thread Gary Jennejohn 
On Wed, 06 Nov 2019 17:23:08 -0800
Chris  wrote:

> I put a box together to test 13 about a mos ago.
> It's a second gen core i3. But whether choosing automatic
> disk layout, or choosing manual. When the install finishes, and
> boots to the drive. The BIOS reports no bootable media.
> I finally gave up, and grabbed the most recent RELENG-12. Which
> worked as expected.
> While I have no troubles booting (U)EFI. Isn't the so-called
> LEGACY boot option still supported?
> 
> Thank you for all your time, and consideration.
> 

I installed the latest FreeBSD 13 memstick image (UEFI) yesterday
and had no problem booting it.  I used manual disk partitioning. 
In fact, when I added the / partition the installer automatically
created and populated the EFI boot partition for me.

I used UEFI because that was already set in the BIOS and the
computer doesn't belong to me.

LEGACY mode should still work as long as the BIOS offers that. 
My main FreeBSD 13 box uses LEGACY booting.

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"