Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Apr 2020 14:08:37 -0700
From:      Chris <bsd-lists@BSDforge.com>
To:        Miroslav Lachman <000.fbsd@quip.cz>
Cc:        Pete Wright <pete@nomadlogic.org>, <freebsd-stable@freebsd.org>, Chuck Tuffli <ctuffli@gmail.com>
Subject:   Re: support of PCIe NVME drives
Message-ID:  <d8b6735fc22545fc7cd1305b4ebb5c5f@udns.ultimatedns.net>
In-Reply-To: <ccf177ce-e2dc-4d09-bec7-c13ada23e13d@quip.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Apr 2020 22:57:10 +0200 Miroslav Lachman 000=2Efbsd@quip=2Ecz said

> Chuck Tuffli wrote on 04/16/2020 22:29:
> > On Thu, Apr 16, 2020 at 12:30 PM Miroslav Lachman <000=2Efbsd@quip=2Ecz> wr=
ote:
> >>
> >> Pete Wright wrote on 04/16/2020 20:23:
> >>>
> >>>
> >>> On 4/16/20 11:12 AM, Miroslav Lachman wrote:
> >>>> Kurt Jaeger wrote on 04/16/2020 20:07:
> >>
> >>> I would try booting via UEFI if you can=2E  I just installed a laptop
> >>> yesterday which has a nvme root device, it was detected by the 12-STA=
BLE
> >>> snapshot I used to boot from=2E  no other modifications were necessary =
on
> >>> my end=2E
> >>
> >> I changed BIOS settings to use UEFI boot method, booted 12=2E1 installer
> >> ISO but without luck=2E Still no NVME disks :(
> >>
> >> You can see it on printscreen from iDRAC https://ibb=2Eco/tPnymL7
> >>
> >> Anything more I can test?
> >=20
> > Fair warning, I don't deal much with Dell, but it's curious that iDrac
> > lists the device protocol as MI
> >> Device Protocol:      NVMe-MI1=2E0
> >=20
> > MI or the Management Interface is defined by NVMe, but it isn't the
> > same as a block interface=2E MI typically uses SMBUS and not PCIe to
> > communicate with the device=2E So it's possible that the device is
> > visible to iDrac via SMBUS but may not be on the PCIe bus for
> > $reasons=2E Does iDrac have any tools to interact with the device via
> > MI?
>=20
> iDRAC does not allow me to do anything with the drives=2E
> But I booted Linux SystemRescueCd and nvme devices are there visible in=
=20
> /dev/
> printscreen https://ibb=2Eco/sj22Nwg
>=20
> So I think the HW is OK, but FreeBSD does not recognize the controller?

Does mps(4) or any of the other (often Dell) rebranded LSI drivers expose a=
nything?

>=20
> Kind regards
> Miroslav Lachman

--Chris





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8b6735fc22545fc7cd1305b4ebb5c5f>