Intel Ethernet Controller I225-LM Support?

whizatit

Ok so thats f***** up it works in their own appliance but not public release? Stingy holding out on us lol. Not being mean just saying...

stephenw10

It was just unfortunate timing. We had a bunch of cool fixes for things in the 2.5.2 branch, including this. We had to eventually build 2.5.2 on the 2.5.0 branch because it was going to take too long to get everything fixed and tested when there were security patches ready to go.

I have 2.6 running on a bunch of things without issue but there are still some outstanding things, most notably captive portal. https://redmine.pfsense.org/issues/12217
That may be fixed in tomorrows snap though.

But check the list and decide for yourself:
https://redmine.pfsense.org/projects/pfsense/issues?query_id=106

Steve

whizatit

I am soooo damn slow... I just now realized your an admin and work with Netgate lol. Thanks for the heads up sir!

I'm just like everyone else, WE want "the" answer or answers and don't pay attention to everything else/details.

Goes to show READ EVERYTHING BEFORE doing ANYTHING!

arodd

I'm running the latest 2.6.0 snapshot with the QNAP QXG-2G2T-I225 and it is detected in the initial boot, but doesn't detect any interfaces and then shuts down. There are no other nics enabled(onboard is disabled in the BIOS). Maybe this specific device id isn't enabled, though I would have expected it to be a popular option. Has anyone else successfully gotten this specific card working? It is significantly cheaper than the 10Gb Intel varieties that support 2.5Gb 10GbaseT.

silvercharge

@arodd I've had inconsistent results as well using two of the single interface versions of the QNAP i225s - QXG-2G1T-I225. Also running 2.60. Sometimes the driver loads and others it does not. Currently running 2.6.0.a.20210907.0100 with success.

stephenw10

You have any logs showing it detected but not attaching maybe?

arodd

@stephenw10 I think I would need to fetch them via serial interface or something. It shuts down as soon as it boots up since there are no interfaces detected so there isn't an opportunity to fetch them and log to a flash drive or anything. Will see if I can get a serial port to dump the boot log.

Edit: Scratch that my unit doesn't have a serial port. Will try and find another way to capture them if the boot/system log persists on disk after multiple boots.

arodd

@stephenw10 dmesg.txt
Was able to fetch everything via single user mode, attached the dmesg output. The igc0 specific lines are below. This is from the latest 2.6.0.a.20210910.0100. Looks to be the same issue as previous posters, but still occurring in 2.6.x.

igc0: <Intel(R) Ethernet Controller I225-LM> mem 0xf7c00000-0xf7cfffff,0xf7d00000-0xf7d03fff irq 16 at device 0.0 on pci3
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6
igc0: <Intel(R) Ethernet Controller I225-LM> mem 0xf7900000-0xf79fffff,0xf7a00000-0xf7a03fff irq 18 at device 0.0 on pci6
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6
igc0: <Intel(R) Ethernet Controller I225-LM> mem 0xf7c00000-0xf7cfffff,0xf7d00000-0xf7d03fff irq 16 at device 0.0 on pci3
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6
igc0: <Intel(R) Ethernet Controller I225-LM> mem 0xf7900000-0xf79fffff,0xf7a00000-0xf7a03fff irq 18 at device 0.0 on pci6
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6
igc0: <Intel(R) Ethernet Controller I225-LM> mem 0xf7c00000-0xf7cfffff,0xf7d00000-0xf7d03fff irq 16 at device 0.0 on pci3
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6
igc0: <Intel(R) Ethernet Controller I225-LM> mem 0xf7900000-0xf79fffff,0xf7a00000-0xf7a03fff irq 18 at device 0.0 on pci6
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6

arodd

So it turns out my issue was related to booting via BIOS vs. UEFI. Realized this when it attached and was working in the installer CD via UEFI. Switched the install over to UEFI and everything is working now.

Update: Things work fine without VLANs, but traffic isn't flowing when using VLAN interfaces.

stephenw10

Try disabling any vlan hardware off-loading options. I'd start with VLAN_HWFILTER if it's enabled on that variant.

The driver 2.6. is now identical to what we build in 21.05.1 (or 21.09) so oy must be some hardware difference.

Steve

ndemmon

@stephenw10

FYI, the Dell Optiplex I'm trying to use has the same driver attach problem reported above, if the internal NIC is linked up at boot time then the igc driver won't attach to my QNAP card.

The difference is that I'm an actual *nix kernel developer who knows how crazy that sounds...there must be some timing issue involved. I'd be willing to dive in on my free time and do some debugging or info gathering, but I'm currently hampered by the fact that I haven't touched FreeBSD ever so I'm doing things like searching for links on "this is how you build the kernel" :)

