Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

lexb
lexb
Posted
Posted

Okay, so what I found for the HD400 (i7-3770K) was the following:

		<key>AAPL,ig-platform-id</key>
		<integer>0x01620005</integer>
		<string>Intel HD Graphics 4000</string>

I have no idea if specific iterations of the HD4000 CPUs have different codes. I'm not really sure how to verify, or find more details. I spent around 40 minutes looking it up but kept getting unrelated results.

---

I don't have the videocard yet. Can you tell me, does changing these values:

Framebuffer, disable AtiInjection?True, disable IntelInjection? False, diss-Nvid?True

before having the card cause the onboard Intel graphics to have problems?

I will have to use the onboard graphics for around a week before buying/receiving the card.

---

I looked it up, and VoodooHDA relates to audio. I plan to use the regular audio output from the TRS output, but plan to use HDMI audio output in the future, if I'm able to. Can you tell me the scenario where someone would want to DisableVoodooHDA?

---

Lastly, I do not know what to put in for:

        <key>ProductId</key>
        <string>xxxxxxxxxxxxxxxx</string>

        <key>HardwareAddress</key>
        <string>xx:xx:xx:xx:xx:xx</string>

Were you stating that I don't need to change those 2 entries? I assume from your post that putting in the ROM entry as I did will work properly.

Cheers.

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

As know the things on your plist file should now work, disabling ATI set true, if you don't have it, same thing here for Nvidia, audio same  but i'm not experimented on that thing of audio, what i know is to set it to False if you're planing to use it, HDMI, you will have to look at the Readme.md for that XMASS plist tweakS, so here's:

Because almost everything was changed, improved, re-factored and bug-fixed since last release,
here are highlighted the most important ones for the end-user:

Start-up HotKeys
================

 'Function'        || 'Shortcut'           || 'Notes'
===================||======================||=========
 Disable Ozmosis   ||  Escape              ||  Press at start-up, screen will flash red to indicate Ozmosis is disabled.
 Reset NVRAM       ||  Option+Command+P+R  || From F12 menu, Ozmosis GUI, Shell or BIOS Setup.
 Start Ozmosis GUI ||  Option/Home         || It can be controlled with mouse only for now.
 Safe Boot Mode    ||  Shift               ||
 Verbose Mode      ||  Command+V           ||
 Single-User Mode  ||  Command+S           ||
 32 Bit Boot Mode  ||  3+2                 || Start Up In 32 Bit Mode
 64 Bit Boot Mode  ||  6+4                 || Start Up In 64 Bit Mode


Mac/PC Keyboard Legend
======================

'Mac' Key  || 'PC' Key
 Option    || Alt
 Command   || WinLogo


Added the ability to control graphics and audio injection using NVRAM variables, complete list of variables:

Default Settings 1F8E0C02-58A9-4E34-AE22-2B63745FA101
======================================================

 'Key'                        || 'Value' || 'Note/Example'
==============================||=========||==================================
 AcpiLoaderMode               || INTEGER || Control ACPI Loader
 UserInterface                || BOOLEAN || Display User Interface/GUI
 TimeOut                      || INTEGER || Time-out In Seconds
 DisableAtiInjection          || BOOLEAN || De/activate ATI GFX device property injection
 AtiFramebuffer               || STRING  || Name of the specific ATI framebuffer
 DisableNvidaInjection        || BOOLEAN || De/activate Nvidia GFX device property injection
 DisableIntelInjection        || BOOLEAN || De/activate Intel GFX device property injection
 DisableVoodooHda             || BOOLEAN || Disables loading VoodooHDA from firmware
 EnableVoodooHdaInternalSpdif || BOOLEAN || Enable/Disable onboard S/PDIF header when using VoodooHDA from firmware
 DisableBootEntriesFilter     || BOOLEAN || Disables filtering of firmware generated boot entries
 AAPL,snb_platform_id         || INTEGER ||
 AAPL,ig-platform-id          || INTEGER ||
 BootEntryTemplate            || STRING  || $label $guid
 DarwinDiskTemplate           || STRING  || $label $platform $major $minor $build
 DarwinRecoveryDiskTemplate   || STRING  || $label $platform $major $minor $build

