No interfaces found after upgrading J1900 (Intel 82583V nics) from 2.3 to 2.4
I have a J1900 device that uses Intel 82583V nics. I have been running 2.3 for a while now and had no issues. I kicked off the 2.4 upgrade and it seemed to have failed.
The upgrade process seemed to complete without any issues, and the machine rebooted. However, when it came back up, I am presented with the interface assignment option with the message:
"Network Interface Mismatch – Running interface assignment option"
But, the valid interfaces list is empty and I am then presented with:
"No Interfaces found!"
I am not able to get it to detect any of my 4 nics. However, if I boot the machine into the old kernel (using the kernel.old from the pfSense boot menu), I am able to boot completely and my NICs will show up and be useable, and pfSense will route and work normally...somewhat.
I notice a few things don't work as expected:
1. CPU usage is reporting at 100% in the webui
2. WAN inbound and outbound traffic gets reported under OUT for both in/out traffic.
It doesn't look like this new kernel has support for the NIC's in the J1900 boxes? Really? Checking dmesg and other tools reveals this about the NICs:
[2.4.0-RELEASE][admin@pfSense.localdomain]/root: dmesg |grep em0 em0: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k=""> port 0xe000-0xe01f mem 0xd0900000-0xd091ffff,0xd0920000-0xd0923fff irq 16 at device 0.0 on pci1 em0: No MSI/MSIX using a Legacy IRQ em0: Ethernet address: 00:78:2a:e8:33:d4 em0: netmap queues/slots: TX 1/4096, RX 1/4096 em0: link state changed to UP em0: link state changed to DOWN em0: link state changed to UP</intel(r)>
em0@pci0:1:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82583V Gigabit Network Connection' class = network subclass = ethernet
Any suggestions as to why I can't get the new 2.4 version of the kernel to work with these Intel NICs when the old version seems to work?
Similar issue with my J1900 Protectli Vault. In addition to missing libraries, would not assign IP addresses.
Backup /cf/conf/config.xml, clean install, restore config.xml
If a clean install works, some part of the upgrade must have failed, leaving you with a mismatched kernel and base system. If you still have access to the broken system, please get the contents of /conf/upgrade_log.latest.txt and /conf/upgrade_log.txt and post them.
At least judging by that output it all seems to have upgraded OK.
I'm surprised it's working at all when booting kernel.old though. What shows in "uname -a"?
Hmm. This is odd.
[2.4.0-RELEASE][admin@pfSense.localdomain]/root: uname -a FreeBSD pfSense.localdomain 10.3-RELEASE-p19 FreeBSD 10.3-RELEASE-p19 #1 76a12c4e6(RELENG_2_3_4): Fri Jul 14 15:02:35 CDT 2017 root@ce23-amd64-builder:/builder/pfsense-234/tmp/obj/builder/pfsense-234/tmp/FreeBSD-src/sys/pfSense amd64 [2.4.0-RELEASE][admin@pfSense.localdomain]/root:
I have attached the text files in this reply.
I have not yet reinstalled, as I am right now booting the unit to the kernel.old to get it running.
Exactly the same problem (failed with same error after upgrade, works with kernel.old)
Motherboard : ASRock D1800M (Celeron Processor J1800)
NIC (not working after upgrade and new kernel) : Intel EXPI9301CTBLK (PCIe), SYBA SY-PEX24028 Dual Port (PCIe, Realtek Chipset 8111E)
NIC (working after upgrade and new kernel) : Realtek RTL8111GR (integrated)