Tyan S8030GM2NE

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

RolloZ170

Well-Known Member
Apr 24, 2016
5,509
1,665
113
Wonder if I can use EFI Flash tool to save the current BIOS
only the half, second half is protected.
if you compare the rev.
first S8030GM4NE-2T is V1.00 2020 / 03 / 05
first S8030GM2NE is V3.00 2020 / 03 / 05
the v3.00 BIOS I had on my S8030GM4NE-2T was definitely weird as it did not include any config for my 10GigE ports in the BIOS
sure, V3.00 only exists for S8030GM2NE
 

xtr

New Member
Jan 6, 2023
11
0
1
So I'm seeing errors with a new Proxmox install. I'm getting the same error as the link to serverfault.com below.

I have the ASUS Hyper M.2 x16 Gen 4 Card NVMe expansion card. Setting the slot to AUTO or PCIe GEN4 generate the issue in the screenshots below. Setting to GEN3 as mentioned in the link stop these errors all together. Is there a fix for this? Should I just ignore the error and keep it at GEN4?

Also if the slots are numbered bottom to top in the BIOS, why do you think the error says "slot 0"?


 

Attachments

xtr

New Member
Jan 6, 2023
11
0
1
I found this..


Only one entry for AER in the manual.

1677663533265.png

Enabling this does nothing to solve the issue. So AER must be enabled for ACS to work, how do you turn AER on?

1677663486634.png
 

rigel.local

New Member
Feb 17, 2023
22
2
3
Hi, thank you all for this amazing thread.

@hmw Can you confirm that two of the available SlimSAS ports on this board can be connecter to regular 3.5 SATA drives? or this SlimSAS to SATA breakout cable only works for 2.5 SATA SSD drives?

Previously I thought these two SlimSAS ports can ONLY be connected to U.2 NVMe SSD drives.


 

RolloZ170

Well-Known Member
Apr 24, 2016
5,509
1,665
113
@rigel.local
SlimSAS and miniSAS HD connectors are not in every case SAS outputs. the connectors are often used with other signals
like the SlimSAS on the S8030GM2NE is a NVMe (2x U.2 i.e.)
the miniSAS HD on the S8030GM2NE have each 4x SATAIII for regular SATA drives( SSD or HDD )
 
  • Like
Reactions: rigel.local

codgician

New Member
Dec 14, 2022
15
6
3
La La Land
Hello,

Since there seems to be a bunch of knowledge about the S8030 on this thread I am going to try my question here.

I have just received a S8030GM4NE-2T with 8x32GB RAM and a EPYC 7302. I have it POSTing and seems happy, first thing I was going to do is update BIOS and BMC to latest then do a memtest. But the BIOS information seems 'weird'

My BIOS version according to the motherboard BIOS and POST screens and the BMC screen:

Code:
BIOS version
V3.00
Build Date
03/05/2020 15:37:06
But if I look at Motherboards S8030 S8030GM4NE-2T the latest version of the BIOS there is:

File Name:S8030GM4NE_2T-bios_v202 (23.2M)
File Date:2023 / 01 / 06
Version:V2.02

So am I looking at the wrong WWW site for BIOS updates? Or is something weird in that I have an older build date with a newer version on the board?

Thanks, Jeff
The BIOS of S8030GM2NE and S8030GM4NE-2T could be cross-flashed. You might be running the BIOS for S8030GM2NE.
 

codgician

New Member
Dec 14, 2022
15
6
3
La La Land
I found this..


Only one entry for AER in the manual.

View attachment 27523

Enabling this does nothing to solve the issue. So AER must be enabled for ACS to work, how do you turn AER on?

View attachment 27522
Tyan S8030 has PCIE AER enabled by default, and does not expose option in BIOS UI to enable/disable it.

If you really want to disable it, you may try ignoring AER errors at OS level, or manually edit bits using IFRExtractor and RU.efi. The setting should lie in AMDCBS.

Disabling AER only suppress errors instead of resolving them.
 

dante4

Member
Jul 8, 2021
45
9
8
Enabling Remote BIOS

