This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DP83869HM: Fails to link reliably with Intel NICs with disabled next page support (e.g., Dell 3660, Getac S410G2, Getac S410G3, Getac G4100G4) on Windows

Part Number: DP83869HM
Other Parts Discussed in Thread: DP83869

A customer reported problems with our copper to fiber media converter. It links reliably with devices that have next page support enabled but not with devices with this support disabled:

We have a dell 3660 PC with same issue with intel nic. Also we have a Panasonic tough book with dual nics (one intel nic, one broadcom).

It appears all the issues are with Intel network driver. (Dell 3660, Getac S410G2, Getac S410G3, Getac G4100G4). On the Toughbook,
when using the intel NIC, it doen't work, move the cable to the Broadcom nic on the same laptop, works fine. Tried few other dongles and dell docking stations, all using Realtek USB driver or AXIS and those work 100% so far. One thing we've just come across, if we reboot the system with the OM1G plugged in, we get E-link; unplug the copper/etc and plug
it back into OM1G.. E-Link. If we power cycle the OM1G, and plug it in, no E-Link. Need to reboot laptop. Running latest intel drivers.

If laptop is powered up already and it's plugged into the OMG1G, it won't get link until you reboot the device. If you
unplug the ethernet cable and back in, the e-link will come right back up. But if the OM1G is powered off, then the laptop
needs to be rebooted.

Here is register dump when unit is connected to laptop that fails to link:



As can be seen, bit 3 in register 6 (ANERR) is zero. We suspect this is the cause of auto-negotiation problems.

Here is configuration and status output.



Is there a way to work around this issue?

A similar issue was reported here:
support.xilinx.com/.../ti-dp83867-autonegotiation-problem

