Lenovo YUM Repository
Release and Change History








Bundle Release Information:
Targeted Server Family (Machine Type): Lenovo ThinkSystem SR655 (7Y00, 7Z01)
Targeted Operating System: SLES12SP4
YUM Repository Build Date: 2025_10_21

YUM Repository Release Version: SIAgile23-1

Device:
ThinkSystem Intel X710-T2L 10GBASE-T 2-port OCP Ethernet Adapter Part Number: 4XC7A08278
Feature Code: AUZW
PCIe Sub Vendor ID: 0x8086
PCIe Sub Device ID: 0x000F


Release History:

Release Change History Documents

Intel Networking Adapter/Device Utility



Release: 30.1 05/25/2025
============================
New OS Support:
  - Support RHEL 9.5
  - Support RHEL 9.6
  - Support RHEL 10.0

New adapters:
  - Intel E610-XT4 10GBASE-T 4-Port PCIe Ethernet Adapter
  - Intel E610-XT4 10GBASE-T 4-Port OCP  Ethernet Adapter
  - Intel E610-XT2 10GBASE-T 2-Port OCP  Ethernet Adapter
  - Intel E610-IT4 1GBASE-T  4-port OCP  Ethernet Adapter

E610
-------------
New features:
  - Basic driver support.
  - Tx Hang detection mechanism.
  - Thermal sensor events support.
  - FW logging support.
  - FW API Version Compatibility.
  - Debug Dump support.
  - Recovery and Rollback mechanisms.

Bug fixes:
  - IPS: 00913030 - The system hang at DXE INIT during POST when bios enabled E610.

    Description:
    After the bios image upgrade, the uefi bios took very long time to boot.
    The undi.initialize took about 2 hours, and the server finally entered the OS.

    Fix:
    The PF driver cann't able to get ownership after immediate reboot triggered by the BMC.
    Added clearing the ownership data (including timeout flags) to the PCI Reset flow.

  - IPS: 00944368 - During AC cycle stress, the first 2 ports of the E610 4-port OCP adapter can't link up.

    Description:
    The issue reported that port 0 and port 1 of the E610-XT4 OCP/E610-IT4 OCP could not link up
    after some AC power cycles.

    Fix:
    The root cause is LESM state machine ends up in unknown state and returns an error.
    If Link FW detects such an error for selected port then such port will be reset
    in the Link periodic task i.e. no more than 100ms later.

E810
-------------
New features:
  - Add ethtool reset support
  - Add ETF timestamp debug logging

Bug fixes:
  - IPS: 00860421 - [Oahu_AU_SIT_MQT2]Run MQT2 test ,XCC report E810-DA4 OCP link
    speed degraded from 16 GT/s to 8.0 GT/s.

    Description:
    XCC report E810-DA4 OCP link speed degraded from 16 GT/s to 8.0 GT/s after
    Run MQT2 test

    Fix:
    Replaced "CVL_PCIE_ANALOG"  v 2347.10A0.04D with
    "CVL_PCIE_ANALOG_ENG_2347_010A_04E" v 000.000.000 inside EML PCIe Analog Module

  - IPS: 00913030 - E810 Media Detection setting is not preserved during
    firmware updates

    Description:
    The Intel E810 Media Detection setting is not preserved during an Intel E810
    firmware upgrade. After each firmware upgrade the Media Detection setting
    is set to "Disabled".

    Fix:
    - MEDIA_DETECTION_MODE=1 means strict mode.
    - Removing OverrideEnable manipulation by switching LinkSpeedMethod to be
      OverridePhyTypes related

  - IPS: 00915231 - Intel E810 NIC port flaps during Windows boot up with ice 1.15.121.0 driver.

    Description:
    E810 adapter experienced a one-time link flap during OS boot.

    Fix:
    The Windows driver removes the enhancement so it tries to reset the link
    during the initialization and consequently causes the link flap once.

  - IPS: 00916160 - "Transmit Balancing" and "Virtualization Mode" options are missing from the UCM.

    Description:
    The EFI driver in CVL4.6 (EFI 4.2.97) didn't provide the
    "transmit balancing" and "virtualization mode" settings to the Lenovo UCM.

    Fix:
    Duplicate OpCodes had been removed from Transmit Balancing and Virtualization Mode.

  - IPS: 00961945 - There are many useless resource ID provide by E810 NIC firmware

    Description:
    There are many useless resource ID provide by E810 NIC firmware.
    Lenovo found NetworkDeviceFunctionMetrics and PortMetrics have two many useless resource ids.

    Fix:
    Use special API to get number of PFs defined by topology (number of PFs depends on number of MACs).


  - IPS: 00956338 - [PA_BHS_Andros_SDV_HW_SO]E810-DA2 OCP display multiple Function ID on xcc Inventory web.

    Description:
    When tested on SR630v4,the E810-XXVDA2 OCP with CVL4.8 NVM image lists multiple
    Function IDs on xcc Inventory web

    Fix:
    Using the API that returns the max number of possible ports in current product (based on Netlist).