Examples:
=========

  !! Note on VoodooHDA, it covers ONLY the onboard codec and is enabled for the moment only for ALC892/ALC1150 !!
  !! For discrete graphics HDMI/DP audio AppleHDA is used instead. Those who use internal GPU (IGPU) only will !!
  !! have to disable VoodooHda and use AppleHda for HDMI/DP audio                                              !!

  To Disable loading VoodooHda.kext from Firmware

    sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda=%01

  To Enable loading VoodooHda.kext from Firmware

    sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda=%00


 Changing ATI Framebuffers
=========================

  sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer=Futomaki

 Or based on VendorSubsystemId

  sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer10029440=Futomaki

 Or based on pci addressing

  sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer00.01.00=Futomaki

Changing AAPL,ig-platform-id
============================

  sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AAPL,ig-platform-id=0x01620005

Changing AcpiLoader Mode
============================

  Add The Following Values Together For Default Acpi Loader Mode

  ACPI_LOADER_MODE_DISABLE        0x00000000
  ACPI_LOADER_MODE_ENABLE         0x00000001
  ACPI_LOADER_MODE_DUMP           0x00000002
  ACPI_LOADER_MODE_WINDOWS        0x00000008
  ACPI_LOADER_MODE_UPDATE_LEGACY  0x00000040

  Default Value : ACPI_LOADER_MODE_ENABLE | ACPI_LOADER_MODE_DARWIN | ACPI_LOADER_MODE_UPDATE_LEGACY = 0x45

  To Change

  sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiLoaderMode=0x45

Note: They can also be controlled by using Defaults.plist placed on boot hard-drive efi system partition and path is /EFI/OZ/Defaults.plist, see bellow for example.

WARNING! Defaults.plist will override the one found in firmware and values are used only if variables are not already added.
For example if you want to set BiosVersion using Defaults.plist and was already set by Defaults from Firmware, you will need
to do a 4 finger NVRAM reset or delete the BiosVersion variable from shell, for the new one to be used.

Default Settings Example of Modifications on Defaults.plist
===========================================================

// If AcpiLoaderMode NEEDS to be changed, change second line, put desired value, then add both line in Defaults.plist
<key>AcpiLoaderMode</key>
<integer>0x45</integer>

// If UserInterface NEEDS to be enabled on every boot, change second line and set to true, then add both line in Defaults.plist
<key>UserInterface</key>
<false/>

// If TimeOut NEEDS to be changed, change second line and put desired value in seconds, then add both line in Defaults.plist
<key>TimeOut</key>
<integer>5</integer>

// If DisableAtiInjection NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>DisableAtiInjection</key>
<false/>

// If AtiFramebuffer NEEDS to be changed, modify second line bellow and set to correct one, then add both line in Defaults.plist
<key>AtiFramebuffer</key>
<string>ReplaceMe</string>
!! WARNING DisableAtiInjection needs to be set to false to function !!

// If DisableNvidaInjection NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>DisableNvidaInjection</key>
<false/>

// If DisableIntelInjection NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>DisableIntelInjection</key>
<false/>

// If AAPL,snb_platform_id NEEDS to be changed, change second line bellow and set to correct one, then add both line in Defaults.plist
<key>AAPL,snb_platform_id</key>
<integer>0x00030010</integer>
!! WARNING DisableIntelInjection needs to be set to false to function !!

// If AAPL,ig-platform-id NEEDS to be changed, modify second line bellow and set to correct one, then add both line in Defaults.plist
<key>AAPL,ig-platform-id</key>
<integer>0x0166000A</integer>
!! WARNING DisableIntelInjection needs to be set to false to function !!

// If DisableVoodooHda NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>DisableVoodooHda</key>
<false/>

// If EnableVoodooHdaInternalSpdif NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>EnableVoodooHdaInternalSpdif</key>
<false/>
!! WARNING DisableVoodooHda needs to be set to false to function !!

// If DisableBootEntriesFilter NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>DisableBootEntriesFilter</key>
<false/>
  • Like 1
Link to comment
Share on other sites
lexb
lexb
Posted
Posted

Hello again,

To verify; I dont need to change ProductId or HardwareAddress from the x's to actual values?

I should place the file in "EFI/Oz/" Correct?

Do I need to rename the file from OzmosisDefaults.plist to Config.plist or Defaults.plist?

