Chelsio T580-SO-CR
-
Hello
I just build pfsense capable system with DELL R320 and Chelsio T580-SO-CR.
The pfsense installed with no problem at all. My question is should I make any firmware or driver changes to trunk the vlans trough this adapterThank you
-
I would not expect any changes to be required.
If you've not seeing problems run as it is.
Steve
-
@stephenw10 Ok is chelsio driver or firmware have some setting for a vlan or trunking because i kind of crash the server firmware and I will have to fix it before I can test the vlans
if anyone know any guide how to configure or what can be configure on the driverJust note to anyone who is going to install pfsense on DELL R320 :
1st make sure you get the server with BIOS 1.5.2 and Lifecycle Controller 1.1.5
DO NOT UPGRADE THE FIRMWARE ON THE SERVER pfSense will not work with the latest firmware. Remove any PERC controller before you install pfSense R320 have embedded controller that will work fine with pfsense. If you get R320 with latest firmware roll them back in a proper way not like me :) 1st roll back Lifecycle controller to legacy version then IDRAC7 (if any) then BIOS. Unplug the power cords hold the power on/off key for at least 1 min and then power it on.
I know is off the topic but I learn from my mistake because there was no info on internet how to do it property and I believe I've damage the main board.I hope someone can share with me how to configure or what I can configure on the driver for this card
Thank you
-
I'm unsure what the situation was then. As far as I know there is no special setting required for that card. It should be supported by cxgbe(4).
I expect the NICs to appear as cxl0 and cxl1, did that not happen?Steve
-
Did happen until I upgraded to pfsense 2.4.4 no longer supported or I don't know !!!!
any suggestions -
The card was working in 2.4.3 and is not in 2.4.4?
Check the boot log for errors from the card/driver.
Steve
-
@stephenw10 here it go 2.4.3 all interfaces working perfectly when upgrade to 2.4.3_1 or 2.4.4 that's it I feel like I am giving you hardware information to frucked up on the next version so you can sell your own hardware. No one had used this hardware before because I was looking all over this forum and then I start talking for this particular adapter well next not major version is no longer plug-n-play How about that ? Ether I am crazy or there is a conspiracy going on
Yes I will check the log for errors if I find it !!!
I do not have much of experience with freebsd that's why was looking for something that is plug-n-play and match my network gearThank you
-
@xlameee said in Chelsio T580-SO-CR:
Ether I am crazy or there is a conspiracy going on
You are crazy. Driver updates and deprecation is largely done by the FreeBSD developers, not the pfSense developers. If at all the pfSense devs add additional drivers.
-
There is no conspiracy to break NICs I assure you. But feel free to review the source code:
https://github.com/pfsense/FreeBSD-src/tree/RELENG_2_4_4/sys/dev/cxgbeWhat is the actual PCI ID of that card? Is it listed here?:
https://github.com/pfsense/FreeBSD-src/blob/021c0c7c1ad07dad2227fb7529e176648cc53716/sys/dev/cxgbe/t4_main.c#L648Yes, if there are no errors you can see there a good test here would be to try the adapter in FreeBSD 11.2. If it works there and not in pfSense then it could be a change we've accidentally introduced and we can look into that.
Steve
-
@stephenw10
Sep 30 13:40:57 kernel t5nex0: <Chelsio T580-LP-SO-CR> mem 0xd9d00000-0xd9d7ffff,0xd8000000-0xd8ffffff,0xd9ffa000-0xd9ffbfff irq 48 at device 0.4 numa-domain 0 on pci2
Sep 30 13:40:57 kernel t5nex0: fw init failed: 5.
Sep 30 13:40:57 kernel t5nex0: error during attach, adapter is now in recovery mode. -
Hmm, so some firmware issue. The t5 firmware modules seem to be loaded:
[2.4.4-RELEASE][root@4220.stevew.lan]/root: kldstat -v | grep t5 112 pci/t5iov 118 t5nex/cxl 115 pci/t5nex 124 t5fw_cfg_fw
What firmware version is on the card? Has it been updated?
Testing in FreeBSD 11.2 is probably the next step though just to be sure it works as expected there.
Steve
-
I'm not sure whether this is helpful, but I have the T520-SO-CR version of the card and also experienced some issues after the upgrade from 2.4.3_1 to 2.4.4, though nothing nearly as severe as what the OP is going through. When 2.4.4 came up I lost one of the network card tunables I had set. I had disabled Flow Control on the card, and while the tunable was still set in advanced settings, the card showed flow control as enabled after the system booted. Oddly enough, going into advanced settings and opening the flow control tunable and saving it again would then disable flow control. I have not found a way to get around this, including adding the flow control options into loader.conf.local. The system will boot with flow control enabled until I manually disable it. Could it be that something with the driver did change in FreeBSD?
-
It might have been. I'm not aware if any changes there though. Even if there were I would still expect it to conform to the sysctl settings.
What values are you actually setting?
hw.cxgbe.pause_settings
?Steve
-
Hi @stephenw10 - actually I'm setting this tunable (covers both ports on the card):
dev.cxl.0.pause_settings=0
dev.cxl.1.pause_settings=0This worked perfectly in 2.4.3_1 and prior. In 2.4.4 even with these values set under System Tunables and within loader.conf.local, flow control is enabled when the system fresh boots. Maybe something changed?
-
Well I would certainly try that variable I posted that should cover both ports. I wasn't aware that had changed but...
Steve
-
According to the 11.2 cxl manual page nothing has changed there.
How are you determining flow control is still enabled after boot?
-
Thanks @stephenw10 and @Derelict.
Two ways:
- I first saw on the interfaces widget in the dashboard that besides just "10Gbase-SR <full-duplex>", "RX Pause", "TX Pause" were now also included between the < >.
- I confirmed this by via sysctl from the shell and saw that dev.cxl.x.pause_settings was set equal to 3 for both ports.
I'll try hw.cxgbe.pause_settings=0 next to see if that might make a difference. Thanks again for all your help.
-
@stephenw10 here is what I get
-
Ok so nothing different. Are you able to test that card in FreeBSD 11.2?
Steve
-
@tman222 I had that problem after I upgraded to 2.4.2_1 and then the same problem with 2.4.4