A simple method to make OCNG3 BIOS work on H8QGL board without disabling IPMI

quickz

Limp Gawd
Joined
Jul 30, 2012
Messages
256
The IPMI on H8QGL is incompatible with OCNG BIOS, H8QGL boards with OCNG BIOS would fail to post if IPMI is enabled, so it usually needs to disable IPMI by jumper (JPB1) before using the OCNG BIOS.
But I like IPMI remote control functions as well, so I'm looking for if there is any method could let OCNG BIOS work together with IPMI.
Now, I think I have found a simple method that would probably work for it.

The detailed steps to enable IPMI on H8QGL with OCNG3 BIOS:
1. power off the system
2. remove the jumper cap from JPB1
3. power on the system and wait for several minutes
5. hot reboot the system (you will hear some whistling sound if the refclock was modified, just ignore it)
6. wait about 20 - 30 minutes (don't know why we should wait so long, seems to have something to do with DHCP)
7. ok, now IPMI should be ready for you

The manual of H8QGL said that connecting pins 1-2 of JPB1 is to enable BMC (IPMI) and pins 2-3 to disable it, while the behavior of completely removing the jumper cap is undocumented.
I'm not sure if this should work for all H8QGL boards, but it did work for me. :)

update:
1. seems we could omit step 6 if static IP address was set for IPMI.
2. sometimes the system would fail to hot restart, use IPMI reset instead.
 
Last edited:
Interesting - thanks for the tip. I actually found that Wake On Lan plus ssh was sufficient for about anything I needed to do. IPMI is nice to have, though. I'll give this a try the next time I reboot (which may be a while - I am a 108 days of uptime on my GL at the moment.)
 
Hi quickz,

Sorry for resurrecting old thread ;)

I'm posting just to let you know that removing JPB jumper worked on two GLs (sc0tty's and mine)
and somehow neither of us needed to wait 20-30 minutes (even though both our systems were
set up for IPMI DHCP).

Basically, the process was:
0. Ensuring that IPMI works
1. AC power-off
2. Removing JPB1 jumper
3. AC power-on
4. Done!

The refclocks on our test systems are 240 and 250 and the BIOS version is OCNG4 (doubt it's any
different in this regard to OCNG3 -- stating for the record).
IPMI firmware was 2.06 and 2.03.

I will point IPMI/GL folks to this thread :)



Also, interesting side observation: both our systems were actually able to boot with JPB1 jumper present [sic!].
There was small problem with CPU bring-up, though:
Code:
Ts:9535361 -
Node 0  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 33
Node 1  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 33
Node 2  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 24
Node 3  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 24
Node 4  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 57
Node 5  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 57
Node 6  c0:ps0 - c1:ps0 - c2:ps0 - c3:ps0 - c4:ps0 - c5:ps0 - Tctl: 49
Node 7  c0:ps4 - c1:ps4 - c2:ps4 - c3:ps4 - c4:ps4 - c5:ps4 - Tctl: 40

Every time the machine was booted, there would be one node locked P-state 4 and we were not able to change it.
This problem went away when the jumper was removed. Weird.
 
Last edited:
Back
Top