Firmware for MHJH29 ?

On the Firmware page for ConnectX (here: Firmware for ConnectX® Firmware for ConnectX® ), there’s firmware for many cards… but the MHJH29 (dual, QDR, CX4) is not there, only the MHQH (QSFP insteqd of CX4). They are revision X5.

Anyone know where I could find the latest firmware ?

(Picture of the cards with 3D printed brackets in this thread: )

Thanks in advance & cordially

Hello Romain -

Service for this Hardware and FW has ended. So it will not be hosted on our site.

Many thanks for your support & patience…

Steve

Stephen Yannalfo wrote:

Could you get the board_id with “ibv_devinfo”

Sure; took a little time as I had to get a system running to put the HCA in ;-)

When I put some IB between systems at home years ago, the PCIe

would limit me to about DDR anyway (one 8x 1.0, and 4x 2.0 …), so

i used DDR boards with available firmware. I have since upgraded

some bits of hardware, and wondering if I couldn’t get QDR on 8x 2.0.

But it seems QDR was mostly deployed with QSFP connector, not

CX4, so the MHJH29 seems a bit of a black sheep from that era…

Thanks for your help !

Host is a Supermicro X9SRi, primary PCIe slot (16x 2.0). Running

CentOS 7.3

[root@localhost ~]# ibv_devinfo

hca_id: mlx4_0

transport: InfiniBand (0)

fw_ver: 2.6.900

node_guid: 0002:c903:0002:173a

sys_image_guid: 0002:c903:0002:173d

vendor_id: 0x02c9

vendor_part_id: 26428

hw_ver: 0xA0

board_id: MT_04E0120005

phys_port_cnt: 2

port: 1

state: PORT_DOWN (1)

max_mtu: 4096 (5)

active_mtu: 4096 (5)

sm_lid: 0

port_lid: 0

port_lmc: 0x00

link_layer: InfiniBand

(second port same as first, nothing is plugged in).

2.6.9 feels old, the latest seems to be 2.9.1[000]

And the part number with:

lspci | grep Mell NOTE: the bus:dev.func of the device

lspci -s bus:dev.func -xxxvvv

That’s one verbose lspci :-)

02:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s - IB QDR / 10GigE] (rev a0)

Subsystem: Mellanox Technologies Device 0005

Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-

Latency: 0, Cache Line Size: 64 bytes

Interrupt: pin A routed to IRQ 61

NUMA node: 0

Region 0: Memory at fba00000 (64-bit, non-prefetchable) [size=1M]

Region 2: Memory at 38ffff000000 (64-bit, prefetchable) [size=8M]

Capabilities: [40] Power Management version 3

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [48] Vital Product Data

Product Name: Eagle QDR

Read-only fields:

[PN] Part number: MHJH29-XTC

[EC] Engineering changes: X5

[SN] Serial number: MT0821X00122

[V0] Vendor specific: PCIe Gen2 x8

[RV] Reserved: checksum good, 0 byte(s) reserved

Read/write fields:

[V1] Vendor specific: N/A

[YA] Asset tag: N/A

[RW] Read-write area: 111 byte(s) free

End

Capabilities: [9c] MSI-X: Enable+ Count=256 Masked-

Vector table: BAR=0 offset=0007c000

PBA: BAR=0 offset=0007d000

Capabilities: [60] Express (v2) Endpoint, MSI 00

DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns, L1 unlimited

ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 75.000W

DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-

RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-

MaxPayload 256 bytes, MaxReadReq 512 bytes

DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-

LnkCap: Port #8, Speed 5GT/s, Width x8, ASPM L0s, Exit Latency L0s unlimited, L1 unlimited

ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-

LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-

ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

LnkSta: Speed 5GT/s, Width x8, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-

DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported

DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled

LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-

Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

Compliance De-emphasis: -6dB

LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-

EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-

Capabilities: [100 v1] Alternative Routing-ID Interpretation (ARI)

ARICap: MFVC- ACS-, Next Function: 1

ARICtl: MFVC- ACS-, Function Group: 0

Kernel driver in use: mlx4_core

Kernel modules: mlx4_core

00: b3 15 3c 67 06 04 10 00 a0 00 06 0c 10 00 00 00

10: 04 00 a0 fb 00 00 00 00 0c 00 00 ff ff 38 00 00

20: 00 00 00 00 00 00 00 00 00 00 00 00 b3 15 05 00

30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00

40: 01 48 03 00 00 00 00 00 03 9c ff 7f 00 00 00 78

50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

60: 10 00 02 00 01 8e 2c 01 20 20 00 00 82 f4 03 08

70: 00 00 82 00 00 00 00 00 00 00 00 00 00 00 00 00

80: 00 00 00 00 1f 00 00 00 00 00 00 00 00 00 00 00

90: 02 00 00 00 00 00 00 00 00 00 00 00 11 60 ff 80

a0: 00 c0 07 00 00 d0 07 00 05 00 8a 00 00 00 00 00

b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Hello Romain -

Good day to you…

Could you get the board_id with “ibv_devinfo”

And the part number with:

lspci | grep Mell NOTE: the bus:dev.func of the device

lspci -s bus:dev.func -xxxvvv

See:

Read-only fields:

[PN] Part number:

If you could update this thread with this information it would be very helpful.

thanks - steve

Hello Romain -

I hope all is well…

Do you have an email address so I can send you a link to the file?

thanks - steve

Thank you. I sent you a direct message with my e-mail.

BTW, naive question - any reason the link can’t simply be made public?

(my guess would be, this is somehow a prerelease HCA and there was never any official release for it?)

Cordially & thanks for the great support,

Romain

Service for this Hardware and FW has ended. So it will not be hosted on our site.

Thank you for your help. Seems this new firmware is no newer than the one I already have, unfortunately.

Those are 10+ years old cards… no surprise they are difficult to put back in service.

Cordially & thanks again for the great support,