Error: PFSense cannot continue without at least one network interface card
-
2.7 is released now, no need to use a snapshot:
https://www.pfsense.org/download/ -
@stephenw10
Forgive me for my ignorance, but I did the installation of 2.7 and the same problem appears in the attached image of the friend cg50000. I am upset. -
What NICs does it have?
-
@stephenw10 04 ports I226-V.
-
Like rev4 or it has 4 NICs?
[root@test4.stevew.lan]/dev: pciconf -lvc igc0 igc0@pci0:25:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000 vendor = 'Intel Corporation' device = 'Ethernet Controller I226-V' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 5 messages, enabled Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR RO NS max read 512 link x1(x1) speed 5.0(5.0) ASPM L1(L1) ecap 0001[100] = AER 2 0 fatal 0 non-fatal 0 corrected ecap 0003[140] = Serial 1 0008a2ffff12ecd4 ecap 0018[1c0] = LTR 1 ecap 001f[1f0] = Precision Time Measurement 1 ecap 001e[1e0] = L1 PM Substates 1
-
@stephenw10
I can't enter any command, because PFSENSE hangs on the same screen as the first question in this post. Is there another way I can extract this information? -
I would try to boot something else to confirm. Something Linux based is most likely to function.
You could boot a FreeBSD 14 snapshot, that will allow you install even if it doesn't find any NICs.
https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/14.0/ -
Hello!
I was able to boot PFSense (version 2.6) with a USB/LAN interface. I updated to version 2.7 and now it recognizes the I226-V ports!Thank you very much for all your attention!
-
Nice!
That's odd though. The 2.7 installer did not find that NICs directly?
There should be no difference between and upgrade from 2.6 or a clean 2.7 install. Certainly the kernel and drivers are the same.Steve
-
@stephenw10
I also found it very strange, because I installed version 2.7 before and it didn't recognize it. But this morning I tried to install the 2.6 version, use the USB interface and perform the update and this way it worked. Maybe it's something about the motherboard. Can I create a new topic about this case and point out this alternative? -
It seems more like a bug if that's repeatable. Though it could be something specific to that board. It's hard to see how it would be any different.
-
@stephenw10
I believe it could be yes. But resolved on my part. Thanks again for all the help!