Possibly the Ram or the CPU, a G3258 and some 4GB generic Gskill udimm.
interestingly, there is once 5V on the mentioned pin, and then twice 3.3V on JP18, pin 6 and 4 to be precise. JP17 Pin2 is GND to have at least mentioned where or how i wired it up.
Pin 1 of JP18 is 5V on mine. thinking about the circuit on the back behind the 8pin powerblug with Q130, Q131 and Q126, i came to the conclusion that THAT pin needs to be connected to ground.
JP17 pin 5 on the other hand seems to need some voltage to then pull Q130 down and allow the Enable pin to not be pulled low.
With 3.3V on pin 5, led5 turns off.
I would also love a summary of the pinout. From your investigation, it sounds like the following:interestingly, there is once 5V on the mentioned pin, and then twice 3.3V on JP18, pin 6 and 4 to be precise. JP17 Pin2 is GND to have at least mentioned where or how i wired it up.
I got the same result except the board didn't blew up. First launch got a SUPERMICRO screen, but I was lacking a heatsink. I installed one and after that power button stopped working. Very confusing.I am really confused what I did differently with my first blown-up board, which at least show me the SUPERMICRO screen.
I am currently out of ideas.
$ python read_header.py --extract ../x10sle-f_bmc.bin Read 33554432 bytes Warning: bootloader (first 64040 bytes of file) md5 doesn't match. This parser may not work with a different bootloader Expected 166162c6c9f21d7a710dfd62a3452684, got c72bf051f0569a6ca809eb7750364562 Dumping bootloader to data/bootloader.bin Error: Unable to determine what type of IPMI firmware this is!
export rm_files="lighthttpd.conf OEMPSBlock service.conf bmc_hostname ddns PSBlock FWBlock SDRBlock network ntp/ntp.conf SELBlock server.pem timezone vm_image.conf wsman enSSL.config sysmacaddr.conf wsman/simple_auth.passwd wsman/openwsman.conf ipctrl/rultbl.sav snmpd.conf ddns/DDNS_CONFIG ddns/ddns.key ddns/ddns.private IKVMViewerLang stunnel.conf redfish/event.ini"