Yes, all versions of the S8030 can take the latest BIOS, and can be updated via BMC. It's the BMC that cannot be updated past v3 if the BMC SPI flash chip is only 32MB.
It's SMD, pretty tricky. Heat shield / aluminum foil the surrounding area, hot air gun, magnifying glass, hope you don't loosen any other components or create solder bridges, drag solder.
It's SMD, pretty tricky. Heat shield / aluminum foil the surrounding area, hot air gun, magnifying glass, hope you don't loosen any other components or create solder bridges, drag solder.
i usualy cut the old out with a mini precision pliers. then clean pads with tiny std.soldering iron and solder new chip (or socket)
no hot air required.
Yes, all versions of the S8030 can take the latest BIOS, and can be updated via BMC. It's the BMC that cannot be updated past v3 if the BMC SPI flash chip is only 32MB.
The Tyan site mentions the 4.07 BMC will brick a board with a 32MB chip.
However, a similar warning is not present for the 4.10 and 4.11 version, and the zip file is slightly smaller. Does that mean it can be flashed to the 32MB chip?
Looking at the sizes of the ima files inside the zips, I would assume this is not the case, as these files are exactly 64MB for all 4.x version.
However, a similar warning is not present for the 4.10 and 4.11 version, and the zip file is slightly smaller. Does that mean it can be flashed to the 32MB chip?
Wll, that's absolutely not clear from the way their download area is written.
But it makes sense: what use is it to have a "dangerous" version on the site if newer ones solve the problem.
Anyway, was looking in the images to flash, and the last 32MB of the 64MB IMA file only contains FF bytes, except for a small section at 0x03FF000 that contains some info on the firmware. That's at 0x01FF0000 in the V3.0 BMC.
So it looks like it could fit in 32MB. There's absolutely less than 32MB of code in the 64MB file. No idea why they then went this incompatible route...
So it looks like it could fit in 32MB. There's absolutely less than 32MB of code in the 64MB file. No idea why they then went this incompatible route...
well my board is fully upgraded latest bmc and bios ( I do have the 64MB version ). This combo with 7302 and 64GB ram is running great. Almost done moving my ESX VM's to proxmox. I am keeping ESX 8 around for abit while I get used to proxmox.
This combo has replaced my old e3 SM combo that served me well for many years.
If the BMC is the culprit, it is possible to flash a new BMC firmware using this serial port but it will be painfully slow, but if you have 24 hours + to spare it should be fine. (There is a faster way but that requires way more setup and instruction work and a working u-boot bootloader).
(I can provide details later if you are willing to take this route)
quick note: if you don't want to try to hack something together for the 32MB issue, you can send your board in Tyan and they'll upgrade it for you for free. Did that with mine.
quick note: if you don't want to try to hack something together for the 32MB issue, you can send your board in Tyan and they'll upgrade it for you for free. Did that with mine.
Does anyone have issues powering off ESXi hosts on the S8030? I'm observing that shutting down / powering off ESXi from vCenter or from the ESXi web portal (or even via API / PowerCLI / esxcli ) causes it to shutdown and then restart again - really weird.
update: just reinstalled ESXi 8.0U2 fresh and tested with the same result - the S8030 somehow after the newer BIOSes just won’t shutdown properly in ESXi. Either that or it’s some kind of configuration issue with the rest of the hardware
Does anyone have issues powering off ESXi hosts on the S8030? I'm observing that shutting down / powering off ESXi from vCenter or from the ESXi web portal causes it to shutdown and restart - really weird.
Does anyone have issues powering off ESXi hosts on the S8030? I'm observing that shutting down / powering off ESXi from vCenter or from the ESXi web portal (or even via API / PowerCLI / esxcli ) causes it to shutdown and then restart again - really weird.
update: just reinstalled ESXi 8.0U2 fresh and tested with the same result - the S8030 somehow after the newer BIOSes just won’t shutdown properly in ESXi. Either that or it’s some kind of configuration issue with the rest of the hardware
TYAN S8030GM2NE will often fail to boot into windows.
Boot sequence looks like this:
BMC loading starts → ends
BIOS loading starts → ends
Windows loading starts → several spins of dotted donut
Keyboard lighting blinks and everything goes to 1.
I tried different BIOS versions (4.02 and 4.00), removing all USB devices (i though it could be KVM’s fault), resetting CMOS and BMC HW, checking windows for errors (scannow, etc) - nothing found. 20 hours of memtest86 also gave no errors.
Later, Windows event log states kernel-power with 0’s in all fields. (Not every time this bootloop happens, though)
Board is from the early revisions, with 32MB BMC flash.
Current BMC and BIOS versions are v3.00 and v4.00. Windows Server 2019 was updated to the lastest version.
Full hardware list:
CPU - EPYC 7302
MB - TYAN S8030GM2NE
CPU Cooler - Exegate ESNK-P0064AP4
RAM - SK Hynix 16Gb 2Rx8 PC4-3200AA HMA82GR7CJR8N-XN, 8 sticks
Case - SilverStone Grandia GD07
PSU - DEEPCOOL PQ750M
NIC - Mellanox ConnectX-3 CX354A
SSD - Intel 545s SSDSC2KW256G8XT.
Checked windows boot logs. Failed one differs with the good one at “BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys”
Bad one has that string 2 times, and ends exactly at the second attempt. Good one keeps loading further, gets a 3rd (failed?) attempt and keeps going.
All failed boot logs look exactly the same, while successful ones usually have several driver entries in different positions in the log (overall number of entries is the same).
Hi all - I finally received all my parts for my build an put my server together today. I'm in the process of building a server with the Tyan Tomcat HX S8030 (S8030GM2NE) motherboard and EPYC 7302p. When flip the PSU switch to give the board power the BMC green led is solid, then after 15 seconds it switches to blinking and the CPU fan starts spinning. I checked for the IPMI IP on my router but do not see it. When I press the power button on the case, nothing happens. There is no video output via the integrated VGA port on the motherboard. I can't tell if the power button on the case does anything because the CPU fan comes on its own when the BMC starts blinking green. When I hold the power button down nothing happens. All of the jumpers on the board are in the default configuration. When I press the System Reset button on board nothing happens. When I press the power button on board nothing happens. I cleared the CMOS following the procedure in the manual. I tried it with 1 stick of memory. Tried it with 4 sticks. Tried it with 0 sticks. Still no luck. No video output. Without a video feed, I'm at a loss as to what else to try.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.