Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hi folks, I've tried trawling through this thread to find an answer, but haven't been able to, so...

I've got 10.14.3 up and running with no issues on my late 2009 iMac, apart from the fact that apps refuse to download updates from the App Store. The updates display ok, but when I click the Update button, it just keeps spinning and never actually downloads or installs.

Any ideas? Thanks!
Hdd formatted to APFS?
 
  • Like
Reactions: TimothyR734
And the webcam. And the inability to reboot. Or have those been solved as well?
The "webcam" or iSight did not work since 10.10. on the 4.1 - seems to be not related to Mojave. Would like to solve it somehow, too.
Re-boot does in fact work, just with a KP at shutdown that gets mentioned on the next boot. Seems to be caused by BT kexts.
But hey, my glass on the 4.1 is way more than half full. Others might find it only 49% ;-)
Depends on the perspective, I´d guess.
Next frontier: Catalina. See you over there (too).
 
The "webcam" or iSight did not work since 10.10. on the 4.1 - seems to be not related to Mojave. Would like to solve it somehow, too.
Re-boot does in fact work, just with a KP at shutdown that gets mentioned on the next boot. Seems to be caused by BT kexts.
But hey, my glass on the 4.1 is way more than half full. Others might find it only 49% ;-)
Depends on the perspective, I´d guess.
Next frontier: Catalina. See you over there (too).


I'm not complaining by any means, it's amazing what you guys have accomplished on the Macbook4,1. Just listing the issues. The rebooting issue is really the one that is holding me back on the mb4,1. The webcam isn't too awfully important but not being able to reboot without notifications every time is a hard pill to swallow.
 
I'm not complaining by any means, it's amazing what you guys have accomplished on the Macbook4,1. Just listing the issues. The rebooting issue is really the one that is holding me back on the mb4,1. The webcam isn't too awfully important but not being able to reboot without notifications every time is a hard pill to swallow.
I´ll try to find a workaround for the KPs on reboot (I had a version of kext combos running here without that problem, but with reduced BT functions - perhaps this is a small sacrifice for you to get rid of the annoying popups after rebooting). Interestingly, if you power down and cold start, in most cases you get around the messages...
 
I´ll try to find a workaround for the KPs on reboot (I had a version of kext combos running here without that problem, but with reduced BT functions - perhaps this is a small sacrifice for you to get rid of the annoying popups after rebooting). Interestingly, if you power down and cold start, in most cases you get around the messages...

I would definitely be interested in that, BT is not as important to me as the rebooting issues. I know I know, different strokes for different folks. I do remember noticing that if you power off and back on manually there was no Kernel Panic.
 
  • Like
Reactions: TimothyR734
This is what I'm doing now ...
You might try and reinstall the legacy video patch just an idea :)

Unfortunately it did not work for me.

As an alternative, I'm using Macgo Mac Media Player

Nice!
[doublepost=1559862804][/doublepost]
The "webcam" or iSight did not work since 10.10. on the 4.1 - seems to be not related to Mojave. Would like to solve it somehow, too.
Re-boot does in fact work, just with a KP at shutdown that gets mentioned on the next boot. Seems to be caused by BT kexts.
But hey, my glass on the 4.1 is way more than half full. Others might find it only 49% ;-)
Depends on the perspective, I´d guess.
Next frontier: Catalina. See you over there (too).

iSight = reinstall Mojave and do not install any Legacy USB Patch, or iSight Patch, in version 10.14.5 it is natively running.
 
IMG_20190606_211942.jpg
 
  • Like
Reactions: TimothyR734
So I wasn’t paying attention and just ran updates and now my system won’t boot... saw this now;

10.14.4 and later CANNOT be patched properly using Mojave Patcher version 1.2.3 and older. If you update to 10.14.4 or later, and HAVE NOT updated your installer volume with version 1.3.0 or later of Mojave Patcher, you WILL NOT be able to get your system to boot after updating!

Now I’m not having any luck to get a USB stick to boot or anything to reload the o/s or get into a recovery mode...

Any ideas?
 
  • Like
