9.99.26 now indeed goes through the installation in GPT/EFI without
any problems. The only wiggle - at least when booting under VirtualBox
6.1 - was it did not boot from the bootx64.efi by default; I had to
manually select the file from the 'Manage Boot Environments'
interface.
On Mon, 16 Dec
On Mon, Dec 16, 2019 at 01:52:32PM +0100, Martin Husemann wrote:
> Yes, but as a fallback it is good (and sometimes you have "serial console"
> and working copy & paste - though with modern server management this seems
> to be a lost property).
As a fallback, you can boot hd0b:/netbsd
The dev
On Mon, Dec 16, 2019 at 12:50:39PM +, Emmanuel Dreyfus wrote:
> I thought about it, but requiring the user to enter an UUID to boot
> seems harsh.
Yes, but as a fallback it is good (and sometimes you have "serial console"
and working copy & paste - though with modern server management this
On Mon, Dec 16, 2019 at 12:45:52PM +0100, Martin Husemann wrote:
> P.S.: sysinst offer naming the partitions (in the partitions detail menu),
> but it does not come up with names by itself. Could the boot code fall back
> to the guid if no name is available?
I thought about it, but requiring the
On Mon, Dec 16, 2019 at 08:52:29AM +, Emmanuel Dreyfus wrote:
> The attached patch fixes the bug by avoid using NAME= when there
> is no label. Once applied, rebuild src/sts/arch/i386/stand and
> install updated bootstrap.
This makes my old installation boot again!
Please commit + request
On Thu, Dec 12, 2019 at 08:41:15AM +0100, Martin Husemann wrote:
> Yes, it is. I took a bootable UEFI installation (in VirtualBox) and replaced
> the efi/boot/*.efi files on the MSDOS/EFI partition with the ones from
> the latest netbsd-9 build and it stopped booting as you describe.
I have a fix
On Fri, Dec 13, 2019 at 03:26:07AM +0100, Emmanuel Dreyfus wrote:
> I still cannot reproduce it. I installed a VM from
> http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/images/NetBSD-9.0_RC1-a
> md64-uefi-install.img.gz
>
> It does not suggests creating an EFI partition.
Did you boot it
Martin Husemann wrote:
> This one had been created manually and worked with old efiboot.
> Instructions would be: boot 9.0 RC1 installer uefi image, let sysinst
> install onto hard disk.
I still cannot reproduce it. I installed a VM from
Hello, there are problems with bootarm.efi also. The snapshot is
from yesterday. The kernel doesn't boot also with old bootarm.efi
or directly booting the ub version, I reported that to port-arm.
Regards,
adr.
===
U-Boot 2018.11nb4
I did install 9.0_RC1 on a bare metal machine accepting all the
defaults, and it boots fine with UEFI.
On 12/12/19 5:00 AM, Chavdar Ivanov wrote:
I can confirm - in the case of yesterday's -current - that there is
nothing wrong with the efi/gpt installation procedure and the problem
is with
I can confirm - in the case of yesterday's -current - that there is
nothing wrong with the efi/gpt installation procedure and the problem
is with the two .efi files. On VirtualBox I attached the new 'bad'
disk to the working EFI NetBSD instance, renamed the 'boot' folder in
the FAT partition to
On Thu, Dec 12, 2019 at 09:10:57AM +0100, Emmanuel Dreyfus wrote:
> Martin Husemann wrote:
>
> > Emmanuel, could you please have a look?
>
> I do not reproduce that one. Can you share the exact commands to build
> the testbed?
This one had been created manually and worked with old efiboot.
Martin Husemann wrote:
> Emmanuel, could you please have a look?
I do not reproduce that one. Can you share the exact commands to build
the testbed?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
On Thu, Dec 12, 2019 at 07:54:08AM +0100, Martin Husemann wrote:
> On Wed, Dec 11, 2019 at 10:30:44PM +, Chavdar Ivanov wrote:
> > in efi with gpt; it performs the installation lege artis, but then the
> > boot fails - the efi file tries and fails to find netbsd, nebsd.gz,
> > onetbsd etc...
>
On Wed, Dec 11, 2019 at 10:30:44PM +, Chavdar Ivanov wrote:
> in efi with gpt; it performs the installation lege artis, but then the
> boot fails - the efi file tries and fails to find netbsd, nebsd.gz,
> onetbsd etc...
That sounds like a regression in bootx64.efi, checking
Martin
Just to confirm the same. I still have a NetBSD EFI VirttualBox guest
working just fine, built around 9.99.10 or thereabouts, perhaps
following the manual installation procedure mentioned above. Upon
seeng this thread, I tried to test the installation of a fresh 9.99.21
in efi with gpt; it
On Wed, Dec 11, 2019 at 01:34:27PM -0500, Ron Georgia wrote:
> Thanks for responding Martin. Actually I did both. Selecting GPT did set
> things up but it does not boot.
OK, it worked for me when I tried last (but that is a bit ago).
Does the UEFI offer the installed drive as a bootable target?
Thanks for responding Martin. Actually I did both. Selecting GPT did set
things up but it does not boot.
On 12/11/19 1:31 PM, Martin Husemann wrote:
On Wed, Dec 11, 2019 at 01:28:31PM -0500, Ron Georgia wrote:
I installed NetBSD 9.0_RC1 as a guest on VirtualBox 5.2.34 r133883 with
GhostBSD as
On Wed, Dec 11, 2019 at 01:28:31PM -0500, Ron Georgia wrote:
> I installed NetBSD 9.0_RC1 as a guest on VirtualBox 5.2.34 r133883 with
> GhostBSD as a host. I enabled EFI and booted from the iso image. I did
> follow the "instructions" on creating a gpt partition for efi
I guess you followed the
This feels like this question has been asked before, but I could not
find what I was looking for in the mailing list archives.
I installed NetBSD 9.0_RC1 as a guest on VirtualBox 5.2.34 r133883 with
GhostBSD as a host. I enabled EFI and booted from the iso image. I did
follow the
20 matches
Mail list logo