Regards,
Dave
  • Note: In the register dump, LP_NP_ABLE=0 in ANER and AUTONEG_ERR=1 in INTERRUPT_STATUS.

    There is some issue with the DP83869HM or its configuration as other devices link with the Intel NICs in these devices.

  • Hi Dave,

    What speed is expected to be established? I see from the register dump that the DP83869 is only advertising 1000Base-T full duplex support, but the link partner does not support 1000Base-T (register 0xA) and is only advertising 10Base-T support. 

    Can you share the Intel driver you are using? Please see this page for the latest DP83869 Linux driver.

    Thanks,

    David

  • We obtained a Getac s410g2 for testing.  It has a Intel I219-LM adapter. I will try to get the specific driver version.  This laptop does not link reliably with the DP83869 in our OM1G media converter.

    You are correct the DP83869 is only advertising 1000Base-T full duplex support.  It is configured as a 1000BASE-T to 1000BASE-X media converter.  The DP83869 in the OM1G is configured initially by strap options, and then by an embedded micro in the unit based on switch and console configuration.

    The laptop is configured for 1 Gbps Full Duplex.  Same problem occurs when it is configured to Auto Negotiation mode.  If one switches between these two modes, the units will link. But if the OM1G is powered on after the laptop is up, the laptop invariably starts advertising only 10BASE-T or 10/100BASE-T and the units don't link. The next page bit for gigabit is always 0.

    We built a cable breakout to look at the fast link pulses (FLP) from units.  We see the laptop get stuck only sending 1000011000000000 FLPs.

    I have personally tested an Intel I219-V adapter with the OM1G and don't see the link problem with it.

  • Getac driver version is Intel 12.18.9.7.

  • Updating driver to 12.19.2.55 didn't help.  This latest Intel driver for the I219-LM.

  • Hi Dave,

    It sounds like the issue is on the laptop side, and the laptop is somehow being configured to only advertise 10mbps. Do you know what PHY is inside the laptop? If it is another DP83869, can you share the register dump from the laptop? The previous register dump you shared was from the DP83869 inside the OM1G, correct?

    Can you share the actual intel driver file itself?

    Thanks,

    David 

  • Driver for I219-LM can be obtained here:

    https://www.intel.com/content/www/us/en/products/sku/82185/intel-ethernet-connection-i219lm/downloads.html

    We tried Intel Complete Driver Pack dated 8/25/2023.

    The laptop's PHY is contained in the Intel I219-LM part.

    I think the Intel I219-LM must be getting stuck in link fail mode and FLPs from the DP83869HM aren't causing it to resume normal auto-negotiation. I don't believe it's a configuration issue. Multiple laptops with this part have been tested and they all have same behavior.  Possibly, both devices get stuck in link fail mode.

    See section 9.4.10.6 in DP83869 datasheet for info on restarting auto-negotiation in DP83869HM.

    The laptop will link with DP83869HM in OM1G when rebooted; or when Speed & Duplex configuration is changed between Auto Negotiation and 1 Gbps Full Duplex.

    The units generally re-link on short cable breaks; but they fail to link on breaks longer than 5 or 6 seconds.

    When the two units are not linked, the laptop immediately links at 1 Gbps when the OM1G is replaced with a device with a different PHY (e.g., Marvell). It links with all other devices that we have tried.

  • If we reboot the PC with the OM1G plugged in and powered, we get E link; unplug the copper and plug it back into OM1G within 4 seconds.. E-Link.  If unplugged longer than 5 seconds, no E-Link when re-connected. If we power cycle the OM1G, and plug it in, no E-Link. Need to reboot laptop.
    
  • I believe the issue is likely a problem with the Intel I219-LM adapter.

    I worked around the link issue with the Intel I219-LM adapter by advertising 10BASE-T full
    and half duplex support in our 1000BASE-T Media Converter mode. It is possible this
    might result in an incorrect link speed (10BASE-T) but the converter won't work
    at this speed because the copper and fiber speeds must be the same.

  • Hi John,

    Yes, if you advertise 10Base-T on the DP83869 while the laptop is advertising the same, they will link in 10Mbps.

    The problem is that your laptop is not advertising 1000Mbps Full Duplex Operation. Please configure the laptop to advertise 1000mbps full duplex operation, and then restart the autonegotiation process by writing register 0x1F = 0x4000 on the DP83869. Then, check that bit[11] of register 0xA is set, and that the 1000mbps link is up in register 0x11.

    Thanks,

    David

  • No, you misunderstand.  The laptop is configured to 1 Gbps full duplex (1000 Mbps full duplex).  It does not link reliably with the DP83869 when it only advertises 1 Gbps full duplex.  When I changed  the DP83869 to also advertise 10BASE-T full and half duplex, the laptop links with the DP83869 at 1000BASE-T full duplex (1 Gbps full duplex), not 10BASE-T (10 Mbps), every time.

    This fixes the failure to link when the DP83869 is powered up after the laptop.  It also fixes the failure to link after disconnecting and reconnecting the cable.

    The software controlling the DP83869 always restarts auto-negotiation at the end of the configuration sequence.

  • Hi John,

    That is interesting, I cannot think why the addition of advertising 10Mbps on the DP83869 would allow the link to be created in 1000Mbps. In the register dump you shared, the laptop was not advertising 1000Mbps. Can you share another register dump after this fix?

    Thanks,

    David 

  • Hi David,

    Here is a register dump with the fix:

    0x000: 0x1140 0x7969 0x2000 0xa0f1 0x0c61 0xcde1 0x006f 0x2001

    0x008: 0x4006 0x0200 0x3800 ...... ...... 0x401f 0x1ff4 0xf000

    0x010: 0x5048 0xaf02 0x0000 0x1dc0 0x2dc7 0x0000 0x0000 0x0040

    0x018: 0x615b 0x4574 0x0002 ...... ...... ...... 0x0012 0x0000

    0x020: ...... ...... ...... ...... ...... 0x0480 ...... ......

    0x028: ...... ...... ...... ...... 0x141f 0x2000 0x0221 ......

    0x030: 0x0000 0x10b0 0x0050 0x0000 ...... ...... ...... 0x0003

    0x038: ...... 0x0000 0x0000 ...... ...... ...... ...... ......

    0x040: ...... ...... ...... 0x07a0 ...... ...... ...... ......

    0x048: ...... ...... ...... ...... ...... ...... ...... 0x0126

    0x068: ...... ...... ...... ...... ...... ...... 0x081c ......

    0x080: ...... ...... ...... ...... ...... ...... 0x0077 ......

    0x0d0: ...... ...... ...... ...... 0x1200 ...... ...... ......

    0x130: ...... ...... ...... ...... 0x1000 0x0000 ...... ......

    0x170: 0x0c12 ...... ...... ...... ...... ...... ...... ......

    0x180: 0x0752 0xc850 0x5326 0xa01e 0xe976 0x19cf ...... ......

    0x188: ...... ...... ...... ...... ...... ...... ...... ......

    0x190: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

    0x198: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

    0x1a0: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 ......

    0x1d8: ...... ...... ...... ...... ...... ...... ...... 0x0044

    0x1e0: 0x417a ...... ...... ...... ...... ...... ...... ......

    0x1e8: ...... ...... ...... ...... 0x1ff4 ...... ...... ......

    0xc00: 0x1140 0x616d 0x2000 0xa0f1 0x01a0 0x4060 0x0007 0x2001

    0xc08: 0x0000 ...... ...... ...... ...... ...... ...... ......

    0xc10: ...... ...... ...... ...... ...... ...... ...... ......

    0xc18: 0x01ff 0x0031 ...... ...... ...... ...... ...... ......

    There are reports of similar problems on the Internet with the I219-LM.  For example,
    forums.freebsd.org/.../

    Many of our customers use fiber to the desktop for security.  Thus, the need for media converters and the limitations they impose on data rates.  Your original comment that the link partner was only advertising 10BASE-T made me suspect that it was necessary to advertise 10BASE-T in the DP83869.  We also saw in the FLPs that the base page being transmitted by the laptop only advertised 10BASE-T support when the DP83869 was powered down.

    It's a puzzle why this change results in the devices linking at 1000Mbps.

  • For completeness, I've added a screen shot of FLPs captured from Getac laptop when link is down.