Solved: Re: Re:Problem with ICE drivers and ts2phc program [E810-XXVDA4T]

RobertWojtowicz · ‎08-14-2025

Hi, All

I have no problems with the native Linux driver (RockyLinux, 6.12.0-55.25.1.el10_0.x86_64+rt) with E810-XXVDA4T, the ts2phc configuration file looks like this:

[global]
ts2phc.pulsewidth 100000000

ts2phc.nmea_serialport /dev/gnss0
leapfile /usr/share/zoneinfo/leap-seconds.list

[/dev/ptp0]
ts2phc.extts_polarity rising

Launching:

ts2phc -f /etc/ts2phc.conf -c /dev/ptp0 -s nmea -m -q -l 6

When compiling and installing ice-2.2.9 drivers, you will see the following message in dmesg:

driver cannot use function 1 and channel 0 on pin 0

In ts2phc logs:

PTP_PIN_SETFUNC2 failed: Operation not supported
ts2phc[20.394]: PTP_PIN_SETFUNC request failed
ts2phc[20.394]: failed to create sink
failed to add PPS sink

How to solve this problem? I would like to use the vendor's drivers.

BR,

Robert

RobertWojtowicz · ‎08-19-2025

Hi, @Azhari_Intel

last working drivers with SDP pin settings for DPLL are ice-1.17.8. It definitely doesn't work with 2.2.9, I report an error on GitHub.

You may close this topic

BR,

Robert

View solution in original post

vish1 · ‎08-14-2025

Hello RobertWojtowicz,

Greetings for the day!!

To effectively troubleshoot the issue you're facing, we require some additional information from your end.

Could you kindly provide the following details.

Kindly share the system details.
Please confirm if the product was purchased separately or if it came along with the system.
Please provide front and back pictures of the adapter, including details of the label markings.
Could you please let us know if any troubleshooting has been performed.

Your prompt response with this information will greatly assist us in diagnosing and resolving the issue as quickly as possible.

We look forward to hearing from you soon.

Best Regards,

Vishal Shet P

Intel Customer Support Technician

RobertWojtowicz · ‎08-14-2025

@vish1

The product was borrowed 2 units (one with GNSS module) from the distributor for testing purposes.

We are planning to purchase minimum 3 units.

At the moment, I have no way of checking this, as I am working remotely and the card is installed in the server.

After analyzing documentation 1.6 and 1.7, significant changes were made in terms of pin handling. From my observations, the native driver (RockyLinux 10, 6.12.0-55.25.1.el10_0.x86_64+rt) works as described in documentation 1.6 and I suspect that ts2phc is trying to communicate in old way.

Another problem, regardless of whether I use the native driver or ice 2.2.9 (firmware 4.80) according to documentation 1.6 and 1.7:

[root@E810-ptp-osc1 ~]# echo 1 0 0 0 100 > /sys/class/net/enp1s0f0np0/device/ptp/ptp0/period
-bash: echo: write error: Input/output error
[root@E810-ptp-osc1 ~]# echo 2 0 0 1 0 > /sys/class/net/enp1s0f0np0/device/ptp/ptp0/period
-bash: echo: write error: Input/output error
[root@E810-ptp-osc1 ~]# cat /sys/class/net/enp1s0f0np0/device/ptp/ptp0/period
cat: /sys/class/net/enp1s0f0np0/device/ptp/ptp0/period: Permission denied

For example, with the native driver and documentation 1.6, it accepts:

[root@E810-ptp-gmc ~]# echo 2 2 > /sys/class/net/enp1s0f0np0/device/ptp/ptp0/pins/SMA2
[root@E810-ptp-gmc ~]# cat /sys/class/net/enp1s0f0np0/device/ptp/ptp0/pins/SMA2
2 2

or driver ice 2.2.9 and documentation 1.7:

[root@E810-ptp-osc1 ~]# echo 2 > /sys/class/net/enp1s0f0np0/device/SMA2
[root@E810-ptp-osc1 ~]# cat /sys/class/net/enp1s0f0np0/device/SMA2
2

in dmesg:

[ 46.148174] ice 0000:01:00.0: SMA2 set to Tx. U.FL2 automatically enabled as Rx.

BR,

Robert

Akshaya1 · ‎08-15-2025

Hello RobertWojtowicz,

