Support

Download LSI 2308_P16.zip from https://download.asrock.com/TSD/LSI 2308_P16.zip

1. Unzip “LSI 2308 FW update” to bootable USB Drive.
   You can follow below link to build a bootable USB drive. http://rufus.akeo.ie/
2. Boot to DOS environment.
3. Execute readaddr.bat (save sas address and create info.txt)
   example:
   
4. Execute start.bat to update LSI2308 FW.
5. Restart and press Ctrl+C into LSI RAID ROM.
   You can check the FW revision, SAS address and compare with info.txt(stpe1)
   
   
6. If SAS address have been changed please type command (in DOS)“sas2flsh.exe -o -sasadd XXXXXXXXXXXXXXXX” Your SAS address
7. Restart and check SAS address
8. Finish

There are 2 methods for updating the BIOS using Instant Flash.

Method 1:

1. Save the BIOS files on a device such as USB disk (FAT32 format), hard disk (FAT32 format) and floppy drive.
2. Press [F2] during POST to get into BIOS setup menu.
3. Select the Instant flash under [Advanced] menu to execute it.
   
   
4. ASRock Instant Flash will automatically detect all devices and only list those BIOS versions which are suitable for your motherboard, and select the suitable BIOS version and flash.
   
   
5. Please DO NOT power off during BIOS update.
   
   
6. After update success, it will pop up below massage. Please press Enter to reboot system.
   
   
7. After system restart, press [F2] or [Del] to enter the BIOS setup utility during boot up to check BIOS version.
   
   
8. In Exit menu, please select "Load Default Settings" and press [Enter] to continue.
9. Select "Exit Saving Changes" and press [Enter] to exit the BIOS setup utility.

Method 2:

1. Save the BIOS files on a device such as USB disk (FAT32 format), hard disk (FAT32 format) and floppy drive.
2. Press [F6] when you see this (or similar) page.
   
   
3. Select the suitable BIOS version and flash.
   
   
4. Please DO NOT power off during BIOS update.
   
   
5. After update success, it will pop up below massage. Please press Enter to reboot system.
   
   
6. After system restart, press [F2] or [Del] to enter the BIOS setup utility during boot up to check BIOS version.
   
   
7. In Exit menu, please select "Load Default Settings" and press [Enter] to continue.
8. Select "Exit Saving Changes" and press [Enter] to exit the BIOS setup utility.
9. Now, system is booting up with new BIOS.

If you encounter problems while updating the new BIOS, DO NOT turn off your system since this corrupt BIOS might cause your system failed to boot up. Just repeat the process, and if the problem still persists, update the original BIOS file. If the Flash Memory Writer utility was not able to successfully update a complete BIOS file, your system may not be able to boot up. If this happens, your system will need service.

BIOSfilename.EXE: The Flash Memory Writer utility is included in the WinZip format of BIOS file. It updates the BIOS by uploading a new BIOS file to the programmable flash ROM chip on the motherboard.

1. Create a bootable system USB pen drive.
2. Download an updated ASRockRack BIOS file (WinZip format with .zip file extension) from the web site, unzip the BIOS file and save all files to the drive you created in step 1.
3. Boot from the disk you created in step 2.
4. At the "C:\" prompt, type BIOSfile.exe, then press [Enter]. For example: C:\2D16C4~1.exe
   
   
5. When see below massage, please press any key to continue.
   
   
6. System will auto restart, and update BIOS. Please DO NOT power off during BIOS update.
   
   
7. After update success, it will pop up below massage. Please press Enter to reboot system.
   
   
8. After system restart, press [F2] or [Del] to enter the BIOS setup utility during boot up to check BIOS version.
   
   
9. In Exit menu, please select "Load Default Settings" and press [Enter] to continue.
10. Select "Exit Saving Changes" and press ]Enter] to exit the BIOS setup utility.
11. Now, system is booting up with new BIOS.

If you encounter problems while updating the new BIOS, DO NOT turn off your system since this corrupt BIOS might cause your system failed to boot up. Just repeat the process, and if the problem still persists, update the original BIOS file. If the Flash Memory Writer utility was not able to successfully update a complete BIOS file, your system may not be able to boot up. If this happens, your system will need service.

This utility works in Microsoft® Windows 7 (32 / 64 bit), Windows 8 (32 / 64 bit), Windows 8.1 (32 / 64 bit), Server 2008 R2 SP1 (64 bit), Server 2012 (64 bit),Server 2012 R2 (64 bit).

1. Download the BIOS package (WinZip format with .zip file extension). And close all programs.
2. Unzip and save all files to the same directory of any storage location accessible by the host system.
3. Click BIOSfilename.exe
   
   
4. It shows a dialog icon to remind you need to restart the system before updating BIOS. Click "Yes".
   
   
5. System will auto restart, and update BIOS. Please DO NOT power off during BIOS update.
   
   
6. After update success, it will pop up below massage. Please press Enter to reboot system.
   
   
7. After system restart, press [F2] or [Del] to enter the BIOS setup utility during boot up to check BIOS version.
   
   
8. In Exit menu, please select "Load Default Settings" and press [Enter] to continue.
9. Select "Exit Saving Changes" and press [Enter] to exit the BIOS setup utility.
10. Now, system is booting up with new BIOS.

If you encounter problems while updating the new BIOS, DO NOT turn off your system since this corrupt BIOS might cause your system failed to boot up. Just repeat the process, and if the problem still persists, update the original BIOS file. If the Flash Memory Writer utility was not able to successfully update a complete BIOS file, your system may not be able to boot up. If this happens, your system will need service

Marvell provides a new FW improve Marvell 9230 HDD stability, please follow below procedure to update Marvell 9230 FW.

Download M9230_1063.zip from https://download.asrock.com/TSD/M9230_1063.zip

1. Make a DOS bootable drive on USB disk, can follow below link to do it. http://rufus.akeo.ie/
2. Make sure your MB BIOS is the latest version.
3. Unzip attached M9230_1063.zip file to bootable USB drive.
4. After boot to DOS, type “start” in the command line as below screen shot.
   
   
   
   
   
5. Shut down/Reboot the system.

To update the BMC firmware via IPMI, please follow the steps below.

1. Enter the management system and click the Firmware Update from the top menu bar.
   *Note: please make sure your browser is IE v11.0.9600.17239, FireFox v31.0, Chrome v37.0.2062.120 or above version.
   
2. Click Enter Update Mode > OK.
   
   
3. Click Browse… to select the BMC firmware file from the directory. Click Open > Upload.
   
   
4. Click Proceed > OK to start.
   
   
5. When you see the screen below, firmware upgrade is completed.
   
   
6. Go back to your server and, in the BIOS screen, press [F10] and Yes to save the configuration changes and reboot the server.
   
   

