Lenovo Driver Free Download

[Adah Orhenkowski]

Ithought that there was a new version after the ones released on December 13 but I could be wrong. Anyway, you can check the adrenaline software to see what version you have. The device manager should tell you as well.

Under the driver update of the Legion space, I see 50916731 available to be updated, and the current one is 11012, so at least Legion space is reporting the old driver. I haven't been able to figure out how to confirm whether the chipset is updated or not. Could be really not updated, or not being reported coprrectly

Oh I see what you're saying if I'm thinking correctly. If you go into the adrenaline software I believe there is something under settings or preferences I forget which tab but there's a drop-down box that shows all of the informatin for the driver

Lenovo ThinkSystem servers include a rich portfolio of firmware and driver update tools. Most of these tools include an easy-to-use graphical user interface to perform updates interactively, as well as utilities that provide methods to acquire and apply updates in complex scenarios.

This guide introduces the tools provided with Lenovo ThinkSystem servers and is especially useful if you are managing a few servers interactively and have no operational constraints, such as Internet access.

The reader should have basic skills such as booting the server from a specific device, setting up the management controller for remote control access, running a graphical program as a privileged user in Windows or Linux, and running a command line utility with parameters.

Advanced procedures: The instruction provided here is generally applicable to ThinkSystem V1, V2 and V3 servers. However, for new firmware update capabilities offered by ThinkSystem V3 family, please refer to the Advanced Guide for additional instruction.

Firmware is essential to the operation of a server. It controls every single hardware component found in the server; from the onboard chipset, to the built-in modules, to the add-on adapters and drives, and all the way to the entire system, including the self-contained management controller.

Lenovo has the richest portfolio of firmware and drivers update tools in the industry. These tools provide easy-to-use graphical utilities to perform updates interactively. They also provide a complete set of utilities to meet more complex scenarios to acquire and apply updates. The utilities support:

This guide provides introductory instruction for users who are new to Lenovo ThinkSystem products. If you are managing a few servers interactively and have no operational constraints, such as Internet access, this is the place to start. This guide will present three simple interactive tools, which are part of the XClarity Essentials toolset:

A subsequent guide will provide advanced level instruction to users managing a complex mix of servers and operating systems. The advanced guide will describe how to update firmware in a distributed environment while minimizing downtime to your workload.

Tip: While this guide is focused on Lenovo ThinkSystem servers, the provided recommendations and instructions apply to Lenovo System x M5 or X6 generation servers with very minor variations.

Lenovo recommends that you update the entire system to the latest UpdateXpress System Pack (UXSP) level before you deploy the server into a production environment. This includes system firmware, all adapter and hard-drive firmware, and the corresponding device drivers in the operating system.

Tip: Install all the hardware components (modules, adapters, and drives) and power on the system at least once before updating the entire system, so that everything will be activated, detected, and updated together.

If new system management controller firmware (IMM or XCC) is applied, either a system management controller restart (via the XCC/IMM web interface or CLI) or a full power cycle (unplug the server) will be required to activate the pending updates. A virtual reseat will also restart the controller (if the function is available in your server).

If new UEFI firmware is applied, a server reboot is required to activate the updates. If delayed activation is being used, such as in XClarity Administrator, then the updates will remain as pending (unapplied) on the system until server is restarted.

If the system management controller firmware update package also includes updated FPGA firmware (as indicated in the change history for the update), then both the system management controller will need to be restarted (via XCC/IMM web interface/CLI) and the server will need to be rebooted before the FPGA change becomes effective. A full power cycle (unplug the server) will achieve both.

If you install or upgrade hardware components later, make sure that you perform a full system update to ensure that the system can handle the new hardware, and that the newly installed components have the proper firmware and drivers.

Updating firmware manually: If you are updating individual firmware manually or via your own script but are not using the XClarity tools mentioned above, you should always update the BMC (XCC or IMM) first, restart the BMC and wait 5 minutes, then update UEFI, reboot the server, then update the rest of the system. This order ensures that critical dependencies are satisfied.

Make sure that you visit the Lenovo Support web site regularly, or that you subscribe to product notifications to be informed of critical updates for your devices. Then, plan your maintenance schedule accordingly.

Every Lenovo server that is shipped to a customer contains a set of firmware that has been comprehensively tested together to provide optimal performance. Due to a variety of factors, firmware for one or more components may need to be updated. Firmware updates to individual components may be planned or unplanned, e.g. a fix to a problem not identified previously. To ensure continued optimal performance, the firmware updates are integrated and thoroughly re-tested together. The updated firmware and drivers are available on the Lenovo Support web site.

While it is safe to receive a new server, install a certified operating system, and put the server into production, Lenovo recommends that you update the server to the latest firmware and driver pack before putting the server into production.

Lenovo actively works with the major software partners to certify our servers for their software, and vice-versa. We also provide our device drivers to be included in their official software release, such as Windows Server, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and VMware ESXi. However, device drivers that are shipped in the official OS release might be out of date or might not support the complete set of features and functions advertised by Lenovo. Therefore, the drivers need to be refreshed at the same time as the firmware.

UpdateXpress System Pack (UXSP) is a bundle of firmware and device drivers that are validated together as a whole for compatibility and stability across all of the supported system models, and that are released on a predefined schedule (typically, 3 times a year).

The UXSP contains additional metadata for the Lenovo tools to optimize sequencing and minimize reboots while applying the updates. Unless explicitly mentioned, this guide always recommends that you use the UXSP for updates, not the individual packages.

Other tools can be used to update firmware, but they are not in the scope of this guide. For example, users can always update device drivers through the operating system. Windows Server and VMware have their own way to update drivers individually and on a large scale.

This tool runs on your Windows computer or Linux-based workstations, to acquire the UXSP online based on your selected system model(s). It creates an image that includes a bootable operating system, the update tool, and all the firmware files applicable to the selected system model(s). It can write the image directly to a DVD or USB drive that you can carry to the target server and boot.

Alternatively, if you are working remotely from the target server, the ISO image that it creates can be remotely mounted to the management controller as a virtual DVD, if the function is available on your server. Then you can boot the server from the mount and apply the updates.

Remote mounting of ISO images: Use of remote ISO files on ThinkSystem servers requires XClarity Controller Advanced, which may be an optional upgrade for your server, depending on your server model and configuration.

Upon confirmation or timeout, the tool automatically applies the updates and reboots the system. The update process runs unattended. However, you can also intervene manually after the comparison result is displayed, if you want to.

If the server to be updated has the same or newer firmware than what is in the image, the update process automatically skips those items, unless you intervene and select an item manually. Likewise, If you boot the image on a server model that is different from the server for which the image was create, the tool skips the update process and indicates that there is nothing to update.

If you just bought a batch of servers of the same or various models, you can create one image for all of them and use it among those servers. You can also burn the image onto several DVDs or several USB keys to update them all at the same time. If you have similar servers across a number of remote branch offices, you can also send the image to the remote branch office. You can get someone in the remote branch office to burn a DVD, and then boot the server to update it locally.

BoMC doesn't update drivers: The image created by BoMC does not update the device drivers for the operating system. You will need use the methods provided by the operating system to update the device drivers, as needed.

This is the easiest tool for updating the entire system if your environment has no constraint on Internet access or running the management tool. This tool does not need to be installed, nor does it create any permanent daemon or background service at runtime. Therefore, you can run it from a temporary folder then delete it at the end.

3a8082e126