Thanks again for all your assistance, my friend.


Im posting this here just for posterity if anyone else running the i7-3440K with Quo board and no video card as an example.

<?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>AAPL,ig-platform-id</key>
		<integer>0x01620005</integer>
		<string>Intel HD Graphics 4000</string>
		<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>DisableAtiInjection</key>
		<true/>
		<key>DisableIntelInjection</key>
		<false/>
		<key>DisableNvidaInjection</key>
		<true/>
		<key>DisableVoodooHda</key>
		<true/>
		<key>LinuxDiskOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid ro</string>
		<key>LinuxDiskTemplate</key>
		<string>$label $build</string>
		<key>LinuxRescueDiskTemplate</key>
		<string>$label Rescue</string>
		<key>LinuxRescueOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid ro</string>
		<key>TimeOut</key>
		<integer>5</integer>
		<key>UserInterface</key>
		<true/>
	</dict>
	<key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
	<dict>
	    <key>ROM</key>
        <data>rC3ClxDQ</data>
		<key>BaseBoardAssetTag</key>
		<string>Base Board Asset Tag#</string>
		<key>BaseBoardSerial</key>
		<string>C022104054NDNJKCB</string>
		<key>BiosReleaseDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>
		<key>BoardType</key>
		<integer>10</integer>
		<key>ChassisAssetTag</key>
		<string>iMac-Aluminum</string>
		<key>EnclosureType</key>
		<integer>13</integer>
		<key>FirmwareFeatures</key>
		<integer>3759006007</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>
		<key>FirmwareVendor</key>
		<string>Apple</string>
		<key>HardwareAddress</key>
		<string>xx:xx:xx:xx:xx:xx</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>ProductFamily</key>
		<string>iMac</string>
		<key>ProductId</key>
		<string>xxxxxxxxxxxxxxxx</string>
		<key>ProductName</key>
		<string>iMac13,1</string>
		<key>SystemSKU</key>
		<string>System SKU#</string>
		<key>SystemSerial</key>
		<string>C02HD2I6DNCT</string>
		<key>SystemVersion</key>
		<string>1.0</string>
	</dict>
	<key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
	<dict>
		<key>boot-args</key>
		<string>darkwake=0</string>
		<key>csr-active-config</key>
		<integer>127</integer>
	</dict>
	<key>Timestamp</key>
	<integer>0</integer>
	<key>Version</key>
	<string>1.0.1</string>
</dict>
</plist>
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

 

Hello again,

To verify; I dont need to change ProductId or HardwareAddress from the x's to actual values?

I should place the file in "EFI/Oz/" Correct?

Do I need to rename the file from OzmosisDefaults.plist to Config.plist or Defaults.plist?

Thanks again for all your assistance, my friend.

Im posting this here just for posterity if anyone else running the i7-3440K with Quo board and no video card as an example.

<?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>AAPL,ig-platform-id</key>
		<integer>0x01620005</integer>
		<string>Intel HD Graphics 4000</string>
		<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>DisableAtiInjection</key>
		<true/>
		<key>DisableIntelInjection</key>
		<false/>
		<key>DisableNvidaInjection</key>
		<true/>
		<key>DisableVoodooHda</key>
		<true/>
		<key>LinuxDiskOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid ro</string>
		<key>LinuxDiskTemplate</key>
		<string>$label $build</string>
		<key>LinuxRescueDiskTemplate</key>
		<string>$label Rescue</string>
		<key>LinuxRescueOptionTemplate</key>
		<string>initrd=$initfs root=UUID=$uuid ro</string>
		<key>TimeOut</key>
		<integer>5</integer>
		<key>UserInterface</key>
		<true/>
	</dict>
	<key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
	<dict>
	    <key>ROM</key>
        <data>rC3ClxDQ</data>
		<key>BaseBoardAssetTag</key>
		<string>Base Board Asset Tag#</string>
		<key>BaseBoardSerial</key>
		<string>C022104054NDNJKCB</string>
		<key>BiosReleaseDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>
		<key>BoardType</key>
		<integer>10</integer>
		<key>ChassisAssetTag</key>
		<string>iMac-Aluminum</string>
		<key>EnclosureType</key>
		<integer>13</integer>
		<key>FirmwareFeatures</key>
		<integer>3759006007</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>
		<key>FirmwareVendor</key>
		<string>Apple</string>
		<key>HardwareAddress</key>
		<string>xx:xx:xx:xx:xx:xx</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>ProductFamily</key>
		<string>iMac</string>
		<key>ProductId</key>
		<string>xxxxxxxxxxxxxxxx</string>
		<key>ProductName</key>
		<string>iMac13,1</string>
		<key>SystemSKU</key>
		<string>System SKU#</string>
		<key>SystemSerial</key>
		<string>C02HD2I6DNCT</string>
		<key>SystemVersion</key>
		<string>1.0</string>
	</dict>
	<key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
	<dict>
		<key>boot-args</key>
		<string>darkwake=0</string>
		<key>csr-active-config</key>
		<integer>127</integer>
	</dict>
	<key>Timestamp</key>
	<integer>0</integer>
	<key>Version</key>
	<string>1.0.1</string>
