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

    X-540 T2 didn't boot up on pfSense CE 2.5.0-RELEASE (amd64)

    Scheduled Pinned Locked Moved Hardware
    22 Posts 3 Posters 2.3k Views
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      What test did you do exactly?

      The response on the FreeBSD ticket about the NIC is question here is interesting.

      Seems like it should not exist in the wild! So will never be officially supported.

      Steve

      1 Reply Last reply Reply Quote 0
      • T
        techanalyst @json
        last edited by

        @jnz07 loader.conf

        add this line if_ixgbe_load="YES"

        He meant the 540 :) mine didnt load under 2.5 either, I have to add this line to the loader.conf, after a reboot no problem

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Hmm, that absolutely should not be required. It's the same driver that's in kernel.

          jsonJ 1 Reply Last reply Reply Quote 0
          • jsonJ
            json @stephenw10
            last edited by

            @stephenw10 So to summarize do we do something in this area ? Or we just can close the thread ? If there's nothing we can do, than let's close it.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              There is nothing we can do in pfSense and if looks like FreeBSD upstream can't do anything either since it should not exist.
              If you really needed to use it for some reason you could probably recompile the kernel module with the patch on the FreeBSD bug to add the IDs. But you would be stuck compiling it again at each release.
              Better to just use a different NIC.

              Steve

              T jsonJ 2 Replies Last reply Reply Quote 1
              • T
                techanalyst @stephenw10
                last edited by

                @stephenw10 I was able to get mine going, not sure "why they shouldnt exist" as I have something like 100 workstations at one site and they all have the 540-t2 cards. So if its a card that shouldnt exist, I know for one, I have a lot of them

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  With that same PCI ID?

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    techanalyst @stephenw10
                    last edited by

                    @stephenw10 Correcto, enabling the line above made them work otherwise machine wouldnt even boot

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Hmm, well two weird things there.

                      Enabling the identical driver as a kernel module should make no difference at all. A timing difference maybe?

                      The guy from Intel commented in that bug report that it is a:

                      non-production internal-only device id
                      

                      So I would not expect to find it on a whole bunch of cards.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • jsonJ
                        json @stephenw10
                        last edited by json

                        @stephenw10 said in X-540 T2 didn't boot up on pfSense CE 2.5.0-RELEASE (amd64):

                        There is nothing we can do in pfSense and if looks like FreeBSD upstream can't do anything either since it should not exist.
                        If you really needed to use it for some reason you could probably recompile the kernel module with the patch on the FreeBSD bug to add the IDs. But you would be stuck compiling it again at each release.
                        Better to just use a different NIC.

                        Steve

                        @stephenw10 I already changed to Intel X520-DA2 SFP+ 10Gb Dual Port ;).

                        Anyway I guess that this thread will be more for information purposes for others that Intel X540T2 is not working with pfSense CE 2.5.0-RELEASE (amd64) .

                        T 1 Reply Last reply Reply Quote 1
                        • T
                          techanalyst @json
                          last edited by

                          @jnz07 I replaced mine with a 550-t2 to avoid future issues

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