- Thread Starter
- #51
Apparently the SFP module only accepts 1 byte reads only. So you can read it in this thread.
LINK
I don't know if the FreeBSD driver supports that type of reading, how would I know? In some list of the driver?
I have synchronization problems at least that's what I can see, from the cxgbe(4)driver manual:
It gives me to understand that if I get a -1 it is that autonegotiation is not possible and the module will not be able to work
And it is effectively the result I get, this is an output of the kernel state:
Being port 1 where the SFP is connected, if I exchange the port SFP the same thing happens, port zero becomes -1 and port one becomes 1.
My loader.conf:
But apparently the Chelsio T520-CR card and the module cannot be set to the same speed. These are the speeds supported by the card.
According to chelsio’s paper the T520-CR supports the IEEE802.3z coding. But according to ifconfig it doesn’t support the 1000baseLX standard which is what the module is supposed to use.
What gives me to understand that the card is not designed to use a single fiber module if not multiple, according to the standard.
Gigabit Ethernet
Which gives me to understand all those failures, forgetting the possible problem with reading a single byte of the module.
What do you think?
LINK
I don't know if the FreeBSD driver supports that type of reading, how would I know? In some list of the driver?
I have synchronization problems at least that's what I can see, from the cxgbe(4)driver manual:
Link autonegotiation settings. This tunable establishes the de-hw.cxgbe.autoneg
fault autonegotiation settings for all ports. Settings can be
displayed and controlled on a per-port basis via the
dev.<port>.X.autoneg sysctl. 0 disables autonegotiation. 1 en-
ables autonegotiation. The default is -1 which lets the driver
pick a value. dev.<port>.X.autoneg is -1 for port and module
combinations that do not support autonegotiation.
It gives me to understand that if I get a -1 it is that autonegotiation is not possible and the module will not be able to work
And it is effectively the result I get, this is an output of the kernel state:
$ sysctl -a |grep autoneg
hw.cxgbe.autoneg: 1
dev.cxl.1.autoneg: -1
dev.cxl.0.autoneg: 1
Being port 1 where the SFP is connected, if I exchange the port SFP the same thing happens, port zero becomes -1 and port one becomes 1.
My loader.conf:
if_cxgbe_load="YES"
hw.cxgbe.autoneg=1
dev.cxl.0.autoneg=1
dev.cxl.1.autoneg=1
But apparently the Chelsio T520-CR card and the module cannot be set to the same speed. These are the speeds supported by the card.
$ ifconfig -m cxl1
cxl1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6,HWRXTSTMP,NOMAP>
capabilities=6ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6,HWRXTSTMP,NOMAP>
ether 00:07:43:33:a2:08
media: Ethernet 1000baseSX <full-duplex,rxpause,txpause>
status: no carrier
supported media:
media 1000baseSX mediaopt full-duplex,rxpause,txpause
media 1000baseSX mediaopt full-duplex,rxpause
media 1000baseSX mediaopt full-duplex,txpause
media 1000baseSX mediaopt full-duplex
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
According to chelsio’s paper the T520-CR supports the IEEE802.3z coding. But according to ifconfig it doesn’t support the 1000baseLX standard which is what the module is supposed to use.
What gives me to understand that the card is not designed to use a single fiber module if not multiple, according to the standard.
Gigabit Ethernet
Which gives me to understand all those failures, forgetting the possible problem with reading a single byte of the module.
What do you think?