1. Make sure you have connected a LAN cable from the laptop (client) to the dedicated IPMI LAN port on the Server. Prepare an USB device with the BIOS firmware installed.
   
   
2. Enter the management system from your laptop (client). Go to Remote Control > Console Redirection.
   
   
3. Click Java Console > Open to open the JViewer.
   
   
4. Select “I accept the risk and want to run this application.” and click Run to launch the JViewer.
   
   
5. In the BIOS screen, go to Advanced > Instant Flash.
   
   
6. Insert the USB device with the BIOS firmware installed into your laptop (client).
   
   
7. Click Hard Disk/USB Redirection.
   
   
8. Select the inserted USB and click Connect Hard disk/USB.
   
   
9. Confirm the inserted USB device is found and click Close to exit.
   
   
10. In the BIOS, go to Advanced > Instant Flash and press the [Enter] key on the keyboard to select.
    
    
11. Choose the desired BIOS firmware and press [Enter].
    
    
12. The BIOS updating begins.
    
    
13. After upgrade, press [Enter] key to reboot the server and confirm the BIOS and BMC versions.
    
    

1. Download driver package utility from VM.
   http://esxi-customizer.googlecode.com/files/ESXi-Customizer-v2.7.1.exe
2. Download driver from VM.
   https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI55-INTEL-IGB-5051&productId=352
3. Unzip both, then~
4. Select “Yes”
   
   
5. Use New iso file to install VM.
   
   

If the error icon is visible, then this will prevent you from have any audio functionality on your PC or virtual machine. The first image below highlights the error icon.

1. Windows Server 2012 or 2012R2 : Click Start > Administrative Tools > Services
2. Locate the Windows Audio service as shown below:
   
3. Right-click on the Windows Audio and select Properties
4. Set the Startup type to Automatic
5. Click Start. Wait for the start process to complete.
6. Click OK to complete the process.
   

Now your Windows Audio service should be running and the error icon has been removed as shown below.

Preparation

