Jump to content
Leoyzen

** Hackintosh ** Tips to make a bare metal MacOS

642 posts in this topic Last Reply

Recommended Posts

Can i use a copy of this now fine working OC EFI also for my Mojave VM's, so is it downwards compatibe ? Or do i need to use a specific older version or some other changes ? (assuming same vanilla OS install for simplicity sake)

Share this post


Link to post

As lockdown is the best time to experiment i just went ahead (after making a few extra zfs snapshots as am not crazy) and migrated all my VM's incl productive to OpenCore.

With a minor hickup to get the Radeon passthru to work (remove your device properties entry from the plist) everyting worked straight out the box with the exact same EFI/plist. Crazy and amazing.

Love it.

Tnx again for all your work. Clover is history......

Share this post


Link to post

@chalbolyNot required. But I'd prefer add it in order to staying the same with standard hackintosh procedure.

Share this post


Link to post

Thanks @Leoyzen.

 

I am currently trying to passthrough my entire Intel USB controller, but macOS does not seem to recognize the devices connected to it, it shows as an USB controller but is not named correctly. I have tried with USBInjectAll.kext and XHCI-unsupported.kext without luck. Do I need to rename the device under DeviceProperties? 244192357_ScreenShot2020-03-31at1_25_01AM.thumb.png.34d2fd095403c106ed7680bedbb0b5a1.png2021241368_ScreenShot2020-03-31at1_25_11AM.thumb.png.f7cced99a67871d34d2f33da494eb865.png1530262788_ScreenShot2020-03-31at1_25_26AM.png.388b5751c79ce1f1f154caaab724fcbb.png  

Share this post


Link to post
Posted (edited)

@Leoyzen I just changed the bus to 0x00 and changed the slot, I can see the controller type is now named S30. I know it must be renamed properly so it can be recognized by the USBInjectAll.kext. How can you rename the device in the config.plist?

Edited by chalboly

Share this post


Link to post

@chalbolyNo, it not related to ACPI name. USBInjectAll find the device by vendor_id and device_id.You should check whether your usb controller (8086_8d2d)  is supported by USBInjectAll.kext.

Share this post


Link to post

@Leoyzen Unfortunately it does not seem to be supported by USBInjectAll.kext.

 

What is strange is that I can see the controller and the devices connected, this controller is internal and the only device is the Bluetooth, but this is not detected at boot but rather later when in macOS and when I open the IOregister app. Of course Bluetooth does not work because it can't be patched by BrcmPatchRAM at boot.

Share this post


Link to post
Posted (edited)

@Leoyzen I decided to just pass through a different USB controller (ASM1042A) and is working fine. Bluetooth is internal USB on my motherboard so I'm just passing through the USB device, works without any patches except that I am having issues with connected devices. If I use AirPods they disconnect after a while or have audio dropouts. Apple Watch unlock works for a moment and then disconnects. Handoff is also intermittent, so something seems off.  Do you know if SSDT patching is required? Map the virtual USB ports correctly depending on the SMBios?

Edited by chalboly

Share this post


Link to post

@chalbolyWe can't map virtual usb ports now.(I can't find a way to do that like standard usb3 ways).So the bluetooth we passthrough is not recoginized as internal which may cause problem.Try using usb bluetooth instead.

Share this post


Link to post

@Leoyzen Thanks, I just tested with a USB Bluetooth device, based on the same chipset BCM920702 which is supported without additional kexts, but the same issue persists. There is audio dropouts when connected to Bluetooth headphones, Continuity works sporadic and Apple Watch unlock does not stay connected to the watch. There are a lot of errors in the logs about this. My Wi-Fi is natively supported (BCM4360). I also moved the USB Bluetooth right next to my devices using an extension. The signal did not improve much (checking with Bluetooth Explorer), and had the same issues, so not sure what else to try.

 

 

Image 4-5-20 at 6.19 PM.jpg

Share this post


Link to post
Posted (edited)

Supplemental update for Catalina 10.15.4 is out, backup your vm and try your luck ;)

Updating now.

 

Update: update was successful, no problems, new version build: 19E287.

Edited by ghost82

Share this post


Link to post

Updated yesterday no problem. Also updated to 0.5.7 opencore too.

Share this post


Link to post
13 hours ago, david279 said:

Updated yesterday no problem. Also updated to 0.5.7 opencore too.

Can u make a pull request in git using 0.5.7?I can't boot with 0.5.7

Share this post


Link to post
34 minutes ago, Leoyzen said:

Can u make a pull request in git using 0.5.7?I can't boot with 0.5.7

Not at home, at work. When i get home tomorrow i will try to git it up. 

Share this post


Link to post

I found it won't boot when I set Target=83(logging to file), it is strange. Can someone test it and give some feedback?

Share this post


Link to post
2 hours ago, Leoyzen said:

I found it won't boot when I set Target=83(logging to file)

Confirmed, happens also with the latest 0.5.8 dev.

Share this post


Link to post
21 minutes ago, chalboly said:

I am running 0.5.7 and have Target set 83.

The release version?

Share this post


Link to post
1 minute ago, ghost82 said:

The release version?

Yes, I replaced the boot files on the EFI partition, added OpenRuntime and removed FWRuntimeServices and updated my config.plist, used OCConfigCompare. There are several new keys I needed to add and two or three that I had to remove. Make sure to remove those old keys, otherwise it won't boot.

 

Just now, Leoyzen said:

@chalbolySo, did it work or not?

It is working for me, I still have Target set to 83 and it is booting.

Share this post


Link to post

My config works good, I'm able to boot with target 0, not with 83.

Share this post


Link to post

@chalbolyIt is quite strange because I may find the root cause but your is working.Maybe you did not truely update to 0.5.7 but using 0.5.6?

 

Also to all:

I recommand to switch EFI qcow2/img to usb, this make my bootcamp works(but not work for MacPro7,1, it required no external disk injected.)

    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/mnt/user/domains/Catalina/opencore.beta.qcow2' index='1'/>
      <backingStore/>
      <target dev='hdc' bus='usb'/>
      <address type='usb' bus='0' port='1'/>
    </disk>

 

Share this post


Link to post

I noticed, after passing through a GPU to macOS, I can no longer boot up the VM without an actual GPU attached. I created a copy of the VM, removed the GPU, and added the Spice display through virt-manager. On bootup it now hangs on "PCI configuration begin". If I add the GPU back, it boots fine then.

 

Anyone else encounter this? I would like to have a copy of my VM that I can boot quickly without passing through a GPU, just for testing purposes.

 

Using OpenCore with the config provided here https://github.com/Leoyzen/KVM-Opencore

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.