Reactions: TimothyR734
So I wasn’t paying attention and just ran updates and now my system won’t boot... saw this now;

10.14.4 and later CANNOT be patched properly using Mojave Patcher version 1.2.3 and older. If you update to 10.14.4 or later, and HAVE NOT updated your installer volume with version 1.3.0 or later of Mojave Patcher, you WILL NOT be able to get your system to boot after updating!

Now I’m not having any luck to get a USB stick to boot or anything to reload the o/s or get into a recovery mode...

Any ideas?
can you restore with a backup if you have one or do you have another Mac did you try command option P and R then try booting with the version of the Mojave Patcher you have you can reinstall over 10.14.4 with 10.14.3
 
  • Like
Reactions: K two
I never was able to get a successful install. I had a full backup that was HFS so I reformatted my drive to HFS and now I have 10.14.0 and everything is working. I was almost at the point of just installing Debian and calling it. I'm glad to have my mac back again. Thanks to everyone that tried to help me, esp. @pkouame and @hvds
[doublepost=1559909105][/doublepost]
can you restore with a backup if you have one or do you have another Mac did you try command option P and R then try booting with the version of the Mojave Patcher you have you can reinstall over 10.14.4 with 10.14.3
So I wasn’t paying attention and just ran updates and now my system won’t boot... saw this now;

10.14.4 and later CANNOT be patched properly using Mojave Patcher version 1.2.3 and older. If you update to 10.14.4 or later, and HAVE NOT updated your installer volume with version 1.3.0 or later of Mojave Patcher, you WILL NOT be able to get your system to boot after updating!

Now I’m not having any luck to get a USB stick to boot or anything to reload the o/s or get into a recovery mode...

Any ideas?

I feel your pain. I did the exact same thing. You can try making a new USB with the newer version and trying again. My problem was I didn't have another Mac to use so I borrowed one of my student's Macbook. If you have a Windows box, you can use VMWare and make a VM of Mojave and make one there. That's what I have now, should I need it.

Good luck!
 
  • Like
Reactions: TimothyR734
You are right it just crashes even if I open a new Xcode project I even checked the downloads section doesn't have command line tools available and check softpedia for a new version of Swift the latest one is Swift 5.01 for Xcode 10.2

You can easily download either Xcode11beta and a full "Xcode 10.2.1" without a Developer Annual subscription, since they are free from apple, just login with your Apple ID here: https://developer.apple.com/download/release/

It will download the full "Xcode.xip" , XIP is a kind of auto-extractor-Installer, but as you know to install Xcode you need at least 15 Gb free + the 7 gb of the installer size.
 
  • Like
Reactions: TimothyR734
You are right it just crashes even if I open a new Xcode project I even checked the downloads section doesn't have command line tools available and check softpedia for a new version of Swift the latest one is Swift 5.01 for Xcode 10.2
and @jackluke

Command line tools are always available - they are installable within Xcode 11betas or via the more direct link:

https://developer.apple.com/download/more/ (if you have access)

A new version of Xcode is always paired with command line tools (actually has all the new core goodies: c compilers, linkers , code signing tools etc.)

Again, word of caution, early Xcode betas are only good for targeted inspection of new features. From experience you have to wait for a few more updates for quasi-stability. Especially if you have a large project. For 11 most of the interesting features require running on Catalina proper. Running on Mojave is probably even more quirky.
 
I never was able to get a successful install. I had a full backup that was HFS so I reformatted my drive to HFS and now I have 10.14.0 and everything is working. I was almost at the point of just installing Debian and calling it. I'm glad to have my mac back again. Thanks to everyone that tried to help me, esp. @pkouame and @hvds
[doublepost=1559909105][/doublepost]


I feel your pain. I did the exact same thing. You can try making a new USB with the newer version and trying again. My problem was I didn't have another Mac to use so I borrowed one of my student's Macbook. If you have a Windows box, you can use VMWare and make a VM of Mojave and make one there. That's what I have now, should I need it.

Good luck!

