On Wed, 26 Mar 2025, Paul Goyette wrote:
Here's my current info - what would you want me to try? And if the
wrong thing gets deleted, how do I recover?
# efi -v
Boot0004* UEFI OS
HD(1,GPT,143a1b62-7eee-4032-adf8-dfe20a383bdb,0x800,0x640)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* UEF
On Sat, 22 Mar 2025, Paul Goyette wrote:
My machine doesn't work this way. It fails to boot if I mark the
NetBSD partition; instead it proceeds to the next bootable device.
The bootme flag seems to be acting as "this is where bootx64.efi is
found".
Can you see if there are bogus EFI boot ent
Date:Sun, 23 Mar 2025 06:12:53 +0100
From:Michael van Elst
Message-ID:
| UEFI doesn't even know the "bootme" attribue, so that must be something
| else.
It is even worse than that, despite what our gpt(8) might allow one to
believe, it is impossible to set "boot
On Wed, 26 Mar 2025, RVP wrote:
Here's my current info - what would you want me to try? And if the
wrong thing gets deleted, how do I recover?
# efi -v
Boot0004* UEFI OS
HD(1,GPT,143a1b62-7eee-4032-adf8-dfe20a383bdb,0x800,0x640)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* UEFI OS
HD(1,GPT,
On Sun, 23 Mar 2025, Paul Goyette wrote:
What do I use for ?
The efi(8) man-page explains this:
Many efi options require a number () indicating which ``Boot''
argument to modify. Many options take this as an argument, but it can
also be set with the -b option.
On Sun, 23 Mar 2025, Paul Goyette wrote:
On Mon, 24 Mar 2025, RVP wrote:
On Sat, 22 Mar 2025, Paul Goyette wrote:
My machine doesn't work this way. It fails to boot if I mark the
NetBSD partition; instead it proceeds to the next bootable device.
The bootme flag seems to be acting as "this i
On Mon, 24 Mar 2025, RVP wrote:
On Sat, 22 Mar 2025, Paul Goyette wrote:
My machine doesn't work this way. It fails to boot if I mark the
NetBSD partition; instead it proceeds to the next bootable device.
The bootme flag seems to be acting as "this is where bootx64.efi is
found".
Can you s
On Sat, 22 Mar 2025, Michael van Elst wrote:
p...@whooppee.com (Paul Goyette) writes:
My boot.cfg file looks like this:
dev=NAME=NVME-sys:
If I just let it boot and take the default option 7, the ``dev'' is not
set and the boot fails since the default dev is NAME=NVME-efi which
doesn't have
On Sun, Mar 23, 2025 at 06:46:19PM +0700, Robert Elz wrote:
> | UEFI doesn't even know the "bootme" attribue, so that must be something
> | else.
>
> It is even worse than that, despite what our gpt(8) might allow one to
> believe, it is impossible to set "bootme" on an ESP. "bootme" is one
On Sat, Mar 22, 2025 at 04:58:14PM -0700, Paul Goyette wrote:
> > I think its intention is to set which partition is to be the default root.
>
> My machine doesn't work this way. It fails to boot if I mark the
> NetBSD partition; instead it proceeds to the next bootable device.
> The bootme flag
On Sun, 23 Mar 2025, Robert Elz wrote:
Date:Sat, 22 Mar 2025 12:29:12 -0700 (PDT)
From:Paul Goyette
Message-ID:
| My default is the efi wedge, since that is the one marked with the
| ``bootme'' attribute.
That sounds wrong to me, bootme is a BSD invention (FreeBSD
Date:Sat, 22 Mar 2025 12:29:12 -0700 (PDT)
From:Paul Goyette
Message-ID:
| My default is the efi wedge, since that is the one marked with the
| ``bootme'' attribute.
That sounds wrong to me, bootme is a BSD invention (FreeBSD orig I believe),
there would be no
On Sat, 22 Mar 2025, Michael van Elst wrote:
p...@whooppee.com (Paul Goyette) writes:
My boot.cfg file looks like this:
dev=NAME=NVME-sys:
If I just let it boot and take the default option 7, the ``dev'' is not
set and the boot fails since the default dev is NAME=NVME-efi which
doesn't have a
p...@whooppee.com (Paul Goyette) writes:
>>> My boot.cfg file looks like this:
>>> dev=NAME=NVME-sys:
>>> If I just let it boot and take the default option 7, the ``dev'' is not
>>> set and the boot fails since the default dev is NAME=NVME-efi which
>>> doesn't have a /netbsd
>> How old is that bo
p...@whooppee.com (Paul Goyette) writes:
>My boot.cfg file looks like this:
>dev=NAME=NVME-sys:
>If I just let it boot and take the default option 7, the ``dev'' is not
>set and the boot fails since the default dev is NAME=NVME-efi which
>doesn't have a /netbsd
How old is that bootx64.efi ?
My boot.cfg file looks like this:
=
banner=Please select from the following menu:
userconf=disable dwiic*
userconf=disable genfb*
dev=NAME=NVME-sys:
menu=Boot normally:rndseed /var/db/entropy-file;boot NAME=NVME-sys:/netbsd
menu=Boot single user:rndseed /var/db/entropy-file;boot NAME
16 matches
Mail list logo
