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

    2.0 -> 2.2 upgrade Intel Pro 1000 Dual NIC

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    10 Posts 6 Posters 3.6k 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.
    • D
      Delirius
      last edited by

      After upgrading to 2.2 I can only get one of the ports working on my Intel Pro 1000 Dual NIC.
      When running command pciconf -lv I can see that the other port is detected as none2 while the first port that's working is detected as em0.

      In 2.0 the NIC was working flawless. I will provide more information from dmesg and pciconf as soon as I get home.

      Anyone have any suggestions what to look for or todo? Maybe I need to downgrade? or you need more information to tell?

      1 Reply Last reply Reply Quote 0
      • D
        Delirius
        last edited by

        I have now run dmesg and found the following:
        em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.6="">port 0x1040-0x107f irq 20 at device 0.0 on pci5
        em0: Setup of Shared code failed
        device_attach: em0 attach returned 6
        em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.6="">port 0x1000-0x103f irq 21 at device 0.1 on pci5

        also output of pciconf -lv is:
        none1@pci0:1:0:0:      class=0x020000 card=0xd6258086 chip=0x816810ec rev=0x06 hdr=0x00
            class      = network
            subclass  = ethernet
        none2@pci0:5:0:0:      class=0x020000 card=0x10128086 chip=0x10108086 rev=0x03 hdr=0x00
            class      = network
            subclass  = ethernet
        em0@pci0:5:0:1: class=0x020000 card=0x10128086 chip=0x10108086 rev=0x03 hdr=0x00
            class      = network
            subclass  = ethernet</intel(r)></intel(r)>

        1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by

          https://forum.pfsense.org/index.php?topic=88559.30

          1 Reply Last reply Reply Quote 0
          • D
            Delirius
            last edited by

            I found it could be relevant to post this from dmesg as well.
            pcib5: <acpi pci-pci="" bridge="">at device 30.0 on pci0
            pcib5: failed to allocate initial memory window: 0xe0100000-0xe01fffff

            since NIC is attached to pcib5</acpi>

            1 Reply Last reply Reply Quote 0
            • C
              charliem
              last edited by

              Try adding hint.agp.0.disabled=1 in /boot/loader.conf.local.  It's worked a few times for folks using 2.2, first here: https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793

              Root cause is a FreeBSD PCI bus issue that interferes with setting up the bridge.  Details here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501

              1 Reply Last reply Reply Quote 0
              • D
                Delirius
                last edited by

                @charliem:

                Try adding hint.agp.0.disabled=1 in /boot/loader.conf.local.  It's worked a few times for folks using 2.2, first here: https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793

                Root cause is a FreeBSD PCI bus issue that interferes with setting up the bridge.  Details here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501

                Thank you, it worked. For anyone else that might have this issue you should try this.

                1 Reply Last reply Reply Quote 0
                • C
                  charliem
                  last edited by

                  @Delirius:

                  Thank you, it worked. For anyone else that might have this issue you should try this.

                  Great, I'm glad it worked.  I see the bug report is marked as 'fixed', even though it's only a manual work-around.  So, it may not get much attention from FreeBSD proper; maybe this workaround should be mentioned in pfSense 2.2.1 release notes.  Though it stems from a PCI issue, It seems to only manifest itself with intel NICs.

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

                    Mmm, it's an interesting bug.
                    If you have the time (or inclination) it would be interesting to know if this bug could also by fixed by using the hostres disabled tunable:

                    debug.acpi.disabled="hostres"
                    

                    That seemingly prevents the BIOS sending bad ACPI info about all sorts of things that cause issues in FreeBSD 9 onwards.

                    For the sake of anyone Googling this seems linked to failing to mountroot with "failed with error 19"

                    http://wiki.pcbsd.org/index.php/Talk:Installation_Troubleshooting

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • C
                      cherrypie
                      last edited by

                      @charliem:

                      Try adding hint.agp.0.disabled=1 in /boot/loader.conf.local.  It's worked a few times for folks using 2.2, first here: https://forum.pfsense.org/index.php?t

                      Worked for me!

                      1 Reply Last reply Reply Quote 0
                      • Y
                        Yowsers
                        last edited by

                        Just another data point.  pfsense nanobsd 4GB vga v2.2.2.  Adding hint.agp.0.disabled=1 as a boot option worked for me as well to get my Intel Pro/1000 and Realtek Onboard NIC to be recognized in pfsense.  I also agree that this fix may (depending on frequency and scale) need to be added to the https://doc.pfsense.org/index.php/Boot_Troubleshooting section on the wiki.

                        Neither my Intel Pro/1000 (em0) nor Realtek 8111E (re0) were available as WAN/LAN NICs in pfsense but the FreeBSD boot process showed unable to attach the device for both of them:

                        em0: Setup of Shared code failed
                        device_attach: em0 attach returned 6

                        My hardware is as follows:

                        Intel Desktop Board D525MW (running latest BIOS, 0132)
                        http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-d525mw.html?wapkw=d525mw

                        Intel Atom D525
                        http://ark.intel.com/products/49490/Intel-Atom-Processor-D525-1M-Cache-1_80-GHz

                        Standard 4GB USB key - booting from USB running pfsense nanobsd 4GB vga v2.2.2

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