Contribute
Register

macOS 10.13.4 Update

Status
Not open for further replies.
Yes. This one is much more legible. However, I've never seen this message... I still feel that creating an SSDT for USB is the best solution and resilient against breaking when updating macOS.

Well, I was using: XHCI-300-series-injector.kext, and USBInjectall.kext. And it was working great in 10.13.3.....the thing is, it got all the way through the upgrade (from the App store), seemed fine (I had removed my nVidia drivers entirely), and I was ready to boot into 10.13.4 and install the new nvidia drivers and bang, this happens...

If you boot without -v, what you see is the system loading and then the circle with a slash sign.

Maybe somebody else has seen this? Or has an idea of what it might indicate?
 
Well, I was using: XHCI-300-series-injector.kext, and USBInjectall.kext. And it was working great in 10.13.3.....the thing is, it got all the way through the upgrade (from the App store), seemed fine (I had removed my nVidia drivers entirely), and I was ready to boot into 10.13.4 and install the new nvidia drivers and bang, this happens...

If the upgrade to 10.13.4 has completed, the new PMHeart USB port limit patch should work. I believe the XHCI-300-series-injector.kext and USBInjectAll.kext should be removed if you use the PMHeart patch.
 
Hi all,

I was wondering if there was anyone using Vega 64 having monitor sleep issues with 10.13.4.
My monitor does not wake even when the main computer unit gets back up.
I tried placing Whatevergreen.kext 1.1.7 into EFI/Clover/kexts/Other. darkwake=0 does not help either.
 
Hi all,

I was wondering if there was anyone using Vega 64 having monitor sleep issues with 10.13.4.
My monitor does not wake even when the main computer unit gets back up.
I tried placing Whatevergreen.kext 1.1.7 into EFI/Clover/kexts/Other. darkwake=0 does not help either.

I had the same exact issue when i removed Lilu and Whatevergreen (using an RX 480) It would take about 30 seconds before the screen would come back on. However, putting both of these kexts back fixed my issue.
 
I use Clover Configurator successfully to perform this and other tasks, see screenshot of where and how you need to add it.

But here is a thorough tutorial about hotpatching, get stuck in!
https://www.tonymacx86.com/threads/guide-using-clover-to-hotpatch-acpi.200137/

Hey, interesting that screenshot. I've seen a few folks use FakeCPUID - what's the benefit of this? I don't have anything in that field and am wondering if I can improve my machine by using a fake ID.
 
This is probably not the place to ask this, but why is my IntelMausiEthernet kext saying "Don't support Tonymacx86.com" in boot? I mean, whatever issue is here, placing it in user's boot messages is kinda, super ****ing wrong IMO.

Would you take a photo of this and post it here for review ?
 
Easiest is using Clover Configurator.
  • Open your config.plist in clover configurator.
  • In left hand pane select Kernel and Kext Patches.
  • Now in big white box, bottom right click on +
A new line will be created.
  1. Under Name* - com.apple.driver.usb.AppleUSBXHCI
  2. Under Find*[HEX] - g32UDw+DlwQAAA==
  3. Under Replace*[HEX] - g32UD5CQkJCQkA==
  4. Under Comment - USB 10.13.4+ by PMHeart (or anything useful that will remind you what this patch is all about)
  5. Under MatchOS - 10.13.x
  6. Don't write anything else. Save your config.plist

Restart.


So, thanks for your response. So, in my post, the final line that I didn't see because Apple obscures it is: "Still waiting for root device" (which becomes the prohibited sign if you don't boot with -v) This line comes right after the HID Legacy shim 2 line.

And, when I entered the new PMHeart patch, I did so by copying and pasting it via Text Wrangler. Didn't enter it via Clover Configurator.

So, I entered what you responded with, in Clover Configurator, just so you know, and deleted my original PMHeart patch.

Is that of some help?
 
Last edited:
6034B37F-66EE-49AD-8078-454DAEBE1954.jpeg ok, not news to anyone, but still. who does that.
 
Last edited:
Status
Not open for further replies.
Back
Top