FVL/SGVL
-------------
Bug fixes:

  - IPS: 00876990 - Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter
    failed to wake up in Windows server 2022.

    Description:
    In windows OS, BIOS enable WOL, when we set PME to Disable,
    the WOL function will not work anymore, even we turn it back to enable.

    Fix:
    Remove code check for PFPM_APM for a WoL supported port.

  - IPS: 00914122 - Some ports on the Intel x710-T4L PCIe negotiate to 100Mb
    on reboot from OS RHEL8.8.

    Description:
    X710-T4L PCI adapte sometimes linked up at 100Mb on RHEL 8.8
    when the link partner was Lenovo NE1032T switch.

    Fix:
    Restores old behaviour While continuing to ensure that D3hot is reached
    and WoL is disabled when NVM update requires a full shutdown.

  - IPS: 00936091 - Intel firmware update does not support inbox Linux driver For 700 series.

    Description:
    Intel firmware update does not support inbox Linux driver. Given this,
    the Intel firmware update tool needs to detect the inbox driver then
    fail gracefully with a message about the OOB driver requirement.

    Fix:
    Add SUPS script to require install OOT driver.

  - IPS: 00934339 - SR630 x722 4x10Gb SFP+ link down when 1 port connected to Cisco C93180YC-FX3.

    Description:
    When 1 port of the X722 4x10Gb SFP+ is connected to the Cisco switch, all LEDs on the x722 PHY
    card flash continuously. If we connect the X722 in pairs using 1&4 or 2&3 we do not see the failure.

    Fix:
    Adapt the original hotfix once made for FPK5.60 to FPK6.50 and force the OCP PnP Autodetection
    flow after NVM update.


Release: 29.3 07/25/2024
============================
New OS Support:
  - Support RHEL 8.10/9.4
  - Support SLES 15.6

E810
-------------
New features:
  - Disable Optical Module Laser when Link/Port is disabled

  - GET_LLDP type command : get all ports LLDP information

  - Disabling of port 0 (as long it’s not associated with PF 0).

  - Use Rx Loss to detect cable disconnect from Module

  - Expanding i2c write handling to enable 4 bytes


Bug fixes:
  - IPS: 00860421 - [Oahu_AU_SIT_MQT2]Run MQT2 test ,XCC report E810-DA4
    OCP link speed degraded from 16 GT/s to 8.0 GT/s.

    Description:
    XCC report E810-DA4 OCP link speed degraded from 16 GT/s to 8.0 GT/s when
    run MQT2 test. The issue occurred after 5 times of AC power cycle.

    Fix:
    The target PCIe PHY firmware has optimized on Receiver equalization
    recipe to handle low loss channel condition over PCIe training process.

  - IPS: 00815616 - [Kahauale_BBFV_HCT]E810-DA4 NIC port didn't disable
    after changed the "Active Physical" setting on uEFI menu.

    Description:
    Port 3 of the E810-xxvDA4 adapters was always enabled no matter
    whatever  "active physical functions" was set to. but the customer
    expects to have port 3 disabled  when "active physical functions" is
    set to "PF0,PF1 and PF2",  "PF0 and PF1" or "PF0 only"

    Fix:
    Change the setting of "Active Physical functions", and corresponding
    help display text

  - IPS: 00841566/00846731 - E810-DA4 adapter's device name doesn't display
    as expected

    Description:
    The DA4 adapter's device name under UEFI setup is different from the
    one in the UCM.

    Fix:
    The efi driver changes to display as the customer wants.

  - RAMON specific workaround implemented in DreadnoughtLake scripts in
    case of caui4 no FEC links, was modified being applied only when outer
    phy is RAMON (and not Parkvale).

  - The NetworkDeviceFunction.MTUSize property is changed to reflect the
    current OS defaults before the user configures specific value.

  - Fixed a rare timing issue of nc-si oem command: plug-out optics and
    plug-in again, BMC can NOT get temperature by reason code 0x5089.

  - Removed the need for EMPR after temperature fatal threshold is
    exceeded.

  - When link goes down, recovered clock switches to an incorrect
    frequency, and the external DPLL shifts the system timing.

  - FW incorrectly mapped NC-SI channels to Physical ports when responding
    to the Intel OEM NC-SI command 0x26 (no other command affected).

  - Unsupported SMBus write command caused HW to trigger improperly handled
    FW behavior, which blocked subsequent SMBus writes other than MCTP.

  - If user configured 1G and needs to go back to 10G, not able to do so.

  - Fixed PTP Time Error to be under 5 ns when running PTP in Boundary Mode
    between PF with PKVL PHY and PF w/o PKVL PHY.


