Hi,
> > > I changed the number of namespaces my controller reports to 1 and it
> > > worked fine. Is there an easy way to get around this or do I have to
> > > fix the code? I haven't looked at the code in detail, but I think we
> > > don't have to allocate the array of namespaces in
> > > nvme_
> -Original Message-
> From: Gerd Hoffmann
> Sent: 08 April 2021 11:10
> To: Thanos Makatos
> Cc: seabios@seabios.org; John Levon ; Swapnil
> Ingle ; Liu, Changpeng
>
> Subject: Re: [SeaBIOS] SeaBIOS fails to boot from NVMe controller with lots
> of namespaces
>
> On Thu, Apr 01, 202
Hi,
> > -#define VBE_DISPI_MAX_XRES 2560
> > -#define VBE_DISPI_MAX_YRES 1600
> > +#define VBE_DISPI_MAX_XRES 3840
> > +#define VBE_DISPI_MAX_YRES 2160
> > +{ 0x199, { MM_DIRECT, 3840, 2160, 32, 8, 16, SEG_GRAPH } },
> I'm not sure ab
On Thu, Apr 01, 2021 at 12:42:18PM +, Thanos Makatos wrote:
> I'm using SeaBIOS (b0d61ec) to boot from a virtual NVMe controller that has
> relatively many namespaces (64). The exact error is :
>
> /3ff9f000\ Start thread
> |3ff9f000| Searching bootorder for: /pci@i0cf8/*@6
>
Hi,
> > > > Add a config option for fast device init (i.e. skip non-bootable
> > > > devices). This optimization breaks boot in some rare configurations,
> > > > specifically in case the boot loader needs access to secondary disks.
>
> Unfortunately, I missed the initial email due to seabios m
