[Chameleon + FileNVRAM] nvram..plist doesn't have UUID in filename?

[g0l3m]

Hi,

 

I have 3 hacks (Gigabyte UD3H-B3 v.13, BIOS F12, Core i5/i7). Every PC has a unique SystemId set in org.chameleon.Boot.plist.

 

Software environment is the same on every computer: Chameleon 2.2svn (svn-r2187), FileNVRAM.dylib v1.1.3 with OS X 10.8.2.

 

iMessage is working but on 2 machines I don't have the UUID in nvram.plist. Its filename written with double dot, look at the output of console's ls:

 

# /Extra

# ls -got
-rw-rw-rw- 1 18882 21 Okt 15:46 DSDT.aml
-rw-r--r-- 1	 945 16 Mai 2012 SSDT.aml
drwxr-xr-x 4	 136 20 Sep 11:52 Themes
drwxr-xr-x 4	 136 6 Mär 10:25 modules
-r-------- 1 1287 6 Mär 11:15 nvram..plist
-rwxr-xr-x@ 1	 608 6 Mär 10:46 org.chameleon.Boot.plist
-rw-rw-rw-@ 1	 470 6 Mär 10:43 smbios.plist

 

Why i don't habe an UUID in nvram..plist on 2 machines? On the last machine the UUD is in nvram.plist.

 

Any idea? Thank you.

Edited March 6, 2013 by g0l3m

[meklort]

That means that the module was unable to read out the UUID form the motherboard (the smbios table was not found.)

[g0l3m]

Thank you for your answer. Is there a way to fix it?

 

Why is the module on 1 one of the 3 identical configured machines with same hardware able to read the uuid?

Edited March 6, 2013 by g0l3m

[meklort]

They may have a different bios version. In any case' it's not too big of a deal unless if you have multiple machines with the same nvram file and plan on moving the boot disk between the two. The primary reason for a separate file is so that the nvram is persistent only for the booted hardware.

[g0l3m]

Thank you again. I've flashed the same BIOS to every board. It's curious…