macOS 10.14 Mojave on Unsupported Macs Thread

[Dilli]

HERE it is @jackluke

Crazy issues keeps cropping up. When you click on Siri on top status bar only animation works and there is no answer sometimes its very erratic. But if you click on Siri app on the dock all works well with animation and response.

 

[jackluke]

HERE it is @jackluke

Crazy issues keeps cropping up. When you click on Siri on top status bar only animation works and there is no answer sometimes its very erratic. But if you click on Siri app on the dock all works well with animation and response.

Still don't have the wave animation, however my Mojave build is 18G2007 , through OTA it installed this version not sure exactly if it's a beta build.

edit:
Replacing the @alphascorp CoreServices/Siri.app and the SiriUI.framework (version 146.12.3) uploaded by @Dilli worked also on 18G2007 , now I have the Siri wave animation on non-metal machine.

 

[Dilli]

Still don't have the wave animation, however my Mojave build is 18G2007 , through OTA it installed this version not sure exactly if it's a beta build.

You maybe right since we have the latest security patch 10.14.6 installed 18G103

Edit: Latest security patch is 18G1012

 

[Dilli]

Apple has screwed up syncing of Reminders from Mojave to IOS 13.0. Now all my reminder list has gone missing in Mojave and it has broke with yellow triangle icon. Apparently after reminder app update in Catalina & IOS 13.0 both running similar UI it is all good and smooth however Mojave Reminder does not sync both ways. It does not even pop up in hands-off. Below clip is from Apple support site.

 

[Larsvonhier]

You maybe right since we have the latest security patch 10.14.6 installed 18G103

The 18G103 is definitely not the latest sec. patch: It would show as 18G1012, out since a couple of days - see page #1 where we all try to keep up the list.

 

[Dilli]

The 18G103 is definitely not the latest sec. patch: It would show as 18G1012, out since a couple of days.

Yes you are right I got confused while replacing Siri app from the security update 10.14.6

 

[Larsvonhier]

I ran into some trouble with the SSE4.2 partial emulator by @Syncretic that is included now in @dosdude1 tools. Somehow Excel 2016 causes kernel panics related to the SSE emu due to an invalid frame pointer there. I attach a crash dump here:

Spoiler: Crash log

*** Panic Report ***

panic(cpu 0 caller 0xffffff80036dbadd): Kernel trap at 0xffffff7f843c1e00, type 6=invalid opcode, registers:

CR0: 0x0000000080010033, CR2: 0x000000010caed2ce, CR3: 0x0000000117c09000, CR4: 0x00000000000026e0
RAX: 0x000000010caed2c4, RBX: 0x00007ffeec6edbd0, RCX: 0x000000010caed2d0, RDX: 0x00007ffeec6edbd0
RSP: 0xfffff6bd40080130, RBP: 0x00007ffeec6ed870, RSI: 0x00007ffeec6edb68, RDI: 0x000000000000000f
R8: 0x00007ffeec6edbd0, R9: 0xbe792c8288f23546, R10: 0x0000000000000003, R11: 0x0000000181905000
R12: 0xbe792c8288f23546, R13: 0x00007ffeec6eddb0, R14: 0x00000000000ae2b8, R15: 0xffa0ffffff830b0f
RFL: 0x0000000000010083, RIP: 0xffffff7f843c1e00, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x000000010caed2ce, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0
Backtrace (CPU 0), Frame : Return Address
0xffffff800337fcd0 : 0xffffff80035ae6ed
0xffffff800337fd20 : 0xffffff80036ea185
0xffffff800337fd60 : 0xffffff80036db8ba
0xffffff800337fdd0 : 0xffffff800355bb40
0xffffff800337fdf0 : 0xffffff80035ae107
0xffffff800337ff10 : 0xffffff80035adf53
0xffffff800337ff80 : 0xffffff80036dbadd
0xffffff80033800f0 : 0xffffff800355bb40
0xffffff8003380110 : 0xffffff7f843c1e00
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0x7ffeec6ed870
Kernel Extensions in backtrace:
AAA.LoadEarly.MouSSE(0.38)[7DDA536B-57F7-33B2-A5DC-7ABB923F9C59]@0xffffff7f843c1000->0xffffff7f843c5fff
BSD process name corresponding to current thread: Microsoft Excel
Boot args: -no_compat_check
Mac OS version:
18G103