FVL/SGVL
--------
Bug fixes:
  - PATCH request with request to change FlowControlConfiguration property
    returns success, but do not really apply changes.

  - LLDP receive property preserves the last received data, even when LLDP
    traffic doesn't contain the TLV item/data.

  - NetworkDeviceFunction schema Ethernet. The MACAddress property is not
    updated to the value in PATCH JSON. This is a regression. The issue is
    under investigation.

  - PATCH request with request to to change FlowControlConfiguration
    property returns success, but do not really apply changes. The issue is
    under investigation.

  - Fixed an issue where X710DA2 cannot get SFF temperature when another
    port is empty.


Release: 29.1 04/11/2024
============================
New OS Support:
  - Support RHEL8.9/9.3

E810
-------------
New features:
  - Get SFF Info NC-SI OEM Command

  - Disable FW LLDP agent in and allow LLDP frames to be sent and received
    in the VF.

  - Supports Log of MNG packets for debugging purposes.

  - Supports PLDM Type 4s for FRU data.

  - The E810-CQDA2T adapter now supports 2x2x25 Gbps configuration.

  - Supports reduced PTP jitter by improved timestamp accuracy and Port
    timer compensation.

  - E810-XXVDA4T and E810-CQDA2T now support DPLL updates.

  - Supports shorter DPLL lock time

  - Force FW LOG to uART even if PF Driver disables

  - Option to disable PLDM FRU backup data response when NVM FRU
    manufacturing data is not available