I’ve had no luck in getting my old patcher and old USB to even boot so far... it just gets to 100% of the boot loading screen full and sits.... ill play around more on weekend and make another bootable one from someone else’s Mac.... =/ but I’m happy to know other people have had luck getting past the boot screen.
 
when you get Mojave back up and running run this script in the terminal it should bring back recovery and anytime you do an upgrade for example 10.14.3 to 10.14.4 you have to run the script again
 

Attachments

  • MojaveRecoveryFix.sh.zip
    5.6 KB · Views: 224
Rather surprising no one is posting yet about the results of using the new ATI metal driver patch that got pushed earlier in the week.
 
  • Like
Reactions: ASentientBot
Rather surprising no one is posting yet about the results of using the new ATI metal driver patch that got pushed earlier in the week.
Well does anyone besides netkas know how to make it?
(as he likely won't make more beyond the essential proof of concept for 10.14.5 based on how he worded his forum post)

I have a RX580 in another machine that I think I'll borrow for the 3,1 to test out to see if we can get AirPlay and hardware encode / decode (using the method from Activate AMD hardware acceleration thread --> https://forums.macrumors.com/posts/27439520/ )

I was really hoping to do that today but I don't see it happening.
I did just get updated from 10.14.0 to 10.14.5 on the 3,1 which was a bit of a hassle as I am unable to get dosdude's tool to work I have to do things manually. What his tool creates never loads the installer all the way (kext version mismatches for graphics is what it looks like the issues are based on verbose boot, so i never get a desktop to do an install)
 
Well does anyone besides netkas know how to make it?
(as he likely won't make more beyond the essential proof of concept for 10.14.5 based on how he worded his forum post)

I have a RX580 in another machine that I think I'll borrow for the 3,1 to test out to see if we can get AirPlay and hardware encode / decode (using the method from Activate AMD hardware acceleration thread --> https://forums.macrumors.com/posts/27439520/ )

I was really hoping to do that today but I don't see it happening.
I did just get updated from 10.14.0 to 10.14.5 on the 3,1 which was a bit of a hassle as I am unable to get dosdude's tool to work I have to do things manually. What his tool creates never loads the installer all the way (kext version mismatches for graphics is what it looks like the issues are based on verbose boot, so i never get a desktop to do an install)

The Patch Updater automatically installed it here on my MacPro 3,1 with GTX-680 (but from the speed of the kernel cache rebuild step, it was unclear if that was a NOP for this configuration). Considering that dosdude1 made it an automatically applied patch, I would assume it should be relatively stable.
 
I have a MacBookPro 4,1 17" early 2008 2.5GHz Intel Core Duo running MacOS Mojave 10.14.3 via DosDudes patcher.

I have lost my bluetooth after upgrading but continue to have Wifi using this Version 2 of this third party card:

https://www.quickertek.com/product/mcard/

Here is my system read out for wifi...bluetooth shows no information....a ktext rebuild problem?

Do any forum members know if there another WiFi/Bluetooth card that will work with my 4,1 OS 10.14.3 setup?

Card Type: AirPort Extreme (0x14E4, 0x112)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2)
MAC Address: ac:29:3a:ec:60:a2
Locale: FCC
Country Code: US
Supported PHY Modes: 802.11 a/b/g/n/ac
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 144, 149, 153, 157, 161, 165
Wake On Wireless: Supported
AirDrop: Supported
AirDrop Channel: 149
Auto Unlock: Supported
Status: Connected
Current Network Information:
 
The Patch Updater automatically installed it here on my MacPro 3,1 with GTX-680 (but from the speed of the kernel cache rebuild step, it was unclear if that was a NOP for this configuration). Considering that dosdude1 made it an automatically applied patch, I would assume it should be relatively stable.
I'm not sure that you and I are talking about the same patch then...
I am talking about a patch from Netkas to enable the 3,1 to use GCN AMD cards in 10.14.5 by emulating the single SSE4.2 call in the AMD metal driver.

I did give it a go today actually, WindowServer crashes.
What I get is Display turns on with black screen and I can move the cursor around, via ScreenSharing I get the same behavior, I also tried the HDMI, DVI and DP connectors, all methods show that behavior.

System profiler showing the AMD RX 580 running in a 3,1 in 10.14.5 (removed my GTX 650 to do this test):
Code:
Graphics/Displays:

    Radeon RX 580:

      Chipset Model: Radeon RX 580
      Type: GPU
      Bus: PCIe
      Slot: Slot-1
      PCIe Lane Width: x16
      VRAM (Total): 8 GB
      Vendor: AMD (0x1002)
      Device ID: 0x67df
      Revision ID: 0x00e7
      Metal: Supported, feature set macOS GPUFamily2 v1

Hardware:

    Hardware Overview:

      Model Name: Mac Pro
      Model Identifier: MacPro3,1
      Processor Name: Quad-Core Intel Xeon
      Processor Speed: 3.2 GHz
      Number of Processors: 2
      Total Number of Cores: 8
      L2 Cache (per Processor): 12 MB
      Memory: 32 GB
      Boot ROM Version: MP31.006C.B05
      SMC Version (system): 1.25f4

PCI:

    Radeon RX 580:

      Name: ATY,AMD,RadeonFramebuffer
      Type: Display Controller
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-1
      Vendor ID: 0x1002
      Device ID: 0x67df
      Subsystem Vendor ID: 0x148c
      Subsystem ID: 0x2377
      Revision ID: 0x00e7
      Link Width: x16
      Link Speed: 2.5 GT/s

    pci1002,aaf0:

      Type: Audio Device
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-1
      Vendor ID: 0x1002
      Device ID: 0xaaf0
      Subsystem Vendor ID: 0x148c
      Subsystem ID: 0xaaf0
      Revision ID: 0x0000
      Link Width: x16
      Link Speed: 2.5 GT/s

    pci1b4b,9230:

      Type: AHCI Controller
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-3
      Vendor ID: 0x1b4b
      Device ID: 0x9230
      Subsystem Vendor ID: 0x1b4b
      Subsystem ID: 0x9230
      Revision ID: 0x0010
      Link Width: x1
      Link Speed: 2.5 GT/s

    pci1000,411:

      Type: RAID Controller
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-4@6,14,0
      Vendor ID: 0x1000
      Device ID: 0x0411
      Subsystem Vendor ID: 0x1000
      Subsystem ID: 0x1008
      Revision ID: 0x0000

WindowServer crashes in a loop:

Code:
Jun  7 15:12:17 macpro-osx WindowServer[690]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Jun  7 15:12:17 macpro-osx com.apple.xpc.launchd[1] (com.apple.AmbientDisplayAgent): Service only ran for 4 seconds. Pushing respawn out by 6 seconds.
Jun  7 15:12:17 macpro-osx sessionlogoutd[691]: DEAD_PROCESS: 668 console
Jun  7 15:12:17 macpro-osx com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root[689]): Binary is improperly signed.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.imklaunchagent): This service is defined to be constantly running and is inherently inefficient.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.coreservices.UASharedPasteboardProgressUI): Unknown key for Boolean: DrainMessagesAfterFailedInit
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1](com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.pluginkit.pkd (lint): Service sets EnableTransactions=false and EnablePressuredExit=true, which makes no sense. Enabling Transactions.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.UserEventAgent-LoginWindow): This service is defined to be constantly running and is inherently inefficient.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.universalaccessd (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.VoiceOver (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.AssistiveControl (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.DwellControl (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.universalaccesscontrol (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.noticeboard.agent (lint): EnablePressuredExit is not compatible with KeepAlive=true. Ignoring EnablePressuredExit.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.noticeboard.agent): This service is defined to be constantly running and is inherently inefficient.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.tiswitcher (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.coreservices.useractivityd): Unknown key for Boolean: DrainMessagesAfterFailedInit
Jun  7 15:12:19 macpro-osx SecurityAgent[706]: objc[706]: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf078) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10e415ce8). One of the two will be used. Which one is undefined.
Jun  7 15:12:19 macpro-osx SecurityAgent[706]: objc[706]: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf0a0) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10e415d10). One of the two will be used. Which one is undefined.
Jun  7 15:12:19 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.SecurityAgent.706): Path not allowed in target domain: type = uid, path = /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/XPCServices/ViewBridgeAuxiliary.xpc/Contents/MacOS/ViewBridgeAuxiliary error = 1: Operation not permitted, origin = /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle
Jun  7 15:12:19 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.SecurityAgent.706): Path not allowed in target domain: type = uid, path = /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/XPCServices/com.apple.FCiCloudPrefUpdater.xpc/Contents/MacOS/com.apple.FCiCloudPrefUpdater error = 1: Operation not permitted, origin = /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle
Jun  7 15:12:19 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.SecurityAgent.706): Path not allowed in target domain: type = uid, path = /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/XPCServices/com.apple.accessibility.mediaaccessibilityd.xpc/Contents/MacOS/com.apple.accessibility.mediaaccessibilityd error = 1: Operation not permitted, origin = /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle
Jun  7 15:12:20 macpro-osx ctkahp[712]: objc[712]: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf078) and /System/Library/Frameworks/CryptoTokenKit.framework/ctkahp.bundle/Contents/MacOS/ctkahp (0x1068d0738). One of the two will be used. Which one is undefined.
Jun  7 15:12:20 macpro-osx ctkahp[712]: objc[712]: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf0a0) and /System/Library/Frameworks/CryptoTokenKit.framework/ctkahp.bundle/Contents/MacOS/ctkahp (0x1068d0760). One of the two will be used. Which one is undefined.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.WindowServer[690]): Binary is improperly signed.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.WindowServer): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.ViewBridgeAuxiliary): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.sessionlogoutd): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.