</dict>
</plist>

 

 

Rename this OzmosisDefaults to Defaults.plist and put it in Efi\Oz\Defaults.plist, but i don't know if you have to add darkwake=0 for QUO board, all things should work OOTB

Link to comment
Share on other sites
lexb
lexb
Posted
Posted

This macOS update process has been brutal. I kept having issues getting the High Sierra update to run at the BIOS screen
I was, at least, able to get El Capitan installed.
I realized after looking some stuff up, that you can’t have the old Mac Pro system profile or High Sierra wont install. I used the following commands in Terminal to update that info:
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion=xxxxxxxxxxxxxxxxxxxxxxxxxxx
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName=iMac13,1
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=xxxxxxxxxxxxxxxxx
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily=iMac
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId=Mac-xxxxxxxxxxxxxxxxxx
Updating to El Capitan killed the onboard audio (regardless of whether I have “DisableVoodooHda” set true or false) and updating the SMBIOS detai;s seemed to have killed my PCI Express bluetooth card's functionality as well (It’s a bluetooth card from a Mac).
Luckily, I had an old wired mouse sitting around so I can still work on the machine, but there is now no audio or bluetooth. Arghhhh.

PS: One thing I hadn’t brought up before, is that I was never able to get the Apple Store to allow me to download the full High Sierra installer, so I used this High Sierra patcher tool to download the full installer: http://dosdude1.com/highsierra/
I didn’t utilize the patching function as I didn’t need it, but when you run that patcher app, it happens to have a way to download the full installer under the “Tools” menu.
I guess I’m just going to try to update using the 19mb download and see what happens. At this point, I'm having a hard time figuring out any other ideas or how to proceed.


But this file is corrupt!

 

What do you mean?

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

Did you copy the content of the defaults.plist from the content i've posted? If so this is why!

Run an plist editor app and start from it a fresh one, never copy the content from the code given because the script is not the same!

 

 

Sent from ammoune78's iPhone using Tapatalk

Link to comment
Share on other sites
lexb
lexb
Posted
Posted

Thanks again. At this point, I'm feeling pretty confused, to be honest. I wasn't aware that I had to use a Plist editor. I have Plist Edit Pro now, and opened the file you provided to edit it. I started the whole process over again for getting a serial etc. in the Clover Configurator, because my serial on checkcoverage.apple.com/us/en/ showed as registered to someone else. So I repeated the steps you provided here:

 

CloverConfigurator\SystemParameters=>Generate NEW:custom UUID
Copy it and paste it over: SMBios\SmUUID
Copy from there Board Serial Number
Now go to RT Variables and paste it over MLB, Now click generate,
you will have new ROM to put on ROM in OzmosisDefaults
Same thing for MLB : BaseBoardSerial

and here:

 

iMac 13,2
FirmwareFeatures: e001f537 & FirmwareFeaturesMask: e003ff37
Then it will be as
FirmwareFeatures: 37f501e0 & FirmwareFeaturesMask: 37ff03e0
Then convert it to integer
"FirmwareFeatures: 938 803 680 & FirmwareFeaturesMask: 939 459 552" this is what you have to put in the plist as number
Go to clover configurator and generate new serial for your board as iMac 13,2 copy paste the things on your OzmosisDefaults.Plist