Bug fixes:
  - IPS: 00788617 - [PA_SI Agile 23-1_USI_SDV_Pass 1_HW_SE450] Qtester
    shows "VPD FW check failed (Error)

    Description:
    1. Power on system and boot into WS2022.
    2. Setup Qtester to run 72hrs AC cycle test.
       after AC power on, the BMC software calls PLDM_GetFirmwareParameters
       and it sometimes (may be once after 300 AC power cycles) returns
       Completion Code = 0x01(PLDM Base: Error).

    Fix:
    Firmware now returns PLDM_ERROR_NOT_READY Completion Code instead of
    generic 0x01(PLDM Base: Error) when firmware is not fully ready after
    platform reboot.

  - When plugging DAC cables into two ports at the same time on Clifton
    Channel, it is possible for one port to be unable to establish link.

  - To have the metrics data shown on the respective port, map the port to
    MAC address before accessing counter registers.

  - Resolved an issue where 0x5089 was returned for command
    get_sff_temperature when only port1 had optics of E810.

  - PLDM T2 NumericSensors didn't send async event when any threshold was crossed.

  - NCSI1.2 command Get Transceiver Temperature(0x4A) returned incorrect
    temperatures due to wrong endianness.

  - Module temp thresholds check running too early causes 0 return, which
    is taken as valid and shuts down port.

  - GetSensorReading command returns error code 0x1 in case when plug
    temperature is higher than 78C (0x4E).

  - E810 doesn't support non-contiguous TCs within the LLDP configuration.
    It may result in a hang situation if receiving such LLDP packets during
    power-on stage. A timeout was added to the firmware polling loop to
    trigger a core reset which clears the hang and allows the device to
    continue functioning.

  - E810 4.3 NVMs use a common map, which introduces a change (new entries)
    to an immediate TLV in PFA. FW fails to interpret the new entries in
    this specific TLV, which results in adding those new entries again and
    again upon every update from the former 4.3 image to 4.3 and above.
    Eventually, due to the lack of space in that TLV, any normal attempt to
    update will fail.

  - NetworkDeviceFunction.Ethernet.PermanentMACaddress should stay with
    factory setting if it has been programmed. Read relevant section from
    Factory Settings.

  - PLDM Type4 showing incorrect default Part Number

  - NIC disappeared after NVM signature corruption

  - Incorrect log entry format for timestamp value

  - Get Link Status command does not return External Device Power Class
    value

  - Previously, the PLDM Type 5 Command "Activate Firmware" could
    potentially cause a subsequent PLDM Type 2 event.

  - Resolved an issue where during an ActiveFirmware request coming from
    Update Agent (BMC) PLDM Type2, a PlatformEventMessage was generated by
    the Firmware Device (Network Adapter). As a result, the response did
    not happen, and Update Agent (BMC) treated it as Update Failed.

  - Fixed an issue where the UEFI HII interface could not save the setting
    of virtualization mode.

  - Previously, in PLDM Platform Monitoring and Control, the
    sensor_data_size field of SFP thermal sensor PDR was containing wrong
    value: unsigned instead of signed char/byte.

  - Previously, during ActiveFirmware request coming from Update Agent
    (BMC) PLDM Type2 PlatformEventMessage was generated by our Firmware
    Device (Network Adapter). As a result, response did not happen and
    Update Agent (BMC) treated it as Update Failed.

  - Firmware now acquires semaphore before "Load Factory Settings to PFA"
    and releases it immediately after.

  - Previously, when BMC subscribed to PLDM events, the NIC issued two
    equivalent redfish events for the different origins (Network Adapter
    and Port) caused by the same trigger (link state change for given
    port). This issue caused unnecessary redfish event flood. The
    resolution was to change firmware design in order to avoid sending
    multiple redfish events for the same trigger.

  - Previously, in Network Controller Sideband Interface after
    EnableChannel command invoked, the OEM command IANA=0x02A2 GetLldp
    occasionally returned LLDP TLVs with missing mandatory values for
    chassis_id and port_id.

  - Set packageID SDP to correct values for E810-CQDA1.

  - Now the patched property of NetworkDeviceFunction.Ethernet.MACAddress
    is persistent during reboot. Users can restore to PermanentMACAddress
    with ResetSettingsToDefaults.


FVL/SGVL
--------
New features:
  - Enable E700 X722 Tx signal to "always on".

  - Enable E700 to store events details on the NVM in Recovery Mode.When
    entering the Recovery Mode, X710 will store the details of the event in
    the NVM.

Bug fixes:
  - Resolved an issue where POST to the
    NetworkAdapter.ResetSettingsToDefault looked successful from postman,
    but after reboot the adapter's Port 1 LLDP setting did not reset to
    default.

  - Previously, there were cases of Fortville disappearing from the PCIe
    bus during reboot stress testing reported on Icelake-based platforms.
    These platforms performed a PCIe Hot Reset before asserting PERST# as
    part of the warm reboot cycle. PERST# is asserted at approximately the
    end of the Hot Reset, but due mostly to the Fortville LCB
    implementation, there was a variation in the relative timing of about
    65 us, so many edge cases could occur.

  - Previously, after configuring "ifconfig ethX down" command on Marvell
    devices series 88E1512/88E1514, the peer side (loopback configuration)
    was still reporting link up.

  - Fixed an issue. Unexpected EMP Reset occurred in a rarely BMC request
    combination in a very low probability, which may cause: 'tx_timeout' or
    'ARQ: Unknown event 0x0000 ignored' or 'bond down' if bonding is
    configured.

  - IPS: 00879846 - Intel XXV710-DA2 PCIe 25Gb 2-Port SFP28 Adapter link
    speed and status incorrect

    Description:
    Link event is reported only once at when the machine is powered on,
    after that no link event will be generated any more even after the
    network cable is inserted and removed, this is incorrect, link event
    should be reported when we plugin or remove the AOC cable.

    Fix:
    Firmware reported link speed value based on advertised capability value
    using DNL declaration, changes to read link speed from MAC

  - IPS: 00852370 - IEPD Hot Issue: SR645v3 X710 T2L PCIe bandwidth degraded

    Description:
    X710 PCIe may enter x1 on the AMD Genoa platform in reboot and AC
    process.
    Customer updated system firmware XCC: KAX318V >> KAX322V UEFI: KAE112O
    >> KAE116K Following event occurs intermittently, but high fail rate
    PCIe Link Width has degraded from x8 to x1 in physical slot number 3.
    Slot 3 is Intel X710-T2L 10GBASE-T 2-Port PCIe Ethernet Adapter,
    customer had tried new NIC FW, replace NIC but no help. this system no
    re-timer.

    Fix:
    The firmware changes to enter the PCIE detection phase when PERST
    becomes de-asserted