Perhaps this can be resolved or more ppl report such incidents?
The tricky thing here for possible debugging is that most of the time the system (and Excel, yuck) work, but from time to time it just kernel panics.

 

[Syncretic]

I ran into some trouble with the SSE4.2 partial emulator by @Syncretic that is included now in @dosdude1 tools. Somehow Excel 2016 causes kernel panics related to the SSE emu due to an invalid frame pointer there. I attach a crash dump here:

{snip}

Perhaps this can be resolved or more ppl report such incidents?
The tricky thing here for possible debugging is that most of the time the system (and Excel, yuck) work, but from time to time it just kernel panics.

I will look into this as soon as time permits, hopefully later today.

 

[Larsvonhier]

I will look into this as soon as time permits, hopefully later today.

If I can help in any way (test installing a new version, sending more detailed logs etc.) pls. let me know!

 

[jackluke]

The 18G103 is definitely not the latest sec. patch: It would show as 18G1012, out since a couple of days - see page #1 where we all try to keep up the list.

I just updated yesterday and currently beta should be 10.14.6 Security Update 2019-002 build 18G2007, mixing two methods yours SiriUI replacement and @alphascorp Siri.app , now I have a working Siri with wave animation, however (not for Siri fault) I am encountering random Mojave freeze, no kp crashes or evident errors, just freeze, and I have to force power-off , so I'd advise to avoid the 2019-002 on unsupported machines.

 

[mrploppy]

Apple has screwed up syncing of Reminders from Mojave to IOS 13.0. Now all my reminder list has gone missing in Mojave and it has broke with yellow triangle icon. Apparently after reminder app update in Catalina & IOS 13.0 both running similar UI it is all good and smooth however Mojave Reminder does not sync both ways. It does not even pop up in hands-off. Below clip is from Apple support site.


View attachment 875798

Not so much a screw up. If you want the new Reminders interface, your devices have to be ios 13 or Catalina. That warning popped up when I first opened the Reminders app on my iPhone after the ios update. Since I'm running High Sierra (unsupported) on one laptop and Mojave on another, I declined the update. It's a bit naughty of Apple to obsolesce devices in this way but they at least gave a warning, so you can stick with the existing interface if you wish.

 

[shirsch]

Where is the resource file that tells Patch Updater what is currently installed? I have updated to a metal-capable video card and no longer need or want the legacy video patch. Unfortunately, the updater believes I do and is constantly popping up and prompting me to update the legacy video patch.

Update: Found it.

/Library/Application Support/macOS Mojave Patcher/installedPatches.plist

Removed the stanza for legacyGPU and all is well.

 

[Bill Forest]

Hi @Bill Forest,

Copy "bkltpatch10.14.2.zip" ON YOUR DESKTOP and unziped it
You have now on your desktop a folder named bkltpatch10.14.2 with 4 files inside
Open Terminal and write (or copy) this:

cd desktop/bkltpatch10.14.2;
install.sh

This should work properly

On iMac7,1 and iMac8,1 (I have not tested on iMac 9.1) this does not work and gives Kernel Panic, 2 files should not be replaced but only "DisplayServices.framework"
Take a look at this:

Fix Backlight control with F1/F2 keys on Unsupported iMac7,1 & 8,1 with macOS 10.14 Mojave

Hi everybody I run a new thread because someone deleted my addition about this on the first page of the thread "macOS 10.14 Mojave on Unsupported Macs" perhaps thinking that my discovery was useless and not worth it! All is in the title! I have two unsupported iMac8,1 with macOS Mojave and I...

forums.macrumors.com

• Add bookmark
• #2