kextstat info:
Code:
macpro-osx:~ ludacrisvp$ kextstat |grep AMD
  146    2 0xffffff7f83f77000 0x201000   0x201000   com.apple.kext.AMDSupport (2.0.9) A212D4A1-95AA-3284-B9BF-DECE3D72EC8D <123 121 13 12 8 6 5 3 1>
  147    0 0xffffff7f84178000 0xfa000    0xfa000    com.apple.kext.AMD9500Controller (2.0.9) 0B192707-0B2A-327A-BE03-3B4AD0A64C74 <146 123 121 13 12 6 5 3 1>
  151    0 0xffffff7f84272000 0x11000    0x11000    com.apple.kext.AMDRadeonX4000HWServices (2.0.9) 15ED0BAB-A035-37E0-A350-A6F22E42259C <121 13 12 8 6 5 3 1>
  154    0 0xffffff7f84283000 0x537000   0x537000   com.apple.kext.AMDRadeonX4000 (2.0.9) 6AD64509-77E3-32EB-8800-FCB397DC7DA0 <153 129 121 13 8 6 5 3 1>
  155    0 0xffffff7f847ba000 0x11c3000  0x11c3000  com.apple.kext.AMDRadeonX4000HWLibs (1.0) C30FFC7A-BCAA-3691-8811-4A56BE45B09D <13 6 5 3 1>
  156    0 0xffffff7f8597d000 0x3c000    0x3c000    com.apple.kext.AMDFramebuffer (2.0.9) AFECA5EC-3965-39FA-9FA6-2D51C7D22F6E <146 121 13 12 8 6 5 3 1>