Release: 28.2 08/01/2023
========================
New OS Support:
  - Support RHEL8.8/9.2, SLES 15.5

E810
-------------
New features:
  - Support NC-SI 1.2 thermal monitoring commands.

Bug fixes:
  - IPS: 00833367 - E810-DA2 10/25GbE SFP28 2-Port OCP Ethernet Adapter cannot
    enable SRIOV in UEFI

    Description:
    SRIOV can not be enabled in UEFI

    Fix:
    Added logic to support on for all PFs

  - Resolved an issue were an incorrectly interpreted BDF during MCTP
    Endpoint discovery led to sending PLDM events to a non-existing device.

  - Resolved an issue where the id field of Event BEJ was changed from the
    originating resource Id as the resource number to a deferred binding
    resource Id.

  - A "Cannot initialize port" failure occurs when running nvmupdate
    1.39.32.6 in SLES15SP3, because the tool doesn't support ioctl.

  - A SyncE-related transaction between driver and device may cause a PHY
    loading failure, during NVM upgrade. Subsequently, PHY errors are
    reported to UEFI driver during reboot, resulting in a BIOS hang.

  - Resolved an issue where E810-XXV-4T didn't expose one of the On Chip
    thermal sensors via PLDM. The sensor was not visible via BMC.

  - Resolved an issue where CVL4.1 and CVL4.2 had a problem with Recovery
    Clock configuration on port 4, in the case of fully reversed PF<>MAC
    mapping. Other configurations were not impacted.

  - Resolved an issue where the NC-SI "Reset Channel" (0x05) command was
    not reverting the port link state change made by for Real Time
    Comprehensive Embedded Management "Network Port Control' (0x34)
    command.

  - Resolved an issue where, during communication via PLDM Type 6, FW did
    not move the operation to the failed state and did not return
    INVALID_DATA. Instead, it returned UNSUPPORTED in the case of an
    invalid payload.

  - Reverted an incorrectly added strict handling of the payload-less action.

  - Resolved an issue where the Network Device and Port Metrics are
    disabled due to an BMC issue and missing support on BMC side.

  - Resolved an issue where in order to change the Forward Error Correction
    setting in the UEFI HII the user needs to change the Media detection
    setting, save the changes, and then change the FEC setting.

  - Previously, promiscuous mode did not see all packets; it only saw those
    packets arriving over the wire (that is, not sent from the same
    physical function (PF) but a different virtual function (VF).

  - Resolved an issue where during the second time of a POST operation,
    NetworkAdapter.ResetSettingsToDefault failed with the BMC reporting
    "Internal Server Error."

  - Resolved an issue when both RMII-based transport (RBT) and Management
    Component Transport Protocol (MCTP) were enabled, and PT was enabled on
    RBT, then OEM command 0x26 (config LLDP) was being rejected from NC-SI
    over MCTP with reason code 0x5081.

  - Corrected an issue where updating an NVM image of E810 could result in
    a "PHY NVM is not supported in devlink" warning message.

  - Previously, E8102CQDA2 adapter showed Linkcap width as x16.


FVL/SGVL
--------
New features:
  - Get Link Status AQC response when SFP module is not initialized.

    Description:
    If the Get Link Status AQC is sent when the SFP module is not
    initialized yet, the link can be lost.

    When the SFP module is not initialized yet, FW will try again in a
    reasonable timeout.

Bug fixes:
  - IPS: 00819239 - [Kahauale_BBFV_HCT]X710-T4L NIC adapter can't saved the
    "Active Physical Functions" option on uEFI menu.
    IPS: 00831264/00844425 - XXV710-DA2 PCIe Adapter NIC port didn't
    disable after changed the "Active physical functions"

    Description:
    Intel XXV710-DA2 PCIe 25Gb 2-Port SFP28 Adapter NIC port didn't disable
    after changed the "Active Physical" setting on uEFI menu.

    Fix:
    Reset the length of the PCIe Alt Autoload section during image
    downgrade to a version earlier than FVL9.2

  - IPS: 00840914 - [PA_IO Agile-Sprint202310_BDC_Storage_flex]SRIOV
    enable/disable both can do SRIOV features

    Description:
    OS can still create SRIOV VFs when the adapter HII already disables SRIOV
    in the BIOS

    IPS: 00841528 - [PA_IO Agile-Sprint202310_BDC_Storage_SD530] Intel X722
    LOM test SR-IOV function cannot enable VF under ESXi8.0u2 OS

    Description:
    Open to enter ESXi Host Client-Manage-Hardware-PCI Devices-Select Port
    "Intel X722 10GB SFP+" Configure SR-IOV 2.UEFI has set SR-IOV function
    3.ESXi8.0u2 Unable to enable VF redhat 9.2 can work well.

    Fix:
    Correctly set SR-IOV Control Capable bit for Lenovo images,

  - IPS: 00839473 - [PA_IO Agile-Sprint202209_BDC_oceancat_Sprint202310]X722
    lom WOL fail in SD650.

    Description:
    WOL function UEIF page show gray, OS can not enable WOL function

    Fix:
    Enable force link down requests and map channel number in a descending
    order. Enable AltRAM implementation then reset corrupted memory block and
    recalculate MSI_X VF vectors.

  - IPS: 00831248 - XXV710 VPD info question

    Description:
    lspci -s BUS:Device.Function -vvv command to check VPD info, but it
    can't show out the VPD info

    Fix:
    Enable VPD bit in NVM image

  - IPS: 00769725 - [Hakuba] Abnormal cable plug (unplug) event on port 2
    and 3 with Intel X710-T4L

    Description:
    Port2 and port3 of X710-T4L PCIE cannot display event in audit log and
    link status/speed in inventory when plug/unplug the cable.

    Fix:
    There are missing MCTP link status changes as mixed PF no. with port
    no. in the MCTP Link Status change handler, and overflowing PLDM queue
    with RDE events that were classified as Big Event.

    Map Port No. to the corresponding PF and continue, add additional
    condition to disable unplanned eventReceiver physical address change.
    Disable RDE events in the presence of asynchronous MCTP implementation
    without polling for Big Events

    Note: it may still occur in loopback mode.

  - IPS: 00725539 - Link down on x722 4x10Gb SFP+ PHY card with 27.3 code
    level (800039xx)

    Description:
    After upgrading the FW, all ports are down.

    Fix:
    Force OCP PnP Autodetection flow after NVM update.

  - Resolved an issue where a rare PCI speed degradation with Gen3 to Gen2
    was seen during extensive link tests after a reset is caused by a core
    reset on an ICX-D platform.

  - Resolved an issue where during a write, with http PATCH method
    triggered, the LLDP Disable Valid bit was ignored, which resulted in a
    skip of write in all scenarios instead of just for the same LLLDP
    Enabled value.

  - Resolved an issue where if BMC bonding was disabled, NCSI mode was set
    to a Manual Switch Mode (depending on the platform), and BMC share port
    has changed before doing a power cycle, recovery mode would occur.
    Other prerequisites include disabled WOL, disabled LLDP, enabled PXE no
    drop, and disabled auto power-on after power loss (in BIOS).

  - Fixed an issue where the processing port id was always the same as the
    mac address

  - Previously, the addition of PCIe re-timers added to the total channel
    latency causing replay timer timeout correctable errors.

  - Resolved an issue where PLDM type MCTP packets were not accepted due to
    missing configuration for PCIe VDM


I350/340/210
------------
New features:
  - IPS: 00699338 - Name of I350 interlock in XCC is inconsistent with V1

    Description:
    Card Name field shall be taken from V1 VPD field instead of "large
    resource string". This change applies to 1G Lenovo devices with enabled
    AIM support and existing V1 VPD field.





Lenovo Data Center Group Linux OS Support Home Page
linux.lenovo.com

© 2018-2025 Lenovo. All rights reserved