Thank you for your response.

To assist you further with your query, could you please share the SSU logs?

Please refer to the below link for your reference:

Help Guide for the Intel® System Support Utility

I look forward to your response.

Regards,

Akshaya

Intel Customer support Technician

RobertWojtowicz · ‎08-15-2025

Hi, @Akshaya1 @vish1

There is a slight lack of consistency in section 6.2.2 TimeReceiver Adapter. I understand what is meant in terms of pins.

Work onyly z Intel drivers (tested on 2.2.9):

1. Set output (transmission) to channel 1 in the SDP20 pin:
echo 2 1 > /sys/class/ptp/ptp0/pins/SDP22

2. Set channel 1 with frequency 10 MHz (for synchronizing 1PPS outputs):
echo 1 0 0 0 100 > /sys/class/net/enp1s0f0np0/device/ptp/ptp0/period

3. Set output (transmission) to channel 2 in the SDP22 pin:
echo 2 2 > /sys/class/ptp/ptp0/pins/SDP22

4. Set channel 2 with frequency 10 MHz (for synchronizing 1PPS outputs):
echo 2 0 0 0 100 > /sys/class/net/enp1s0f0np0/device/ptp/ptp0/period

There is still a problem with ts2phc, which confirms the issue with pin changes:

in ice-2.2.9 drivers:

[root@E810-ptp-osc1 ~]# cat /sys/class/ptp/ptp0/pins/
SDP20 SDP21 SDP22 SDP23

in native drivers:

[root@E810-ptp-gmc ~]# cat /sys/class/ptp/ptp0/pins/
GNSS SMA1 SMA2 U.FL1 U.FL2

BR,

Robert

Akshaya1 · ‎08-15-2025

Hello RobertWojtowicz,

Thank you for your response.

To understand and further analyze your query, kindly share the server model and the SSU log. Also, please confirm whether the adapter was purchased separately or preinstalled on the server.

Regards,

Akshaya

Intel Customer support Technician

RobertWojtowicz · ‎08-15-2025

Hi, @Akshaya1 @vish1

Again, confusion in the manual regarding 5.8 Example ts2phc Configuration File, I found the cause, ts2phc.pin_index 1 helped, I quote section 4.8: "When the DPLL is synchronized to the GNSS module or an external 1PPS source, the ts2phc tool can be used to synchronize the E810-XXVDA4T time to the 1PPS signal."

BR,

Robert

Dineshbabu · ‎08-15-2025

Hello RobertWojtowicz,

Thank you for your response. To assist you further, kindly share the server model and the SSU log. Also, please confirm whether the adapter was purchased separately or preinstalled on the server.

You can refer to the article below for instructions on collecting the SSU log:

https://www.intel.com/content/www/us/en/support/articles/000008563/ethernet-products.html

Regards,

Dinesh

Intel Customer support Technician

RobertWojtowicz · ‎08-17-2025

Hi @Dineshbabu

as I wrote earlier "The product was borrowed 2 units (one with GNSS module) from the distributor for testing purposes." - in my opinion, it is OEM

I am attaching the SSU log.

Hardware: HP DL380 Gen9 (P89)

This is a virtual machine (ordinary slave clock) with direct network card passthrough (full PCI Express 3.0 x16). Proxmox VE 9 virtualizer. In theory, everything works, but in reality, the commands does not change the DPLL status?:

echo 2 1 > /sys/class/ptp/ptp0/pins/SDP20

echo 2 2 > /sys/class/ptp/ptp0/pins/SDP22

echo 1 0 0 0 100 > /sys/class/ptp/ptp0/period

echo 2 0 0 0 100 > /sys/class/ptp/ptp0/period

I waited those few hours as instructed in the manual:

"As a side effect of having a very accurate DPLL, synchronization between the two E810-
XXVDA4T adapters can take up to several hours to change to a locked state."

Does it cause changes to DLLP (from ordinary slave clock)?

Found ZL80032 CGU
DPLL Config ver: 1.3.0.1
DPLL FW ver: 6201