I had issues though. The Rom I got is way different than I got last time, as it was only like 5 digits previously but it now like 12 digits:
ROM: F63278BA1F4D
Also the firmware features and firmware features mask ; Am I just supposed to take the numbers from Clover configurator and convert them to decimal?
Firmware Features: 0xE00DE137=3759006007
Firmware Features Mask: 0xFF1FFF3F=4280287039

I don't know what I'm supposed to put for Firmware Revision or SystemSKU.
I'm really lost, man. I don't know what I'm doing and am not a coder.
I have the defaults.plist filled out to the best of my understanding, but it doesn't appear to be correct.

I know I've taken a bunch of your time. My apologies for my lack of understanding.

post-2326580-0-61842100-1513346825_thumb.png

post-2326580-0-76244800-1513346865_thumb.png

Defaults.zip

Link to comment
Share on other sites
uglyJoe
uglyJoe
Posted
Posted

There is no 'ROM' key with Ozmosis. From Pavo's guide:

 

(Remember ROM must be 12 digits HEX and MLB must be 17 digits)

ROM:

Clover config.plist:

<key>ROM</key>

<data>xxxxxxxxxxx</data>

OzmosisDefaults.plist:

<key>HardwareAddress</key>

<string>xx:xx:xx:xx:xx:xx</string>

You can use your MAC-Address for this.

 

 

To get iMessage working it's may good to have a

<key>HardwareSignature</key>
<string>A2A353F1-8BE9-480F-9596-2C43EC9895E0</string> 
Generate a unique one with 'uuidgen' from Terminal.app

 

 

SystemSKU is IMHO the Apple Part Number - something like MD389LL/A - and not really necessary.

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

There is no 'ROM' key with Ozmosis. From Pavo's guide:

 

 

You can use your MAC-Address for this.

 

 

To get iMessage working it's may good to have a

<key>HardwareSignature</key>
<string>A2A353F1-8BE9-480F-9596-2C43EC9895E0</string> 
Generate a unique one with 'uuidgen' from Terminal.app

 

 

SystemSKU is IMHO the Apple Part Number - something like MD389LL/A - and not really necessary.

 

 

Are you sure about ROM? Because I've got it from an Oz friend!

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