macpro-osx:~ ludacrisvp$ kextstat |grep -i Lilu
   17    2 0xffffff7f80ea1000 0x23000    0x23000    as.vit9696.Lilu (1.3.6) 793EEE62-381C-3F9D-B54F-8515397591B5 <8 6 5 3 2 1>
macpro-osx:~ ludacrisvp$ kextstat |grep -i green
   18    0 0xffffff7f80ec4000 0x64000    0x64000    as.vit9696.WhateverGreen (1.2.9) 7C9AFF33-DB1A-352E-9569-1F23DF0193BE <17 13 8 6 5 3 2 1>


boot-args shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94 debug=0x144 -v
 
I'm not sure that you and I are talking about the same patch then...
I am talking about a patch from Netkas to enable the 3,1 to use GCN AMD cards in 10.14.5 by emulating the single SSE4.2 call in the AMD metal driver.

I did give it a go today actually, WindowServer crashes.
What I get is Display turns on with black screen and I can move the cursor around, via ScreenSharing I get the same behavior, I also tried the HDMI, DVI and DP connectors, all methods show that behavior.

System profiler showing the AMD RX 580 running in a 3,1 in 10.14.5 (removed my GTX 650 to do this test):
Code:
Graphics/Displays:

    Radeon RX 580:

      Chipset Model: Radeon RX 580
      Type: GPU
      Bus: PCIe
      Slot: Slot-1
      PCIe Lane Width: x16
      VRAM (Total): 8 GB
      Vendor: AMD (0x1002)
      Device ID: 0x67df
      Revision ID: 0x00e7
      Metal: Supported, feature set macOS GPUFamily2 v1

