Jump to content
xpamamadeus

Ozmosis

6,187 posts in this topic

Recommended Posts

Advertisement

You could also put the file into EFI/Boot folder. Afterwards name it BOOTX64.efi if you don't mind. This way it will automatically get added...

Which shell do you use, could you attach it?

Share this post


Link to post
Share on other sites

 

HS DP6  install Success on QUO SysDef iMac 13,2 after changing Defaults.plist

		<key>BiosDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>

 

High Sierra DP7 from DP6 .. nothing to do, just works.

Share this post


Link to post
Share on other sites

High Sierra DP7 from DP6 .. nothing to do, just works.

		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

Share this post


Link to post
Share on other sites
		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

 

 

For 13,2.

post-971914-0-23015700-1503496967_thumb.png

Share this post


Link to post
Share on other sites
		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

 

<key>FirmwareFeatures</key>
<integer>0xE907F537</integer>
<key>FirmwareFeaturesMask</key>
<integer>0xFFFFFFFF</integer>

Share this post


Link to post
Share on other sites

Ok, a fresh question from an old time user. I have a Fusion Disk with Sierra on it booting from Ozmosis (a very old version that allowed for Fusion drives I believe it was 894M) it has served me very well thus far, however with High Sierra I can only get a KP, and it is so fast that It doesn't give me an option to view the error before it scrolls past with a full screen of debug followed by mach restart 3 times.

 

This is on a separate single SATA drive I use for Beta testing on my hack vs beta testing on my MacBook Pro (where I installed the OS on the disk like I did Sierra). All protections are disabled in firmware so it should see the FakeSMC.ffs like Sierra does, and load it.  Any help would be greatly appreciated.

 

HBP

:: Edited ::

After Screencapturing the monitor with my iPhone, the KP is on com.apple.driver.AppleACPIPlatform(6.1)

 

it does pick up FakeSMC but for some reason, the ACPI for Sierra doesn't work for High Sierra?  any thoughts?

Share this post


Link to post
Share on other sites

TY @Kynyo BackDash's post and my German Helped allot, now I just have to get my Nvidia card to be willing to work in something other than Vesa mode and I can begin testing it in earnest.

 

HBP

Share this post


Link to post
Share on other sites

I think I found a solution to the background image issue though it is a work around and have not implemented it. Think what would work is if you load another bootloader like Refind from the firmware volume setting up a background, and from there chain load Ozmosis or your choice of bootloader after from the fs0 or fs1 drive. I've done this virtually in OVMF and I think this is a better option than having Ozmosis load from the firmware. From there it would be theoretically possible to mod Clover to run from the firmware as well with a little work. 

Share this post


Link to post
Share on other sites

Why would you want to run Clover from Firmware? No offense but I think your solution is a little very complicated :|  :D

 

I really like the scripts that THe KiNG posted, they make it really fast setting up new Themes.

But there's one thing that really bothers me and that is that there's no way to setup an image for new OS X versions as Sierra atm. It appears that badges with an even number are supposed to be shown for OS X Installers. The ones with an odd numbers are there for the main OS X version. Following this scheme, Sierra should have the number 17 and the SierraInstaller the number 16. Setting it up like that, the PNG files are loaded but not displayed for Sierra. Instead the GUI shows the Generic.png. Since there's a typo in the Yosemite (Yosimite) badge, I figured that the name of the badge doesn't really matter which can be validated with tests.

The official HorizontalTheme in it's newest version consists of a badge for Sierra. But also here, the badge isn't displayed in the GUI.

This issues was the main reason for me to start this theme discussion which ended with THe KiNG releasing the scripts. But this must be something about Theme implementation in the main driver. Since Sierra is the first OS that behaves like that with badges and also the first OS to have the name "macOS" rather than "OS X", that rename could be a starting point. I don't have any access to source code or anything which is why I can't help myself and am asking this over here. I would love to be able to setup badges for upcoming macOS Versions since I would like to use Ozmosis as long as that is still possible.