So here premature bin release EDK2 version of rEFIt dbounce (https://sourceforge.net/p/refit/code/HEAD/tree/trunk/refit/dbounce/). The drv will load efi drivers from specified path / from sorted array of paths and launch specified efi app / driver.

DriversPath: Drivers full path to scan & load (Ignored with DriversList).
DriversList: Array of full individual driver path.
LoaderPath: Main driver / app to load.
NoVerbose: Suppress verbose msg by drivers (eg apfs).
Preferences->Debug: Show more dbg msg / NVRAM boot-args "-DBounceDbg".
Preferences->Off: Disable this driver / NVRAM boot-args "-DBounceOff".
Preferences->SaveLogToFile: Save log to path\DBounceLog.txt / NVRAM boot-args "-DBounceLog".
bcfg driver add n DBounce.efi "DBounce"

https://1drv.ms/f/s!AjxLshYT0HDug1WrRel8gnipT6HW (bin + plist + log + this text).

 

Also like to UP a good project "rEFInd feat. Ozmosis" -> http://www.insanelymac.com/forum/topic/330421-refind-feat-ozmosis/?do=findComment&comment=2550559

  • Like 2
Link to comment
Share on other sites
uglyJoe
uglyJoe
Posted
Posted

ROM and MLB are working in default.plist

under this section

Defaults:4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14

Ok, thank you for pointing this out!

 

So we can use ROM or HardwareAddress

and MLB or BaseBoardSerial?

 

 

So here premature bin release EDK2 version of rEFIt dbounce (https://sourceforge.net/p/refit/code/HEAD/tree/trunk/refit/dbounce/). The drv will load efi drivers from specified path / from sorted array of paths and launch specified efi app / driver.

...

I did a quick test with VirtualBox and it was loading hfsplus, apfs and ozmosis from path and array. Very cool!

DBounce.plist stored in ESP/Efi.

 

Is this working from the bios, too? If yes - can you build a version that is loading from path by default and debug / logging disabled.

Than we need no config, dbounce in bios and other drivers like apfs in the ESP.

 

Thank you!

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

@uglyJoe: you should verify your things before posting comments to disapoint someone! This is what i understood from your posts, be clear or keep calm! We aren't in war but in Forum, which it meant to give help, not shutting down people. I'm posting to help the guy, you just keep quoting my posts, what is that  :angry: 

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

So we can use ROM or HardwareAddress

and MLB or BaseBoardSerial?

 

Better use the latter ones because they end up in SMBIOS tables too. MLB/ROM are not used by Oz directly

 

@uglyJoe: you should verify your things before posting comments to disapoint someone! This is what i understood from your posts, be clear or keep calm! We aren't in war but in Forum, which it meant to give help, not shutting down people. I'm posting to help the guy, you just keep quoting my posts, what is that  :angry:

 

What the hell are you talking about?

  • Like 1
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)

Better use the latter ones because they end up in SMBIOS tables too. MLB/ROM are not used by Oz directly

 

 

What the hell are you talking about?

 

There's no hell Download-Fritz, look at my posts he don't reply to the guy he only keep posting my things, I've seen that from my first quote for he's problem when Oz for High Sierra was for testing! Excuse me give help or keep calm, if you're sure i'm doing something wrong then it will be a pleasure to understand my mistakes, but not like that! I give help if I know, he know how to do Defaults.plist, but why not posting it instead of quoting me?

 

This makes me nervous, but forget!

Edited by ammoune78
Link to comment
Share on other sites
lexb
lexb
Posted
Posted

I appreciate the help from all of you guys. I think there is just a miscommunication, as I think you are all with the best intentions. Sometimes text and quotes doesnt convey the intended tone. Thank you all, guys. Ill try to incorporate all the info you guys gave to get the MAC running again and updated.

Link to comment
Share on other sites
uglyJoe
uglyJoe
Posted
Posted

@ammoune78

I'm sorry but I really don't understand, what's the problem here.

 

My first post in this context was addressed at you and anybody following this thread because I "discovered" TheRacerMaster's super cool script some month ago and didn't found much about it on IM. If you are aware of this script already - it's fine but where is the problem?

 

My second post was addressed to lexb because he posted a corrupt plist and ask some specific questions that are all covered in the link I posted.

And lexb wrote, that he normally is good in puzzling things together.

 

The third post was meant as a warning because lexb wrote that he has only one machine running and the file (you reposted!) was corrupt.

 

In the forth post I tried to give some last hints that may be relevant and not answered until that.

I wasn't aware of the 'ROM' key and never read about it in any of the guides and it doesn't make sense to have two keys for the same value and I really could believe this if I see it in source code ;)

Link to comment
Share on other sites
uglyJoe
uglyJoe
Posted
Posted

Better use the latter ones because they end up in SMBIOS tables too. MLB/ROM are not used by Oz directly

...

Do you now some more about the "SystemSerial"?

 

From ozmosis with a hex-editor:

    <key>SystemSerial</key>
    <string>CK84593EXYL</string>
    <key>BaseBoardSerial</key>
    <string>CK84593EXYL</string>
    <key>ProcessorSerial</key>
    <string>CK0020DZE1D</string>

"SystemSerial" has the same value like "BaseBoardSerial".

So MLB = SystemSerial = BaseBoardSerial and best to use BaseBoardSerial? 

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

 

 

Do you now some more about the "SystemSerial"?

 

From ozmosis with a hex-editor:

    <key>SystemSerial</key>
    <string>CK84593EXYL</string>
    <key>BaseBoardSerial</key>
    <string>CK84593EXYL</string>
    <key>ProcessorSerial</key>
    <string>CK0020DZE1D</string>
"SystemSerial" has the same value like "BaseBoardSerial".

So MLB = SystemSerial = BaseBoardSerial and best to use BaseBoardSerial?

No, it's not the same, don't go after sample data ;)

SystemSerial = "Mac Serial Number"

BaseBoardSerial = MLB = "Logic Board Serial Number"

HardwareAddress = ROM = not even sure

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

 

 

In the forth post I tried to give some last hints that may be relevant and not answered until that.

I wasn't aware of the 'ROM' key and never read about it in any of the guides and it doesn't make sense to have two keys for the same value and I really could believe this if I see it in source code ;)

ROM is the Apple var and HardwareAddress the Oz var... Oz sets the Apple var, if the Oz var exists

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