stephenw10

I would start by booting with verbose enabled and see if the driver gives any sort of useful error output when it fails to attach.
Also that can change the timing so you may find it does attach when booting verbose, if it is a timing issue. I have seen that before with other hardware.

At the loader prompt:

set boot_verbose=1
boot

Steve

ndemmon

@stephenw10

no new messages with boot_verbose. Looking at the source code, this makes sense as the debug output is all wrapped in a compile-time #define that's turned off. Any hints how to recompile the kernel so I can dig into this?

stephenw10

You don't need to recompile the kernel for most drivers, you can just compile the module and load it in preference to the in-kernel driver. I haven't actually tried that for igc though.

Steve

ndemmon

@stephenw10
This is where the "I've never touched freeBsd" bit is hitting me. I got the pfsense source code loaded onto a freebsd vm. While I couldn't get "make" working from {SRCROOT}/sys/modules/igc (some error about a bad definition of struct thread that implies to me that the include path was messed up but that was about as far as I was going to take it), I did get "make buildkernel" working fine from {SRCROOT}, and I went and found if_igc.ko in /usr/obj/...

And I think I'm stuck. I added a string/device_printf to an always-run path (right before the call to igc_setup_init_funcs() that's returning the error). I can grep for the string in my built if_igc.ko file and it's there. I made an assumption that if I replaced the /boot/kernel/if_igc.ko file on the pfsense box with the one I built, I'd get my debug printf in either dmesg -a, /var/log/dmesg.boot, or /var/log/* somewhere.

I did not, it's like it's still using the original driver to boot. What bit of FreeBSD magic am I missing?

stephenw10

You need to load it at boot by adding:

if_igc_load="YES"

to /boot/loader.conf.local. Create that file if it doesn't exist.

I've done that in the past with quite a few different modules but not with igc specifically.

Steve

ndemmon

@stephenw10
Woo hoo, "phy initialization error". Now I just have to fix the debug messages to actually print out debug information (like what values are being read and written to the phy so I can tell what it doesn't like in the error case). Just as an FYI, with more test cycles it's not tracking the link state of em0 anymore. The most reliable reproduction method is to halt the system (option 6 from the login menu) and then when I start the system via the on button the attach fails. Thinking maybe something doesn't get reset on that particular path, will update again if I find a fix and/or give up and just give an info dump.

Thanks for saving me the hours trying to find the loader.conf.local magic by myself.

ndemmon

@stephenw10

Found it.

        /* Make sure the PHY is in a good state. Several people have reported
         * firmware leaving the PHY's page select register set to something
         * other than the default of zero, which causes the PHY ID read to
         * access something other than the intended register.
         */
        ret_val = hw->phy.ops.reset(hw);

(igc_i225.c, line 168-ish)

phy->ops.reset = igc_null_ops_generic;

(igc_phy.c, line 37)
So something about that boot path leaves the phy's page select at non-default, which makes the phy revision come out unexpected. The code tries to fix this by issuing a reset of the phy, but nobody wrote and/or assigned the phy reset function. (Function tracing shows that igc_null_ops_generic() is getting called there instead.)

The problem is that that's not exactly a risk-free fix of throwing an actual phy reset into the boot path.

ndemmon

So if I throw in:

        phy->ops.acquire        = igc_acquire_phy_base;
        phy->ops.check_reset_block = igc_check_reset_block_generic;
        phy->ops.commit         = igc_phy_sw_reset_generic;
//Adding a reset function so phy_id always works.
        phy->ops.reset          = igc_phy_hw_reset_generic;
        phy->ops.release        = igc_release_phy_base;

it passes my initial tests. Assuming that this phy works like most of the dozens of phys that I've worked with, it implements two copies of the first few standard registers, one copy that tracks the "host side" of the phy that connects to the MAC and one copy that tracks the "line side" where you plug in the cable. The software reset bit is in that register window, so software reset doesn't affect the page you're reading from (you just reset the half of the phy that the page select currently has selected) so it has to be the hw_reset function.

This WILL cause an extra link-flap at boot time...I don't really care for my home setup. If I was looking for something safer to do in public code, I'd probably leave the path that grabs the phyID alone, but if it failed I'd do the hardware reset and retry. Or you could manually select page 0 before grabbing the phyID, but who knows what other stale info the PHY has that might screw something else up.

Thanks for the help!

stephenw10

Ah, nice!

Might be time to open a FreeBSD bug for that if nothing already exists.

Is this you?: https://reviews.freebsd.org/D32772

If not it looks like this is already being addressed.

That is in FreeBSD source now but not our fork yet.

Steve