Intel i226-V not recognized
-
Yeah i226-V should be recognised even in 2.6. So either yours have a new device ID or they driver is failing to attach for some other reason The boot logs would show errors if that was the case though.
Steve
-
Im in the same boat. Sadly I dont have access to my device for a while, but i did notice in dmesg that there seem to be a problem attaching the driver to the device. All I have for now is this snippet from my search history:
ifdi_attach_pre failed 6
the NICS are visible when using pciconf -lv but they are not listed when i try to ifconfig.
I tried latest DEVEL daily version as well but to no avail. The opnsense does work and recognize the NICs though. I wanted to try pfsense plus version, but is there a way to install plus if I cant get CE started (since NICS are not recognized)?
-
@steadysheep said in Intel i226-V not recognized:
the NICS are visible when using pciconf -lv but they are not listed when i try to ifconfig.
Do they show as igcX or noneX?
If you have no functioning NICs you would need to either install one such as a USB NIC or install in something else and transfer the driver back to the i226 box.
Or wait for CE snapshots to restart after we have fixed most of the larger issues. There will still be some issues for a while though.
Steve
-
@stephenw10 thank you for the encouraging reply, I have the old machine already with pf plus running, sorry if it's a noob question but can you describe in short how can I transfer the driver from it to the 226 machine?
-
The driver is in-kernel so you can't easily move that individually.
I would suggest just moving the boot drive from the old device running Plus to the new device with the i226 NICs. At least as a test.
Steve
-
@stephenw10 the old machine has an mSata SSD as the new machine has an NVMe drive, will imaging the mSata ssd and restore the image to the new machine's NVMe drive work?
Edit:
After reading some posts it's not really recommended approach...
Any advise will be more than welcome
-
Since it's only really as a test you could try installing to USB and booting from that in the new device.
-
@stephenw10 not sure I understood your suggestion,what about this idea - l'll do a fresh install, connect 2 usb to lan adapters, assign them, convert to pf plus (which now raises another Q) upgrade reboot and check.
It should do the job, right?
And for other Q raised:
If the old machine is already running pf plus(activated with a key I got a while back) , will I be able to use the same key to upgrade the new machine? Will the older one needs to disconnected from the internet in order for me to use the same key?
What's the recommended approach?
As you can see, I'm eager to get it working, I'm more than happy to help, just need the proper guidance
-
Yes, that should work. You only actually need one USB NIC to allow it to install and upgrade.
You need a different key to upgrade as the NDI will be different on the new box
Steve
-
@stephenw10 Just to clarify :-)
only 1 is needed?
Should this 1 adapter be assigned as LAN or WAN?
Does pf requires an internet connection to do the upgrade?
trying to understand the logic
if no internet required than I can understand to assign it to LAN and upgrade via the UI, if not than I guess I'm missing something here -
It will always be WAN when there's only one NIC detected.
Yes it requires an internet connection to upgrade from CE to Plus.
So you would connect it to your existing network behind another router. The WAN will pull a DHCP lease in that subnet. You will be able to connect to it from a client in that subnet because with only one NIC the default rules apply to WAN.
Run the upgrade. It should then see the 226 NICs and you can assign them as normal.Steve
-
@stephenw10 You my friend are the man!!!
I can confirm that (after 2 hours of fiddling) pf plus 22.05 was able to identify the i-226v NICs.
I'm currently running on the new machine!!!
I haven't been able to test long run times and stability (yet)
, speed looks great so far - I'll keep updating.
Steve - Thank you again for your time and support
-
Nice result!
-
I ran into the same situation. This post was super helpful to me!! Thank you for the help!
-
Hi all,
I'm happy you've found this post helpful and I hope it saved you from frustration and precious time trying to understand why it's not working.
I'm updating that the machine's uptime is1 Day 06 Hours 44 Minutes 41 Seconds. No errors/link status change seen in the logs of my NICs.
Look and feel very stable.
pfSense FTW! -
wrong site, sorry!
-
@dobby_ Sorry, I don't understand your post and how it's related here. care to elaborate?
-
Hmm, yeah that looks like a mis-post?
-
Hi community
I'm also in the same boat. Is there any ETA for this to work in pfSense CE 2.7 Development?
Depending on the timeframe, Im willing to use the "Plus" method with a USB to Ethernet device. Any recommendations for working USB NIC?
-
I had a Spigen CA100 USB adapter that worked great. Pfsense recognized it as an interface without any problems. I also tried a "Pluggable USBC-E2500" and that one wasn't recognized by pfsense. I had both adapters and one of them worked and the other did not. I'm not really sure what made the difference.