Hi,
I have an iMac 9,1 and just tried your method to fix the fact that the Brightness buttons (F1, F2) do not work after installing dosdude's Mojave patch (Mojave 10.14.6).
First I must say that I am a novice in working with Terminal, so I may have done something incorrectly. At any rate, I tried both the manual and automatic fixes, and now the F1/F2 buttons adjust the Brightness, but only for about 2 seconds. It will turn Brightness up or down, but after 2 seconds, it reverts to low level brightness.
Do you have any suggestions?
Here is what I get when I run it in automatic:

sudo /Users/name/Downloads/Fix\ Backlight\ control\ with\ F1-F2\ keys\ for\ iMac\ 7\,1\ \&\ 8\,1/install.sh
Password:
cp: DisplayServices.framework: No such file or directory
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f8542d48800 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/AppleHDA.kext/", ID = "com.apple.driver.AppleHDA" }
kext file:///System/Library/Extensions/BJUSBLoad.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/EPSONUSBPrintClass.kext/ is in hash exception list, allowing to load
Kext with invalid signatured (-67062) allowed: <OSKext 0x7f85443c5470 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/GeForceTesla.kext/", ID = "com.apple.GeForceTesla" }
kext file:///System/Library/Extensions/hp_designjet_series.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Deskjet_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_fax_io.kext/ is in hash exception list, allowing to load
Kext with invalid signatured (-67062) allowed: <OSKext 0x7f85443eb2d0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/hp_Inkjet1_io_enabler.kext/", ID = "com.hp.print.hpio.Inkjet1.kext" }
kext file:///System/Library/Extensions/hp_Inkjet3_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Inkjet4_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Inkjet7_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Inkjet8_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Inkjet_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Officejet_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_Photosmart_io_enabler.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/hp_qc_io_enabler.kext/ is in hash exception list, allowing to load
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f85440e7680 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/", ID = "com.apple.iokit.IOUSBFamily" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f85440edc70 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.kext/", ID = "com.apple.driver.AppleUSBMergeNub" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f85440f0d30 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriver.kext/", ID = "com.apple.driver.AppleUSBComposite" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f85440f28b0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kext/", ID = "com.apple.iokit.IOUSBHIDDriver" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f85440f8200 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.kext/", ID = "com.apple.iokit.IOUSBUserClient" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7f85440ea3c0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBHostFamily.kext/", ID = "com.apple.iokit.IOUSBHostFamily" }
kext file:///System/Library/Extensions/JMicronATA.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/LexmarkUSBMerge.kext/ is in hash exception list, allowing to load
Kext with invalid signatured (-67062) allowed: <OSKext 0x7f854467a540 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/MacOSXCameraDriver.kext/", ID = "com.flipvideo.IOUSBCameraMassStorage" }
Kext with invalid signatured (-67062) allowed: <OSKext 0x7f85446a4ef0 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/LegacyUSBInjector.kext/", ID = "com.parrotgeek.LegacyUSBInjector" }
Kext with invalid signatured (-67030) allowed: <OSKext 0x7f854471e6c0 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/LegacyUSBVideoSupport.kext/", ID = "com.parrotgeek.LegacyUSBVideoSupport" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8544718c20 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/SIPManager.kext/", ID = "com.parrotgeek.SIPManager" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7fd0937539f0 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/SIPManager.kext/", ID = "com.parrotgeek.SIPManager" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd09351c330 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/", ID = "com.apple.iokit.IOUSBFamily" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd093527400 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kext/", ID = "com.apple.iokit.IOUSBHIDDriver" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd09352bce0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBHostFamily.kext/", ID = "com.apple.iokit.IOUSBHostFamily" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd093525150 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriver.kext/", ID = "com.apple.driver.AppleUSBComposite" }
Kext with invalid signatured (-67030) allowed: <OSKext 0x7fd09372c390 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/LegacyUSBVideoSupport.kext/", ID = "com.parrotgeek.LegacyUSBVideoSupport" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd093523690 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.kext/", ID = "com.apple.driver.AppleUSBMergeNub" }
Kext with invalid signatured (-67062) allowed: <OSKext 0x7fd09347f320 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/LegacyUSBInjector.kext/", ID = "com.parrotgeek.LegacyUSBInjector" }
kext file:///System/Library/Extensions/JMicronATA.kext/ is in hash exception list, allowing to load
/System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBVHCIBCE.kext - dependency 'com.apple.driver.usb.AppleUSBVHCI' not found.
/System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBVHCIBCE.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd09352dca0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.kext/", ID = "com.apple.iokit.IOUSBUserClient" }
Kext with invalid signatured (-67062) allowed: <OSKext 0x7fd0934231e0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/GeForceTesla.kext/", ID = "com.apple.GeForceTesla" }
Kext with invalid signatured (-67054) allowed: <OSKext 0x7fd091e27dc0 [0x7fffa3f668e0]> { URL = "file:///System/Library/Extensions/AppleHDA.kext/", ID = "com.apple.driver.AppleHDA" }
Invalid signature -67050 for kext <OSKext 0x7fd0937539f0 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/SIPManager.kext/", ID = "com.parrotgeek.SIPManager" }
Invalid signature -67030 for kext <OSKext 0x7fd09372c390 [0x7fffa3f668e0]> { URL = "file:///Library/Extensions/LegacyUSBVideoSupport.kext/", ID = "com.parrotgeek.LegacyUSBVideoSupport" }
kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostCxQueue was not patched because its parent, the vtable for AppleUSBVHCIHostTransferQueue, was not patchable.
kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostTxRxQueue was not patched because its parent, the vtable for AppleUSBVHCIHostTransferQueue, was not patchable.
kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostTransferQueue was not patched because its parent, the vtable for AppleUSBVHCIBCETransferQueue, was not found.
Link failed (error code 5).
Prelink failed for com.apple.driver.AppleUSBVHCI; omitting from prelinked kernel.
KernelCache ID: F322D7383FA9F4B4370DEB60FEAAE3B3

