On Fri, Jan 18, 2019 at 2:53 PM Kurt Jaeger wrote:
> Hi!
>
> Trying to get a 8-port serial PCIe card into operation (Exsys EX-44388).
> After reboot, dmesg shows:
>
> uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0
>
> and /dev/ has cuau2* devices. It's unclear, which of the 8 ports
Hi!
Trying to get a 8-port serial PCIe card into operation (Exsys EX-44388).
After reboot, dmesg shows:
uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0
and /dev/ has cuau2* devices. It's unclear, which of the 8 ports
is cuau2 (I'll test that later, I promise 8-), but where are the
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
26 matches
Mail list logo