Remember the BIOS page the Tyan IPMI interface has?

View attachment 20427


Does your BIOS look like this even after using the default credentials Administrator/superuser ?

View attachment 20426

Don't worry - it's because the Redfish API the BIOS page depends on getting the default password changed (probably because of CA law SB-327 and that's probably why Dell can show remote BIOS screens). All you need is curl / Python / Postman or anything that can send and receive web requests to the Redfish API

Step 1: We need to get the etag value from the server Redfish API (we will use it in the request header later)
Code:
curl -k \
     --request GET 'https://192.168.0.10/redfish/v1/'
Gives us
Code:
{
  "@odata.context":"/redfish/v1/$metadata#ServiceRoot.ServiceRoot",
  "@odata.etag":"W/\"<some_number>\"",
  "@odata.id":"/redfish/v1/",
  "@odata.type":"#ServiceRoot.v1_4_0.ServiceRoot
...
}
Step 2: In the result above, note down the value for the etag W/"<some_number>" without the <> of course. Now remember the default Administrator:superuser username and password? We will pass it to the Redfish API and see what the problem is.
Code:
curl -k -u 'Administrator:superuser' \
        --request GET 'https://192.168.0.10/redfish/v1/AccountService/Accounts/1' \
        --header 'If-Match: W/"<some_number>"'
Gives us
Code:
{
    "error":
    {
        "@Message.ExtendedInfo":
        [
            {
                "@odata.type": "#Message.v1_0_5.Message",
                "Message": "The password provided for this account must be changed before access is granted.  PATCH the 'Password' property for this account located at the target URI '/redfish/v1/AccountService/Accounts/1' to complete this process.",
                "MessageArgs":
                [
                    "/redfish/v1/AccountService/Accounts/1"
                ],
                "MessageId": "Base.1.0.0.PasswordChangeRequired",
                "RelatedProperties":
                [],
                "Resolution": "Change the password for this account using a PATCH to the 'Password' property at the URI provided.",
                "Severity": "Critical"
            }
        ],
        "code": "Base.1.0.0.PasswordChangeRequired",
        "message": "The password provided for this account must be changed before access is granted.  PATCH the 'Password' property for this account located at the target URI '/redfish/v1/AccountService/Accounts/1' to complete this process."
    }
}
Step 3: So now let's use curl to change the default Redfish account username and password to <new_user> and <new_passwd> (Substitute accordingly)
Code:
curl -k -u 'Administrator:superuser' \
        --request PATCH 'https://192.168.0.10/redfish/v1/AccountService/Accounts/1' \
        --header 'If-Match: W/"<some_number>"' \
        --header 'Content-Type: application/json' \
        --data-raw '{"UserName":"<new_user>", "Password":"<new_passwd>" }'
This should give a HTTP 204 (no content) - but I actually got an error message, the command still worked though. Now when you use the BIOS link to login and use your new username and password, you should be able to see the BIOS settings and even change them

View attachment 20428

Hope this helps ...
I did exactly the same, but the screen stays the same :(

The login promts accept my password and i can login via redfish (by using command from step 2) just fine, but the web stays empty.

I even tried plain admin and password without any special symbols, but that didn't hepled :(

Is any log or command that may show me what exactly gone wrong? Sorry I'm totally new to redfish
 
Last edited:

codgician

New Member
Dec 14, 2022
15
6
3
La La Land
I did exactly the same, but the screen stays the same :(

The login promts accept my password and i can login via redfish (by using command from step 2) just fine, but the web stays empty.

I even tried plain admin and password without any special symbols, but that didn't hepled :(

Is any log or command that may show me what exactly gone wrong? Sorry I'm totally new to redfish
Are you using BIOS version v4.01 (or newer) with BMC R3.00 (or older)?

I have consulted TYAN support and they told me newer BIOS requires BMC R4.x for full functionality. If you are stuck with old BMC due to having a 32MB BMC chip you may try file an RMA request (or consult your retailer) to have your BMC chip replaced. Or, you may downgrade to BIOS v4.00 to mitigate the issue.
 
  • Like
Reactions: dante4

hmw

Active Member
Apr 29, 2019
584
232
43
I did exactly the same, but the screen stays the same :(

The login promts accept my password and i can login via redfish (by using command from step 2) just fine, but the web stays empty.

I even tried plain admin and password without any special symbols, but that didn't hepled :(

Is any log or command that may show me what exactly gone wrong? Sorry I'm totally new to redfish
You need to provide more details

- Are you using Windows, Linux or Mac ?
- What are the error messages you get from the curl commands?
- If you can login via step 2 it means your password has NOT changed
 

dante4

Member
Jul 8, 2021
45
9
8
Are you using BIOS version v4.01 (or newer) with BMC R3.00 (or older)?

I have consulted TYAN support and they told me newer BIOS requires BMC R4.x for full functionality. If you are stuck with old BMC due to having a 32MB BMC chip you may try file an RMA request (or consult your retailer) to have your BMC chip replaced. Or, you may downgrade to BIOS v4.00 to mitigate the issue.
Yes, mine board is 32MB (checked by serial number), so I don't think it's possible to upgrade to 4.10. And since i bought it from Aliexpress - I don't think I can RMA :)

You need to provide more details

- Are you using Windows, Linux or Mac ?
- What are the error messages you get from the curl commands?
- If you can login via step 2 it means your password has NOT changed
Windows and Android
There is no errors
I can login with new username and password:

root@rock:/home/rock# curl -k -u 'rock:password' --request GET 'https://192.168.1.16/redfish/v1/AccountService/Accounts/1' --header 'If-Match: W/"1681081473"'
{"@odata.context":"/redfish/v1/$metadata#ManagerAccount.ManagerAccount","@odata.etag":"W/\"1681081473\"","@odata.id":"/redfish/v1/AccountService/Accounts/1","@odata.type":"#ManagerAccount.v1_1_2.ManagerAccount","Description":"Default Account","Enabled":true,"Id":"1","Links":{"Role":{"@odata.id":"/redfish/v1/AccountService/Roles/Administrator"}},"Locked":false,"Name":"Default Account","PasswordChangeRequired":false,"RoleId":"Administrator","UserName":rock"}
 
Last edited:

codgician

New Member
Dec 14, 2022
15
6
3
La La Land
Yes, mine board is 32MB (checked by serial number), so I don't think it's possible to upgrade to 4.10. And since i bought it from Aliexpress - I don't think I can RMA :)



Windows and Android
There is no errors
I can login with new username and password:

root@rock:/home/rock# curl -k -u 'rock:password' --request GET 'https://192.168.1.16/redfish/v1/AccountService/Accounts/1' --header 'If-Match: W/"1681081473"'
{"@odata.context":"/redfish/v1/$metadata#ManagerAccount.ManagerAccount","@odata.etag":"W/\"1681081473\"","@odata.id":"/redfish/v1/AccountService/Accounts/1","@odata.type":"#ManagerAccount.v1_1_2.ManagerAccount","Description":"Default Account","Enabled":true,"Id":"1","Links":{"Role":{"@odata.id":"/redfish/v1/AccountService/Roles/Administrator"}},"Locked":false,"Name":"Default Account","PasswordChangeRequired":false,"RoleId":"Administrator","UserName":rock"}
Then you may be facing the same scenario as I did. Try BIOS version v4.00 and see if Remote BIOS works. If it works, then the issue is on TYAN’s side and I am afraid they currently have no plan to fix this backward compatibility issue.
 
  • Like
Reactions: dante4

hmw

Active Member
Apr 29, 2019
584
232
43
Yes, mine board is 32MB (checked by serial number), so I don't think it's possible to upgrade to 4.10. And since i bought it from Aliexpress - I don't think I can RMA :)



Windows and Android
There is no errors
I can login with new username and password:

root@rock:/home/rock# curl -k -u 'rock:password' --request GET 'https://192.168.1.16/redfish/v1/AccountService/Accounts/1' --header 'If-Match: W/"1681081473"'
{"@odata.context":"/redfish/v1/$metadata#ManagerAccount.ManagerAccount","@odata.etag":"W/\"1681081473\"","@odata.id":"/redfish/v1/AccountService/Accounts/1","@odata.type":"#ManagerAccount.v1_1_2.ManagerAccount","Description":"Default Account","Enabled":true,"Id":"1","Links":{"Role":{"@odata.id":"/redfish/v1/AccountService/Roles/Administrator"}},"Locked":false,"Name":"Default Account","PasswordChangeRequired":false,"RoleId":"Administrator","UserName":rock"}
What does https://{{tyan_ipmi}}/redfish/v1/Systems/Self/Bios give you?

I highly recommend Postman if you're using Windows
 

dante4

Member
Jul 8, 2021
45
9
8
Then you may be facing the same scenario as I did. Try BIOS version v4.00 and see if Remote BIOS works. If it works, then the issue is on TYAN’s side and I am afraid they currently have no plan to fix this backward compatibility issue.
Yep, downgrading to 4.0 helped


What does https://{{tyan_ipmi}}/redfish/v1/Systems/Self/Bios give you?



I highly recommend Postman if you're using Windows


If you are talking about curl - i'm using ubuntu for this. And browser is from Windows & android.



root@mail:/home/rock# curl -k -u 'rock:password' --request GET 'https://192.168.1.16/redfish/v1/Systems/Self/Bios' --header 'If-Match: W/"1681081473"'

{"@Redfish.Settings":{"@odata.type":"Settings.v1_0_4.Settings","SettingsObject":{"@odata.id":"/redfish/v1/Systems/Self/Bios/SD"}},"@odata.context":"/redfish/v1/$metadata#Bios.Bios","@odata.etag":"W/\"1681160414\"","@odata.id":"/redfish/v1/Systems/Self/Bios","@odata.type":"#Bios.v1_0_3.Bios","Actions":{"#Bios.ChangePassword":{"@Redfish.ActionInfo":"/redfish/v1/Systems/Self/Bios/ChangePasswordActionInfo","target":"/redfish/v1/Systems/Self/Bios/Actions/Bios.ChangePassword"},"#Bios.ResetBios":{"@Redfish.ActionInfo":"/redfish/v1/Systems/Self/Bios/ResetBiosActionInfo","target":"/redfish/v1/Systems/Self/Bios/Actions/Bios.ResetBios"}},"AttributeRegistry":"BiosAttributeRegistry8030_.0.1.0","Attributes":{"ACPI005":false,"CPU005":"Enabled","CPU009":"Enabled","CSM002":"Force BIOS","CSM005":"Enabled","CSM007":"Legacy","CSM008":"Legacy","CSM009":"Legacy","CSM010":"Legacy","CbsCmnApbdis":"1","CbsCmnCpuCpb":"Auto","CbsCmnCpuGlobalCstateCtrl":"Auto","CbsCmnCpuL1StreamHwPrefetcher":"Auto","CbsCmnCpuL2StreamHwPrefetcher":"Auto","CbsCmnCpuMcaErrThreshCount":10,"CbsCmnCpuPfeh":"Enabled","CbsCmnCpuSevAsidSpaceCtrl":"Auto","CbsCmnDeterminismMode":"Auto","CbsCmnDeterminismSlider":"Auto","CbsCmnFchSystemPwrFailShadow":"Last State","CbsCmnGnbNbIOMMU":"Auto","CbsCmnMemCtrllerBankGroupSwapDdr4":"Auto","CbsCmnMemCtrllerDataScrambleDdr4":"Auto","CbsCmnMemCtrllerDramEccEnDdr4":"Auto","CbsCmnMemCtrllerDramEccSymbolSizeDdr4":"Auto","CbsCmnMemDataPoisoningDdr4":"Auto","CbsCmnMemDisableNvdimmNFeature":"Enabled","CbsCmnMemMappingBankInterleaveDdr4":"Auto","CbsCmnMemOverclockDdr4":"Auto","CbsCmnMemSpeedDdr4":"Auto","CbsCmnMemTsmeDdr4":"Auto","CbsCmnPPTCtl":"Auto","CbsCmnPPTLimit":0,"CbsCmnPreferredIO":"Auto","CbsCmnPreferredIOBus":0,"CbsCmncTDPCtl":"Auto","CbsCmncTDPLimit":0,"CbsComboFlag":7,"CbsCpuCcdCtrlCp":"Auto","CbsCpuCcdCtrlMts":"Auto","CbsCpuCcdCtrlSsp":"Auto","CbsCpuCoreCtrl":"Auto","CbsCpuCoreCtrl2Ccx":"Auto","CbsCpuSmtCtrl":"Auto","CbsDbgCpuLApicMode":"Auto","CbsDbgGnbDbgACSEnable":"Disabled","CbsDfCmnAcpiSratL3Numa":"Auto","CbsDfCmnDramNps":"NPS4","CbsDfCmnDramScrubTime":"Auto","CbsDfCmnMemIntlv":"Auto","CbsDfCmnMemIntlvSize":"Auto","CbsDfCmnPoisonScrubCtrl":"Auto","CbsDfCmnRedirScrubCtrl":"Auto","CbsGnbDbgPcieAriSupport":"Disabled","GSIO201":true,"GSIO607":"Auto","HWHLT5001":"Manual","HWHLT5002":30,"HWHLT5003":"On","HWHLT5004":"Disabled","HWHLT5005":"1","IPMI000":"Enabled","IPMI001":"No","IPMI002":"Do Nothing","IPMI003":"Error code","IPMI100":"Disabled","IPMI101":"6 minutes","IPMI102":"Do Nothing","IPMI103":"Disabled","IPMI104":"10 minutes","IPMI105":"Reset","IPMI200":"Yes, On every reset","IPMI201":"Clear Log","IPMI5000":"Enabled","IPMI600":"Enabled","IPMI800":"","IPMI805":"","IPMI807":"","MAPIDS":"ACPI005,RFFCF0002,RFFCF0003,RFFCF0005,RFFCF0006,RFFCF0007,GSIO201,GSIO607,TER0A8,TRE07A,TER0A7,TER012,TER0021,CPU005,PCIS004,PCIS005,PCIS006,PCIS007,PCIS011,NWSK5000,CPUCF5000,ACPI5000,RTCW5000,TER5000,PCIS5000,CSM5000,USB5000,OBDEV5000,PCIEBI5000,OPROM5000,TYANUART01,HWHLT5000,RFFCF0001,NWSK000,NWSK001,NWSK006,NWSK002,NWSK007,NWSK003,NWSK004,NWSK005,CPU009,RTCW5002,RTCW5003,RTCW5004,RTCW5005,RTCW5006,TER021,TER030,TER03F,TER04E,TER05D,TER07B,TER089,TER06C,TER5016,TER5018,TER5019,TER5020,TER5002,TER5004,CSM005,CSM002,CSM007,CSM008,CSM009,CSM010,USB003,USB004,USB00F,USB00E,USB00B,USB010,USB00C,USB00D,OBDEV5009,OBDEV5011,OBDEV5004,OBDEV5005,OBDEV5010,OBDEV5014,PCIEBI5001,PCIEBI5002,PCIEBI5003,PCIEBI5004,PCIEBI5005,PCIELS5001,PCIELS5002,PCIELS5003,PCIELS5004,PCIELS5005,OPROM5001,OBDEV5012,OPROM5002,OPROM5010,OPROM5011,OPROM5012,OPROM5013,OPROM5014,HWHLT5001,HWHLT5002,HWHLT5003,HWHLT5004,HWHLT5005,PcieLinkComplianceMode,SETUP001,SETUP002,SECUR5000,SETUP003,SETUP004,SETUP005,SETUP5000,SETUP5001,SETUP006,IPMI600,IPMI000,IPMI001,IPMI002,IPMI003,IPMI200,IPMI201,IPMI800,IPMI805,IPMI807,IPMI100,IPMI101,IPMI102,IPMI103,IPMI104,IPMI105,IPMI5000,TYANSEL0,CbsCmnCpuPfeh,CbsCmnCpuCpb,CbsCmnCpuGlobalCstateCtrl,CbsCmnCpuSevAsidSpaceCtrl,CbsDbgCpuLApicMode,CbsCpuSmtCtrl,CbsCmnCpuL1StreamHwPrefetcher,CbsCmnCpuL2StreamHwPrefetcher,CbsDfCmnDramScrubTime,CbsDfCmnPoisonScrubCtrl,CbsDfCmnRedirScrubCtrl,CbsDfCmnDramNps,CbsDfCmnMemIntlv,CbsDfCmnMemIntlvSize,CbsDfCmnAcpiSratL3Numa,CbsCmnMemDataPoisoningDdr4,CbsCmnMemCtrllerDramEccSymbolSizeDdr4,CbsCmnMemCtrllerDramEccEnDdr4,CbsCmnMemTsmeDdr4,CbsCmnMemCtrllerDataScrambleDdr4,CbsCmnMemMappingBankInterleaveDdr4,CbsCmnMemCtrllerBankGroupSwapDdr4,CbsCmnGnbNbIOMMU,CbsGnbDbgPcieAriSupport,CbsCmnApbdis,CBS5000,CBS5001,CBS5002,CBS5003,CBS5004,CbsComboFlag,CbsCmnCpuMcaErrThreshCount,CbsCpuCcdCtrlSsp,CbsCpuCcdCtrlCp,CbsCpuCcdCtrlMts,CbsCpuCoreCtrl,CbsCpuCoreCtrl2Ccx,CbsCmnMemOverclockDdr4,CbsCmnMemSpeedDdr4,CbsCmnMemDisableNvdimmNFeature,CbsDbgGnbDbgACSEnable,CbsCmnPreferredIO,CbsCmnPreferredIOBus,CbsCmnDeterminismMode,CbsCmnDeterminismSlider,CbsCmncTDPCtl,CbsCmncTDPLimit,CbsCmnPPTCtl,CbsCmnPPTLimit,CbsCmnFchSystemPwrFailShadow,","NWSK000":"Enabled","NWSK001":"Disabled","NWSK002":"Disabled","NWSK003":"Enabled","NWSK004":0,"NWSK005":1,"NWSK006":"Disabled","NWSK007":"Disabled","OBDEV5004":"Enabled","OBDEV5005":"Enabled","OBDEV5009":"Enabled","OBDEV5010":"Disabled","OBDEV5011":"Onboard","OBDEV5012":"PXE","OBDEV5014":"Enabled","OPROM5001":"Disabled","OPROM5002":"Disabled","OPROM5010":"Enabled","OPROM5011":"Enabled","OPROM5012":"Enabled","OPROM5013":"Enabled","OPROM5014":"Enabled","PCIEBI5001":"x16","PCIEBI5002":"x16","PCIEBI5003":"x16","PCIEBI5004":"x16","PCIEBI5005":"x16","PCIELS5001":"Auto","PCIELS5002":"Auto","PCIELS5003":"Auto","PCIELS5004":"Auto","PCIELS5005":"Auto","PCIS004":"Disabled","PCIS005":"Disabled","PCIS006":"Enabled","PCIS007":"Enabled","PCIS011":"Auto","PcieLinkComplianceMode":"Disabled","RFFCF0002":"1.5.b","RFFCF0003":"1.5.b","RFFCF0005":"169.254.0.17","RFFCF0006":"255.255.0.0","RFFCF0007":443,"RTCW5002":"Disabled","RTCW5003":0,"RTCW5004":0,"RTCW5005":0,"RTCW5006":1,"SECUR5000":"Enabled","SETUP001":"","SETUP002":"","SETUP003":1,"SETUP004":"Off","SETUP005":"Disabled","SETUP006":"UEFI: TS-RDF5ATranscend 0007 Partition 1,0x0001,true;UEFI: TS-RDF5ATranscend 0007 Partition 5,0x0002,true;UEFI: TS-RDF5ATranscend 0007 Partition 6,0x0003,true;Hard Drive,0x0004,true;Network Card,0x0005,true;USB,0x0006,true;UEFI: Built-in EFI Shell,0x0007,true;","SETUP5000":"Disabled","SETUP5001":"Disabled","TER0021":"115200","TER012":"VT100+","TER021":"115200","TER030":"8","TER03F":"None","TER04E":"1","TER05D":"None","TER06C":false,"TER07B":true,"TER089":false,"TER0A7":"Always Enable","TER0A8":"COM1","TER5002":false,"TER5016":"VT100","TER5018":"VT-UTF8","TER5019":"115200","TER5020":"None","TRE07A":"80x24","USB003":"Enabled","USB004":"Enabled","USB00B":"20 sec","USB00C":"Auto","USB00D":5,"USB00E":"Enabled","USB00F":"Enabled","USB010":"20 sec"},"Description":"Current BIOS Settings","Id":"Bios","Name":"Current BIOS Settings"}
 
Last edited:

dante4

Member
Jul 8, 2021
45
9
8
Hm, so changes in Remote Bios doesn't apply until reboot?

Does someone know ipmi raw commands to control fan?
 

pixelBit

Member
Jul 16, 2019
31
23
8
Are you using BIOS version v4.01 (or newer) with BMC R3.00 (or older)?

I have consulted TYAN support and they told me newer BIOS requires BMC R4.x for full functionality. If you are stuck with old BMC due to having a 32MB BMC chip you may try file an RMA request (or consult your retailer) to have your BMC chip replaced. Or, you may downgrade to BIOS v4.00 to mitigate the issue.
Did you open a ticket with TYAN via Tyan Support Center?

I'm trying to gauge TYAN's responsiveness to tickets as the line was blown out yesterday (busy signal).
 

SINN78

Active Member
Apr 3, 2016
111
25
28
44
Are you using BIOS version v4.01 (or newer) with BMC R3.00 (or older)?

I have consulted TYAN support and they told me newer BIOS requires BMC R4.x for full functionality. If you are stuck with old BMC due to having a 32MB BMC chip you may try file an RMA request (or consult your retailer) to have your BMC chip replaced. Or, you may downgrade to BIOS v4.00 to mitigate the issue.
My board is also 32mb I am running bios 4.02 with BMC 3.0 (everything seems fine) I ran into the BMC limitation and contacted Tyan and they suggested doing an RMA
for chip replacement anyone ever deal with Tyan for RMA? what's the turn around time like?
 

pixelBit

Member
Jul 16, 2019
31
23
8
My board is also 32mb I am running bios 4.02 with BMC 3.0 (everything seems fine) I ran into the BMC limitation and contacted Tyan and they suggested doing an RMA
for chip replacement anyone ever deal with Tyan for RMA? what's the turn around time like?
TYAN received my board during the first week of Jan 2021 and I got it back early February 2021.
 

dante4

Member
Jul 8, 2021
45
9
8
Hm, so changes in Remote Bios doesn't apply until reboot?

Does someone know ipmi raw commands to control fan?
For everyone who is also looking for this. After ~11 days I finally received the answer from Tyan support:



Get/Set PWM Duty

0x2e 0x5 0xfd 0x19 0x00 <PWM ID> <0x00-0x64|0xfe|0xff>

Note:

PWM ID : 0,1,2,3,4,5

0x00-0x64 = 0 -100% duty

0xfe =Get Current PWM Duty

0xff = return to automatic control


For example:

To read current PWM duty cyle:

ipmitool -I lanplus -U <BMC IP> -U root -P <YourPassword> raw 0x2e 0x05 0xfd 0x19 0x00 0x03 0xfe


To set PWM duty cycle to 60 on PWM ID 0

ipmitool -I lanplus -U <BMC IP> -U root -P <YourPassword> raw 0x2e 0x05 0xfd 0x19 0x00 0x00 0x3C

What even more you can control EACH PWM SEPARATELY