Super Micro X10SLL-SF NIC
-
I'm trying to get pfsense installed on this mobo but no nic's are detected in stable release. When I tried the 7/18 build it detected the 10gbE but no on-board. Shouldn't they just be generic intel? Thanks. :-\
Dual Gigabit Ethernet LAN ports
(1x Intel
i217LM & 1x Intel i210AT)Website: http://www.supermicro.com/products/motherboard/Xeon/C220/X10SLL-SF.cfm
-
That hardware and those NICs are brand new; consider yourself lucky that the system actually boots.
I don't think you're going to get them working until pfSense moves to FreeBSD 8.4 or 9.1. The igb driver in the RC0 builds is 2.3.1. You need 2.3.4 for i210 and 2.3.9 for i217 (based on release notes for newer versions of FreeBSD).
-
Hey guys this interesting - I realized 2.3.1 was there too, though rbgarga backported the latest patches from 8-STABLE which (as in the code) should be "2.3.9 - 8" compare:
-
https://github.com/pfsense/pfsense-tools/blob/master/patches/RELENG_8_3/from-8-STABLE/e1000/0008-MFC-247430.patch
-
https://github.com/freebsd/freebsd/commit/b01e67e7b7a55d67042a0dabc638da351ab2e4cd#sys/dev/e1000
These drivers technically should at least support i210's, the question is if something at the patch level (or between the chair) is wrong, the i217 is also listed in the list of IDs.
weirdI don't have a box available to see if the patches get applied though, but feel free you ask the guys if there is something wrong about the backported patch.
-
-
I believe the patches were backed out because they broke traffic shaping.
http://forum.pfsense.org/index.php/topic,63484.msg346193.html#msg346193Steve
-
crap yes they got backed out, but with valid reason of unbreaking ALTQ, see:
https://github.com/pfsense/pfsense-tools/commit/0d63350445dad1e7281ba085cd9fa0e0fdd7e261 -
So…. no support for the Intel I210-T1? I put one in along with an I350-T2. The former is not recognized by PfSense 2.1RC1 but the latter is. Trying to determine if I have a bad card, bad MB slot, or the T210 is not supported by the igb driver.
-
Until those patches go back in there is no support for the I210. Though I imagine it must be coming because that chip is likely to be very popular.
If you need to run it now, and you don't need ALTQ, you could probably get hold of an old image or recompile your own IGB driver.
Steve
-
Until those patches go back in there is no support for the I210. Though I imagine it must be coming because that chip is likely to be very popular.
If you need to run it now, and you don't need ALTQ, you could probably get hold of an old image or recompile your own IGB driver.
Steve
Yeah, I already contacted support and they offered the newer driver after letting me know that traffic shaping would break. I was looking at a Lanner box that used i210 NICs.
-
How would I be able to go about getting the drivers for this board? I am trying to accomplish the same thing and traffic shaping it not important to me at the moment.
-
How would I be able to go about getting the drivers for this board? I am trying to accomplish the same thing and traffic shaping it not important to me at the moment.
Well, if you have a support agreement, just open a ticket and ask. If not, I dunno. Try sending a message to jimp and asking nicely, I guess.
For what it's worth, I have an open ticket with support about the possibility of a low-cost fix of the issues they had with the 2.3.9 driver based on a post-8.4 to FreeBSD. It's something I asked that they look into AFTER 2.1 drops. With any luck we'll see it drop with 2.3.1. If not, 2.2.
Change defines in the igb driver to allow an easier selection of
the older if_start/non-multiqueue interface from the stack. This
is not the default, but can be turned on in the Makefile now regardless
of the OS level to allow either testing or use of ALTQ. -
Is there something new here?
I have an ASUS P9D-I, Socket-1150 with 2x Intel I210AT onboard and i like to use this insted of buy a intel dual card nic.
Thanks!
