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

    Network card not detected on reboot

    Scheduled Pinned Locked Moved General pfSense Questions
    14 Posts 3 Posters 3.2k 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.
    • X
      xman111
      last edited by

      what happens is I reboot, pfsense looks like it will load normally then when it should pop up to the console, it asks if I want to make vlans because it doesn't find the NICs from my config. I always just shut it down at that point, pull the plug, then reboot to normal.

      How do i enter that command when it asks about vlans?

      thanks for your help.

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

        ah, yeah it'll stop the boot there since it's missing NICs. You can hit ctrl-c at that point to break it out to a shell and then run the pciconf. Make note of the output, then reboot. Run it again while working normally, and compare the output.

        1 Reply Last reply Reply Quote 0
        • X
          xman111
          last edited by

          thanks man, will try and report back..

          1 Reply Last reply Reply Quote 0
          • X
            xman111
            last edited by

            of course now that you are helping it isn't doing it but I guess that is a good thing.. here is the output when it is working normally..

            hostb0@pci0:0:0:0: class=0x060000 card=0x50001458 chip=0x191f8086 rev=0x07 hdr=0x00
            pcib1@pci0:0:1:0: class=0x060400 card=0x50001458 chip=0x19018086 rev=0x07 hdr=0x01
            vgapci0@pci0:0:2:0: class=0x030000 card=0xd0001458 chip=0x19128086 rev=0x06 hdr=0x00
            xhci0@pci0:0:20:0: class=0x0c0330 card=0x50071458 chip=0xa12f8086 rev=0x31 hdr=0x00
            none0@pci0:0:20:2: class=0x118000 card=0x88881458 chip=0xa1318086 rev=0x31 hdr=0x00
            none1@pci0:0:22:0: class=0x078000 card=0x1c3a1458 chip=0xa13a8086 rev=0x31 hdr=0x00
            ahci0@pci0:0:23:0: class=0x010601 card=0xb0051458 chip=0xa1028086 rev=0x31 hdr=0x00
            pcib2@pci0:0:27:0: class=0x060400 card=0x50011458 chip=0xa1698086 rev=0xf1 hdr=0x01
            pcib3@pci0:0:28:0: class=0x060400 card=0x50011458 chip=0xa1128086 rev=0xf1 hdr=0x01
            pcib4@pci0:0:28:4: class=0x060400 card=0x50011458 chip=0xa1148086 rev=0xf1 hdr=0x01
            pcib5@pci0:0:28:5: class=0x060400 card=0x50011458 chip=0xa1158086 rev=0xf1 hdr=0x01
            pcib6@pci0:0:29:0: class=0x060400 card=0x50011458 chip=0xa1188086 rev=0xf1 hdr=0x01
            pcib7@pci0:0:29:4: class=0x060400 card=0x50011458 chip=0xa11c8086 rev=0xf1 hdr=0x01
            isab0@pci0:0:31:0: class=0x060100 card=0x50011458 chip=0xa1448086 rev=0x31 hdr=0x00
            none2@pci0:0:31:2: class=0x058000 card=0x50011458 chip=0xa1218086 rev=0x31 hdr=0x00
            none3@pci0:0:31:4: class=0x0c0500 card=0x50011458 chip=0xa1238086 rev=0x31 hdr=0x00
            em2@pci0:0:31:6: class=0x020000 card=0xe0001458 chip=0x15b88086 rev=0x31 hdr=0x00
            em0@pci0:1:0:0: class=0x020000 card=0x125e8086 chip=0x105e8086 rev=0x06 hdr=0x00
            em1@pci0:1:0:1: class=0x020000 card=0x125e8086 chip=0x105e8086 rev=0x06 hdr=0x00
            igb0@pci0:4:0:0: class=0x020000 card=0xe0001458 chip=0x15398086 rev=0x03 hdr=0x00
            none4@pci0:5:0:0: class=0x028000 card=0x00108086 chip=0x24f38086 rev=0x3a hdr=0x00

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

              Well, you know what to compare it with next time at least. If you see "noneX@" in front of those emX lines when it's not working, then the driver's failing to attach for some reason. That could be a software or hardware issue. If it's not shown there at all, then the card doesn't appear on the PCI bus and there's something wrong at a hardware level.

              1 Reply Last reply Reply Quote 0
              • X
                xman111
                last edited by

                ya, it did it again.  How can i distinguish between a hardware or software problem?

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

                  What I mentioned in my last post, compare whichever NICs it is in that pciconf output (em0/1 or 1/2 I guess), see if that line is there with the "@pci0:1:0:1:  class=0x020000 card=0x125e8086 chip=0x105e8086 rev=0x06 hdr=0x00" (for instance) part, but with "none" in front.

                  1 Reply Last reply Reply Quote 0
                  • X
                    xman111
                    last edited by

                    sorry CMB, just re-read your post, makes sense now, thanks for your time.

                    1 Reply Last reply Reply Quote 0
                    • M
                      mer
                      last edited by

                      Are the NICs onboard or an extra card?  If an extra card, I assume you've checked to make sure it's seated correctly (just in case)?

                      1 Reply Last reply Reply Quote 0
                      • X
                        xman111
                        last edited by

                        it's an Intel dual pci express card.  it is seated tight.  the weird thing is it operates for days on end perfectly,  then the minute I reboot,  not detected.

                        1 Reply Last reply Reply Quote 0
                        • M
                          mer
                          last edited by

                          @xman111:

                          it's an Intel dual pci express card.  it is seated tight.  the weird thing is it operates for days on end perfectly,  then the minute I reboot,  not detected.

                          Warm reboot as in "shutdown -r now" or reboot from the WebGUI?  If you power down (shutdown -h or -p now or via Web GUI) is it always detected on power up?  I've run into devices in the past that did not handle resets very well;  reset pulse may not have been long enough or something just didn't have a reset line to it, sometimes a weird power glitch during a reset.
                          As long as you don't take power away, it doesn't care, that's why it works fine.  A solution may be to get another card and try that, but it could still run into the same issue.  Your OP says "…since I upgrade to 2.3...", did you have the same behavior with an older release?  How old is the hardware?  What is the hardware?

                          1 Reply Last reply Reply Quote 0
                          • X
                            xman111
                            last edited by

                            I always use the webgui to shutdown or reboot.    Sometimes on a shutdown it isn't detected either.  When this happens, always just pull the power plug and then it works perfectly.  I do have another card that I can retry.  Didn't notice that behavior before 2.3, i could reboot whenever I wanted and it worked.. Card is about a year old, computer is a brand new i5.

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