I did a few new tests with your SMBIOSResolver v1.0.8. Thansk for that!
Unfortunately I had an older version (v1.0.7) until now which appears not to include the security-mode fix.
This is what I saw:
1) Chameleon2 with SMBIOSResolver.
Two options nodes exist in the device tree. Very strange, how is this possible? Firewire error eccurs.
ioreg -p IODeviceTree -l says (only relevant info shown):
+-o Root <class IORegistryEntry, retain 17>
+-o / <class IOPlatformExpertDevice, registered, matched, active, busy 0, retain 27>
+-o options <class IOService, !registered, !matched, active, busy 0, retain 4>
| {
| "name" = <"options">
| "IOPlatformUUID" = <0000000000001000800000508d9f42f0>
| }
+-o options <class IOService, !registered, !matched, active, busy 0, retain 4>
{
"resolver" = ""
"security-mode" = "none"
}
2) Installed munky's efi_boot v6.1 with SMBIOSResolver. munky's source is available and I checked that it does not touch the options node.
The node exists as expected but the firewire error is not fixed. I also checked disk transfer to firewire drive and it's slow with high CPU load.
+-o Root <class IORegistryEntry, retain 17>
+-o / <class IOPlatformExpertDevice, registered, matched, active, busy 0, retain 26>
+-o options <class IOService, !registered, !matched, active, busy 0, retain 4>
{
"resolver" = ""
"security-mode" = "none"
}
I can't really make sense of this.