Intel i226-V not recognized
-
2.6 supports some i226 NICs. If it's one of the PCI IDs shown here it should work:
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_6_0/sys/dev/igc/igc_hw.h#L18Otherwise 2.7 snapshots have the current i226 support from FreeBSD main.
Steve
-
@stephenw10 Thanks Steve.
-
@stephenw10 I ran pciconf -l in a shell to see the device IDs. They are 0x125C which is on the list linked above.
I have one of these 4x Intel i226-V "fanless" PCs. 2.7.0 DEV works, but after reading this thread, it seems there is no practical path to upgrading to Plus. So I'm thinking about starting over with 2.6 if it supports my NICs, which theoretically would let me switch to the Upgrade branch for a 22.05 upgrade?
With 2.7.0 DEV, when I select Upgrade branch, it only offers 22.01, which would leave me "NICless", and nobody wants to be NICless before Christmas! ;-) -
Yes, I would try booting the 2.6 installer. You should see the igc NICs in the boot logs without needing to install to test.
-
@stephenw10 I decided to give Proxmox a try and virtualize those i226 out of existence. I installed pfSense 2.6.0 in a VM, but it still wanted to upgrade to 22.01, so I did, then it offered 22.05, or 23.01 on dev. So I think there's a requirement to install 22.01 before 22.05 which is going to make trouble for people with i226 NICs on bare metal. Now on to learning all about vlans!
-
@darryl insert a USB NIC and update could probably help?
-
Mmm, you certainly can do it using a USB NIC but it's a long way to get to the final install.
-
@darryl Nickerless is one thing, but going NIC'less is a whole other ball game.
-
G Gertjan referenced this topic on
-
Hi guys
Completely new to PFsense as a firewall/router appliance, but wanted to start out with this as my ISP router does not provide the solutions I want and retail routers are just overpriced and generally not gigabit speed worthy.
That out of the way, I bought a fanless box with I226-V NICs in them, and although I seem to read here they are supported, it seems my fresh 2.6 install does not recognize them at all and refuses to boot.
I only have a USB-C to Ethernet at hand and this only pops up after it already decided to halt the system so that does not really help either.
Any guide and tips you guys can give me to help and get this thing up and running?
Cheers
Mili
P.S. if I need to make a new thread, please let me know.
-
@milithor I think it’s already mentioned on the forum. Use a nightly build of 2.7.0
-
https://forum.netgate.com/topic/174406/intel-i226-v-not-recognized/14?_=1676027483074
-
M MarinSNB referenced this topic on
-
@thebear
Do I understand correctly this is then a developer build? -
-
@milithor said in Intel i226-V not recognized:
@thebear
Do I understand correctly this is then a developer build?I know what its like to be messing about trying to get your new kit up and running.
Ideally at this point because the latest Stable Version (Community Edition) doesn't offer support for your Intel i226-V, If I was you I would do one of two things so's not to have to mess about too much trying to make it work.
OPTION 1
The keep it simple method:
Get two compatible USB2Ethernet adaptors plug them up install the latest stable COMMUNITY EDITION release, which is currently 2.6.0
Seen here: https://www.pfsense.org/download/
Install it PfSense setting one of your USB2Ethernet adapter to be your WAN and the other to be your LAN
Then proceed to follow this relatively simple procedure which will convert your standard latest stable community edition release (version 2.6.0) to a newer PFSENSE+ version.
Seen Here: https://docs.netgate.com/pfsense/en/latest/install/migrate-to-plus.html
Once that is migrated to PFSENSE PLUS all of your Intel i226v ethernet ports will become available for configuration.
Note This can be done with just one Ethernet2USB device providing you have a network switch that supports VLANS.
Example here: https://www.youtube.com/watch?v=z59_MWWPL-Q
Also Note: It could also be done using one compatible USB2Ethernet adapter without a VLAN compatible switch providing you had say a USB2WIFI adapter or some kind of internal m.2, mpcie WIFI adapter, allowing you to make one device WAN and the other LAN, have internet then proceed to the PFSENSE+ upgrade..
OPTION 2 If all else fails!
Dare I say it just install OPNsense latest iteration. Your i226 NIC will all be detected upon install.
Note: OPNsense is a fork of PFSENSE.
You can use that just so you can get your new equipment up and running for now, especially if you don't have a couple of compatible USB2Ethernet devices or VLAN compatible switch to get you going today.
Theirs not much in it between the OPNsense and PFsense to be honest, although their are far more tutorials for PFSENSE online, allot which actually apply to OPNsense.
-
@souk Or install the development build (nightly) of 2.7.0, play for a few weeks. Export your config and do a fresh install of 2.7.0 if its stil in your mind that nightly build are not great.
It's a lot of work to install clean for 226v nics. In fact with a new router you got the play phase where you enable every option, use that with the nightly build.
-
@thebear firstly, does the nightly build allow you to roll back to Stable?
-
If not who really wants to risk their system becoming broken every time a risky update comes out, I know I don't.
-
You say its allot of effort to do a fresh install for i226 NICs, but is it really considering that user wont have a huge config yet. Remember, as mentioned he's new to it and just bought his nice new shiny hardware. As he's got nice new purpose built hardware why not install a clean STABLE operating system on it and try to have the smoothest experience possible from the start.
-
If he's got two compatible USB2Ethernet adapters and a TopTon unit like mine the whole fresh install and migration can be done in like 20 minutes.
-
Who wants to wait for the update when you've just spend hundreds on hardware and you can have it up and running today ? Some might want to wait, but not me.
-
If he wants as little effort as possible and stability he should just install OPNsense and be done with it.
Both OPNsense and OpenWRT worked great with i226 from fresh installs for me, It was nice to us OpenWRT for a change and actually be able to get amazing WIFI @ the router too, which is something both OPNsense and PFsense fail miserably at still in the year 2023. Madness!
-
-
@souk said in Intel i226-V not recognized:
@thebear firstly, does the nightly build allow you to roll back to Stable?
You can always reuse the config in a higher version, right @stephenw10 ?
All the other choices are up to you, good luck.
-
Indeed the config file is backwards compatible but you can't (or shouldn't at least) use a config from 2.7 in 2.6. You can see the config file versions here:
https://docs.netgate.com/pfsense/en/latest/releases/versions.html
So currently you can use a 2.7 config in 23.01.If you install ZFS you can can roll back between versions but compatibility for that was only added in 22.05 so you can't roll back to a 22.01 or 2.6 BE snapshot.
Steve
-
“ you install ZFS you can can roll back between versions”
That’s good news if its only limited to “newer” versions.
-
Hi all I see on the internet allot of complains regarding the i225-V and i226-V.
For the i225-V have performance problems and no good for more than 1Gb
And the i226-V have connections drop issues.
I assume that these are Windows users so I am wandering if any one here using i226-V with pfsense are heaving problems?
