Yeah, same, better Experience with Aliexpress than eBay.
Inspected or not, since I was using a Freight Forwarding Service (via Sea Shipping, so > 90 Days anyways), eBay Buyer Protection doesn't apply. It was too late for it anyways.
EXPIRED HYVE Edge Metal G10 - Epyc 7642 - 250£/offer
- Thread starter Cruzader
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Inspected or not, since I was using a Freight Forwarding Service (via Sea Shipping, so > 90 Days anyways), eBay Buyer Protection doesn't apply. It was too late for it anyways.
"Only" after Page 7.What happened in that thread? Seems that all messages got deleted, except @luckylinux messages.
@Patrick: seems like (almost ?) my Posts got restored, but apparently other disappeared ? Could it be that re-inserting Posts overwrote some unique IDs in the Database for instance ?
Yeah, I had the most direct feedback. Account blocked on Monday Morning (European Time). Good Way to wake up for the Day !
Also @Patrick had it rough trying to restore my Account and Posts
.In case someone wants a printable NVME mount/fastener for the motherboard, just twist it in to fasten the disk:
Group Question - My metal edge server M2 TEMP sensor has always thrown a warning and reported the temp to be 0.037degrees, which makes the fans "hunt". Has anyone else seen this issue? I can't even find a diagram to tell me where to look to see if this sensor is damaged.
Any insight or help is much appreciated.
Any insight or help is much appreciated.
I manage to control the fan speed and it seems possible to remove sensors (which might help @Ulgracht).
You need to set a user/password for OpenBMC and enable DHCP. Then, you can SSH into OpenBMC. To be clear: instead of SSH to the server itself, you SSH to the IP attached to OpenBMC (the IP attach to the BMC ethernet port).
The SSH credentials is the same user/password of OpenBMC (which you use in the web browser interface).
Then, you can read and modify one file (`/usr/share/swampd/config.json` and can create a copy to `/etc/swampd/config.json`). That file seems to be responsible to control the fan-speed, based on each temperature sensor. MAYBE you can remove the damaged sensor (not a fix, but mitigates the issue) or you can remove the low temperature warning.
In general:
Based on GPT/Claude/Gemini (...), you can also set a specific fan speed, using something like:
------
I didn't investigate it further.
I increase some "setpoints" to make the server accept higher temperature... Of course, it will run hotter and the fan will eventually get louder. My issue is "OCP NIC TEMP", I need to somehow improve the cooling of this NIC [help wanted]. Because that is what is causing the fans to go crazy (it's already the max of 95ºC, which I set as target).
However, as a experiment, it worked. Now, we need some smart way to control it AND make the NIC run cooler overall.
You need to set a user/password for OpenBMC and enable DHCP. Then, you can SSH into OpenBMC. To be clear: instead of SSH to the server itself, you SSH to the IP attached to OpenBMC (the IP attach to the BMC ethernet port).
The SSH credentials is the same user/password of OpenBMC (which you use in the web browser interface).
Then, you can read and modify one file (`/usr/share/swampd/config.json` and can create a copy to `/etc/swampd/config.json`). That file seems to be responsible to control the fan-speed, based on each temperature sensor. MAYBE you can remove the damaged sensor (not a fix, but mitigates the issue) or you can remove the low temperature warning.
In general:
Code:
ssh admin@{open-bmc-ip}
# Change the "setpoints" where it says "temps" (which is CPU, M2, OCP NIC...)
sudo vi /usr/share/swampd/config.json
# Make a copy (not sure if necessary, because I didn't restart)
sudo cp /usr/share/swampd/config.json /etc/swampd/config.json 2>/dev/null || true
# Restart the service
sudo systemctl restart phosphor-pid-control.servicebusctl set-property xyz.openbmc_project.FanSensor /xyz/openbmc_project/control/fanpwm/Pwm_1 xyz.openbmc_project.Control.FanPWM Target t 50. I don't think it will work, but it's like to have a way to set it.------
I didn't investigate it further.
I increase some "setpoints" to make the server accept higher temperature... Of course, it will run hotter and the fan will eventually get louder. My issue is "OCP NIC TEMP", I need to somehow improve the cooling of this NIC [help wanted]. Because that is what is causing the fans to go crazy (it's already the max of 95ºC, which I set as target).
However, as a experiment, it worked. Now, we need some smart way to control it AND make the NIC run cooler overall.
Last edited:
Well, I didn't test that yet, but I appreciated the Instructions.
If you (for whatever Reasons ... Ear Pain being one of them during low-Load testing with one Server stuck with Fans at full Speed for some weird Reason) want to reduce Fan Speeds to a "reasonable" fixed Level:
Code:
MYIPMIHOST:~$ sudo /bin/bash
MYIPMIHOST:/home/admin# systemctl stop phosphor-pid-control.service
MYIPMIHOST:/home/admin# sudo echo 160 > /sys/class/hwmon/hwmon0/pwm1
MYIPMIHOST:/home/admin# sudo echo 160 > /sys/class/hwmon/hwmon0/pwm2
MYIPMIHOST:/home/admin# sudo echo 160 > /sys/class/hwmon/hwmon0/pwm3
MYIPMIHOST:/home/admin# sudo echo 160 > /sys/class/hwmon/hwmon0/pwm4
MYIPMIHOST:/home/admin# sudo echo 160 > /sys/class/hwmon/hwmon0/pwm5
MYIPMIHOST:/home/admin# sudo echo 160 > /sys/class/hwmon/hwmon0/pwm6It always ends up into some Black Screen (there is no POST at all), unless I set a Boot Override in
Operations -> Server power operations -> Boot settings -> Boot settings overrideThe Fans stuck at full speed may have occurred only after I installed 2 x U.2 NVMe Drives into the Server, not entirely sure, as I don't recall that having occurred before. Normally, if "locked out", all I have to do is remove AC Power, let it rest say 30 Seconds, plug AC Power back in, then let it do its 2 Boots/Reboot Loops and finally it will load correctly. Not anymore. Unless I set something for
Boot setting override, then it just shows black Screen in KVM and it's stuck .I manually set the RAM speed to the default Setting via
Overclock -> Enabled and then Memory Clock Speed -> 1333MHz (I have 2666MHz RAM, divided by 2 since DDR).Not sure what else that I changed from default it might not have liked
.On another Note, I feel like the CR2032 RTC Battery is draining VERY quickly if the Server is not plugged in (after a Year the CR2032 Battery was reading 2.7 VDC in IPMI). Anybody else observing the same ?
Last edited:
I have been battling with one of mine which seemed to be screaming all the time under load and it has led me to some info which might be useful.
Firstly I assumed it might be the CPU running close to the high limit, so I removed the heatsink and replaced the crusty thermal paste, I also removed the OCP NIC as it was also hot AND I wasnt using it, immediately the CPU temperatures dropped but now half of the fans were running at 86%, the OCP NIC temperature was no longer visible in the sensors list via the BMC gui.
Since I had the NIC on the bench, I removed the heatsink and the thermal paste had turned into a hard grout, i had to chip it off of the processor and heatsink... So I put some new paste on, reinstalled it and now its running at ~50% PWM on the fans, cpu temp is high again but the fans are much quieter.
If it starts getting hot on the NIC again I might try putting something in to guide the air toward it.
Word of warning though, I had removed this NIC on other servers and the white plastic holding the heatsink in place had become brittle and they fell off as I removed the NIC from the board, indicating that they had been getting hot for some time.#
TLDR; just removing the NIC makes the fans ramp up as the sensor goes missing. and the thermal paste is probably going to need replacing.
So, thanks again for the Tips here.
In my Case,
/etc/swampd/config.json had no effect .I had to write directly to
/usr/share/swampd/config.json.I had the fans ramping up/down all the Time due to the NIC temperature being on the "Edge" (no pun intended).
I feel that the Fan Controller (PI + FF from what I can tell) is particularly unstable with regards to the NIC Temperature (the only one currently near or above the Limit), plus it features an Offset Error, even when an integral Coefficient is set.
Increasing the Integral Gain and lowering somewhat the Proportional Gain seems to at least make it stable, even though there still is a more or less Constant Offset between the Target and the Actual NIC Temperature.
The Fans are at least not super nerve-wracking as they were before.
For those not liking
vi / vim (including me):
Code:
# Make a Backup
if [[ ! -f /usr/share/swampd/config.json.original ]]
then
cp /usr/share/swampd/config.json /usr/share/swampd/config.json.original
fi
# Change the "setpoints" where it says "temps" (which is CPU, M2, OCP NIC...)
cat << 'EOF' > /usr/share/swampd/config.json
{
"version": "R01",
"sensors" : [
{
"name": "SYS_FAN",
"type": "fan",
"readPath": "/xyz/openbmc_project/sensors/fan_tach/SYS_FAN",
"writePath": "/sys/devices/platform/ahb/ahb:apb/1e786000.pwm-tacho-controller/hwmon/**/pwm1",
"min": 0,
"max": 220
},
{
"name": "SYS_FAN1",
"type": "fan",
"readPath": "/xyz/openbmc_project/sensors/fan_tach/SYS_FAN1",
"writePath": "/sys/devices/platform/ahb/ahb:apb/1e786000.pwm-tacho-controller/hwmon/**/pwm2",
"min": 0,
"max": 220
},
{
"name": "SYS_FAN2",
"type": "fan",
"readPath": "/xyz/openbmc_project/sensors/fan_tach/SYS_FAN2",
"writePath": "/sys/devices/platform/ahb/ahb:apb/1e786000.pwm-tacho-controller/hwmon/**/pwm3",
"min": 0,
"max": 220
},
{
"name": "SYS_FAN3",
"type": "fan",
"readPath": "/xyz/openbmc_project/sensors/fan_tach/SYS_FAN3",
"writePath": "/sys/devices/platform/ahb/ahb:apb/1e786000.pwm-tacho-controller/hwmon/**/pwm4",
"min": 0,
"max": 220
},
{
"name": "SYS_FAN4",
"type": "fan",
"readPath": "/xyz/openbmc_project/sensors/fan_tach/SYS_FAN4",
"writePath": "/sys/devices/platform/ahb/ahb:apb/1e786000.pwm-tacho-controller/hwmon/**/pwm5",
"min": 0,
"max": 220
},
{
"name": "SYS_FAN5",
"type": "fan",
"readPath": "/xyz/openbmc_project/sensors/fan_tach/SYS_FAN5",
"writePath": "/sys/devices/platform/ahb/ahb:apb/1e786000.pwm-tacho-controller/hwmon/**/pwm6",
"min": 0,
"max": 220
},
{
"name": "M2_TEMP",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/M2_TEMP",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "OCP_NIC_TEMP",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/OCP_NIC_TEMP",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "CPU_CORE_MOSFET",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/CPU_CORE_MOSFET",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "CPU_SOC_MOSFET",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/CPU_SOC_MOSFET",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "CPU_TEMP",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/CPU_TEMP",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "DIMM_MOSFET_1",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/DIMM_MOSFET_1",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "DIMM_MOSFET_2",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/DIMM_MOSFET_2",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "PSU0_TEMP",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/PSU0_TEMP",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "PSU1_TEMP",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/PSU1_TEMP",
"timeout": 0,
"ignoreDbusMinMax": true
},
{
"name": "SYS_AMB",
"type": "temp",
"readPath": "/xyz/openbmc_project/sensors/temperature/SYS_AMB",
"timeout": 0,
"ignoreDbusMinMax": true
}
],
"zones": [
{
"id": 1,
"minThermalOutput": 10.0,
"failsafePercent": 100.0,
"setpoint": 80.0,
"pids": [
{
"name": "Fan0",
"type": "fan",
"inputs": ["SYS_FAN"],
"setpoint": 40.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": 0.0,
"integralCoeff": 0.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 1.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "Fan1",
"type": "fan",
"inputs": ["SYS_FAN1"],
"setpoint": 40.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": 0.0,
"integralCoeff": 0.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 1.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "Fan2",
"type": "fan",
"inputs": ["SYS_FAN2"],
"setpoint": 40.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": 0.0,
"integralCoeff": 0.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 1.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "Fan3",
"type": "fan",
"inputs": ["SYS_FAN3"],
"setpoint": 40.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": 0.0,
"integralCoeff": 0.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 1.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "Fan4",
"type": "fan",
"inputs": ["SYS_FAN4"],
"setpoint": 40.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": 0.0,
"integralCoeff": 0.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 1.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "Fan5",
"type": "fan",
"inputs": ["SYS_FAN5"],
"setpoint": 40.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": 0.0,
"integralCoeff": 0.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 1.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "cpu_core",
"type": "temp",
"inputs": ["CPU_TEMP"],
"setpoint": 80.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": -6.0,
"integralCoeff": -0.1,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 0.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "m2_temp",
"type": "temp",
"inputs": ["M2_TEMP"],
"setpoint": 75.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": -6.0,
"integralCoeff": -0.1,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 0.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
},
{
"name": "ocp_nic_temp",
"type": "temp",
"inputs": ["OCP_NIC_TEMP"],
"setpoint": 75.0,
"pid": {
"samplePeriod": 1.0,
"proportionalCoeff": -3.0,
"integralCoeff": -1.0,
"feedFwdOffsetCoeff": 0.0,
"feedFwdGainCoeff": 0.0,
"integralLimit_min": 0.0,
"integralLimit_max": 0.0,
"outLim_min": 0.0,
"outLim_max": 100.0,
"slewNeg": 0.0,
"slewPos": 0.0
}
}
]
}
]
}
EOF
# Restart the service
sudo systemctl restart phosphor-pid-control.service
To ensure a minimum sufficient Cooling we can force a Minimum "Duty Cycle" by setting the minimum Output Value of the Controller:
I think that the Value is not normalized but adjusted based on the Fan Configuration out of
255:
Hence 30 * 220 / 255 = 25,88.
Code:
root@pve:~# ipmitool sensor
PSU0_CURRENT_IN | 0.702 | Amps | ok | na | na | na | na | na | na
PSU0_CURRENT_OUT | 11.000 | Amps | ok | na | na | na | na | na | na
PSU1_CURRENT_IN | 0.000 | Amps | ok | na | na | na | na | na | na
PSU1_CURRENT_OUT | 0.000 | Amps | ok | na | na | na | na | na | na
Pwm_1 | 25.872 | unspecified | ok | na | na | na | na | na | na
Pwm_2 | 25.872 | unspecified | ok | na | na | na | na | na | na
Pwm_3 | 25.872 | unspecified | ok | na | na | na | na | na | na
Pwm_4 | 25.872 | unspecified | ok | na | na | na | na | na | na
Pwm_5 | 25.872 | unspecified | ok | na | na | na | na | na | na
Pwm_6 | 25.872 | unspecified | ok | na | na | na | na | na | naTo reduce the Fan Noise during Boot one could probably play with the following Settings, though I did NOT try them myself yet:
Wrong topic? The screenshots you have are of an Intel system, not the EPYC 7642 in this thread.Mine 10 servers arrived. Secure boot is disabled by default that is good, but VT-d is also disabled which is not good for proxmox users
Now to find & order few riser cards, BMC & BIOS updates are welcome sometime later.
10 of the other hyve model they had i suppose, i ordered 2 of it at a 40£/offer that are still sitting in their box.
Hi All,
I've been messing about with replacing the BIOS and BMC IC's.
I was trying all this to see if there was a way to
I removed the old IC's, and replaced with new IC's flashed with the latest bios and BMC for the S8036, using https://forums.servethehome.com/ind...42-cpu-very-basic-bios-and-bmc-options.48039/ for reference.
new BMC version = 4.04.0 (needs a 64mb IC rather than the old 32mb IC)
new BIOS version = 2.06
Download
Case 1: Both new BMC and BIOS IC's installed.
System doesn't finish POST. I get the Tyan POST graphics, but the POST gets to "OEM pre-memory initialization 0022" and hangs. I tried with memory only in DIMM A1, and then memory in DIMM's A1 + C1, and then also DIMM's A1 + E1, but always the same error.
Case 2: New BIOS but old BMC IC's installed.
Same issue as Case 1
Case 3: New BMC but old BIOS IC's installed.
System posts and works. Fans are nice and quiet. Issue is that the new BMC needs the MAC address for its NIC to be hard set, otherwise every time you hard reset or restart the BMC, a new random MAC address is used for it (MAC address is not persistent) Fine if you run DHCP and don't care about this.
I tried setting the MAC with
Another thing is there is no option to turn on SSH to access the BMC, which you can do with the base Hyve BMC.
I also tried updating the BIOS via the new BMC, but this just puts you at the Case 1 issue.
Outcomes
The only positives that Case 3 (the only usable case) produced was the fans were a lot quieter, and the M.2 sensor temp issue was resolved.
The MCX545A-CCUN card still was not recognised by BIOS (because the BIOS couldn't be updated), and the BMC nic MAC address could not be set to a static persistent value.
Perhaps peoples with more experience can chime in with constructive things I could try and report back on.
I've been messing about with replacing the BIOS and BMC IC's.
I was trying all this to see if there was a way to
a) get the full BIOS so I could try and get an OCP 2.0 MCX545A-CCUN card working in the machine.
b) see if it sorted out my M.2 sensor temp of 0.37 degC issue which caused the fans to hunt
c) give more control in both BIOS and BMC
I removed the old IC's, and replaced with new IC's flashed with the latest bios and BMC for the S8036, using https://forums.servethehome.com/ind...42-cpu-very-basic-bios-and-bmc-options.48039/ for reference.
new BMC version = 4.04.0 (needs a 64mb IC rather than the old 32mb IC)
new BIOS version = 2.06
Download
Case 1: Both new BMC and BIOS IC's installed.
System doesn't finish POST. I get the Tyan POST graphics, but the POST gets to "OEM pre-memory initialization 0022" and hangs. I tried with memory only in DIMM A1, and then memory in DIMM's A1 + C1, and then also DIMM's A1 + E1, but always the same error.
Case 2: New BIOS but old BMC IC's installed.
Same issue as Case 1
Case 3: New BMC but old BIOS IC's installed.
System posts and works. Fans are nice and quiet. Issue is that the new BMC needs the MAC address for its NIC to be hard set, otherwise every time you hard reset or restart the BMC, a new random MAC address is used for it (MAC address is not persistent) Fine if you run DHCP and don't care about this.
I tried setting the MAC with
sudo ipmitool lan set 1 macaddr <xx:xx....> but it would not stick.Another thing is there is no option to turn on SSH to access the BMC, which you can do with the base Hyve BMC.
I also tried updating the BIOS via the new BMC, but this just puts you at the Case 1 issue.
Outcomes
The only positives that Case 3 (the only usable case) produced was the fans were a lot quieter, and the M.2 sensor temp issue was resolved.
The MCX545A-CCUN card still was not recognised by BIOS (because the BIOS couldn't be updated), and the BMC nic MAC address could not be set to a static persistent value.
Perhaps peoples with more experience can chime in with constructive things I could try and report back on.
Last edited:
Hi all, wondering if people would mind helping me out. As per my previous post, I've been playing about with the BMC and BIOS IC's of my HYV-S-CF-EDGE-G10-04 server
In my oversight, I seem to have corrupted the motherboard eeprom, and this has had some side affects = fans and sensors disappearing from inside the BMC because the expected value at an address on the eeprom is not there = FANS @ 12,800rpm!
To that end, would some kind person who has a working "virgin" HYV-S-CF-EDGE-G10-04 be willing to help me obtain an uncorrupted copy of their motherboard eeprom?
I have written a text script (attached). Its for linux bash, you just need to rename it to .sh and chmod +x it, then run it.
It makes two read-only dumps of the eeprom, creates a results file, and a checksum file, and tar.gz's them ready to send back. It will ask (but not store) the ip address of the OOB console for your hyve server, the login username, and then twice for the password to ssh into the hyve serverOOB/SSH. You need to have SSH access enabled in the OOB for this to work as well.
I'm in a pickle and would appreciate the help.
Then, if anyone has an ACTUAL Tyan Tomcat S8036GM2NE-LE motherboard, in the interests of continuing my explorations, would you be willing to do the above and provide a copy of your motherboard eeprom for comparison? Like I said in my previous post, I'm tinkering to see if these Hyve boards can be returned to fully functional Tyan/Mitac status.
In my oversight, I seem to have corrupted the motherboard eeprom, and this has had some side affects = fans and sensors disappearing from inside the BMC because the expected value at an address on the eeprom is not there = FANS @ 12,800rpm!
To that end, would some kind person who has a working "virgin" HYV-S-CF-EDGE-G10-04 be willing to help me obtain an uncorrupted copy of their motherboard eeprom?
I have written a text script (attached). Its for linux bash, you just need to rename it to .sh and chmod +x it, then run it.
It makes two read-only dumps of the eeprom, creates a results file, and a checksum file, and tar.gz's them ready to send back. It will ask (but not store) the ip address of the OOB console for your hyve server, the login username, and then twice for the password to ssh into the hyve serverOOB/SSH. You need to have SSH access enabled in the OOB for this to work as well.
I'm in a pickle and would appreciate the help.
Then, if anyone has an ACTUAL Tyan Tomcat S8036GM2NE-LE motherboard, in the interests of continuing my explorations, would you be willing to do the above and provide a copy of your motherboard eeprom for comparison? Like I said in my previous post, I'm tinkering to see if these Hyve boards can be returned to fully functional Tyan/Mitac status.
Is it possible for this eeprom to contain any sensitive/identifying info or is just standard across all motherboards of this type?
It will have the mac address of the oob nic, the manufacturer, model name of the board. I'm after seeing what a healthy dump looks like to mine, with a hope i can replicate the healthy structure with my servers info