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

    Pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    67 Posts 6 Posters 27.4k 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.
    • T
      Topper727
      last edited by

      https://svnweb.freebsd.org/base?view=revision&revision=269196

      This is where they updated the EM driver .. talks about shared code in the update.. Also submitted a bug

      https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501

      Now the question is.  If they fix it in freebsd10.1 will it get into Pfsense and how fast?

      Is there a way to downgrade to the driver used in 8.1 till they fix maybe?

      I got the older driver but MAKE and PKG_Add are not part of pfense.. PKG_add use to be.. really starting to hate PFSENSE

      http://doc.pfsense.org/index.php/Add_Packages_HOWTO_Add_Packages_from_a_shell

      Dell 2950 g3 server
      Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
      Current: 2000 MHz, Max: 2667 MHz
      8 CPUs: 2 package(s) x 4 core(s)
      8152 MiB and 600meg 10k drive
      Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

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

        Drivers are not FreeBSD packages that you can add.
        There are no build tools at all in pfSense, including them would only be a security risk.
        FreeBSD 10 moved to the pkgng package system.
        The driver subsystems changed a lot between 8.3 and 10.1, i'd be surprised if you're able to compile an 8.3 driver against 10.1 source.
        It's my belief that it's not the driver anyway but some resource management component.

        You might try to find exactly which FreeBSD version introduced the issue. Looking at the other bug reports we've referenced in this thread it may have been 9.0 or 9.1.

        Steve

        1 Reply Last reply Reply Quote 0
        • T
          Topper727
          last edited by

          Solved!

          hint.agp.0.disabled=1
          in loader.conf fixes the problem. :)

          Dell 2950 g3 server
          Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
          Current: 2000 MHz, Max: 2667 MHz
          8 CPUs: 2 package(s) x 4 core(s)
          8152 MiB and 600meg 10k drive
          Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

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

            Huh, how did you find that? Well done.  :)

            Steve

            1 Reply Last reply Reply Quote 0
            • T
              Topper727
              last edited by

              I found by submitting a bug to Intel and someone gave me that to try.. that fixed it.

              https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501

              Dell 2950 g3 server
              Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
              Current: 2000 MHz, Max: 2667 MHz
              8 CPUs: 2 package(s) x 4 core(s)
              8152 MiB and 600meg 10k drive
              Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

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

                Ah. Importantly that person was John Baldwin. I'm not going to feel bad not knowing something he does.  ;)
                Anyway I'm happy a workaround exists and that key FreeBSD people are aware of it.

                Steve

                1 Reply Last reply Reply Quote 0
                • ?
                  Guest
                  last edited by

                  Interestingly, this isn't a em driver bug (as upthread wanted to pursue), but rather a PCI bus issue.

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