Share this post


Link to post
Share on other sites

Why would you want to run Clover from Firmware? No offense but I think your solution is a little very complicated :|  :D

 

I really like the scripts that THe KiNG posted, they make it really fast setting up new Themes.

But there's one thing that really bothers me and that is that there's no way to setup an image for new OS X versions as Sierra atm. It appears that badges with an even number are supposed to be shown for OS X Installers. The ones with an odd numbers are there for the main OS X version. Following this scheme, Sierra should have the number 17 and the SierraInstaller the number 16. Setting it up like that, the PNG files are loaded but not displayed for Sierra. Instead the GUI shows the Generic.png. Since there's a typo in the Yosemite (Yosimite) badge, I figured that the name of the badge doesn't really matter which can be validated with tests.

The official HorizontalTheme in it's newest version consists of a badge for Sierra. But also here, the badge isn't displayed in the GUI.

This issues was the main reason for me to start this theme discussion which ended with THe KiNG releasing the scripts. But this must be something about Theme implementation in the main driver. Since Sierra is the first OS that behaves like that with badges and also the first OS to have the name "macOS" rather than "OS X", that rename could be a starting point. I don't have any access to source code or anything which is why I can't help myself and am asking this over here. I would love to be able to setup badges for upcoming macOS Versions since I would like to use Ozmosis as long as that is still possible.

 

I would do it for the same reason as why you would install Ozmosis in the firmware if not for the fact that every new release would require a new flashing because Clover updates are more frequent than Oz. Of course it makes more sense to leave it on your efi folder. Easier to manage. Its doable as difficult as it is to implement and getting close to have Refind bootloader running off of the firmware such that you would have a graphical boot menu. As far as getting Oz to recognize Sierra and Hi Sierra it would take understanding where on the boot drive and what sector address + phrase Oz is using to verify Yosemite or El Cap or Tiger and replace it with the appropriate keyword for Sierra and replace the old bagdes no one ever uses anymore.

 

Anyhow I've given up playing with the Themes for now. Got 'The Kings' theme files unpacked and modded the compile.bat file to use the Tools I posted earlier. Just compile from the root folder like 'compile.bat Horizontaltheme'. Gave up on getting the background to be utilized though even though the script includes it in there. Though think I understand why Hermitshell wont load from firmware memorymapped volume more than once. I read some bioses will resort the boot menu items and the memory mapped volume address gets displaced due to incorrect formatting.

 

Still got work to do..

Share this post


Link to post
Share on other sites

Hi, i' would like to run ozmosis into a asus P9 x79-e ws modo with a i7 3820 and a gtx 660, i followed instruction, but there is somenthing wrong, i was not able to boot one osx from maverick to sierra, another weird thing, i cant go in verbose mode despite i have -v flag into boot options, here is the bios 

 

Many thanks 

P9X79-OROMUPDATED-OZO.zip

Share this post


Link to post
Share on other sites

Hi, I would ask how is ozmosis in High Sierra, and in general if it gets update over time.

I used ozmosis back on Mavericks days (and I were very happy with it) but when I took the r7 260x it had some trouble with ozmosis (black screen on boot) and I switched to Clover.

