Mellanox ConnectX-2 Firmware Request

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
P

poto

Active Member
May 18, 2013
240
91
28
  • Like
Reactions: Chuntzu, Dajinn, neo and 1 other person
D

Dajinn

Active Member
Jun 2, 2015
512
78
28
34
poto said:
I am using firmware 2.10.720 with ConnectX-2 VPI, sourced from STH article:

http://www.servethehome.com/custom-firmware-mellanox-oem-infiniband-rdma-windows-server-2012/

The author did a great job explaining how to extract firmware from driver package, as well as procedure for using firmware utilities.
Click to expand...
The article is great, however, there were some issues with it. The actual Win-OF package of 4.2 on the Mellanox site has an older firmware version, I think it was 2.9.1200 which still wasn't high enough for RDMA.

And then, none of the packages beyond 4.2 on their site had the firmware in the temp folders when running the installer. All I found was ConnectX3 firmware every now and then and yes I looked in every .exe file.

I was able to get this up and running though by using some context clues and downloading the 4.2 package from Dell's website, go figure, lol.
 
A

Aluminum

Active Member
Sep 7, 2012
431
47
28
I see 2.9.8350 buried on their site here, scroll past "Intermediate Firmware Releases Table":

http://www.mellanox.com/page/custom_firmware_table

Not sure why they are weird about this, its in their interest to have the most recent tested release available to users to deal with any bugs/features/etc. I almost wonder if its the stupid server OEMs trying to do the usual end customer mushrooming.
 
  • Like
Reactions: vanfawx and Dajinn
D

Dajinn

Active Member
Jun 2, 2015
512
78
28
34
Aluminum said:
I see 2.9.8350 buried on their site here, scroll past "Intermediate Firmware Releases Table":

http://www.mellanox.com/page/custom_firmware_table

Not sure why they are weird about this, its in their interest to have the most recent tested release available to users to deal with any bugs/features/etc. I almost wonder if its the stupid server OEMs trying to do the usual end customer mushrooming.
Click to expand...
You know what's funny is I called Mellanox for shits/giggles and the guy on the phone was a total tool. He asked me for the PSID like right off the bat as if I would've had it in front of me(luckily I had my cmd prompt open on my server still)and then when I told him he just basically told me the latest is 2.9.1000. Total buzzkill.

At any rate, I'm surprised I missed that firmware. Thanks for the link as I want to test it between 2 of my nodes and see if the firmware makes any difference as far as performance is concerned.

I'll try it and post results once I'm home later.
 
C

Chuntzu

Active Member
Jun 30, 2013
383
98
28
As a side note if looking at mellanox drivers for Windows take note that the newest driver for Windows has depreciated connectx2 support you have to check change log to identify which driver version still has support for connectx2. Thought it was a bit interesting.
 
  • Like
Reactions: Chuckleb
D

Dajinn

Active Member
Jun 2, 2015
512
78
28
34
Chuntzu said:
As a side note if looking at mellanox drivers for Windows take note that the newest driver for Windows has depreciated connectx2 support you have to check change log to identify which driver version still has support for connectx2. Thought it was a bit interesting.
Click to expand...
Without spending too much time checking through all of the versions, version 4.8 is the first one I came across where the release notes explicitly state support for ConnectX-2 adapters.

http://www.mellanox.com/related-docs/prod_software/MLNX_VPI_WinOF_Release_Notes_Rev_4.80.pdf

 
C

Chuntzu

Active Member
Jun 30, 2013
383
98
28
Yes that looks like it, just checked my systems that are using connectx2 cards and 4.8 is the driver.
 
  • Like
Reactions: Dajinn
B

bdark

New Member
Sep 18, 2015
1
1
1
54
So the driver that windows automatically installed for me (on Windows 10) is 4.91.10726.0. Is there some reason I should be preferring 4.8?
 
  • Like
Reactions: jwc
L

Labs

Member
Mar 21, 2019
88
16
8
lex said:
Hi. For anyone with ConnectX-2 cards, with PSID SUN0170000009, here is the latest 2.11.2010 firmware for it.
Click to expand...
This firmware is for the dual port model. Do you know how I can update the single port card with 2.11.2010 but keep the old ini file?
I cannot find a way to use the 2.11.2010 bin file with another ini. I would probably need the mlx file which is not available anywhere.
 
T

Tim111

New Member
Jan 9, 2019
29
3
3
I have some firmware and script for flashing. If you can read a batch file or bash script you will get the idea.

Dropbox

www.dropbox.com www.dropbox.com
 