Hardware:

    Hardware Overview:

      Model Name: Mac Pro
      Model Identifier: MacPro3,1
      Processor Name: Quad-Core Intel Xeon
      Processor Speed: 3.2 GHz
      Number of Processors: 2
      Total Number of Cores: 8
      L2 Cache (per Processor): 12 MB
      Memory: 32 GB
      Boot ROM Version: MP31.006C.B05
      SMC Version (system): 1.25f4

PCI:

    Radeon RX 580:

      Name: ATY,AMD,RadeonFramebuffer
      Type: Display Controller
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-1
      Vendor ID: 0x1002
      Device ID: 0x67df
      Subsystem Vendor ID: 0x148c
      Subsystem ID: 0x2377
      Revision ID: 0x00e7
      Link Width: x16
      Link Speed: 2.5 GT/s

    pci1002,aaf0:

      Type: Audio Device
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-1
      Vendor ID: 0x1002
      Device ID: 0xaaf0
      Subsystem Vendor ID: 0x148c
      Subsystem ID: 0xaaf0
      Revision ID: 0x0000
      Link Width: x16
      Link Speed: 2.5 GT/s

    pci1b4b,9230:

      Type: AHCI Controller
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-3
      Vendor ID: 0x1b4b
      Device ID: 0x9230
      Subsystem Vendor ID: 0x1b4b
      Subsystem ID: 0x9230
      Revision ID: 0x0010
      Link Width: x1
      Link Speed: 2.5 GT/s

    pci1000,411:

      Type: RAID Controller
      Driver Installed: Yes
      MSI: Yes
      Bus: PCI
      Slot: Slot-4@6,14,0
      Vendor ID: 0x1000
      Device ID: 0x0411
      Subsystem Vendor ID: 0x1000
      Subsystem ID: 0x1008
      Revision ID: 0x0000

WindowServer crashes in a loop:

Code:
Jun  7 15:12:17 macpro-osx WindowServer[690]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Jun  7 15:12:17 macpro-osx com.apple.xpc.launchd[1] (com.apple.AmbientDisplayAgent): Service only ran for 4 seconds. Pushing respawn out by 6 seconds.
Jun  7 15:12:17 macpro-osx sessionlogoutd[691]: DEAD_PROCESS: 668 console
Jun  7 15:12:17 macpro-osx com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root[689]): Binary is improperly signed.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.imklaunchagent): This service is defined to be constantly running and is inherently inefficient.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.coreservices.UASharedPasteboardProgressUI): Unknown key for Boolean: DrainMessagesAfterFailedInit
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1](com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.pluginkit.pkd (lint): Service sets EnableTransactions=false and EnablePressuredExit=true, which makes no sense. Enabling Transactions.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.UserEventAgent-LoginWindow): This service is defined to be constantly running and is inherently inefficient.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.universalaccessd (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.VoiceOver (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.AssistiveControl (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.DwellControl (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.universalaccesscontrol (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.noticeboard.agent (lint): EnablePressuredExit is not compatible with KeepAlive=true. Ignoring EnablePressuredExit.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.noticeboard.agent): This service is defined to be constantly running and is inherently inefficient.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.695.4294967295): com.apple.tiswitcher (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Jun  7 15:12:18 macpro-osx com.apple.xpc.launchd[1] (com.apple.coreservices.useractivityd): Unknown key for Boolean: DrainMessagesAfterFailedInit
Jun  7 15:12:19 macpro-osx SecurityAgent[706]: objc[706]: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf078) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10e415ce8). One of the two will be used. Which one is undefined.
Jun  7 15:12:19 macpro-osx SecurityAgent[706]: objc[706]: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf0a0) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10e415d10). One of the two will be used. Which one is undefined.
Jun  7 15:12:19 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.SecurityAgent.706): Path not allowed in target domain: type = uid, path = /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/XPCServices/ViewBridgeAuxiliary.xpc/Contents/MacOS/ViewBridgeAuxiliary error = 1: Operation not permitted, origin = /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle
Jun  7 15:12:19 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.SecurityAgent.706): Path not allowed in target domain: type = uid, path = /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/XPCServices/com.apple.FCiCloudPrefUpdater.xpc/Contents/MacOS/com.apple.FCiCloudPrefUpdater error = 1: Operation not permitted, origin = /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle
Jun  7 15:12:19 macpro-osx com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.SecurityAgent.706): Path not allowed in target domain: type = uid, path = /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/XPCServices/com.apple.accessibility.mediaaccessibilityd.xpc/Contents/MacOS/com.apple.accessibility.mediaaccessibilityd error = 1: Operation not permitted, origin = /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle
Jun  7 15:12:20 macpro-osx ctkahp[712]: objc[712]: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf078) and /System/Library/Frameworks/CryptoTokenKit.framework/ctkahp.bundle/Contents/MacOS/ctkahp (0x1068d0738). One of the two will be used. Which one is undefined.
Jun  7 15:12:20 macpro-osx ctkahp[712]: objc[712]: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff8b0cf0a0) and /System/Library/Frameworks/CryptoTokenKit.framework/ctkahp.bundle/Contents/MacOS/ctkahp (0x1068d0760). One of the two will be used. Which one is undefined.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.WindowServer[690]): Binary is improperly signed.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.WindowServer): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.ViewBridgeAuxiliary): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Jun  7 15:12:20 macpro-osx com.apple.xpc.launchd[1] (com.apple.sessionlogoutd): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.


kextstat info:
Code:
macpro-osx:~ ludacrisvp$ kextstat |grep AMD
  146    2 0xffffff7f83f77000 0x201000   0x201000   com.apple.kext.AMDSupport (2.0.9) A212D4A1-95AA-3284-B9BF-DECE3D72EC8D <123 121 13 12 8 6 5 3 1>
  147    0 0xffffff7f84178000 0xfa000    0xfa000    com.apple.kext.AMD9500Controller (2.0.9) 0B192707-0B2A-327A-BE03-3B4AD0A64C74 <146 123 121 13 12 6 5 3 1>
  151    0 0xffffff7f84272000 0x11000    0x11000    com.apple.kext.AMDRadeonX4000HWServices (2.0.9) 15ED0BAB-A035-37E0-A350-A6F22E42259C <121 13 12 8 6 5 3 1>
  154    0 0xffffff7f84283000 0x537000   0x537000   com.apple.kext.AMDRadeonX4000 (2.0.9) 6AD64509-77E3-32EB-8800-FCB397DC7DA0 <153 129 121 13 8 6 5 3 1>
  155    0 0xffffff7f847ba000 0x11c3000  0x11c3000  com.apple.kext.AMDRadeonX4000HWLibs (1.0) C30FFC7A-BCAA-3691-8811-4A56BE45B09D <13 6 5 3 1>
  156    0 0xffffff7f8597d000 0x3c000    0x3c000    com.apple.kext.AMDFramebuffer (2.0.9) AFECA5EC-3965-39FA-9FA6-2D51C7D22F6E <146 121 13 12 8 6 5 3 1>

macpro-osx:~ ludacrisvp$ kextstat |grep -i Lilu
   17    2 0xffffff7f80ea1000 0x23000    0x23000    as.vit9696.Lilu (1.3.6) 793EEE62-381C-3F9D-B54F-8515397591B5 <8 6 5 3 2 1>
