H12SSL-i IPMI Status: Not working
- Thread starter thulle
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Is the most recent BMC firmware as recent for the dual socket version as it is for the single socket?I've got a H12 dual socket version where no sensor data os showing up, and I cannot reset chassis intrusion, latest bios & ipmi, everything else works, tried differrent os, and ram etc.
I also purchased a H12SSL-i from the same vendor and am experiencing the same issue. I updated both firmware and BIOS when I received the mobo, which went fine, but I didn't power it on since I didn't have RDIMMs on hand. When I assembled everything together today I couldn't get the BMC to work, BMC LED never lit up, also shows up as IPMI: not working under BIOS. Took a long time to bios w/ a dGPU, seemingly not progressing beyond UEFI as well.
@RolloZ170: I updated the BIOS to the latest version after updating the BMC.
@thulle: what I noticed was that an IC (could be U4/U5/U6, but I think it's U6 that's running hot) next to the DRAM of the BMC was hot to the touch. Is your BMC LED solid green or off?
@RolloZ170: I updated the BIOS to the latest version after updating the BMC.
@thulle: what I noticed was that an IC (could be U4/U5/U6, but I think it's U6 that's running hot) next to the DRAM of the BMC was hot to the touch. Is your BMC LED solid green or off?
Last edited:
maybe the FW was to old and the update to new. usualy on SM you have to update in steps, not to the latest avail. FW.
if you have issues you have to solve this first. update a BMC with issues is not a good idea.
to see sensor data you have to proceed a FULL POST sequence first after change RAM size & CPU type / cold boot.
if you reset / clear / init. something and a tool or the WebGUI says "ok, operation complete..." DON'T touch the system for some minutes.
mostly the operation is started in the background and some flash NAND init. has to be done. any reset and or power cycle will brick your BMC.
if you have issues you have to solve this first. update a BMC with issues is not a good idea.
to see sensor data you have to proceed a FULL POST sequence first after change RAM size & CPU type / cold boot.
if you reset / clear / init. something and a tool or the WebGUI says "ok, operation complete..." DON'T touch the system for some minutes.
mostly the operation is started in the background and some flash NAND init. has to be done. any reset and or power cycle will brick your BMC.
ipmitool status works fine for me. I see sensor readings and etc.I've got a H12 dual socket version where no sensor data os showing up, and I cannot reset chassis intrusion, latest bios & ipmi, everything else works, tried differrent os, and ram etc.
But I'm unable to reset chassis intrusion. It just doesnt work.
I'm on BMC 01.04.03 BIOS 3.0
Its not the latest BMC, but it is a version that allows setting thresholds for fans. Anything newer than that doesnt allow it
just doesnt work
Code:
# /usr/local/bin/IPMICFG-Linux.x86_64 -clrint
Done.
Code:
# /usr/local/bin/IPMICFG-Linux.x86_64 -sdr
Status | (#)Sensor | Reading | Low Limit | High Limit |
------ | --------- | ------- | --------- | ---------- |
Fail | (1947) Chassis Intru | General chassis intrusion |
| (2148) NVMe_SSDA Temp | N/A | N/A | N/A |
| (2215) GPU1 Temp | N/A | N/A | N/A |
| (2282) NVMe_SSDB Temp | N/A | N/A | N/A |
| (2349) NVMe_SSDC Temp | N/A | N/A | N/A |Ist the cable connected?But I'm unable to reset chassis intrusion. It just doesnt work.
It's connected but I'm now doubting whether it's connected correctlyIst the cable connected?
If I'm not mistaken my intrusion connector on later gen SM MB is not shorted by default (suggesting it's "All is fine" position),
intrusion event is switched when switch shorts contacts.
How did I came to these conclusions?
Haven't done anything with intrusion system once I've got MB and it was working just fine without these events.
Then instead of proper case switch - I've plugged jumper over that MB connector (with two pins) to short contacts.
Immediately my BMC log started showing those "Intrusion events" (with contacts shorted).
Disconnected shorting jumper and cleared "Intrusion event" warning - everything went back to normal (no these events in log anymore).
My conclusions might be wrong but generally it causes no issues with nothing connected there.
intrusion event is switched when switch shorts contacts.
How did I came to these conclusions?
Haven't done anything with intrusion system once I've got MB and it was working just fine without these events.
Then instead of proper case switch - I've plugged jumper over that MB connector (with two pins) to short contacts.
Immediately my BMC log started showing those "Intrusion events" (with contacts shorted).
Disconnected shorting jumper and cleared "Intrusion event" warning - everything went back to normal (no these events in log anymore).
My conclusions might be wrong but generally it causes no issues with nothing connected there.