Thanks for any suggestions!
Bill

 

[alphascorp]

I just updated yesterday and currently beta should be 10.14.6 Security Update 2019-002 build 18G2007, mixing two methods yours SiriUI replacement and @alphascorp Siri.app , now I have a working Siri with wave animation, however (not for Siri fault) I am encountering random Mojave freeze, no kp crashes or evident errors, just freeze, and I have to force power-off , so I'd advise to avoid the 2019-002 on unsupported machines.

Hi @jackluke I had also gels and I had to force the extinction after the installation of (18G1012)
I solved this with ONYX utility, now no more gel and my MBP5.3 turns off without forcing it.

 

[brkr1]

Hi @olad
I installed the update 18G1012 last night on my MBP5,3
After reapplying the post installation patches with force cache rebuild it has rebooted successfully and everything worked EXCEPT "Siri" which has been updated and no longer works.

I just solved this problem by replacing Siri.app in /S/L/CoreServices from (18G103) and Siri works again!

View attachment 875277

EDIT:

I forgot to mention that I did not recreate a USB stick with the latest Patcher (1.3.5), I only extracted "macOS Post Install.app" from (macOS Mojave Patcher.app ▸ Contents ▸ Resources) and replaced the one of my installation USB key in (Applications ▸ Utilities)

Hey, since you have the same model as I do, would you mind sharing with me if you have lag to view videos with higher resolutions (like 4k or even 1080p)?
It's almost impossible for me to watch to those said videos.. lag is unbearable..

 

[jackluke]

Hey, since you have the same model as I do, would you mind sharing with me if you have lag to view videos with higher resolutions (like 4k or even 1080p)?
It's almost impossible for me to watch to those said videos.. lag is unbearable..

Try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-27426326

 

[jowaju]

So, conversion to APFS suceeded, but OS not (14.6) starting.
Trying to apply APFS patch via dosdude installstick, but it's greyed out.
What is the next step?

