> On 2018-07-06 04:17, Warner Losh wrote:
> > On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> >> > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
> >> >
> >> > > [ Charset UTF-8 unsupported, converting... ]
> >> > >> On 5 Jul 2018, at
On 2018-07-06 09:34, Bjoern A. Zeeb wrote:
On 6 Jul 2018, at 6:34, Emmanuel Vadot wrote:
FAT12 can work with all EFI implementation, the problem is the size
of the FAT12 part that sometimes causes problems.
Ok, now that we are all on the same page, changing it to newfs_msdos
-F 32 did not
On 6 Jul 2018, at 6:34, Emmanuel Vadot wrote:
FAT12 can work with all EFI implementation, the problem is the size
of the FAT12 part that sometimes causes problems.
Ok, now that we are all on the same page, changing it to newfs_msdos -F
32 did not make a change to my problem of the boot
On 2018-07-06 04:17, Warner Losh wrote:
On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
>
> > [ Charset UTF-8 unsupported, converting... ]
> >> On 5 Jul 2018, at 17:19, Warner Losh wrote:
> >>
>
On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
> >
> > > [ Charset UTF-8 unsupported, converting... ]
> > >> On 5 Jul 2018, at 17:19, Warner Losh wrote:
> > >>
> > >>> FAT12 isn't good for UEFI.
> On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
>
> > [ Charset UTF-8 unsupported, converting... ]
> >> On 5 Jul 2018, at 17:19, Warner Losh wrote:
> >>
> >>> FAT12 isn't good for UEFI. Use FAT16 or FAT32.
> >>
> >> We use it for the default image we built and the wiki suggests it as
> >> well
On Thu, Jul 5, 2018 at 3:31 PM, Bjoern A. Zeeb <
bzeeb-li...@lists.zabbadoz.net> wrote:
> On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
>
> [ Charset UTF-8 unsupported, converting... ]
>>
>>> On 5 Jul 2018, at 17:19, Warner Losh wrote:
>>>
>>> FAT12 isn't good for UEFI. Use FAT16 or FAT32.
On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
[ Charset UTF-8 unsupported, converting... ]
On 5 Jul 2018, at 17:19, Warner Losh wrote:
FAT12 isn't good for UEFI. Use FAT16 or FAT32.
We use it for the default image we built and the wiki suggests it as
well at
On Thu, Jul 5, 2018, 12:55 PM Bjoern A. Zeeb
wrote:
> On 5 Jul 2018, at 17:19, Warner Losh wrote:
>
> > FAT12 isn't good for UEFI. Use FAT16 or FAT32.
>
> We use it for the default image we built and the wiki suggests it as
> well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI
>
> I
[ Charset UTF-8 unsupported, converting... ]
> On 5 Jul 2018, at 17:19, Warner Losh wrote:
>
> > FAT12 isn't good for UEFI. Use FAT16 or FAT32.
>
> We use it for the default image we built and the wiki suggests it as
> well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI
IIRC FreeBSD
On 5 Jul 2018, at 17:19, Warner Losh wrote:
FAT12 isn't good for UEFI. Use FAT16 or FAT32.
We use it for the default image we built and the wiki suggests it as
well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI
I wonder where this “default” came from?
/bz
FAT12 isn't good for UEFI. Use FAT16 or FAT32.
Warner
On Thu, Jul 5, 2018, 9:32 AM Bjoern A. Zeeb
wrote:
> Hi,
>
> while I can boot memstick images just fine (which are created using
> makefs/mkimg), doing the same thing using gpart/newfs_msdos -F 12/.. I
> am not able to get anything that
Bjoern,
I had this problem earlier this week while using
FreeBSD-12.0-CURRENT-amd64-20180628-r335760-memstick.img on my ThinkPad P50.
I had used `dd` to place the img file on a partition (e.g. /dev/sdb1) of the
USB pen drive and it wouldn't boot properly.
After I used `dd` to place the img on
On 2018-07-05 16:30, Bjoern A. Zeeb wrote:
Hi,
while I can boot memstick images just fine (which are created using
makefs/mkimg), doing the same thing using gpart/newfs_msdos -F 12/.. I
am not able to get anything that boots.
What is the size for the fat12 partition ? Everything over ~30MB
14 matches
Mail list logo
