Hey all,
Trying to get a Broadcom 9600-24i eHBA running in 22.04 virtualized in XCP-ng (pci-e passthrough of the whole card to the VM). Flashed to latest firmware using their Windows 10 tool, and I can see drives detected on the controller in Windows Disk Management. But in Ubuntu and Debian (Openmediavault) I’m not able to get the drives to detect.
Broadcom provides a DEB driver pack (broadcom/products/storage/host-bus-adapters/sas-nvme-9600-24i), which I installed via DKMS. This seemingly completes fine and ‘DKMS status’ outputs: ‘mpi3mr/8.7.1.0.0, 6.2.0-37-generic, x265_64: installed’. LSPCI shows the controller and all the associated capabilities, as well as kernel driver/modules of mpi3mr in use. But I don’t see any of the (4x22TB SATA) drives detecting in ‘fdisk -l’. I see /dev/xvda and /dev/loop0 through loop14, but the loops are all small sizes.
‘Dmesg | grep mpi3’ outputs:
[ 0.748214] mpi3mr: loading out-of-tree module taints kernel.
[ 0.748271] mpi3mr: module verification failed: signature and/or required key missing - tainting kernel
[ 0.751404] Loading mpi3mr version 8.7.1.0.0
[ 0.751429] mpi3mr 0000:00:05.0: PCI_EXT_CAP_ID_DSN is not supported
[ 0.751453] mpi3mr 0000:00:05.0: Driver probe function unexpectedly returned
The first bit makes sense, similar to using Nvidia drivers, but from what little I can find for the rest (lkml.kernel/linux-scsi/[email protected]/), the last bit suggests:
"Read PCI_EXT_CAP_ID_DSN to know security status.
Driver will throw an warning message when a non-secure type controller
is detected. Purpose of this interface is to avoid interacting with
any firmware which is not secured/signed by Broadcom.
Any tampering on Firmware component will be detected by hardware
and it will be communicated to the driver to avoid any further
interaction with that component."
So am I doing something wrong here, or is there some firmware security attestation that is going sideways somewhere? As their own LSA tool was able to update the firmware in Windows, and LSA shows the card and all associated properties, I’m doubting the card is counterfeit or something. Or am I querying them wrong with fdisk or something?