Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Tardisyuan

Members
  • Joined

  • Last visited

Everything posted by Tardisyuan

  1. Thanks so much for confirming that — I really appreciate you taking the time to investigate this! As a possible workaround (suggested by ChatGPT), maybe the plugin could offer an optional legacy mode for older cards like the ConnectX-3, which uses a precompiled mstflint 4.18.0 binary bundled with its own OpenSSL 1.1 libraries. These could be loaded using LD_LIBRARY_PATH to avoid conflicts with Unraid 7’s OpenSSL 3 environment. This approach might allow legacy hardware to remain supported without affecting newer systems or requiring major changes to Unraid itself.
  2. You’re right — I don’t have solid evidence that it’s strictly version-related, just based on my limited testing results. Thanks a lot for taking the time to look into it! As for the BIOS, I did try updating it, but unfortunately the issue still persists. I appreciate the reminder though — I’ll keep looking for possible solutions on that front.
  3. I’ve now attached the Diagnostics log generated and plugin info screenshot while using plugin version 2025.02.10 as requested. unraid-diagnostics-20250430-1814.zip Regarding your question about why I believe the card is no longer supported by newer versions of mstflint: I actually built a custom Docker environment using a Dockerfile for testing purposes. Here’s what I found: When using mstflint v4.20.0, I encountered the exact same error as shown in the Diagnostics—Failed to recognize device (or similar). When I downgraded to mstflint v4.18.0 within the same environment, everything worked perfectly: the NIC was detected and firmware tools operated as expected. This leads me to believe that support for the ConnectX-3 (MCX311A-XCAT) may have been dropped or broken starting from mstflint v4.20.0. Here’s the simplified Dockerfile I used for testing: Dockerfile
  4. Hi,I’m currently using Unraid 7.0.1 with a MCX311A-XCAT 10G single-port NIC (07:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3]). While trying to use the Mellanox Firmware Tools plugin, I ran into an issue with the latest version (2025.02.10)—it fails to recognize the NIC. After some testing, I found that the problem is due to the mstflint version being too new. My card only works properly with mstflint version 4.18.0 or earlier. So I downgraded to the 2021.11.30 version of Mellanox Firmware Tools, which includes the older mstflint. However, when I try to run it, I get the following error: mstflint: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory After reading earlier replies, I confirmed that Unraid 7 uses OpenSSL 3 by default, which seems to be causing the incompatibility. Now I’m in a dilemma: The latest tools don’t work with my NIC. The older tools require OpenSSL 1.1, which Unraid 7 no longer provides. Would it be possible to add support for older NICs like the ConnectX-3 in future versions of the plugin, or provide a build with backward-compatible mstflint and OpenSSL 1.1 included?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.