The CP tag failure has been fixed and will be included in any new
release of Open Firmware.
It was indeed a bug.
Instead of setting the CP tag in the embedded controller (EC), 128
bytes of invalid data was written instead.
The EC just ignored the invalid data and behaved as if the CP tag
wasn't
We're in Hinche, Haiti where we only have access to these 2 XO-4s:
SHC31100371
SHC3110037D
Both have Q7B37 and both fail to auto-boot-on-application-of-power even
with tag "CP" confirmed by ".mfg-data".
While we'd LOVE to fix this problem, we're leaving this part of Haiti
4:30AM, and so ha
On Jan 24, 2014, at 6:36 PM, Adam Holt wrote:
> We've relied on this for many years on XO-1s and XO-1.75s (etc) to ensure
> small XO servers auto-boot after the inevitable power failures -- and yet
> today it (apparently) no longer works.
>
> Is it possible this does not work on XO-4s, or are
We've relied on this for many years on XO-1s and XO-1.75s (etc) to ensure
small XO servers auto-boot after the inevitable power failures -- and yet
today it (apparently) no longer works.
Is it possible this does not work on XO-4s, or are we somehow entering
"add-tag CP" incorrectly at the "ok" pro
