Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

pmcnano
pmcnano
Posted
Posted

@THe KiNG, do you know if there will be a more detailed changelog/readme file?

 

I noticed that I had to use the DisableNvidiaInjection attribute with this version, I never had to use it before. I have a GTX 970.

 

Thanks

Link to comment
Share on other sites
Mr. Xtreme
Mr. Xtreme
Posted
Posted

I built the new Oz for the GA-B75M-D3h Rev 1.2 + El Cappy 10.11.1 and It works nicely and loaded an ssdt fix for hdmi audio good job HermitCrabLabs.

BTW anyone know where I can find Hermitcrablabs' website?  the tor2web link doesn't work andniether does putting the .onuoin link in tor.

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

@THe KiNG, do you know if there will be a more detailed changelog/readme file?

 

I noticed that I had to use the DisableNvidiaInjection attribute with this version, I never had to use it before. I have a GTX 970.

 

Thanks

Nvidia injection is on "transition" to full driver implementation, it may have some failure since it was tested on a limited boards, anyway injection is not required to get minimal stuff working on OSX it was left on especial to get feedback for what boards are working/not.

So you can disable the injection using the DisableNvidiaInjection  variable, yes eventually, someone will write an updated changelog/readme...

You can also use the new HermitShell SETVAR to add boot-args and complete disable nvidia if required...

@THe KiNG: Can i send you the Dump per PM? Is this ok for you? 

Yes

Link to comment
Share on other sites
pmcnano
pmcnano
Posted
Posted

Nvidia injection is on "transition" to full driver implementation, it may have some failure since it was tested on a limited boards, anyway injection is not required to get minimal stuff working on OSX it was left on especial to get feedback for what boards are working/not.

So you can disable the injection using the DisableNvidiaInjection  variable, yes eventually, someone will write an updated changelog/readme...

You can also use the new HermitShell SETVAR to add boot-args and complete disable nvidia if required...

Yes

 

Awesome man. Yes I used DisableNvidiaInjection and it worked fine. Before disabling it I would get nasty output from the videocard, I connected via VNC and it detected 3GB of vram instead of 4 and I knew it was the injection.

 

Thanks for taking the time to answer my questions.

 

Has anybody tested el capitan? Do you think this new ozmosis has any kind of USB fixes? I haven't tested El Cap final (Im using last beta). When I installed with old ozmosis I had usb problems that's why im asking.

  • Like 1
Link to comment
Share on other sites
unexpected_eof
unexpected_eof
Posted
Posted

If anyone is interested in the new Defaults.plist for 1669:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
	<dict>
		<key>BootEntryTemplate</key>
		<string>$label</string>
		<key>DarwinCoreStorageTemplate</key>
		<string>$label</string>
		<key>DarwinDiskTemplate</key>
		<string>$label</string>
		<key>DarwinRecoveryDiskTemplate</key>
		<string>$label ($platform.$major.$minor)</string>
		<key>LinuxDiskOptionTemplate</key>
		<string>initrd=$initramfs root=$root ro quiet</string>
		<key>LinuxDiskTemplate</key>
		<string>Linux $build</string>
		<key>LinuxRescueDiskTemplate</key>
		<string>Linux Rescue</string>
		<key>LinuxRescueOptionTemplate</key>
		<string>initrd=$initramfs root=$root ro quiet</string>
	</dict>
	<key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
	<dict>
		<key>BaseBoardAssetTag</key>
		<string>Base Board Asset Tag#</string>
		<key>BaseBoardSerial</key>
		<string>CK84593EXYL</string>
		<key>BiosDate</key>
		<string>02/29/08</string>
		<key>BiosVersion</key>
		<string>MP31.88Z.006C.B05.0802291410</string>
		<key>BoardVersion</key>
		<string>Proto1</string>
		<key>ChassisAssetTag</key>
		<string>Asset Tag#</string>
		<key>EnclosureType</key>
		<integer>7</integer>
		<key>FirmwareFeatures</key>
		<integer>2147488791</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>3221487415</integer>
		<key>FirmwareRevision</key>
		<integer>65546</integer>
		<key>FirmwareVendor</key>
		<string>Apple</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>ProcessorSerial</key>
		<string>CK0020DZE1D</string>
		<key>ProductFamily</key>
		<string>MacPro</string>
		<key>ProductId</key>
		<string>Mac-F42C88C8</string>
		<key>ProductName</key>
		<string>MacPro3,1</string>
		<key>SystemSKU</key>
		<string>System SKU#</string>
		<key>SystemSerial</key>
		<string>CK84593EXYL</string>
		<key>SystemVersion</key>
		<string>1.0</string>
	</dict>
	<key>Timestamp</key>
	<integer>0</integer>
	<key>Version</key>
	<string>1.0.1</string>