U

up3up4

Member
Jun 10, 2018
88
31
18
Labs said:
This firmware is for the dual port model. Do you know how I can update the single port card with 2.11.2010 but keep the old ini file?
I cannot find a way to use the 2.11.2010 bin file with another ini. I would probably need the mlx file which is not available anywhere.
Click to expand...
github.com

GitHub - BeTeP-STH/mft-scripts: Mellanox firmware files and MFT related scripts

Mellanox firmware files and MFT related scripts. Contribute to BeTeP-STH/mft-scripts development by creating an account on GitHub.
github.com github.com
 
L

Labs

Member
Mar 21, 2019
88
16
8
up3up4 said:
github.com

GitHub - BeTeP-STH/mft-scripts: Mellanox firmware files and MFT related scripts

Mellanox firmware files and MFT related scripts. Contribute to BeTeP-STH/mft-scripts development by creating an account on GitHub.
github.com github.com
Click to expand...
Tried it already but it doesn't seem to update the .bin file with my .ini.

Code: 
update_ini.py sun_2_11_2010_orig_fw.bin Modded.ini

     FS2 failsafe image. Start address: 0x0. Chunk size 0x80000:

     NOTE: The addresses below are contiguous logical addresses. Physical addresses on
           flash may be different, based on the image start address and chunk size

     /0x00000038-0x000011bb (0x001184)/ (BOOT2) - OK
     /0x000011bc-0x0000251f (0x001364)/ (BOOT2) - OK
     /0x00002520-0x00003337 (0x000e18)/ (Configuration) - OK
     /0x00003338-0x0000337b (0x000044)/ (GUID) - OK
     /0x0000337c-0x000034b7 (0x00013c)/ (Image Info) - OK
     /0x000034b8-0x0000a34f (0x006e98)/ (DDR) - OK
     /0x0000a350-0x0000be0b (0x001abc)/ (DDR) - OK
     /0x0000be0c-0x0001923b (0x00d430)/ (DDR) - OK
     /0x0001923c-0x000224df (0x0092a4)/ (DDR) - OK
     /0x000224e0-0x00079193 (0x056cb4)/ (DDR) - OK
     /0x00079194-0x0007985f (0x0006cc)/ (DDR) - OK
     /0x00079860-0x000a0c3b (0x0273dc)/ (DDR) - OK
     /0x000a0c3c-0x000a47bf (0x003b84)/ (DDR) - OK
     /0x000a47c0-0x000a877f (0x003fc0)/ (DDR) - OK
     /0x000a8780-0x000a8c5b (0x0004dc)/ (Configuration) - OK
     /0x000a8c5c-0x000a8cb7 (0x00005c)/ (Jump addresses) - OK
     /0x000a8cb8-0x000a931f (0x000668)/ (FW Configuration) - OK
     /0x00000000-0x000a931f (0x0a9320)/ (Full Image) - OK

FW image verification succeeded. Image is bootable.



.bin is not supported FS2 image file
The .bin file is not touched in the end...
 
L

Labs

Member
Mar 21, 2019
88
16
8
Tim111 said:
I have some firmware and script for flashing. If you can read a batch file or bash script you will get the idea.

Dropbox

www.dropbox.com www.dropbox.com
Click to expand...
I don't see in your script how it is changing the .ini from a .bin firmware. It seems it is only updating the firmware.
 
T

Tim111

New Member
Jan 9, 2019
29
3
3
Labs I am not sure what you mean about not changing ini file. My script can extract ini file from firmware then you can modify it and create new firmware. command for connectx-2 flint -d mt26428_pci_cr0 dc "you're-name.ini" on windows 10. Also be very careful about changing .ini file as you could mess up you're card. Only thing i ever changed is psid for cross flashing.
 
T

Tim111

New Member
Jan 9, 2019
29
3
3
[PS_INFO]
Name = 375-3696-01
Description = Sun Falcon QDR (qFalcon) with Short bracket CX-2

[ADAPTER]
PSID = SUN0170000009
pcie_gen2_speed_supported = true
adapter_dev_id = 0x673c
silicon_rev = 0xb0

gpio_mode1 = 0x0
gpio_mode0 = 0x050e070f
gpio_default_val = 0x0502010f

[HCA]
sriov_en=true
total_vfs=64
hca_header_device_id = 0x673c
hca_header_subsystem_id = 0x673c
dpdp_en = true
eth_xfi_en = true
mdio_en_port1 = 0
sriov_en = true
 
You must log in or register to reply here.
Top Bottom