X-540 T2 didn't boot up on pfSense CE 2.5.0-RELEASE (amd64)
-
-
Is that same device? It shows re0 is recognised there, it should offer that as an interface at least.
Looks like it's failing to recognise the x549 card though. 1512:8086.
Not shown as a known ix device:
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_5_0/sys/dev/ixgbe/ixgbe_type.h#L85Not even a known PCI device: https://pci-ids.ucw.cz/read/PC/8086
There are references to it though and it's not new.
Steve
-
@stephenw10 It's showing re0 but I disabled it in BIOS, so that's why it was shown.
Did I understood you right that this topic will be solved in future for this X549 T2? Or I can create a bug :) ?
-
It looks to be unsupported by the FreeBSD driver, you should open a bug there. If one does not already exist.
Or get a different card.Steve
-
-
This post is deleted! -
I did this test, you need to enable it as a module or a kernel :) Ive tested 540 and 550, both required the setting for the nics to show up
-
What test did you do exactly?
The response on the FreeBSD ticket about the NIC is question here is interesting.
Seems like it should not exist in the wild! So will never be officially supported.
Steve
-
@jnz07 loader.conf
add this line if_ixgbe_load="YES"
He meant the 540 :) mine didnt load under 2.5 either, I have to add this line to the loader.conf, after a reboot no problem
-
Hmm, that absolutely should not be required. It's the same driver that's in kernel.
-
@stephenw10 So to summarize do we do something in this area ? Or we just can close the thread ? If there's nothing we can do, than let's close it.
-
There is nothing we can do in pfSense and if looks like FreeBSD upstream can't do anything either since it should not exist.
If you really needed to use it for some reason you could probably recompile the kernel module with the patch on the FreeBSD bug to add the IDs. But you would be stuck compiling it again at each release.
Better to just use a different NIC.Steve
-
@stephenw10 I was able to get mine going, not sure "why they shouldnt exist" as I have something like 100 workstations at one site and they all have the 540-t2 cards. So if its a card that shouldnt exist, I know for one, I have a lot of them
-
With that same PCI ID?
-
@stephenw10 Correcto, enabling the line above made them work otherwise machine wouldnt even boot
-
Hmm, well two weird things there.
Enabling the identical driver as a kernel module should make no difference at all. A timing difference maybe?
The guy from Intel commented in that bug report that it is a:
non-production internal-only device idSo I would not expect to find it on a whole bunch of cards.
Steve
-
@stephenw10 said in X-540 T2 didn't boot up on pfSense CE 2.5.0-RELEASE (amd64):
There is nothing we can do in pfSense and if looks like FreeBSD upstream can't do anything either since it should not exist.
If you really needed to use it for some reason you could probably recompile the kernel module with the patch on the FreeBSD bug to add the IDs. But you would be stuck compiling it again at each release.
Better to just use a different NIC.Steve
@stephenw10 I already changed to Intel X520-DA2 SFP+ 10Gb Dual Port ;).
Anyway I guess that this thread will be more for information purposes for others that Intel X540T2 is not working with pfSense CE 2.5.0-RELEASE (amd64) .
-
@jnz07 I replaced mine with a 550-t2 to avoid future issues