Now is a while since my last update (I'm stuck with El Capitan on my main hackintosh), and honestly I'm unhappy with Clover: sometime it doesn't do what I choose on config.plist.

It is becoming more and more complicated over time.

 

The motherboard I'm using is the GA-Z87X-UD4H, that needs only two kext and patched dsdt/ssdt. 

Any advice? 

Share this post


Link to post
Share on other sites

it seems that ozmosis ignore boot args, i have set user interface, timeout 10 , -v amd npci=2000 but still stuck on [PciConfiguration Begin]
Any hints? 

 

Thanks 

Share this post


Link to post
Share on other sites

When you change Defaults.plist you need to reset nvram.

Like that Oz will boot with your new boot args.

 

Fred

Thank you Fred, but it seems that is useless, as i wrote it seems that bootargs is ignored by Osx 

Share this post


Link to post
Share on other sites

Hi, I would ask how is ozmosis in High Sierra, and in general if it gets update over time.

I used ozmosis back on Mavericks days (and I were very happy with it) but when I took the r7 260x it had some trouble with ozmosis (black screen on boot) and I switched to Clover.

Now is a while since my last update (I'm stuck with El Capitan on my main hackintosh), and honestly I'm unhappy with Clover: sometime it doesn't do what I choose on config.plist.

It is becoming more and more complicated over time.

 

The motherboard I'm using is the GA-Z87X-UD4H, that needs only two kext and patched dsdt/ssdt. 

Any advice? 

 

 

I have the GA-Z87X-UD5H and would advise you mod your MATS table because your going to have kernel panics. Few pages back I detailed how I was able

to fix that problem on my board and for you should be very similar. Besides that not sure that APFS works at all and you should use HFS+ formated installation.

Share this post


Link to post
Share on other sites

it seems that ozmosis ignore boot args, i have set user interface, timeout 10 , -v amd npci=2000 but still stuck on [PciConfiguration Begin]

Any hints? 

 

Thanks 

It seems that you are disabling NvidiaInjection in OzmosisDefaults and using iMac121.1 SMBios, try enabling NvividiaInjection with npci=0x3000 and using MacPro6.1 SMBios with cpus=2 if x2 CPUs, again if no Web driver use Nvda_drv=0 and 1 if Web driver used.  

Hi, I would ask how is ozmosis in High Sierra, and in general if it gets update over time.

I used ozmosis back on Mavericks days (and I were very happy with it) but when I took the r7 260x it had some trouble with ozmosis (black screen on boot) and I switched to Clover.

Now is a while since my last update (I'm stuck with El Capitan on my main hackintosh), and honestly I'm unhappy with Clover: sometime it doesn't do what I choose on config.plist.

It is becoming more and more complicated over time.

 

The motherboard I'm using is the GA-Z87X-UD4H, that needs only two kext and patched dsdt/ssdt. 

Any advice? 

 

Try enabling AtiInjection from Defaults.plist with the FrameBuffer you are trying to use, disable NvividiaInjection from the Defaults.plist but you still have to patch the PEGP Device in the DSDT.

Share this post


Link to post
Share on other sites

It seems that you are disabling NvidiaInjection in OzmosisDefaults and using iMac121.1 SMBios, try enabling NvividiaInjection with npci=0x3000 and using MacPro6.1 SMBios with cpus=2 if x2 CPUs, again if no Web driver use Nvda_drv=0 and 1 if Web driver used.  

 

Try enabling AtiInjection from Defaults.plist with the FrameBuffer you are trying to use, disable NvividiaInjection from the Defaults.plist but you still have to patch the PEGP Device in the DSDT.

Thanks, but it happens even if i use macpro6.1 , as far you know, is there some connection with wrong smbios and missing reading of bootargs? 

Many thanks 

Share this post


Link to post
Share on other sites

Thanks, but it happens even if i use macpro6.1 , as far you know, is there some connection with wrong smbios and missing reading of bootargs? 

Many thanks 

If always black screen, this is because SATA is not recognized, you have to put patched one in the ESP/Oz or try injecting in BIOS IOAHCIBlockstorage injector instead of Injector.kext, then try other things I've said!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By apianti
      Just so you all know I actually have done something. I have pushed the source to both my github and to sourceforge, please commit to the experimental branch and I will merge it into the stable branch once it is safe. Also, nothing meaningful happens yet so don't get too excited. Only the Visual studio build works right now. I haven't set up the Xcode or Makefile builds yet, I'm trying to do them now.
       
      https://github.com/apianti/Clover
      https://sourceforge.net/p/cloverefiboot/Clover
       
      IA32/X64/ARM/ARM64 testing ISO (6/7/2018): Clover-3.0-experimental.iso
    • By cvad
      Bootdisk Utility Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
×