From: Warner Losh
Subject: Re: Updating EFI boot loader results in boot hangup
Date: Mon, 15 Aug 2022 21:35:52 -0600
> Would you be able to share camcontrol devlist output? Privately if
> need be.
root@rolling-vm-freebsd1[1001]# camcontrol devlist
at scbus0 target 0 lun 0
On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote:
> From: Yasuhiro Kimura
> Subject: Re: Updating EFI boot loader results in boot hangup
> Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST)
>
> > From: Yasuhiro Kimura
> > Subject: Updating EFI boot loader results in boot hangup
> > Date: Sat, 13
From: Yasuhiro Kimura
Subject: Re: Updating EFI boot loader results in boot hangup
Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST)
> From: Yasuhiro Kimura
> Subject: Updating EFI boot loader results in boot hangup
> Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST)
>
>> I made regular update of my
On Sat, Aug 13, 2022 at 10:41:33PM -0400, Dan Mahoney wrote:
|
|
| > On Aug 12, 2022, at 12:35, Doug Ambrisko wrote:
| >
| > On Fri, Aug 12, 2022 at 12:32:56PM -0400, Dan Mahoney wrote:
| > |
| > |
| > | > On Aug 12, 2022, at 12:31, Doug Ambrisko wrote:
| > | >
| > | > On Fri, Aug 12, 2022
On Mon, 15 Aug 2022 22:11:59 +0200, Warner Losh wrote:
>
> This should be fixed now.
>
> commit d98de7440507aea1648c8f4bc302bf88c0eb9458
> Author: Toomas Soome
> Date: Mon Aug 15 00:49:50 2022 +0300
>
> loader: zfs reader should only store devdesc in f_devdata
>
> Use d_opendata for
On 15-8-2022 22:11, Warner Losh wrote:
This should be fixed now.
commit d98de7440507aea1648c8f4bc302bf88c0eb9458
Author: Toomas Soome
Date: Mon Aug 15 00:49:50 2022 +0300
loader: zfs reader should only store devdesc in f_devdata
Use d_opendata for device specific data.
PR:
This should be fixed now.
commit d98de7440507aea1648c8f4bc302bf88c0eb9458
Author: Toomas Soome
Date: Mon Aug 15 00:49:50 2022 +0300
loader: zfs reader should only store devdesc in f_devdata
Use d_opendata for device specific data.
PR: 265825
Reviewed by:imp
On Sun, Aug 14, 2022 at 7:52 AM Graham Perrin
wrote:
> On 12/08/2022 17:54, Yasuhiro Kimura wrote:
>
> … amd64 … (/boot/efi/efi/freebsd/loader.efi) …
>
> Side note: please, why the FreeBSD reserved area?
>
When you create a boot variable using efibootmgr, it's better to specify
something that's
> On 15. Aug 2022, at 18:22, Toomas Soome wrote:
>
>
>
>> On 15. Aug 2022, at 18:01, FreeBSD User wrote:
>>
>> Hello,
>>
>> I'm running a FreeBSD 13.1-RELENG-p1 zroot-based guest in a VirtualBox
>> 4.1.24/26 (do not know
>> exactly). The host is a special system based on Linux und
> On 15. Aug 2022, at 18:01, FreeBSD User wrote:
>
> Hello,
>
> I'm running a FreeBSD 13.1-RELENG-p1 zroot-based guest in a VirtualBox
> 4.1.24/26 (do not know
> exactly). The host is a special system based on Linux und VirtualBox and I
> have no chances to
> configure the VBox.
>
>
Hello,
I'm running a FreeBSD 13.1-RELENG-p1 zroot-based guest in a VirtualBox
4.1.24/26 (do not know
exactly). The host is a special system based on Linux und VirtualBox and I have
no chances to
configure the VBox.
Somehow the VBox crashed and hung up the complete computer, so I had to cold
Hi,
I tried upgrading a 14.0-CURRENT system from somewhere Dec 2021, to the
most recent state.
So I build everything and installed the things...
Reboot and I end up in BTX
Oke, so I perhaps should also update pmbr and gptzfsboot.
Booted from stick, and update...
Still I end up in BTX.
12 matches
Mail list logo
