Re: FreeBSD OS installation stuck after selecting Boot installer

> On 10 Jul 2024, at 17:03, Anantharam, Arjun <[email protected]> wrote:
> 
> Hi,
> 
> On most of our hardware, i still run into mount issues. Can anyone provide some guidance on this ?
> This iso/img file boot is the only option right now for us to boot FreeBSD(no PXE boot option yet), so any inputs are appreciated!!
> 

The issue appears to be the interface the NVMe provides to the kernel.

> found-> vendor=0x8086, dev=0x1457, revid=0x21
>         domain=0, bus=0, slot=1, func=1
>         class=01-08-02, hdrtype=0x00, mfdev=1
>         cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
>         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
>         intpin=a, irq=255
>         powerspec 3  supports D0 D3  current D0
>         MSI supports 1 message, 64 bit, vector masks
>         MSI-X supports 257 messages in map 0x18
>         map[10]: type Prefetchable Memory, range 64, base 0x2220000000, size 25, memory disabled

This looks like the NVMe device that the nvme driver attaches to. The class=01-08-02 indicates it’s an NVMe device using the enterprise nvmhci.

…

> found-> vendor=0x8086, dev=0x1458, revid=0x21
>         domain=0, bus=0, slot=1, func=7
>         class=01-08-00, hdrtype=0x00, mfdev=1
>         cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
>         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
>         intpin=a, irq=255
>         powerspec 3  supports D0 D3  current D0
>         MSI-X supports 257 messages in map 0x18
>         map[10]: type Prefetchable Memory, range 64, base 0x2224000000, size 25, memory disabled

This is the NVMe device the nvme driver doesn’t attach to. As the class is 01-08-00 the driver doesn’t attach. The problem is the 00 at the end.

I don’t know the difference between the different interfaces so am unsure how difficult it would be to support this device.

Andrew