</dict>
</plist>
  • Like 2
Link to comment
Share on other sites
Aigors
Aigors
Posted
Posted

Hi, with this new release i have to use "vanilla el capitan usb stick" or i have to manipulate the original el capitan installation media? 

Many thanks 

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

It may be even better if you attach the plist file. 

Thanks!

 

Or you could download Coderush’s UEFIExtract tool then load up terminal and run

$ ./UEFIExtract /path/to/Z77MXQUOAOS.H2N.OZ1669M.ROM

 

Then drill down to the relevant section of the resulting expanded directory:

 

Z77MXQUOAOS.H2N.OZ1669M.ROM.dump/2\ BIOS\ region/2\ 8C8CE578-8A3D-4F1C-9935-896185C32DD3/0\ FV_MAIN_NESTED/0\ Compressed\ section/0\ Volume\ image\ section/0\ 8C8CE578-8A3D-4F1C-9935-896185C32DD3/191\ OzmosisDefaults

 

and open the 0\ Compressed\ section/0\ Raw\ section/body.bin file in a text editor.

  • Like 5
Link to comment
Share on other sites
bs0d
bs0d
Posted
Posted

here's an untouched version (note the hex numbers used in <integer>)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Version</key>
	<string>1.0.1</string>
	<key>Timestamp</key>
	<integer>0</integer>
	<key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
	<dict>
		<key>BiosVersion</key>
		<string>MP31.88Z.006C.B05.0802291410</string>
		<key>BiosDate</key>
		<string>02/29/08</string>
		<key>ProductName</key>
		<string>MacPro3,1</string>
		<key>ProductFamily</key>
		<string>MacPro</string>
		<key>SystemVersion</key>
		<string>1.0</string>
		<key>SystemSerial</key>
		<string>CK84593EXYL</string>
		<key>ProductId</key>
		<string>Mac-F42C88C8</string>
		<key>BoardVersion</key>
		<string>Proto1</string>
		<key>BaseBoardSerial</key>
		<string>CK84593EXYL</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>ProcessorSerial</key>
		<string>CK0020DZE1D</string>
		<key>SystemSKU</key>
		<string>System SKU#</string>
		<key>BaseBoardAssetTag</key>
		<string>Base Board Asset Tag#</string>
		<key>ChassisAssetTag</key>
		<string>Asset Tag#</string>
		<key>EnclosureType</key>
		<integer>7</integer>
		<key>FirmwareFeatures</key>
		<integer>0x80001417</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>0xC003ff37</integer>
		<key>FirmwareRevision</key>
		<integer>0x0001000A</integer>
		<key>FirmwareVendor</key>
		<string>Apple</string>
	</dict>
	<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
	<dict>
		<key>BootEntryTemplate</key>
		<string>$label</string>
		<key>DarwinDiskTemplate</key>
		<string>$label</string>
		<key>DarwinRecoveryDiskTemplate</key>
		<string>$label ($platform.$major.$minor)</string>
		<key>DarwinCoreStorageTemplate</key>
		<string>$label</string>
		<key>AndroidDiskTemplate</key>
		<string>$label</string>
		<key>AndroidDiskOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string>
		<key>LinuxDiskTemplate</key>
		<string>$label $build</string>
		<key>LinuxDiskOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid ro</string>
		<key>LinuxRescueDiskTemplate</key>
		<string>$label Rescue</string>
		<key>LinuxRescueOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid ro</string>
	</dict>
	<key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
	<dict>
		<key>csr-active-config</key>
		<integer size=32>0x0</integer>
	</dict>
</dict>
</plist>
  • Like 4
Link to comment
Share on other sites
Aigors
Aigors
Posted
Posted

 

It's used in the same way as the other DiskOptionTemplate variables for Ozmosis to know in which format to create boot options for that specific OS.

 

I need to read some doc about it :D i have a lot of lack of knoweledge 

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

The $label is like a macro for what gets used for the name of the boot entry. $label is the volume name.
 
For an example, I have an OS X 10.11.1 system named MainSystem.
If I set:

    <key>DarwinDiskTemplate</key>
    <string>$label ($platform.$major.$minor)</string>

in my defaults plist and reset Ozmosis then on next boot, if I press F8 (Asus mono) to show boot menu I will see the following entry in the list:
MainSystem (10.11.1)
 
or if I set:

<key>DarwinDiskTemplate</key>
<string>$label</string>

I would see:
MainSystem

  • Like 2
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...