On Mon, May 6, 2019 at 1:16 PM Lev Serebryakov wrote:
> On 01.05.2019 0:15, Warner Losh wrote:
>
> > I think all the features are there. You can install loader.efi as you
> > used to install boot1.efi and have it work as well or better than
> boot1.efi.
> Thank you!
>
> >
> > > But then agai
On 01.05.2019 0:15, Warner Losh wrote:
> I think all the features are there. You can install loader.efi as you
> used to install boot1.efi and have it work as well or better than boot1.efi.
Thank you!
>
> > But then again, if you are using stock (generic) OS on embedded
> system, you ar
On Mon, Jan 21, 2019 at 6:13 AM Lev Serebryakov wrote:
> On 21.01.2019 15:59, Toomas Soome wrote:
>
> > Is too complicated? Boot1.efi doesn't allow that, but loader.efi
> does.
> loader.efi lives on ESP partition, do I understand it right? So, it
> could not be damaged with "bad" up
On Fri, 2019-01-18 at 21:24 +0300, Lev Serebryakov wrote:
> On 18.01.2019 21:14, Toomas Soome wrote:
>
> > errm.. you press a key and enter device and or loader path. if it is not
> > working - the code is there to be fixed.
>
> And loader looks to "bootme" attribute and try to boot from partit
On 21.01.2019 15:59, Toomas Soome wrote:
> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
loader.efi lives on ESP partition, do I understand it right? So, it
could not be damaged with "bad" upgrade?
>>>
>>> It could, unless the backup is created.
>> Does it l
> On 21 Jan 2019, at 14:45, Lev Serebryakov wrote:
>
> On 21.01.2019 15:39, Toomas Soome wrote:
>
Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
>>> loader.efi lives on ESP partition, do I understand it right? So, it
>>> could not be damaged with "bad" upgrade?
>>
On 21.01.2019 15:39, Toomas Soome wrote:
>>> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
>> loader.efi lives on ESP partition, do I understand it right? So, it
>> could not be damaged with "bad" upgrade?
>
> It could, unless the backup is created.
Does it live on code
> On 21 Jan 2019, at 14:15, Lev Serebryakov wrote:
>
> On 20.01.2019 20:05, Warner Losh wrote:
>
>> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
> loader.efi lives on ESP partition, do I understand it right? So, it
> could not be damaged with "bad" upgrade?
>
> --
On 20.01.2019 20:05, Warner Losh wrote:
> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
loader.efi lives on ESP partition, do I understand it right? So, it
could not be damaged with "bad" upgrade?
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signa
On Sun, Jan 20, 2019, 9:29 AM Lev Serebryakov Hello Rebecca,
>
> Sunday, January 20, 2019, 7:27:56 AM, you wrote:
>
> > Ultimately, UEFI doesn't care about disks and partitions: it only really
> knows
> > about ESPs -- FAT12/16/32 formatted partitions that contain the EFI
> directory
> > structure
Hello Rebecca,
Sunday, January 20, 2019, 7:27:56 AM, you wrote:
> Ultimately, UEFI doesn't care about disks and partitions: it only really knows
> about ESPs -- FAT12/16/32 formatted partitions that contain the EFI directory
> structure. For now, that means /EFI/BOOT/BOOT{x64,i386,aa64,arm}.efi,
On Sat, Jan 19, 2019 at 11:54:25PM +0300, Lev Serebryakov wrote:
> Hello Rebecca,
>
> Saturday, January 19, 2019, 6:06:52 PM, you wrote:
>
> > Ok, I've checked my desktop Asus Z170-A, but it is graphical and I could
> > not find or understand anything in this home-rown UI with crazy-fast mouse.
On Saturday, 19 January 2019 13:54:25 MST Lev Serebryakov wrote:
> Yes, I know. But what should I do next? There is no "Set UEFI Boot Var"
> item in it. You could select different physical drives (but not partitions
> of the drives) and network cards (if PXE is enabled), and, sometimes, "EFI
> S
Hello Rebecca,
Saturday, January 19, 2019, 6:06:52 PM, you wrote:
> Ok, I've checked my desktop Asus Z170-A, but it is graphical and I could
> not find or understand anything in this home-rown UI with crazy-fast mouse.
> On ASUS systems you normally press F8 during POST to bring up the boot men
On Sat, Jan 19, 2019 at 9:32 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> > > >
> > > > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org
> > > (mailto
On 1/19/2019 10:32, Rodney W. Grimes wrote:
>> ..
> The BIOS does NOT do what our boot0 does, I have seen no BIOS that
> well allow me to select a partition on a drive, you can only select
> the drive.
>
> I think this is the feature that Lev is missing, and I am sure
> others shall miss it to
> On 19 Jan 2019, at 11:52, Lev Serebryakov wrote:
>
> Hello Warner,
>
> Saturday, January 19, 2019, 12:17:29 AM, you wrote:
>
>> Also most UEFI BIOSes I've used (which isn't a lot) allow one to choose
>> which Boot variable to use to boot. Some will even create new Boot
>> variables
> On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes <
> freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
>
> > >
> > > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org
> > (mailto:l...@freebsd.org)) wrote:
> > >
> > > > I have never seen such item in BIOS Setup. I've checked two MoBos
On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org
> (mailto:l...@freebsd.org)) wrote:
> >
> > > I have never seen such item in BIOS Setup. I've checked two MoBos now
> (one is
>
>
> On January 19, 2019 at 2:52:28 AM, Lev Serebryakov
> (l...@freebsd.org(mailto:l...@freebsd.org)) wrote:
>
> > I have never seen such item in BIOS Setup. I've checked two MoBos now (one
> > is
> > Supermicro X9something and other is brand-new Goldmont-based Chinese MiniPC
> > like Intel NUK)
Hello Tomoaki,
Saturday, January 19, 2019, 4:42:21 AM, you wrote:
> I should note that 512-bytes boot0 doesn't have that feature.
> What had it WAS larger boot0ext, which has already gone on stable/11
> and later. IIRC, sysinstall let me select which to install on MBR.
It has, look at
src/stan
On January 19, 2019 at 2:52:28 AM, Lev Serebryakov
(l...@freebsd.org(mailto:l...@freebsd.org)) wrote:
> I have never seen such item in BIOS Setup. I've checked two MoBos now (one is
> Supermicro X9something and other is brand-new Goldmont-based Chinese MiniPC
> like Intel NUK): both have one kno
Hello Emmanuel,
Saturday, January 19, 2019, 12:10:13 AM, you wrote:
> With UEFI Boot* variable you could do :
> - Update previous partition and set BootNext to it
> - If it fail next boot will be on current partition due to BootOrder
> - If it succeed, change the BootOrder to have the new pa
Hello Warner,
Saturday, January 19, 2019, 12:17:29 AM, you wrote:
> Also most UEFI BIOSes I've used (which isn't a lot) allow one to choose
> which Boot variable to use to boot. Some will even create new Boot
> variables that they use when you choose a raw device to boot from.
I have nev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Fri, 18 Jan 2019 14:17:29 -0700
Warner Losh schrieb:
> On Fri, Jan 18, 2019 at 2:11 PM Emmanuel Vadot
> wrote:
>
> > On Fri, 18 Jan 2019 22:50:31 +0300
> > Lev Serebryakov wrote:
> >
> > > On 18.01.2019 22:35, Rodney W. Grimes wrote:
> > >
On Thursday, 17 January 2019 20:02:46 MST David Wolfskill wrote:
> Does the above only apply to UEFI booting, or also to booting from
> BIOS/MBR?
It's only for UEFI booting.
--
Rebecca Cran
signature.asc
Description: This is a digitally signed message part.
On Friday, 18 January 2019 00:48:02 MST Kurt Jaeger wrote:
> > With a recent change I made for UEFI, we now install loader.efi onto the
> > ESP and don???t run boot1. That means that /boot.config is no longer
> > read, and so console settings need to be put in /boot/loader.conf
> Which change is t
On Fri, 18 Jan 2019 22:44:28 +0300
Lev Serebryakov wrote:
> On 18.01.2019 22:27, Warner Losh wrote:
>
> > > errm.. you press a key and enter device and or loader path. if it
> > is not working - the code is there to be fixed.
> > 〓And loader looks to "bootme" attribute and try to boo
On Fri, Jan 18, 2019 at 2:11 PM Emmanuel Vadot
wrote:
> On Fri, 18 Jan 2019 22:50:31 +0300
> Lev Serebryakov wrote:
>
> > On 18.01.2019 22:35, Rodney W. Grimes wrote:
> >
> > >>> errm.. you press a key and enter device and or loader path. if it is
> not working - the code is there to be fixed.
>
On Fri, 18 Jan 2019 22:50:31 +0300
Lev Serebryakov wrote:
> On 18.01.2019 22:35, Rodney W. Grimes wrote:
>
> >>> errm.. you press a key and enter device and or loader path. if it is not
> >>> working - the code is there to be fixed.
> >> And loader looks to "bootme" attribute and try to boot f
> > On 18 Jan 2019, at 21:33, Rodney W. Grimes
> > wrote:
> >
> >>
> >>
> >>> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote:
> >>>
> >>> On 18.01.2019 20:13, Warner Losh wrote:
> >>>
> > Also, there are same problems with GPT/BIOS setup (which uses GPT but
> > legacy boot) :-(
> >
On 18.01.2019 22:35, Rodney W. Grimes wrote:
>>> errm.. you press a key and enter device and or loader path. if it is not
>>> working - the code is there to be fixed.
>> And loader looks to "bootme" attribute and try to boot from partition
>> which has one, even if it is loaded from other partit
On 18.01.2019 22:27, Warner Losh wrote:
> > errm.. you press a key and enter device and or loader path. if it
> is not working - the code is there to be fixed.
> And loader looks to "bootme" attribute and try to boot from partition
> which has one, even if it is loaded from other
> On 18 Jan 2019, at 21:33, Rodney W. Grimes
> wrote:
>
>>
>>
>>> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote:
>>>
>>> On 18.01.2019 20:13, Warner Losh wrote:
>>>
> Also, there are same problems with GPT/BIOS setup (which uses GPT but
> legacy boot) :-(
>
What
> On 18.01.2019 21:14, Toomas Soome wrote:
>
> > errm.. you press a key and enter device and or loader path. if it is not
> > working - the code is there to be fixed.
> And loader looks to "bootme" attribute and try to boot from partition
> which has one, even if it is loaded from other partitio
>
>
> > On 18 Jan 2019, at 19:57, Lev Serebryakov wrote:
> >
> > On 18.01.2019 20:13, Warner Losh wrote:
> >
> >>> Also, there are same problems with GPT/BIOS setup (which uses GPT but
> >>> legacy boot) :-(
> >>>
> >>
> >> What same problems? I don't think we've touched how gptboot has hand
On Fri, Jan 18, 2019 at 11:27 AM Lev Serebryakov wrote:
> On 18.01.2019 21:14, Toomas Soome wrote:
>
> > errm.. you press a key and enter device and or loader path. if it is not
> working - the code is there to be fixed.
> And loader looks to "bootme" attribute and try to boot from partition
> w
On 18.01.2019 21:14, Toomas Soome wrote:
> errm.. you press a key and enter device and or loader path. if it is not
> working - the code is there to be fixed.
And loader looks to "bootme" attribute and try to boot from partition
which has one, even if it is loaded from other partition itself.
>
> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote:
>
> On 18.01.2019 20:13, Warner Losh wrote:
>
>>> Also, there are same problems with GPT/BIOS setup (which uses GPT but
>>> legacy boot) :-(
>>>
>>
>> What same problems? I don't think we've touched how gptboot has handed off
>> to /boot/lo
On 18.01.2019 20:13, Warner Losh wrote:
> If your BIOS allows it, you can set the standard ConOut variables the UEFI
> standard defines with the efivar program. In addition, you can add args to
> the 'binary blob' part of the BOOT OPTIONS variables (Boot), though
> efibootmgr doesn't currently
On 18.01.2019 20:13, Warner Losh wrote:
>> Also, there are same problems with GPT/BIOS setup (which uses GPT but
>> legacy boot) :-(
>>
>
> What same problems? I don't think we've touched how gptboot has handed off
> to /boot/loader in a long, long time. It there's an issue here, it's a
> differ
On Fri, Jan 18, 2019 at 8:55 AM Lev Serebryakov wrote:
> On 18.01.2019 17:10, Kyle Evans wrote:
>
> > There's some UEFI var that's supposed to serve the same kind of
> > purpose as /boot.config -- early boot parameters. I think we had
> > discussed implementing this at some point, but this hasn't
On Fri, Jan 18, 2019 at 8:27 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger >
> > > Hi!
> > >
> > > > With a recent change I made for UEFI, we now install loader.efi onto
> the
> > > ESP and don???t run boot1. That means that /boot.
On 18.01.2019 17:10, Kyle Evans wrote:
> There's some UEFI var that's supposed to serve the same kind of
> purpose as /boot.config -- early boot parameters. I think we had
> discussed implementing this at some point, but this hasn't been done
> yet as far as I've seen. Would this be usable on your
> On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger
> > Hi!
> >
> > > With a recent change I made for UEFI, we now install loader.efi onto the
> > ESP and don???t run boot1. That means that /boot.config is no longer read,
> > and so console settings need to be put in /boot/loader.conf
> >
> > Which chan
On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger Hi!
>
> > With a recent change I made for UEFI, we now install loader.efi onto the
> ESP and don???t run boot1. That means that /boot.config is no longer read,
> and so console settings need to be put in /boot/loader.conf
>
> Which change is that ?
>
Mov
On 18.01.2019 17:03, Olivier Cochard-Labbé wrote:
> > I was wondering if people will expect /boot.config to still be
> read and so code should be added to loader to continue to parse it,
> or if loader.conf can be considered the correct place and
> boot.config forgotten about?
>
The loader.efi (EFI application) can receive command line arguments, set up in
UEFI boot manager.
rgds,
toomas
> On 18 Jan 2019, at 16:14, Kurt Jaeger wrote:
>
> Hello,
>
>> I was wondering if people will expect /boot.config to still be read and so
>> code should be added to loader to cont
Hello,
> I was wondering if people will expect /boot.config to still be read and so
> code should be added to loader to continue to parse it, or if loader.conf can
> be considered the correct place and boot.config forgotten about?
If the early boot messages are not displayed as Olivier mentione
On Fri, Jan 18, 2019 at 8:04 AM Olivier Cochard-Labbé
wrote:
>
> On Fri, Jan 18, 2019 at 2:10 PM Lev Serebryakov wrote:
>
> > On 18.01.2019 5:31, Rebecca Cran wrote:
> >
> >
> > > I was wondering if people will expect /boot.config to still be read and
> > so code should be added to loader to cont
On Fri, Jan 18, 2019 at 2:10 PM Lev Serebryakov wrote:
> On 18.01.2019 5:31, Rebecca Cran wrote:
>
>
> > I was wondering if people will expect /boot.config to still be read and
> so code should be added to loader to continue to parse it, or if
> loader.conf can be considered the correct place and
On 18.01.2019 5:31, Rebecca Cran wrote:
> I was wondering if people will expect /boot.config to still be read and so
> code should be added to loader to continue to parse it, or if loader.conf can
> be considered the correct place and boot.config forgotten about?
Please, not, please support /b
Hi!
> With a recent change I made for UEFI, we now install loader.efi onto the ESP
> and don???t run boot1. That means that /boot.config is no longer read, and so
> console settings need to be put in /boot/loader.conf
Which change is that ?
> I was wondering if people will expect /boot.config
On Thu, Jan 17, 2019, 7:33 PM Rebecca Cran
> With a recent change I made for UEFI, we now install loader.efi onto the
> ESP and don’t run boot1. That means that /boot.config is no longer read,
> and so console settings need to be put in /boot/loader.conf.
> I was wondering if people will expect /b
On Thu, Jan 17, 2019 at 07:31:38PM -0700, Rebecca Cran wrote:
>
> With a recent change I made for UEFI, we now install loader.efi onto the ESP
> and don’t run boot1. That means that /boot.config is no longer read, and so
> console settings need to be put in /boot/loader.conf.
> I was wondering
With a recent change I made for UEFI, we now install loader.efi onto the ESP
and don’t run boot1. That means that /boot.config is no longer read, and so
console settings need to be put in /boot/loader.conf.
I was wondering if people will expect /boot.config to still be read and so code
should
56 matches
Mail list logo