A boot USB drive
(P.S. you can build a boot USB drive by rufus https://rufus.akeo.ie/)

LSI2308_UEFI folder and copy it into bootable USB.
Press to download LSI2308_UEFI.zip

STEP:

1. Use a bootable USB and boot to DOS environment.
2. Go to LSI2308_UEFI folder and type command “START_IR.BAT”
   
   
   
3. Reboot and press Del/F2 into BIOS.
   LSI Controller=> Auto
   Bootable LSI Controller =>Yes
   Lunch Storage Storage OpROM policy =>UEFI only
   
   
4. You will see there is a LSI2308 option ROM “LSI SAS2 MPT controller SAS2308” in BIOS -> Advanced.
   
5. You can use LSI2308 option ROM to manager UEFI RAID.
   
   

Preparation

A boot USB drive
(P.S. you can build a boot USB drive by rufus https://rufus.akeo.ie/)

LSI3008_P8 folder and copy it into bootable USB.
Press to download 3008_P8.zip

STEP:

1. Use a bootable USB and boot to DOS environment.
2. Enter to LSI3008_P8 folder and type command “START_IR.BAT” and update procedure will start.
   
   
   
3. Check version:
   LSI Controller=> Auto
   Reboot and press Del/F2 into BIOS.
   LSI Controller=> Auto
   Bootable LSI Controller =>Yes
   
   CSM parameter -> Lunch Storage Storage OpROM policy =>UEFI only
   
4. You will see there is a LSI3008 option ROM “LSI SAS3 MPT controller SAS3008” in BIOS -> Advanced
   
5. You can check LSI3008 version in controller management-> view controller properities.
   

Preparation:

1. A boot USB drive
   (P.S. you can build a boot USB drive by rufus https://rufus.akeo.ie/ )
2. Copy “9172_ESP1410_UEFI” folder into bootable USB drive.
   Press to Download

Step:

1. Press F2 or Del into BIOS, select “Yes, Boot to SATA3_M0_M1(UEFI Driver)” in BIOS -> Advanced -> Storage Configuration -> Bootable Marvell 9172 SATA3
   
2. Save and exit BIOS.
3. Press F11 while booting and select "UEFI: Built-in EFI Shell".
   
4. Type "fs0:" enter to your USB Drive directory
   
5. Type "cd 9172_ESP1410_Uefi\Utilities" then type "ui64.efi" to enter 9172 UEFI option ROM.
   
6. Select "Create" and press to start creating a RAID mode.
   
7. First select free disks you want and select "NEXT" to continue.
   
8. Select either RAID0 or RAID1 mode to be created and configure other relevant RAID settings. Then select "NEXT" to continue.
   
9. RAID mode is created successfully.
   

Preparation:

1. A boot USB drive
   (P.S. you can build a boot USB drive by rufus https://rufus.akeo.ie/ )
2. Copy "Marvell 9230_UEFI" folder into bootable USB drive.
   Press to Download

Step:

1. Press F2 or Del into BIOS, select "Yes, Boot to SATAIII_M0_M3(UEFI Driver)" in BIOS -> Advanced -> Storage Configuration -> Bootable Marvell 9230 SATAIII
   
2. Save and exit BIOS.
3. Press F11 while booting and select "UEFI: Built-in EFI Shell".
   
4. Type "fs3:" enter to your USB Drive directory
   
5. Type "cd 9230_UEFI\Utility" then type "ui64.efi" to enter 9230 UEFI option ROM.
   
6. Select "Configuration Wizard" to start creating a RAID mode.
   
7. Press space to select free disks you want and select "NEXT" to continue.
   
8. RAID mode is created successfully.
   

Preparation:
Download LSI 2308_P16.zip from https://download.asrock.com/TSD/LSI 2308_P16.zip

1. A boot USB drive
   (P.S. you can build a boot USB drive by rufus https://rufus.akeo.ie/ )
2. 3U8G_PLX_P1.00 update folder and copy it into bootable USB. Press here to download

Procedure:

1. Boot to DOS mode then enter 3U8G_PLX_P1.00update folder.
   
2. Execute the 8747UPD.Bat till see the pass message appear.
   
3. AC power off your system and then power on, you will finish the updateing.
4. If you update FW successfully, you will see belw picture under VM OS:
   

Test Environment:
OS: VMware ESXi 6.0.0, 3620759
GPU card: AMD FirePro W4300
System: 3U8G-C612
BIOS: P2.40
BMC: P7.33.0
PLX FW: P1.00

Note:
If you want to restore PLX FW back to P1.01 ,please use below attached file and repeat 2-3 steps.
Press here to download

1. Equipment preparations:
   RJ45 Ethernet cable
   
2. Make sure RJ45 port plug into IPMI_LAN port on the server side board, the RJ45 port plug into general LAN port on client side.
3. Please follow the BIOS setting for the server side: Advanced→Serial Port Console Redirection→
   SOL
   - Console Redirection: [Enable]
   - Console Redirection Settings:
   Bits per second: [115200]
   
4. Legacy Console Redirection
   - Legacy Serial Redirec: [SOL]
   Legacy Serial Redirec: [SOL]
   
5. Windows EMS
   - Console Redirection: [Enable]
   - Console Redirection Settings:
    Out-of-Band Mgmt Port: [SOL]
    Bits per second: [115200]
   
6. Megarac SP setting (client side): Remote Control→Java SOL
   
   Click the [Java SOL]
   
   NOTE: A compatible JRE must be installed in the system prior to the launch of the JNLP file.
7. Please follow the Java SOL setting, and click [Connect].
    BMC IP: {Station IP address}
    Username: {Megarac SP login ID} ** “admin” in default
    Password: {Megarac SP login password} ** “admin” in default
    Volatile-Bit-Rate: [115.2K]
    Non-Volatile-Bit-Rate: [115.2K]
   
8. eboot server system and SOL has start working.
   SOL to BIOS
   
   SOL to PXE
   
   SOL to UEFI PXE
   
   SOL to OS
   

1. 1. Equipment preparations:
   RS232 COM port
   RS232 COM port cable
   Putty terminal emulator application
   
2. Make sure RS232 COM port plug into COM1 on the board, and the RS232 COM port cable are connect in both server & client side’ RS232 COM port.
   
   
   
3. Execute the Putty terminal emulator application
   
4. BIOS setting: Advanced→Serial Port Console Redirection→COM1 & EMS-Console Redirection: [Enable]
   
5. BIOS setting: Advanced→Serial Port Console Redirection→COM1-Console Redirection Settings & EMS-Console Redirection Settings
   
   Please set the Putty’ “Connection Type” = Serial, and “Speed” are equal with “Bits per second”, and click “Open”.
6. Reboot system and Console Redirection has start working.
   Console to BIOS
   
   Console to PXE
   

1. For Megarac SP Console Redirection does not work on JAVA Version 8 Update 131, kindly rollback to Java version 8 Update 121 for the temporary solution.
   We will release the updating BMC FW to website. Please keep track your model' latest BMC FW on our website from time to time.
2. Setting of Java Version 8 Update 121 to run Console Redirection
3. 1. Uninstall the JAVA Version 8 Update 131, and install to Java Version 8 Update 121.Download link:
   http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html
4. 2. After Java Version 8 Update 121 installed, open the “Configuration Java”.
5. 3. Select “Edit Site List…” from “Security” tab.
6. 4. Add the BMC IP address into the Exception Site List.
7. 5. Open a new web browser to connect to the Megarac SP and launch the JViewer.
8. 

What is Meltdown and Spectre issue

The issue is a new side-channel analysis method developed by external researchers that gathers information by observing the physical behavior of certain processing techniques that are common to modern computing platforms, when operating as designed. Malicious code using this method and running locally on a normally operating platform could infer data values from memory.

Will ASRock Rack release the FW for it?

ASRock Rack has been notified about an industry-wide potential security issue and is taking action to help our customers address their concerns.

• Based on Intel and ASRock Rack current assessment of these exploits we believe that they do not have the potential to corrupt, modify or delete data.
• ASRock Rack is working with Intel to design, test and deploy the appropriate mitigations as early as reasonably possible.
• Firmware mitigations will be available and continue to roll out over the next few weeks.
• For more information please refer to Intel public announcement website:
  https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html

Where can I find OS hotfix for it:

Following is the hot fix for each OS.
P.S
Some Linux distributions have more than one update.
For example: CVE-2017-5753 and CVE-2017-5715 is for “Spectre”, CVE-2017-5754 is for “Meltdown”

Microsoft:
https://support.microsoft.com/sq-al/help/4072698/windows-server-guidance-to-protect-against-the-speculative-execution

RedHat /CentOS 6 :
https://access.redhat.com/errata/RHSA-2018:0008

RedHat /CentOS 7:
https://access.redhat.com/errata/RHSA-2018:0007

Ubuntu:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown

SUSE:
https://www.suse.com/security/cve/CVE-2017-5753
https://www.suse.com/security/cve/CVE-2017-5715
https://www.suse.com/security/cve/CVE-2017-5754


Debian:
https://security-tracker.debian.org/tracker/CVE-2017-5753
https://security-tracker.debian.org/tracker/CVE-2017-5715
https://security-tracker.debian.org/tracker/CVE-2017-5754


Fedora:
https://fedoramagazine.org/protect-fedora-system-meltdown/

VMware:
https://www.vmware.com/us/security/advisories/VMSA-2018-0002.html

Wind River:
https://www.windriver.com/announces/cve-2015-7547_notice/

If you are using priority Linux, and need to patch by yourself.

Linux patches info is in below website for variant 2 and 3.
https://meltdownattack.com/

P.S
Variant 1 (CVE-2017-5753/) Bounds Check Bypass unless you run 4.9 or later. It doesn't have an eBPF problem.
eBPF is fixed upstream already.

How to update BIOS through Server Management Utility?

(Supports server motherboard built with BMC AST2500 controller)

Preparation

1. Download and install the Server Management Utility.
(Download: http://www.asrockrack.com/support/SMU.asp)

Steps

Step 1: Login

1~3: Key-in the IP address range to search out the host machine where need to do the BIOS update procedure.

4~5: Key-in BMC login account, then pull-down to check those searched machines.
(For example: Host machine IP = 192.168.37.29)

Step 2: BIOS Update

1. Tick to select the host machine (ex. 192.168.37.19)
2. Import the host machine BIOS image file
3. Click “Start” button to start the BIOS update process
   

   BIOS update is processing with procedures [Upload --> Upgrading --> Idle]

   

Step 3: Power ON/Reboot system remotely

1. Tick to select the host machine IP (ex. 192.168.37.19)
2. Click “Power on” (“Hard reset” if for reboot)
   
   

Step 4: Remote control system

1. Select the host machine (ex. 192.168.37.19)
2. Click “Launch JAVA KVM”
   
3. Remote the host machine by Jviewer. And check to whether the BIOS update process is success or fail.
   

Step 5: Back to Step 1: Login

Check to the latest BIOS version of the host machine.
(For example: Host machine IP = 192.168.37.29)

Steps to update BIOS firmware via IPMI webUI

(Supports server motherboard built with BMC AST2500 controller)

BIOS Firmware Update

[Maintenance] -> [BIOS Update]

This wizard will takes you through the process of firmware upgrades.

Click the “Browse...” to select the BIOS FW file. Then click “Start BIOS update” for the upgrade process. And click “OK” if confirmed to continue the process.

FW verification processing, please wait a few second..

Click “Proceed” to continue the BIOS FW upgrade process. Then click “OK” to start the actual BIOS FW upgrade operation.

FW updrage is processing, please wait a few second..

BIOS FW upgrade process finished. Click “OK” to reload the webpage.

Remark: Clear the browser cookies after the BIOS FW upgrade process finished.

Steps to update BMC firmware via IPMI webUI

(Supports server motherboard built with BMC AST2500 controller)

BMC Firmware Update

[Maintenance] -> [Firmware Update]

This wizard will takes you through the process of firmware upgrades.

Click the “Choose File” to select the BMC FW file. Then click “Start firmware update” for the upgrade process.

FW verification processing, please wait a few second..

Click “Proceed” to continue the BMC FW upgrade process.

Click “OK” to start the actual BMC FW upgrade operation.

FW updrage is processing, please wait a few second..

BMC FW upgrade process finished. Click “OK” and reboot the system.

Remark: Clear the browser cookies after the BMC FW upgrade process finished.

Environment: DOS mode

Tool: socflash (Double click below socflash v1.22.07 icon to get the socflash tool)

socflash v1.22.07.zip

Steps:

1. Copy the socflash program to USB flash drive.
2. Copy the BMC firmware in same directory with the socflash program.
3. Booting to DOS environment and execute command “socflash.exe if={bmc_image_file.ima}” to flash the BMC firmware.
4. Reboot the system when BMC FW flashing process finished.

Example:

Note: FW flashing process will take a few minutes. Please wait until the process done.

Please restart the system and boot in to the BIOS SETUP to check the BMC FW version when processes finished.

Environment: Windows/Linux/DOS mode

Tool: ipmitool (search & download from Internet)

Interface:
i. BIOS SETUP (mostly for BMC AST2400 series)
ii. IPMI webUI (mostly for BMC AST2500 series)
iii. IPMITOOL command (for barebone/system)

Attn: We DO NOT RECOMMEND that user adjust the fan table due to the system has been fine-tuned from the ASRockRack thermal team.

i. BIOS SETUP(mostly for BMC AST2400 series)

Setting directory:

BIOS SETUP screen→Advanced→H/W Monitor→[Smart Fan Control] or [Fan Control]

ii. IPMI webUI (for BMC AST2500 series)

Setting directory:

IPMI webUI→Settings →[FAN Settings]

iii. IPMITOOL command (for barebone/system)

Manual Full speed
ipmitool raw 0x3a 0x01 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64

Manual Half speed
ipmitool raw 0x3a 0x01 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32

Auto fan control
ipmitool raw 0x3a 0x01 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0

Get fan duty
ipmitool raw 0x3a 0x06 0x01(Fan duty) 0x00(flag)
Ex: ipmitool raw 0x3a 0x06 0x01 0x00

Set fan duty
ipmitool raw 0x3a 0x05 0x01(Fan duty) 0x00( flag) 30 55 60 65 70 75 80 85 90 95 100(Fan duty)
Ex: ipmitool raw 0x3a 0x05 0x01 0x00 30 55 60 65 70 75 80 85 90 95 100

Get Temp table
ipmitool raw 0x3a 0x06 0x02(Temp) 0x00( flag)
Ex: ipmitool raw 0x3a 0x06 0x02 0x00

Set Temp table
ipmitool raw 0x3a 0x05 0x02(Temp) 0x00(flag) 45 50 55 60 65 70 74 78 82 86 90(Temp table)
Ex: ipmitool raw 0x3a 0x05 0x02 0x00 45 50 55 60 65 70 74 78 82 86 90

Note:
if by local --> ipmitool raw 0x3a 0x06 0x01 0x00
if by win OS local --> ipmitool -I ms raw 0x3a 0x06 0x01 0x00
if by remote --> ipmitool -H -U admin -P admin raw 0x3a 0x06 0x01 0x00

Preparation:

Server Management Utility (asrrmgmttool): http://www.asrockrack.com/support/SMU.asp

Steps:

1. Download and install the asrrmgmttool

2. Open asrrmgmttool application

3. Enter the IP address range of the systems you want to update, and click “New”

4. Chose the “Refresh” icon and wait for the process

5. Enter the User/Password, and click “Login”. After login you should see the online system.

6. Chose to BIOS/BMC Update, and select the BIOS/BMC image need for the updating

7. Select the system IP that need for update the BIOS/BMC FW, and click “Start” to proceed

8. Wait for the FW upload and upgrade process
Uploading/Upgrading process

Idle and 100% means upgrade process has completed

9. Wait for 1~3 minutes, then you can recheck to the system updating BIOS/BMC version
[1]click Dashboard >> [2]select the IP address >> [3]check BIOS/BMC version

Step1. Prepare a flash drive, put the tool of socflash (such as the compressed file of attachment) and the ima file to be updated

Socflash Tool download link
https://download.asrock.com/TSD/socflash_v12207.zip

Step2. Before using Socflash tool to update, please enter the BIOS, press "F9" to load default, then press "F10" to save and exit the BIOS

Step3. Enter DOS and execute " Socflash if=filename option=r "

Step4. You will see the last line "Press y to continue if you are agree …." please press y to continue.

Step5. When "update flash chip ok" message appear, it means the update is completed, Please use "Ctrl+Alt+Delete" to restart the system.

Step6. Go to the BIOS home page to check if the BMC version has been updated

Step7. Finish

1. Login to IPMI webUI > Settings > FAN Settings

2. Chose Open Loop Control Table, then set your customize fan table and save.

Sample Desc: Assuming the above Open Loop Fan Table is for CPU temperature sensor, when the CPU temperature reaches between 20~25 degrees, the fan duty will be at 30%. If CPU temperature reaches 57 degrees, fan duty will be at 60%.

3. Chose Close Loop Control Table, then set your customize fan table and save.

Sample Desc: Assuming above Close Loop Fan Table is for CPU temperature sensor, when the CPU temperature is higher than 60 degrees, the fan duty cycle will increase at a rate of 1% per second; when the CPU temperature is lower than 50 degrees, the fan duty cycle will decrease by 1% every 5 seconds.

4. Go to IPMI webUI > Settings > FAN Settings > Temperature Sensor and Corresponding Fan Table

5. Chose the sensor and fan table you want to base on. And select the fan which will follow the rule.

For example, the following screenshot setting is
FAN1~6 will base on CPU1 temperature and follow to FAN table 1 which from the “Open Loop Control Table”.

6. Go to IPMI webUI > Settings > FAN Settings > FAN Mode

7. Select different fan mode

Customized mode
If you want to let the fan to follow fan table
You will need to modify the fan you need to customized mode as following blue frame then save control mode

Manual mode
If you want to set fan to static mode, you need to set fan duty as following red frame first, then save manual mode
Second, select which fan you need in manual mode as following blue frame then save control mode

Environment: EFI Shell
Tool: AFU - AfuEfi
URL: https://www.ami.com/products/firmware-tools-and-utilities/bios-uefi-utilities/
Click here to download AfuEfi64_v5.14.zip

Update steps:

1. Copy the BIOS FW image and the AfuEfi tool into the same folder of USB flash drive.

2. Boot to the EFI Shell and go to the folder where the tool and FW saved.

3. Execute the command: AfuEfix64.efi /p /b /n

4. After process completed, reboot the system and boot into BIOS SETUP to check BIOS version.

1. The Serial Number for your product is located here:

I. For systems/ barebones:

II. For motherboards:

2. Motherboard Model and H/W Rev. could be found on the board itself:

e.g. Motherboard Model = EP2C621D16GM, H/W Rev. = 1.00

3. Motherboard PPID is optional if you have the S/N numberyou’re your product. If the S/N number of the motherboard is missing, please find the white label on the board and key in the part framed in red.

4. BIOS version (UEFI Version) and BMC version could be checked in BIOS Main page:

1.Update BIOS FW

Step1. Login to IPMI Web UI

Step2. [Maintenance] -> [BIOS Update]

Step3. This wizard will takes you through the process of firmware upgrades.
Click the “Browse...” to select the BIOS FW file. Then click “Start BIOS update” for the upgrade process. And click “OK” if confirmed to continue the process.

Step4. FW verification processing, please wait a few second..

Step5. Click “Proceed” to continue the BIOS FW upgrade process. Then click “OK” to start the actual BIOS FW upgrade operation.

Step6.FW updrage is processing, please wait a few second..

Step7. BIOS FW upgrade process finished. Click “OK” to reload the webpage.
Remark: Clear the browser cookies after the BIOS FW upgrade process finished.

2. Update BMC FW

Step1. Prepare a flash drive, put the tool of socflash (such as the compressed file of attachment) and the ima file to be updated
Socflash Tool download link https://download.asrock.com/TSD/socflash%20v1.20.00.zip

Step2. Before using Socflash tool to update, please enter the BIOS, press "F9" to load default, then press "F10" to save and exit the BIOS, and make sure [CSM] is set to [Enabled]

Step3. Enter DOS and execute " Socflash if=filename option=r "

Step4. You will see the last line "Press y to continue if you are agree …." please press y to continue.

Step5. When "update flash chip ok" message appear, it means the update is completed, Please use "Ctrl+Alt+Delete" to restart the system.

Step6. Go to the BIOS home page to check if the BMC version has been updated
Remark: After the completion of the update will automatically restart the machine several times, this is a normal phenomenon

Step7. Finish

Steps:

Clear the CMOS !. you need to:

1. Disconnect the system power cable

2. Remove the CMOS Battery

3. Press the power button to drain residual energy

4. Touch/short the 2 points/pads on the CLRMOS pad with a paperclip for at least 5 seconds.

Sample the shape of the Clr_cmos pad:

5. Power on and re-check to the system.

1. Download the FW package (ODM_P3.15)
https://download.asrock.com/TSD/nvmupdate(3.15).zip

2. Decompress the file into bootable USB key

3. Login USB with UEFI shell

4. Enter into USB directory

5. Execute nvmupdate64e.efi

6. When update complete, please turn off AC then turn on after 10 sec
FW will refresh after AC cycle

If your access to BMC Jviewer iKVM (Launch Java KVM) with NCSI port connected but encountered the intermittent connection issue, please try to enable the “Keep Share NIC UP” setting.

IPMI webUI -> Settings -> “Keep Share NIC UP” -> tick “Enable” and saved.

Preparation

1. BIOS Update Tool for Linux
Click here to download Afulnx.zip
Execute Environment: Linux

Step:

1. Before using AfuLnx64, you have to install some kernel source tool by terminal.

2. Open terminal as a super user, then install following package.
apt-get install linux-headers-$(uname -r)
apt-get install dpkg-dev
apt-get source linux-image-$(uname -r)
Apt-get install process is like following picture:

3. After Unzip AfuLnx64, you can see the file “afulnx_64”.

4. Execute command in terminal: chmod 777 afulnx_64

5. Put BIOS image file into AfuLnx64 folder.

6. Execute ./afulnx_64 {your BIOS image file name} /p /b /n
Flash process will take about 3 minutes, please wait.

7. Reboot, then check BIOS version.

Update FRU in DOS

Preparation

1. FRU tool
Click here to download FRUToolinDOS.zip

2. Bootable USB

Step:

1. Put FRU tool into bootable USB then boot into USB

2. Execute FRUTool.exe will show example parameter.

Ex: FRUTool.exe ID=0 BPN= 1U1G-C422/2T PMF=ASRR PSN=123456789

3. Execute FRUTool.exe ID=0 to check the new value

Update FRU in Linux

Preparation

1. FRU tool
Click here to download FRUToolinLinux.zip

Step:

1. Extract FRU Tool under Linux OS

2. When Execute FRUTool, it will show example cmd.
5. When Execute FRUTool, it will show example cmd.

3. After modify FRU, please execute FRUTool ID=0 to check the value

Update FRU in Windows

Preparation

1. FRU tool
Click here to download FRUToolinWin64.zip

Step:

1. Extract FRU Tool under Windows OS

2. When Execute FRUTool, it will show example cmd.
Ex: FRUTool ID=0 BPN= 1U1G-C422/2T PMF=ASRR PSN=123456789

3. After modify FRU, please execute FRUTool ID=0 to check the value

Preparation:

Booting into OS with PXE is to accomplish a non-USB/disc boot by utilizing a PXE server and Internet. First, a PXE server should be established beforehand.

Step:

1. Go to BIOS menu on the client computer you wish to boot OS on, enable PXE booting option. For this instance, it is the “Boot from onboard LAN”.
   
2. Connect the client motherboard to PXE server with LAN, reboot the system and go to boot menu. Select the option with the very port that the LAN is plugged in. For this instance, it is the “UEFI: PXE IP4 P0”.
   
3. Then the list of available OS to boot in should show. I chose to boot in Ubuntu 20.04.3 x64 for this instance.
   
4. Wait until the booting process finishes, the OS should work properly via PXE server now.
   

Done!

Preparation:

An IPMI-capable device (Client) to remotely manage and establish connection to the very system with AST2500 (Host).

Find out the domain [IP address] of the host system by checking on the boot process.

Make sure the host system has the correct LAN port (Dedicated IPMI) connected so that the client could access to it.

Step:

1. Access HTML5 Web GUI using IE or chrome browser with the link https://[IP address] , and log in using IPMI user under the right domain.
   
2. To access remote media, go “Settings > Media Redirection Settings > General Settings”, tick the “Remote Media Support” and “Mount CD/DVD” boxes. For “Share Type for CD/DVD”, choose “nfs”.
   Then input info as the following picture and click save.
   *Note that choosing “nfs” here and the information framed in blue below is for this instance only. The content should differ by different circumstances.
   
   
   
3. After enabling the access, go “Image Redirection > Remote Images”. Now you shall be able to view all remote media that is accessible. Choose “Cent OS-7-x86” and click the Play button.
   *Again, choosing Cent OS is only for this case. This method doesn’t confine the OS types wished to be installed.
   
   
   
4. After the redirection completes, reboot the host system. Go to “Remote Control”, select a viewer to monitor the process. When the LOGO screen shows up, press F11 and choose “UEFI: AMI Virtual CDROM” to start the install procedure.
   
   
5. Be patient as the mounting and installing proceeds, few minutes later you will have this AST2500 platform installed with Cent OS.
   
   
6. Follow the procedure and the installation shall be completed.

Preparation:

The IPMI connection to the very system to configure network bonding function must be established first.

Step:

1. Access HTML5 Web GUI using IE or chrome browser with the link https://[IP address] , and log in using IPMI user under the right domain.
   
2. To access bonding function in IPMI, go “Settings > Network Settings > Network Bond Configuration” and you shall see an “Enable Bonding” checkbox. And the bond mode is shown below as well. Tick the checkbox on your demand to configure bonding function, and click save.
   
   *Note that changing LAN settings will restart BMC network services. You will need to reconnect using new browser session after applying changes.

Bonding function check (with WebUI):

Bonding function could be checked with IPMI WebUI. If bonding is enabled, go “Settings > Network Settings > Network IP Settings”, you shall find the bond shown in LAN Interface.

However, if the bond is disabled, you shall find the LAN inputs shown individually in LAN Interface.

Bonding Function Check (in BIOS):

To check if the bonding function is working and configured successfully, we may check it out in BIOS menu > Server Mgmt > BMC Network Configuration.

If bonding function is enabled, you shall find one and only one LAN signal detected with “(Failover)” written after the Lan channel.

On the other hand, if the bonding function is disabled, you shall find Lan channels detected individually and listed below.

Done!

To enable/ disable network bonding using IPMI command, the following demonstration shows a way to install IPMI tool on a CentOS and configure with IPMI commands.

Preparation:

Access to the command line/ terminal window of a CentOS you have installed on the system you wish to configure network bonding.

Input “sudo yum update” to update system repositories. Then, install IPMItool on a CentOS or RedHat system by running the command: “sudo yum install OpenIPMI ipmitool”. Wait for the installation to complete. The output should indicate that OpenIPMItool and IPMItool have been installed. You should see the version number of the software installed.

Once you have completed the installation, enable ipmitool access by running the command: “sudo /sbin/chkconfig ipmi on”. Then start the ipmitool service with the command: “sudo service ipmi start”.

Step:

1. Now this OS is ready to configure local network bonding. Run:
   “sudo ipmitool raw 0x32 0x71 0x1 0x0 0x0 0x1 0x64 0x0 0x3 0x1”
   to DISABLE the IPMI bonding on default;
   
2. To ENABLE bonding, it requires two command lines. First input:
   “sudo ipmitool raw 0x32 0x71 6 0 3”, then
   “sudo ipmitool raw 0x32 0x71 0x1 0x1 0x0 0x1 0x64 0x0 0x3 0x1”
   
3. To check if the bonding is enabled or not, run:
   ”sudo ipmitool raw 0x32 0x72 0x1 0x0 0x0”
   If the output shows “00 00 01 64 00 03 01”, the bonding is disabled.
   If it shows “01 00 01 64 00 03 01”, the bonding is enabled instead.
   

Remote IPMI command:

If you wish to remotely configure network bonding, install ipmitool on both the target system and the one you are running commands on.
The preparations and procedures are basically identical, except that you will have to add some information to the configuring command lines.

That is, for instance, Run:
“sudo ipmitool -I lanplus -H $target_ip -U $username -P $passwd raw 0x32 0x72 0x1 0x0 0x0”

Instead of
”sudo ipmitool raw 0x32 0x72 0x1 0x0 0x0” to check if bonding is enabled.

*Please be advised to fill in the right information on the above section labeled in red.

Done!

Preparation:

In order to flash BIOS with EFI shell, an update tool, the BIOS image to update with and an USB flash drive is required.

Tool: AFU – AfuEfi : Click here to download AfuEfi64_v5.14.zip

BIOS image: The version to be updated into

Step:

1. Prepare an USB flash drive and create a folder. Put the BIOS image and AfuEfi tool into this folder, then plug in the USB drive to the system you wish to flash BIOS on.
   
2. Boot with “UEFI: Built-in EFI Shell”. The interface will show up right away. The USB drive should be recognized as “FS0”, input “FS0:” to access the drive.
   
   
3. Use cd command to change directory to the very folder you have the BIOS and AfuEfi tool stored. Once the directory is changed, run:
   “afuefix64.efi B55IDCG0.06 /p /b /n /x” to start the flash procedure.
   It shall take a while for the “process completed” message to show up.
   *Note that the names should depend on the tool and BIOS in use.
   
4. After completion, reboot the system and check the BIOS version in BIOS SETUP page.
   
   
   The old BIOS (before update) version in comparison:
   

Issue

In some Linux hosts, when the host is booted into text mode, CAPS LOCK LED status will not be updated properly. CAPS LOCK LED won’t turn ON/OFF while changing the CAPS lock status in the host OS.

In such cases, H5Viewer CAPS LOCK synchronization functionality will not work properly. The screen capture above shows an example of typing letters in H5Viewer (after pressing CAPS LOCK) will toggle between lower to upper case inside host.

Solution

Currently due to the host side limitation of AMI, the issue could be bypassed with the Virtual keyboard function, or by pressing the Shift button to switch case.

Or simply switch to JViewer to remotely control the system instead using H5Viewer.

Preparation:

The BMC image file and BMC update tool should be at hand, here’s the update tool:

Click here to download uflash_v12207.zip

Step:

1. Decompress “uflash_v12207.zip” under a bootable USB drive.
2. Put the BMC image file you wish to update to in the same directory.
3. Boot up your system with UEFI: Built-in EFI shell.
   (Press F11 while POSTing to enter boot menu and choose it)
   
4. Execute: socflash.efi if= *image_file_name*
   
5. Wait until the update is finished. (It will show a message like “Update Flash Chip OK”)
6. Reboot and check the BMC version in the BIOS page.
   
   
   *If BMC version doesn’t show up, please disconnect AC power from the system for at least 20 seconds, then plug AC back on and check again.

Done!

Preparation:

The BMC image file and BMC update tool should be at hand, here’s the update tool:

Click here to download socflash_linux.zip

Step:

1. 1. Decompress “socflash_linux.zip” under a linux OS. (Using Ubuntu 20.04 for instance)
2. 2. Put the BMC image file you wish to update to in the same directory.
3. 3. Make every socflash file executable by running chmod 777 *filename*, if succeeded the files would turn from white to green. Then execute:
   sudo ./socflash_x64 if= *image_filename*
   
4. 4. Wait until the update is finished. (It will show a message like “Update Flash Chip OK”)
5. 5. Reboot and check the BMC version in the BIOS page.
   
   
   *If BMC version doesn’t show up, please disconnect AC power from the system for at least 20 seconds, then plug AC back on and check again.

Done!

Preparation:

1. For the BIOS method, it requires a more up to date motherboard and BIOS combination to include the “Load BMC Default Settings” item in BIOS Server Mgmt page.

2. For IPMI command, it requires a system with properly working BMC functions and IPMItool installed.

A. Load BMC Default settings via BIOS Configuration

1. Access BIOS page, select “Server Mgmt > BMC Tools”.
*Note that NOT all the motherboards/ BIOS versions include this function.

2. Select “Load BMC Default Settings” and confirm the upcoming questions, the procedure shall begin.

B. Load BMC Default Settings via IPMI Command

1. Open up an OS terminal, update system repositories and install IPMItool. Take Ubuntu for example, run “sudo apt update” and “sudo apt install ipmitool”.

2. Run “sudo ipmitool raw 0x32 0x66” to load BMC default settings.

3. Once the command is done, reboot the system to reset and complete the reset to the BMC.

C. Load BMC Default by updating to a new version/ same version again

It is rather intuitive to update to a whole new version of BMC or to the same version once again as loading to BMC default settings when the two methods mentioned above are unable to be performed.
Here is how: BMC Firmware Update by socflash

Done!

Preparation:

1. Make sure the device you wish to adjust fan speed on has a well-functioning BMC, and IPMItool could be installed.

2. All fans are properly powered and seated to the motherboard/ system so there would not be any unexpected errors to occur.
And make sure the fans have 4-pin or more to support manual speed configuration.

Step:

1. Open up an OS terminal, update system repositories and install IPMItool. Take Ubuntu for example, run “sudo apt update” and “sudo apt install ipmitool”.
   
2. Fans are originally set to default mode. To change it to manually configurable, we run “sudo ipmitool raw 0x3a 0xd8 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x1”. To return to default fan mode, simply change all of the 16 “0x1”s to “0x0”s, so that default mode would take over again.
3. Under manual fan mode, we can set all fans to 100% duty by running:
   “Sudo ipmitool raw 0x3a 0xd6 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64”
   To set all fans to 50% duty, run:
   “sudo ipmitool raw 0x3a 0xd6 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32”
   Run “sudo ipmitool raw 0x3a 0xd7” to see manual fan settings.
   Run “sudo ipmitool raw 0x3a 0xda” to fetch current fan duty.
   
   
   *To set fan duty to a specific value, just change the 0x64 or 0x32’s above to 0xHexValue. As 64 in hex equals to 100 in decimal, 32 in hex equals to 50. Similarly, just input the hex value of any % fan duty you demand.>
   e.g. Use 0x50 if you wish the fans to work at 80% duty.
4. To check if the fans are working physically on our demand, check on the IPMI WebUI Sensor, or go to Settings > FAN Setting > FAN mode:
   Sensor Reading:
   
   
   
   FAN Mode:
   

Done!

Before requesting for RMA, there are few methods to try and find out if your issue at hand is actually caused by our product itself:

1. If your system has issue booting up, please try below:

I. CMOS clearing: https://www.asrockrack.com/support/faq.asp?k=CMOS

II. Reseat all your hardware components and cables, make sure they are installed to the motherboard properly.

III. Remove all other hardware components until there is only one CPU and DIMM left, then try booting up again.

IV. If you have multiple systems or spare components at hand, you could try swapping some components which could be issue related with them.

V. If there is a later version of BIOS listed for your product on our site, please try updating to it and see if it fixes your issue.
How to update BIOS: ASRock Rack > Support

2. What information can you provide us to help:

I. Fill out your system configuration completely including firmware version (both BIOS and BMC) on our support site: https://event.asrockrack.com/tsd.asp?ln=en

II. If there is a “Dr. Debug” on your motherboard, record the current code showing when the issue occurs.

Steps to update BIOS/BMC firmware via OpenBMC

Login page

Default Username: root | Password: 0penBmc

BIOS/BMC Firmware Update

1. [Operations] -> [Firmware]
   This wizard will guide you through the firmware upgrade process.
   
2. Click “Add file” to select the BIOS/BMC FW file. Then click “Start update” for the upgrade process.
3. Click “Start update” to continue the BIOS/BMC FW upgrade process.
   
4. The BIOS/BMC FW upgrade is being processed, please wait for a few minutes.
   
5. BIOS/BMC FW upgrade is completed. Click "Refresh" and restart the system.
   
6. Remark:
   Clear the browser cookies after the BIOS/BMC FW upgrade is completed.

This guide features the cURL commands to update BIOS and BMC firmware for your server system which supports RedFish. Before we start, please make sure your host system has an IPMI or NC-SI LAN port connected to the internet and the BMC IP address of it for a client end in the same network segment to access.

1. BIOS Update:

curl -k -v -X POST https://[IP_address]/redfish/v1/UpdateService/upload --form 'UpdateFile=@[File_location]' --form 'UpdateParameters={"Targets":["/redfish/v1/UpdateService/FirmwareInventory/BIOS"]};type=application/json' --form 'OemParameters={"ImageType":"BIOS", "Config": 4, "Action": 3};type=application/json' -u [username]:[password] -H If-None-Match:W/\"1667287258\" -H "Expect:"

*We recommend this command which shuts down the host immediately and perform BIOS update.

For BIOS update, here are the definitions to the available values for "config" and "action":
'OemParameters={"ImageType":"BIOS", “Config”: config, “Action”: action}’
config
2: Preserve BIOS settings
4: Overwrite BIOS settings
action
1: Update on host shutdown
2: Update immediately without changing host state
3: Shutdown host to update

If the update request is successfully sent off, the system would return an Accepted message with a 2xx code:

You may also check the update progress by visiting:
https://[host_IP_addr]/redfish/v1/UpdateService

2. BMC Update:

curl -k -v -X POST https://[IP_address]/redfish/v1/UpdateService/upload --form 'UpdateFile=@[File_location] ' --form 'UpdateParameters={"Targets":["/redfish/v1/UpdateService/FirmwareInventory/BMC"]};type=application/json' --form 'OemParameters={"ImageType":"BMC"};type=application/json' -u [username]:[password] -H If-None-Match:W/\"1667287258\" -H "Expect:"

If the update request is successfully sent off, the system would return an Accepted message with a 2xx code as well.

3. Reboot Host:

In case you are not using a shutdown action parameter (3) for the BIOS update command, or to view the latest firmware information of your current host after the update, please reboot your host with the following command:

curl -k -v -X POST https://[BMC_IP]/redfish/v1/Systems/Self/Actions/ComputerSystem.Reset -d '{"ResetType" : "GracefulRestart"} -H "Content-Type: application/json" -H "X-Auth-Token: [token]"

4. Troubleshooting:

If an issue occurs during the update (e.g. the procedure did not start, or an error code "Status:500 Internal Server Error" occurred), you can try below methods such as the power actions or resetting BMC to default according to the scenarios:

i. Double checking your command:

If your cURL request was returned by an error code 400, it means that the request command was incorrect. In other words, the request sent by the client to the host server did NOT follow the rules. The client should modify the request command before retrying so that it could be understood by the host.

ii. Reboot Host:

If the expected update procedure does not start up, you may try powering off your system, or try rebooting it:

curl -k -v -X POST https://[BMC_IP]/redfish/v1/Systems/Self/Actions/ComputerSystem.Reset -d '{"ResetType" : "GracefulRestart"} -H "Content-Type: application/json" -H "X-Auth-Token: [token]"

ResetType Allowable values :
“On” for Host power on
“GracefulRestart” for Host reboot
“GracefulShutdown” for Host soft power off
“ForceOff” for Host hard power off

iii. BMC set to default:

If you encountered an error code 500 issue, this could be related to corrupted RedFish data. The overall solution is to resend a brand new copy of RedFish data to the server again. To do so, we flash BMC to the same version with items other than RedFish preserved, or simply update your BMC.
To preserve your current BMC config:

curl -k -v -X PATCH https:// [BMC_IP]/redfish/v1/UpdateService -d '{"Oem": {"AMIUpdateService": {"PreserveConfiguration": {"Authentication": true,"FRU": true,"IPMI": true,"KVM": true,"NTP": true,"Network": true,"REDFISH": false,"SDR": true,"SEL": true,"SNMP": true,"SSH": true,"Syslog": true,"WEB": true} } } }' -u [username]:[password] -H If-None-Match:W/\"1667287258\" -H "Expect:" -H "Content-Type: application/json"

5. Report an issue to us:

If there is an issue that cannot be resolved or further assistance is required, please visit https://event.asrockrack.com/tsd.asp and fill out the form as detailed as possible so we could provide an efficient tech support.

Preparation

The following guide will help you through enabling dual screen with your Ubuntu OS on your ASRock Rack product. This example would be based on the scenario of enabling dual-screen on a B650D4U system with Ubuntu 22.04.4. Before this procedure, the system is only capable of displaying video through the onboard VGA port but not the HDMI port simultaneously.

For detail and further resource, please refer to:
Radeon™ Software for Linux® Installation — amdgpu graphics and compute stack unknown-build documentation (amdgpu-install.readthedocs.io)

Steps

1. First, we install the AMDGPU driver:

After that, run “sudo amdgpu-install -y --accept-eula” to finish installation:

2. Then, proceed to install the ASPEED Graphics Driver:ASPEED - Drivers Download (aspeedtech.com)

Download the package and direct into the DKMS folder. Then run “sudo dpkg -i ast-drm-linux6.2.deb” to install the latest Linux package.

Completion:

3. Finally, install LightDM display manager by running “sudo apt install lightdm”, and choose lightdm as your Default display manager:

4. Reboot the system, and click on the Ubuntu LOGO and choose “Ubuntu on Wayland”.

5. Upon login, you will notice that both the onboard VGA and the HDMI are now displaying video. Be advised that the HDMI output is restricted to only be used as a secondary monitor with the VGA output being the primary one.

Preparation

1. Make sure your Altra motherboard / system to adjust fan speed on has a well-functioning BMC, so it can later be configured with ipmitool commands.

2. All fans are properly powered and seated to the motherboard / system so there would not be any unexpected errors.
Also make sure that the fans do have 4-pin or more to support manual speed configuration.

Steps

1. Open up a Linux terminal, update system repositories and install ipmitool. Take Ubuntu for example, run “sudo apt update” and “sudo apt install ipmitool”.

2. All the fans are set to act correspondingly to the CPU temperature by default. To manually configure them, here are some sample commands to apply your designated fan speed:
a. All fans run at full speed:
>> sudo ipmitool raw 0x3a 0x1 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
b. All fans run at half speed:
>> sudo ipmitool raw 0x3a 0x1 0x32 0x32 0x32 0x32 0x32 0x32 0x32 0x32
c. All fans set to default mode (operate based on CPU temperature):
>> sudo ipmitool raw 0x3a 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0

*To set fan speed to a specific value, simply change the 0x64 or 0x32’s above to 0xHexValue. As 64 in hex equals to 100 in decimal, 32 in hex equals to 50. Similarly, apply the hex value of any % fan duty on your demand.
e.g. Use 0x50 for the fans to work at 80% speed.

3. To check if the fans are working correctly at the designated speed, check out the OpenBMC WebUI > Hardware status > Sensors, all the fans should be listed with their key information such as Current Speed value, Upper and Lower critical value, etc.

Here is an easy method to monitor the boot procedure for our ALTRA series motherboard and systems. Simply follow below steps to access the host system via SSH session remotely:

1. Run the ssh command below with the Host system IP at your command prompt on a client system to start an SSH session:

ssh root@＜Host_BMC_IP＞ -p 2200

2. First time running the command, you may receive a return message which requires you to grant access. Simply enter “yes” to proceed.

3. Then enter your BMC password, the default password would be “0penBmc”.

4. After that, power on or reboot the host. Soon, you shall see the boot process begins updating rapidly in the window above.

Steps:

1. Access your system’s BMC WebUI by visiting https://IP_address with a web browser. Then login with the correct credential (default login username and password are both admin), you should be directed to the Dashboard of your system.

2. Click on “Maintenance” on the left, and choose “BIOS Update”.

3. In the BIOS Update page, we recommend keeping the default settings, which is to NOT Preserve BIOS configuration; As for Option, choose Immediately shutdown server to flash BIOS to perform a cleanest and most stable BIOS update. Then proceed to Select your firmware image, make sure you are correctly choosing your BIOS firmware to flash to, and then hit the Start firmware update button:

4. After that, the firmware upload shall begin. When it is done, please confirm your current and new firmware version, then hit Proceed and OK to continue to your BIOS update.

5. You shall receive a message upon the BIOS update completion, hit the button to confirm, and your system shall be rebooting with the newly updated firmware.

6. After the system has completed its auto reboot, you can now refresh your Dashboard page and find that the BIOS Firmware Version is updated as expected.