CGU Input status:
| | priority | |
input (idx) | state | EEC (0) | PPS (1) | ESync fail |
----------------------------------------------------------------
CVL-SDP22 (0) | invalid | 8 | 8 | N/A |
CVL-SDP20 (1) | invalid | 255 | 3 | N/A |
C827_0-RCLKA (2) | invalid | 4 | 4 | N/A |
C827_0-RCLKB (3) | invalid | 5 | 5 | N/A |
SMA1 (4) | invalid | 1 | 1 | N/A |
SMA2/U.FL2 (5) | invalid | 2 | 2 | N/A |
GNSS-1PPS (6) | invalid | 0 | 0 | N/A |

EEC DPLL:
Current reference: CVL-SDP22
Status: freerun

PPS DPLL:
Current reference: CVL-SDP22
Status: freerun
Phase offset [ps]: 0

From Grand master clock its fine (other VM):

Found ZL80032 CGU
DPLL Config ver: 1.3.0.1
DPLL FW ver: 6201

CGU Input status:
| | priority | |
input (idx) | state | EEC (0) | PPS (1) | ESync fail |
----------------------------------------------------------------
CVL-SDP22 (0) | invalid | 8 | 8 | N/A |
CVL-SDP20 (1) | invalid | 255 | 3 | N/A |
C827_0-RCLKA (2) | invalid | 4 | 4 | N/A |
C827_0-RCLKB (3) | invalid | 5 | 5 | N/A |
SMA1 (4) | invalid | 1 | 1 | N/A |
SMA2/U.FL2 (5) | invalid | 2 | 2 | N/A |
GNSS-1PPS (6) | valid | 0 | 0 | N/A |

EEC DPLL:
Current reference: GNSS-1PPS
Status: locked_ho_acq

PPS DPLL:
Current reference: GNSS-1PPS
Status: locked_ho_acq
Phase offset [ps]: 717

BR,

Robert

Poojitha · ‎08-17-2025

Hi RobertWojtowicz,

Greetings for the day!

Thank you for sharing the details. Could you kindly provide front and back pictures of the adapter, including details of the label markings?

This information will help us review the complete details and assist you further.

We appreciate your understanding!

Best regards,

Poojitha N

Intel Customer Support Technician

RobertWojtowicz · ‎08-18-2025

Hi, @Poojitha

as I wrote earlier "At the moment, I have no way of checking this, as I am working remotely and the cards is installed in the server."

I have an archive photo of one card on the front, attached.

BR,

Robert

Simon-Intel · ‎08-18-2025

Hi RobertWojtowicz,

Thank you for your response.

Based on the pictures shared, we see that the part is an OEM (UBlox) component. As this is an OEM part, there may be custom BIOS and drivers provided by the OEM/manufacturer. Therefore, we kindly request you to use the drivers provided by the OEM and contact them for any further assistance, as they are best equipped to troubleshoot your issue with this product.

If you have any further questions or need assistance with other Intel products, please feel free to reach out.

Regards,

Simon

Intel Customer Support Technician

RobertWojtowicz · ‎08-18-2025

Hi, @Simon-Intel

The second card does not have a GNSS module (u-blox, originally added to first card) and I have a problem with it. I have attached an archive photo.

The first card is the grandmaster (with a GNSS module), the second card, which is the subject of the problem, receives PTP synchronization packets, and I have a problem with changing the DPLL status on it. See the new photo.

I am using the original firmware (latest 4.80) and Intel drivers (latest 2.2.9).

BR,

Robert

vish1 · ‎08-18-2025

Hello RobertWojtowicz,

Greetings!!

Thank you for sharing the pictures. We have carefully reviewed them, and based on the details, the part appears to be an OEM (UBlox) component.

As this is an OEM product, it may include custom BIOS and drivers provided by the manufacturer. Therefore, we kindly recommend using the drivers offered by the OEM and contacting their support team for further assistance, as they are best equipped to troubleshoot and resolve issues specific to this component.

If you have any further questions or need assistance with other Intel® products, please do not hesitate to reach out. We will be happy to support you.

Best Regards,

Vishal Shet P

Intel Customer Support Technician

RobertWojtowicz · ‎08-18-2025

Hi, @vish1

I wrote that the problem concerns the second card without a u-blox GNSS module, a clean, original card with official firmware and drivers from the distributor, borrowed for testing. I want to make/set changes in it according to the instructions.

I'm sorry, but it sounds like you don't want to help solve the problem. How can we decide to buy your products if there is no support in solving the problem?

BR,

Robert