macpro-osx:~ ludacrisvp$ kextstat |grep -i green
   18    0 0xffffff7f80ec4000 0x64000    0x64000    as.vit9696.WhateverGreen (1.2.9) 7C9AFF33-DB1A-352E-9569-1F23DF0193BE <17 13 8 6 5 3 2 1>


boot-args shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94 debug=0x144 -v
Yes, it's the same patch. It looks like it could be an issue with your macOS install. If possible, I'd recommend doing a clean 10.14.5 install on a spare volume, and then giving it a try. Ensure you set permissions correctly after copying the patched binary to the appropriate location.
 
  • Like
Reactions: ASentientBot
Yes, it's the same patch. It looks like it could be an issue with your macOS install. If possible, I'd recommend doing a clean 10.14.5 install on a spare volume, and then giving it a try. Ensure you set permissions correctly after copying the patched binary to the appropriate location.
Good to know this is something you are able to be providing.

This is a pretty clean install, the only apps I've installed is the OpenGL Extensions viewer and VideoProc to see if I can get AMD hardware en/decode working ... I installed 10.14 when it came out to test it out on this machine and it worked, I powered off and moved PCIe cards around which made my mSATA carrier become unbootable for an unknown reason, so I wasn't able to access it for months until now when i was motivated to get access to it again ... used CCC to clone to a reliable boot location (a partition on a normal SATA 840 Evo) and then updated that install.

I wasn't able to do a real 'clean install' as I can't get your patched version of the installer to load all the way, it gets stuck complaining that there is already older versions of a few graphics kexts loaded already and it refuses to load another version of the kext.

Maybe in a week or so I'll be able to test again.

Permissions for the file appear correct to me, I used the copy of the file from netkas.org:
Code:
macpro-osx:Contents ludacrisvp$ ls -lh /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver 
-rwxr-xr-x@ 1 root  wheel   1.7M Jun  7 14:23 /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
macpro-osx:Contents ludacrisvp$ md5 !$
md5 /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
MD5 (/System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver) = 097e047881b74b3796a47326b1712e3e
 
Good to know this is something you are able to be providing.

This is a pretty clean install, the only apps I've installed is the OpenGL Extensions viewer and VideoProc to see if I can get AMD hardware en/decode working ... I installed 10.14 when it came out to test it out on this machine and it worked, I powered off and moved PCIe cards around which made my mSATA carrier become unbootable for an unknown reason, so I wasn't able to access it for months until now when i was motivated to get access to it again ... used CCC to clone to a reliable boot location (a partition on a normal SATA 840 Evo) and then updated that install.

I wasn't able to do a real 'clean install' as I can't get your patched version of the installer to load all the way, it gets stuck complaining that there is already older versions of a few graphics kexts loaded already and it refuses to load another version of the kext.

Maybe in a week or so I'll be able to test again.

Permissions for the file appear correct to me, I used the copy of the file from netkas.org:
Code:
macpro-osx:Contents ludacrisvp$ ls -lh /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
-rwxr-xr-x@ 1 root  wheel   1.7M Jun  7 14:23 /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
macpro-osx:Contents ludacrisvp$ md5 !$
md5 /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
MD5 (/System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver) = 097e047881b74b3796a47326b1712e3e

Definitely if you currently have the legacy video patches installed, you'll need to reinstall from the full installer over your existing installation to purge those out for metal to work properly.

FYI, on my MacPro 3,1 with GTX 680, I just reinstalled with a newly recreated patched installer using the current macOS Mojave Patcher 1.3.3 and the Install macOS Mojave 4.5.02 with no issues.
 
Last edited:
Definitely if you currently have the legacy video patches installed, you'll need to reinstall from the full installer over your existing installation to purge those out for metal to work properly.

FYI, on my MacPro 3,1 with GTX 680, I just reinstalled with a newly recreated patched installer using the current macOS Mojave Patcher 1.3.3 and the Install macOS Mojave 4.5.02 with no issues.
When you create the patched installer you can’t choose to have it make it with or without the legacy video patch. I don’t need / want the legacy video patch since I have a supported card.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.