Emmanuel Dreyfus wrote:
> - in UEFI mode, bootstrap does not read boot.cfg and while it sees the
> GPT partitions, it is unable to access a RAID that has a GPT inside. It
> can access a RAID that has a disklabel inside, though, but that does not
> help for > 2 TB.
Reading the sources, I find
Emmanuel Dreyfus wrote:
> I try to boot NetBSD/Xen from a GPT, with little success.
>
> I understand NetBSD EFI bootstrap does not support multiboot, so I
> should use BIOS boot.
That poins seems false, I found multiboot code in EFI boot after all.
I made some progress: it seems the BIOS/UEFI
They both point to 1 sector or 64 block. Also, you must have booting
partition end
lined up too, so it never can be bigger than 2Gb.
I mean 2Tb, but this statement is anyway wrong. However - I have all
booting wedges less than MBR partition, but never succeeded if boot
wedge was bigger than
I installed /boot, ran installboot and gpt biosboot. Here is fdisk
output for the disk:
What flags installboot was used with?
installboot -o console=com0,speed=115200 /dev/rdk2
/usr/mdec/bootxx_ffsv2
Did you installed MBR ever? I always do that separately.
Here is the result:
# dkctl
wrote:
> I guess it's on a i386/amd64 arch? Because, if my memory is right,
> there is the need of the "\x55\xAA" in the two last bytes of the
> first 512b block (the signature) for the BIOS.
Yes, this is amd64. The magic number is there, indeed:
# dd if=/dev/rwd2d bs=512 count=1|hexdump
On Thu, Jul 25, 2019 at 05:46:31PM +0200, Emmanuel Dreyfus wrote:
> Martin Husemann wrote:
>
> > You may want to use rwd2d instead of rdk2
>
> What is the rationale? I expect that to destroy the GPT.
There are various architectures that write the boot record to the disk,
not the NetBSD root
On Thu, Jul 25, 2019 at 04:20:59PM +0200, Emmanuel Dreyfus wrote:
> Hello
>
> I try to boot NetBSD/Xen from a GPT, with little success.
>
> I understand NetBSD EFI bootstrap does not support multiboot, so I
> should use BIOS boot.
>
> I installed /boot, ran installboot and gpt biosboot. Here is
Martin Husemann wrote:
> You may want to use rwd2d instead of rdk2
What is the rationale? I expect that to destroy the GPT.
# installboot -o console=com0,speed=115200 /dev/rwd2d
/usr/mdec/bootxx_ffsv2
And indeed:
# gpt show wd2
start size index contents
0
On Thu, Jul 25, 2019 at 05:20:12PM +0200, Emmanuel Dreyfus wrote:
> Dima Veselov wrote:
>
> > > I installed /boot, ran installboot and gpt biosboot. Here is fdisk
> > > output for the disk:
> >
> > What flags installboot was used with?
>
> installboot -o console=com0,speed=115200 /dev/rdk2
>
Dima Veselov wrote:
> > I installed /boot, ran installboot and gpt biosboot. Here is fdisk
> > output for the disk:
>
> What flags installboot was used with?
installboot -o console=com0,speed=115200 /dev/rdk2
/usr/mdec/bootxx_ffsv2
Here is the result:
# dkctl wd2 listwedges
/dev/rwd2d: 3
I understand NetBSD EFI bootstrap does not support multiboot, so I
should use BIOS boot.
I installed /boot, ran installboot and gpt biosboot. Here is fdisk
output for the disk:
What flags installboot was used with?
Partition table:
0: GPT Protective MBR (sysid 238)
start 1, size
Hello
I try to boot NetBSD/Xen from a GPT, with little success.
I understand NetBSD EFI bootstrap does not support multiboot, so I
should use BIOS boot.
I installed /boot, ran installboot and gpt biosboot. Here is fdisk
output for the disk:
Partition table:
0: GPT Protective MBR (sysid 238)
12 matches
Mail list logo
