Jump to content
xpamamadeus

Ozmosis

6,205 posts in this topic

Recommended Posts

Advertisement

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

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!

Let me explain, i have already putted correct ( i think ) smbios into defaults.plist and i have setup bootargs in verbose mode, but, it seems is non recognized by Osx, if i use command+v , start in verbose but it stuck at Pci Confifuration Begin even if add npci=0x3000 or 0x2000 i dont have blank screen, i stuck on apple logo without progress bar, or, with sierra, at forbidden signal 

 

Edit, what do you mean 2 cpus=2? 

do i have to put cpus=2 into bootargs? 

Share this post


Link to post
Share on other sites

Yes SIP also, cpus=1 if only one CPU installed, try this one: attachicon.gifOzmosisDefaults.zip

One little step ahead , now boot ion verbose mode and go ahead, but, after dsmos arrived switch off monitor 

Share this post


Link to post
Share on other sites

Add: nvda_drv=0 into that boot args in the OzmosisDefaults.plist

Edited by ammoune78

Share this post


Link to post
Share on other sites

Add: nvda_drv=0 into that boot args in the OzmosisDefaults.plist

Booting, another info, during boot i saw IOBlueToothHcicontroller not found 

No, same behavior, i have a gtx660 connected via DVI i can try hdmi 

Sorry, forgot to wrote i'm using Yosemite , with sierra i get kernel panic , as i read, suspect MATS table 

This is where stuck

post-840738-0-77105600-1505159695_thumb.jpg

post-840738-0-85161100-1505159707_thumb.jpg

Share this post


Link to post
Share on other sites

You can try this ROM but use it at your own risk...

 

Also use a custom Defaults.plist.

 

P9X79-OROMUPDATED-OZO.rom.zip

 

 

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.

I don't load Ozmosis from the firmware just because I can. If you load every single required driver from EFI by using bcfg, you will have to do it over again once you do a single NVRAM reset. That sucks and thats also why I'd include it in firmware, given that you want to use Ozmosis.

 

 

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.

So you would edit Ozmosis.efi according to what you found out during your research?

Share this post


Link to post
Share on other sites

You can try this ROM but use it at your own risk...

 

Also use a custom Defaults.plist.

 

P9X79-OROMUPDATED-OZO.rom.zip

 

 

I don't load Ozmosis from the firmware just because I can. If you load every single required driver from EFI by using bcfg, you will have to do it over again once you do a single NVRAM reset. That sucks and thats also why I'd include it in firmware, given that you want to use Ozmosis.

 

 

So you would edit Ozmosis.efi according to what you found out during your research?

 

Well I haven't had the time to study the code and modify it to substitute High Sierra Badge for Yosemite or something but I think it's doable.

 

As far as loading a bootloader such as Clover from the firmware I'm close to understanding how to do it as far as I have already been able to load the Refind Bootloader from firmware at least inside an OVMF Qemu virtualized environment.

 

If Oz doesn't come up with an update version soon I'll detail how to do it and release the required efi drivers.

 

Thanks

Share this post


Link to post
Share on other sites

Well I haven't had the time to study the code and modify it to substitute High Sierra Badge for Yosemite or something but I think it's doable.

 

As far as loading a bootloader such as Clover from the firmware I'm close to understanding how to do it as far as I have already been able to load the Refind Bootloader from firmware at least inside an OVMF Qemu virtualized environment.

 

If Oz doesn't come up with an update version soon I'll detail how to do it and release the required efi drivers.

 

Thanks

Do you think is possible put clover into bios? 

amazing project! 

If you want a  "dummy" beta tester keep me in your mind, i can try in X79 chipset and Z97 chipset,  

Share this post


Link to post
Share on other sites

Do you think is possible put clover into bios?

amazing project!

If you want a "dummy" beta tester keep me in your mind, i can try in X79 chipset and Z97 chipset,

Yeah I think it's totally possible. Like I said I already did it with Refind. With Clover It would need to be optimized to fit insides one firmware and a few tweaks to the source code. I'll probably have it going in a couple weeks.

Share this post


Link to post
Share on other sites

It's something weird with Oz and APFS, i use shell to bcfg add apfs.efi from EFI partition, ad bcfg efi dump looks ok, but it doesen't appear in boot manager and i can't understand why. Startup Disk manager from macOS Sierra, says volume can't be blessed. I tried to bless, still not working. Which may be the problem?

Share this post


Link to post
Share on other sites

It´s not enought to add the driver it also has to be connected (on ervery boot) since this driver won´t jumpstart if added with the bcfg command.

Share this post


Link to post
Share on other sites

I converted latest .efi to ffs then inserted into bios, all working flawless. Single downside its that i have to reflash eventually if apfs driver gets updated.

Well, how typically i "connect" the driver?

 

LE: Got it.

 

45f6f08ae9.png

Share this post


Link to post
Share on other sites

As I understand the reason you guys are loading the AFPS driver with bcfg from shell is because just in case a newer version comes out you dont have to reflash? Also there is an issue with load priority of the driver? I mean does not the driver auto load when inserted into the rom? I thought that it did. Also do we have access to the source code? Maybe alter the depex section if thats the case?

 

Thanks

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 dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
    • By cvad
      View File 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.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By ErmaC
      Slice is glad to present a new EFI bootloader.

      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      https://sourceforge.net/projects/cloverefiboot/?source=directory
      There is a WIKI 
      http://clover-wiki.zetam.org/
      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      Post#2 CloverGrower - create Clover by yourself Post#3 Downloads Post#4 Installation of the bootloader Post#5 How to do UEFI boot Post#6 How to use - common words Post#7 Calculator for Automatic DSDT fix Post#8 Instructions for GraphicsInjector Post#9 ATIConnector patching Post#10 Any kexts patching with some Samples Post#11 CustomEDID Post#12 Hiding unnecessary menu entries Post#13 Instruction for DSDT corrections to do DeviceInjection works Post#14 Development Post#15 Themes Post#16 About kexts injection Post#17 Instructions for P- and C-states generator Post#18 Patching DSDT to get Sleep working Post#19 CPU settings and geekbench Post#20 ACPI tables loading Post#21 DSDTmini Post#22 Custom SMBios Post#23 F.A.Q. Post#24 iCloudFix Post#25 Using mouse. Post#26 How to make orange icons to be metallic Post#27 How to make software RAID (by Magnifico) Post#28 How to modify InstallESD.dmg (by shiecldk) Post#29 Config.plist settings Post#30 Using extra kexts and skipping kernelcache Post#31 Choosing EFI drivers Post#32 Configuration files Post#33 Automatic config.plist creating Post#34 Custom DSDT patches Post#35 How to do sleep/wake working with UEFI BOOT Post#36 DeviceID substitution (FakeID) Post#37 Using Custom OS Icons Post#38 Hibernation Post#39 Floating regions Post#41 Property List Editor Post#42 Blocking Bad Kext Post#43 AAPL,slot-name Post#44 FakeCPUID for unsupported CPU Post#45 Multiple Boot Options - to write into UEFI BIOS boot menu Post#46 How to install Windows UEFI Post#47 How to speedup Clover boot Post#48 Info.plist patching Post#49 Arbitrary device injection Post#50 Non-Standard Legacy Boot Files Post#51 Reboot to Windows UEFI from Mac OSX Post#52 Deprecated Features Post#53 Using UDK2018 Post#54 Device Properties Post#55 Scalable themes Post#56 How to search Clover mistakes (bisection) -----------------
       
      Slice:
      I edited all posts in the thread to correspond to actual Clover revision.
      Please install Clover at least 2652 and use new instructions.
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
×