Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Upgrade to 2.6.0 failed, NICs appear unsupported.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    5 Posts 2 Posters 1.2k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      Starfire 0
      last edited by

      After upgrading to 2.6.0, my router gave an interface mismatch error, indicating that my mlxen0 interface (and associated vlans) were unavailable. I suspect that support for the Mellanox 40G infiniband card was left out. I've reverted back to 2.5.2.

      Media 40Gbase-CR4 <full-duplex,rxpause,txpause>

      The machine is a Dell R210 II, which has been working fine since 2.4.5, which was when mellanox support was added to pfsense.

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        The kernel has the same drivers included. Do you see any sign of them in the boot log? Does the interface assignment prompt offer them but with different names?

        It's possible there was a driver change that made the interface names change in some way, but the kernel configuration has all of the same mlx5 and mlx4 devices it had on previous versions.

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          Starfire 0 @jimp
          last edited by

          The only valid interfaces shown were bce0 and bce1. Unfortunately, I didn't retain any logs.

          I do run a couple of system tunables; has the way they work changed?

          sys.device.mlx4_core0.mlx4_port1 Set Mellanox card to Ethernet mode. eth
          sys.device.mlx4_core0.mlx4_port2 Set Mellanox card to Ethernet mode. eth

          1 Reply Last reply Reply Quote 0
          • jimpJ Offline
            jimp Rebel Alliance Developer Netgate
            last edited by

            I'm not familiar with that specific hardware or driver but it's possible. I don't see any notes in the current man pages that mention having to change sysctl values, or anything in the recent FreeBSD release notes about changes in the driver. I haven't gone digging through their code, though.

            If you do try again, try to keep as much info as you can (e.g. a status output file from /status.php in the GUI) and possibly even try a fresh install to see if it makes a difference.

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              Starfire 0 @jimp
              last edited by

              Since the recovery process is relatively straightforward, I can attempt it again. Is there anything else you'd like me to gather to aid in diagnosis?

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.