Finally dug into this issue this week and have come up with a working solution that does not require an in-place install. The issue is you have a working HFS+ bootable partition with Mojave 10.14 installed. You want to convert to APFS. Booting to a patched installer, running disk utility, unmount the volume to be converted, then choosing convert to APFS from the Edit menu will convert your drive to APFS successfully, but will result in a non-bootable system. This occurs because the Preboot container is not created during a conversion, but is needed for proper booting of the APFS container as a whole. We need to manually create the Preboot volume, copy a few system files over, and re-bless the container for booting.

If you want a working Recovery partition, I suggest doing it BEFORE the APFS conversion, I had zero success getting it to work once the drive was converted. What did work for me was using the script here :
https://github.com/rtrouton/create_macos_recovery to create the Recovery partition, then boot to the patched Mojave installer, choose post-install, and ONLY check the box that says "Recovery Partition Patch". Reboot and verify your Recovery partition is working properly. Note - The script above requires a full installer app as an argument for the script, it also downloads a .pkg file with a High Sierra Recovery image. When it actually builds the recovery partition, it puts whatever version is in the installer app you provide, NOT the High Sierra one it downloads. I fed it my 10.14.3 Mojave app and that's what the Recovery partition had when it got done. I simply dragged the script to a terminal window and then dragged the App to the same terminal window and hit enter.

Now for the magic-

1. Boot to your Recovery Partition / Patched USB Installer

2. Open a Terminal Window

3. Check disk numbers - type the following command and press enter

diskutil apfs list

4. Find the APFS Container Reference disk# - We will need this disk#. We will also need the UUID of the main partition, in my case it was disk1s1 (No Specific Role) with a Mount Point of / (easiest way is to highlight and copy with the trackpad then paste later when we need it.) In the picture below the disk# is disk1 and the UUID is 3E57DC70-8876-3F79-9AE0-FEC3D7A49BF3, the volume name is Untitled

5. Create the Preboot volume manually - type the following command and press enter

