You were missing a defaults.plist in your ROM...
I reworked your ROM, there you go:
macOS Mojave Ozmosis BETA − OZ167X-XMAX
-
- Erledigt
- kuckkuck
- Erledigt
-
-
-
@seabo1224 please don't quote full posts.. you can write a @'name of the user' instead
-
@kuckkuck I don't think @'seabo1224 's problem caused by where is the ozmosisdefaults located,cause I have same problem with my HD4600,when I want to boot Mojave,I must use only dedicated card,otherwise I'll see the frozen apple logo and no progress bar.
I have told this to @cecekpawon,he said he couldn't do anything.
And in sanelymac,the guy named TypeThree said following:For me it works just normal... I can't say what the problem is and why Mojave refuses to boot for some people when iGPU and dedicated GPU are activated.
I had that problem in the beginning and the only way I could start Mojave with both GPUs, was when I had Mojave as the first boot priority, entered the BIOS and exited it again without saving (the behaviour doesn't make sence to me).
Then I reset my BIOS to defaults and ever since that day I can start Mojave completely normal with both GPUs activated.
Maybe somebody has a clue what this might be about...I have tried many times according to the above methods，but not always works.
-
still stuck in Mac logo
When you were using your dedicated GPU, did you disable your iGPU in your BIOS?@taoarch I know of this problem but as far as I am concerned it's only present when both iGPU and ded. GPU are used. Normally the MojaveBoot should work when only one GPU is activated, so it should work too, when only the HD4000/HD4600 is present...
The whole issue is very weird because the error appears so early in the boot process that I don't think that any driver or AGDP could possibly be responsible for that. Also I really don't understand why Clover users don't face this issue. There has to be some patch that Clover automatically applies, that Ozmosis doesn't perform (maybe MSR or Lapic but I tested that and that wasn't the issue).
Also I experienced that issue too but very inconsistently. Sometimes the PC would just work as normal with both GPUs and one restart later the Ozmosis Logo would freeze, no verbose output (too early in the boot process?)
I don't know if this could have anything to do with Ozmosis internal AptioFix or similar. I don't know if there's a difference for AptioFix (or the problematic memory-sections) if the iGPU is activated or not. Maybe @Download-Fritz could help us with that.
The fact though, that the issue is that inconsistent, let's me think that it could be AF related... -
I don't know if this could have anything to do with Ozmosis internal AptioFix or similar. I don't know if there's a difference for AptioFix (or the problematic memory-sections) if the iGPU is activated or not. Maybe @Download-Fritz could help us with that.
I know of an Oz AF bug which, in very unlikely conditions, could cause freezes, reboots or anything really. I can't really recommend keeping to use it at this point.
If you want to be sure, disable Oz' AF via "-norelocate" and load AptioMemoryFix instead, while that might cause issues on its own... -
-
@Download-Fritz Excuse me，how to "disable Oz' AF via "-norelocate" and load AptioMemoryFix instead"?
I put
" <key>norelocate</key>
<true/>"
under Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101 or Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82
in ozmosisdefaults.plist ,then covert it and aptiomemoryfix.efi to ffs,insert them to bios ,but it doesn't work at all!
thx！ -
-
No I did not try it but I would redommend loading AptioFix with load (Shell) for testing purposes. Also I'd recommend starting boot.efi manually through shell with the selected boot options: fsX: ... boot.efi -norelocate
I don't know if this could have anything to do with Ozmosis internal AptioFix or similar.
Since the issue is so early in the boot process, I have the feeling that we are on the right track... -
-
Happy to hear that feedback! Enjoy!
-
IQSV
If I boot from the boot menu, then after the appearance of the apple, it will immediately restart. But if I am loading from Hermit Shell, as in the screenshot, the system is loading. Thought that a problem with Darboot. Already removed it from the BIOS. The problem is not in it. I now wonder why it loads from Shell, and if I add an entry to the boot menu, then no. Any ideas? AptioFix and -norelocate does not work.
-
Does the issue also appear when you disable the iGPU in your BIOS?
With the IGPU disabled, everything is working fine.
-
With the IGPU disabled, everything is working fine.
Most likely wrong ApplePlatformID and/or wrong RAM amount for the iGPU.
Had this happen to me as well. With the wrong ID and right amount of RAM for the iGPU I got reboots. Also with right ID and wrong amount of RAM.
Addendum:
It doesn't work either...did you try it?