diskutil apfs addVolume disk(Put your correct disk # from above here) apfs Preboot -role B

*The B must be capitalized at the end

6. Mount the Preboot folder so we can copy files to it - type the following command and press enter

diskutil apfs list

Find the disk# for the Preboot volume to mount then type the following command and press enter

diskutil mount disk#(put the correct one from above)
example diskutil mount disk1s2

7. CD into the Preboot volume - type the following command and press enter

cd /Volumes/Preboot

8. Create a folder with the same name as the UUID you copied earlier - type the following command and press enter

mkdir 3E57DC70-8876-3F79-9AE0-FEC3D7A49BF3

9. Copy files from the attached High Sierra Preboot Folder zip file to the newly created folder on the Preboot drive - type the following command and press enter

cp -R '/Volumes/Untitled/High Sierra Preboot Folder/' /Volumes/Preboot/3E57DC70-8876-3F79-9AE0-FEC3D7A49BF3

10. Re-bless the APFS container to allow booting - type the following command and press enter

bless --folder '/Volumes/Untitled/System/Library/CoreServices' --bootefi --verbose

11. Now simply reboot and your APFS drive should be visible and boot normally, you will need to choose it from the Startup Drive preferences pane once it boots to remove the 30 second default boot delay.

Please remember your machine must be able to boot APFS for this to work, install the Dosdude firmware update package to make sure it is up to date if you are unsure. Also the UUID, disk# and Volume name will all be different on your machine, this is just a guide, make sure you change the variables to your specific ones.


Rename High Sierra Preboot Folder001.zip to High Sierra Preboot Folder.zip.001 and
Rename High Sierra Preboot Folder002.zip to High Sierra Preboot Folder.zip.002

The archive was too big to upload here in one piece.

https://ipfs.io/ipfs/QmZ5KmpG4SeHF8gWrHmoLcG9a3BNAcWWQoERg4q2J1kuQL/OfficialAPFSFWUpdate.zip

 

[HDMC]

Hey guys !
Where I can download the full installer for macOS 10.14.3 ?
Anyone can provide a link ?
Thanks !

 

[Syncretic]

I ran into some trouble with the SSE4.2 partial emulator by @Syncretic that is included now in @dosdude1 tools. Somehow Excel 2016 causes kernel panics related to the SSE emu due to an invalid frame pointer there. I attach a crash dump here:

Spoiler: Crash log

*** Panic Report ***

panic(cpu 0 caller 0xffffff80036dbadd): Kernel trap at 0xffffff7f843c1e00, type 6=invalid opcode, registers:

CR0: 0x0000000080010033, CR2: 0x000000010caed2ce, CR3: 0x0000000117c09000, CR4: 0x00000000000026e0
RAX: 0x000000010caed2c4, RBX: 0x00007ffeec6edbd0, RCX: 0x000000010caed2d0, RDX: 0x00007ffeec6edbd0
RSP: 0xfffff6bd40080130, RBP: 0x00007ffeec6ed870, RSI: 0x00007ffeec6edb68, RDI: 0x000000000000000f
R8: 0x00007ffeec6edbd0, R9: 0xbe792c8288f23546, R10: 0x0000000000000003, R11: 0x0000000181905000
R12: 0xbe792c8288f23546, R13: 0x00007ffeec6eddb0, R14: 0x00000000000ae2b8, R15: 0xffa0ffffff830b0f
RFL: 0x0000000000010083, RIP: 0xffffff7f843c1e00, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x000000010caed2ce, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0
Backtrace (CPU 0), Frame : Return Address
0xffffff800337fcd0 : 0xffffff80035ae6ed
0xffffff800337fd20 : 0xffffff80036ea185
0xffffff800337fd60 : 0xffffff80036db8ba
0xffffff800337fdd0 : 0xffffff800355bb40
0xffffff800337fdf0 : 0xffffff80035ae107
0xffffff800337ff10 : 0xffffff80035adf53
0xffffff800337ff80 : 0xffffff80036dbadd
0xffffff80033800f0 : 0xffffff800355bb40
0xffffff8003380110 : 0xffffff7f843c1e00
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0x7ffeec6ed870
Kernel Extensions in backtrace:
AAA.LoadEarly.MouSSE(0.38)[7DDA536B-57F7-33B2-A5DC-7ABB923F9C59]@0xffffff7f843c1000->0xffffff7f843c5fff
BSD process name corresponding to current thread: Microsoft Excel
Boot args: -no_compat_check
Mac OS version:
18G103

Perhaps this can be resolved or more ppl report such incidents?
The tricky thing here for possible debugging is that most of the time the system (and Excel, yuck) work, but from time to time it just kernel panics.

That panic report is strange.

The operation of MouSSE is straightforward: if an illegal instruction (abbreviated #UD) occurs anywhere - user space or kernel space - the CPU traps it and sends it to MouSSE. MouSSE examines the illegal instruction to see if it's POPCNT or PCMPGTQ. If it is, MouSSE emulates the instruction, and control passes back to the original code, which never even knows the #UD happened. (That's the "normal" case.) If the illegal instruction is not POPCNT or PCMPGTQ, MouSSE loads the bytes of the illegal instruction into XMM15 (16 bytes) and R15 (first 8 bytes), and passes control to the original #UD handler (MacOS). When MacOS handles the #UD and dumps the registers, backtrace, etc., MouSSE is out of the picture - you see the illegal instruction in its original context, with all registers (including RIP, the instruction pointer) referring to the original problem. The only clue that MouSSE was involved is that XMM15 and R15 are altered (to help debug the illegal instruction problem) - it does not appear in the backtrace or anywhere else.

MouSSE is hand-crafted assembly code. There should be no case where an illegal instruction can occur, but let's assume it can - so, the scenario is that a #UD occurred somewhere (Excel?), MouSSE was in the middle of handling it, then MouSSE itself threw a #UD. In that case, MouSSE is re-entered, which it was designed to handle. If the #UD in MouSSE was in a common code path, it would simply throw another #UD, invoking MouSSE again, repeating until the system crashed. We don't see that (many instances of MouSSE) here. In this case, the second #UD was successfully handled by MouSSE (presumably including loading R15) and passed on to MacOS, which panicked and created the report. What we see in the backtrace is supportive of this - one instance of MouSSE, and a plausible value for R15.

Here's where it gets strange. The bytes in R15 do, in fact, represent an invalid instruction. However, those bytes don't appear anywhere in the MouSSE executable code. In addition, the instruction pointer (RIP) in the panic report points to a valid instruction in the MouSSE code (which does not even resemble the bytes in R15).

If the RIP in the panic report is correct, the MouSSE code must have been modified, which should be impossible since the text (code) sections are marked read/execute-only (unless you're running another kext that makes the kernel writable).

I'm going to ponder this some more. In the meantime, please provide some more detail/confirmation (PM is fine, so we don't derail this thread):

• Is this a MP3,1? Mojave (exact version)?
• Are you running MouSSE for the AMD drivers? If so, is the system stable when not using Excel?
• This crash only happens when using Excel (no other programs)? I realize it doesn't always happen, but when it does, it's only when running Excel?
• Other than the dosdude1 patches, are you running any other non-Apple kexts? Especially hackintosh-type kexts (lilu, whatevergreen, etc.)? Are you using Clover or another bootloader?
• Do you have more than one crash report you could PM me? I'd like to see if there's any consistency about the addresses and/or the invalid instructions.

Thanks. I'd really like to understand this, because it shouldn't be possible.

 

[jafnelson]

hi there...installed Mojave using the latest dosdude installer on my 8,2 Macbook Pro and am getting errors trying to run either of Final Cut or iMovie,
"
This graphics configuration does not support hardware acceleration, which is required to run iMovie.
"

Tried rolling back to an old version (iMovie 9.09) which was running on High Sierra and that gives an architecture error that's barking about Skylight. Any ideas?

 

[dosdude1]

hi there...installed Mojave using the latest dosdude installer on my 8,2 Macbook Pro and am getting errors trying to run either of Final Cut or iMovie,
"
This graphics configuration does not support hardware acceleration, which is required to run iMovie.
"

Tried rolling back to an old version (iMovie 9.09) which was running on High Sierra and that gives an architecture error that's barking about Skylight. Any ideas?

Re-installing the Legacy Video Card Patch using Patch Updater should solve that issue.

 

[jackluke]

Finally dug into this issue this week and have come up with a working solution that does not require an in-place install. The issue is you have a working HFS+ bootable partition with Mojave 10.14 installed. You want to convert to APFS. Booting to a patched installer, running disk utility, unmount the volume to be converted, then choosing convert to APFS from the Edit menu will convert your drive to APFS successfully, but will result in a non-bootable system. This occurs because the Preboot container is not created during a conversion, but is needed for proper booting of the APFS container as a whole. We need to manually create the Preboot volume, copy a few system files over, and re-bless the container for booting.

View attachment 875872


If you want a working Recovery partition, I suggest doing it BEFORE the APFS conversion, I had zero success getting it to work once the drive was converted. What did work for me was using the script here :
https://github.com/rtrouton/create_macos_recovery to create the Recovery partition, then boot to the patched Mojave installer, choose post-install, and ONLY check the box that says "Recovery Partition Patch". Reboot and verify your Recovery partition is working properly. Note - The script above requires a full installer app as an argument for the script, it also downloads a .pkg file with a High Sierra Recovery image. When it actually builds the recovery partition, it puts whatever version is in the installer app you provide, NOT the High Sierra one it downloads. I fed it my 10.14.3 Mojave app and that's what the Recovery partition had when it got done. I simply dragged the script to a terminal window and then dragged the App to the same terminal window and hit enter.

Now for the magic-

1. Boot to your Recovery Partition / Patched USB Installer

2. Open a Terminal Window

3. Check disk numbers - type the following command and press enter

diskutil apfs list

4. Find the APFS Container Reference disk# - We will need this disk#. We will also need the UUID of the main partition, in my case it was disk1s1 (No Specific Role) with a Mount Point of / (easiest way is to highlight and copy with the trackpad then paste later when we need it.) In the picture below the disk# is disk1 and the UUID is 3E57DC70-8876-3F79-9AE0-FEC3D7A49BF3, the volume name is Untitled

View attachment 875879


5. Create the Preboot volume manually - type the following command and press enter

diskutil apfs addVolume disk(Put your correct disk # from above here) apfs Preboot -role B

*The B must be capitalized at the end

6. Mount the Preboot folder so we can copy files to it - type the following command and press enter

diskutil apfs list

Find the disk# for the Preboot volume to mount then type the following command and press enter

diskutil mount disk#(put the correct one from above)
example diskutil mount disk1s2

7. CD into the Preboot volume - type the following command and press enter

cd /Volumes/Preboot

8. Create a folder with the same name as the UUID you copied earlier - type the following command and press enter

mkdir 3E57DC70-8876-3F79-9AE0-FEC3D7A49BF3

9. Copy files from the attached High Sierra Preboot Folder zip file to the newly created folder on the Preboot drive - type the following command and press enter

cp -R '/Volumes/Untitled/High Sierra Preboot Folder/' /Volumes/Preboot/3E57DC70-8876-3F79-9AE0-FEC3D7A49BF3

10. Re-bless the APFS container to allow booting - type the following command and press enter

bless --folder '/Volumes/Untitled/System/Library/CoreServices' --bootefi --verbose

11. Now simply reboot and your APFS drive should be visible and boot normally, you will need to choose it from the Startup Drive preferences pane once it boots to remove the 30 second default boot delay.

Please remember your machine must be able to boot APFS for this to work, install the Dosdude firmware update package to make sure it is up to date if you are unsure. Also the UUID, disk# and Volume name will all be different on your machine, this is just a guide, make sure you change the variables to your specific ones.


Rename High Sierra Preboot Folder001.zip to High Sierra Preboot Folder.zip.001 and
Rename High Sierra Preboot Folder002.zip to High Sierra Preboot Folder.zip.002

The archive was too big to upload here in one piece.

https://ipfs.io/ipfs/QmZ5KmpG4SeHF8gWrHmoLcG9a3BNAcWWQoERg4q2J1kuQL/OfficialAPFSFWUpdate.zip

I guess the HighSierra Preboot files/folder are valid for Mojave (and probably Catalina too) because essentially the APFS Preboot is just an UUID bootloader, moreover the HighSierra Preboot should be always correctly generated when you convert from DiskUtility the HighSierra HFS+ to APFS, because apple officially allowed that, instead when someone attempt to convert a Mojave HFS+ to APFS, apple officially don't allowed that, that's why resulting in an incomplete APFS scheme, so manually creating the Preboot UUID folder, in this case copying the HighSierra content, it will work, probably on Catalina too.

But I guess this might not work if the hard drive is encrypted with Filevault 2.

Instead I can say (because I've already tested), if you clone only the Mojave APFS System Volume content inside an empty formatted HFS+ Volume, this will make one only Mojave HFS+ bootable Volume.

 

[0403979]

BlueSky 2.0 is out now. Older versions will no longer function. https://github.com/rmc-team/bluesky/releases/tag/2.0

Release notes for BlueSky 2.0:

• Add new SkyLight patches, full transparency patch
• Use bash for script
• Include resources in source

Important notes:

• This tool isn't needed for macOS Patcher users.

 

[shirsch]

BlueSky 2.0 is out now. Older versions will no longer function. https://github.com/rmc-team/bluesky/releases/tag/2.0

Release notes for BlueSky 2.0:

• Add new SkyLight patches, full transparency patch
• Use bash for script
• Include resources in source

Important notes:

• This tool isn't needed for macOS Patcher users.

Did you ever get a chance to look into the problems I reported with Macports Emacs and the XQuartz environment?

 

[0403979]

Did you ever get a chance to look into the problems I reported with Macports Emacs and the XQuartz environment?

I did not, but these patches are completely different. Only SkyLight is patched as detailed here.