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.
Good morning. Suddenly my MacBook 5.1 running the DP of Mojave 10.14.0 crashed (spinnig ball stopped spinning) and when rebooted my primary SSD with the booting partition with Mojave is not detected anymore. It was formattted as HFS++, nothing special done, there was no any sign of any potential damages... What can be an explanation for this, has anybody already seen such?
Thank you
 
Did a reinstall and issue resolved.
I think it was one of the patches I installed.
[doublepost=1542329307][/doublepost]
Change the patches selected with a reinstall it resolved mine

I guess the BT kexts inside the USB Installer are equivalent to those when reinstalling, your Mini server 2011 doesn't require the USB patches since it's a Sandy Bridge, however even patching with the USB legacy doesn't affect in any way the BT because on your machine the BT/Wifi is a combo all-in-one mini-PCIExpress card then the only patch involved into BT is the Wifi Patch, so most probably your machine doesn't need USB/Wifi patches but only a stock Mojave BT kext.
 
  • Like
Reactions: TimothyR734
I guess the book only shows additional I / O as long it's connected. Tested here on a supported MBP 2012.
Partially correct: In system report (audio section) it was shown at any time, connectors plugged in or not.
Only in the system settings for audio input/output S/PDIF seems only to be available when an optical connector is plugged in. This was the case on MacBook Pro (with "miniTOSLink"), but different on Mac Pro having larger connectors for TOSLink and separate 3.5mm jacks for analog audio.
See screenshot (Mojave, MB 4,1) / photo (El Cap, MB 4,1).
 

Attachments

  • IMG_9327.jpg
    IMG_9327.jpg
    3.3 MB · Views: 177
  • Bildschirmfoto 2018-11-16 um 11.16.47.jpg
    Bildschirmfoto 2018-11-16 um 11.16.47.jpg
    72.9 KB · Views: 153
  • Like
Reactions: TimothyR734
I have the same machine. Download Patcher v1.2.3, download full Mojave 14.1 from the Patcher, make a brand new USB with 14.1 through the Patcher and finally proceed to instal as per @dosdude1 instructions.
Forget about updates from Software Update and Mojave betas. Both are a pile of trouble. Especially betas are for moments when you are bored to death and are looking for ways to complicate your life. Most of the time the benefit of betas is pretty much zero.
[doublepost=1542368094][/doublepost]Hello! I'm experiencing a strange behavior of my Mac mini 2010 (macmini4,1) with Mojave 10.14.1 patched with @dosdude1 patcher v1.2.3 after months of perfect working. Suddenly, after reboot, macOS 10.14.1 loading bar is stucked endlessly. I have tried installing on external and Macintosh HD drives, also reinstalling patches, forcing cache clearing, resetting the PRAM with command-option-P-R. After working well for some time soon suddenly on reboots again the loading bar is stucked >50% endlessly. PS: How can I try unpached recovery on a patched system? If I try to start it, system stops immediately with the forbidden sign.

[Edit] Solved reinstalling all from scratch on a new partition and then transferring data and apps from the blocked system. I think that was caused by Clean my Mac X optimization scripts, and @dosdude1 patch was perfectly working as always. But if I would load macOS Mojave recovery mode, how can I solve system hanging? I cannot apply Mojave Patches on recovery from USB installer.
 
Last edited:
Hi recently I get problem with wifi in mojave 10.14 so my wifi work but I cant connect to any of ssid so sometimes its lag searching over and over ssid s and unable to connect anymore im on macbook 5.2 mid 2009
[doublepost=1542380946][/doublepost]
Hi recently I get problem with wifi in mojave 10.14 so my wifi work but I cant connect to any of ssid so sometimes its lag searching over and over ssid s and unable to connect anymore im on macbook 5.2 mid 2009

@dosdude1
 

Attachments

  • Screen Shot 2018-11-16 at 6.35.07 PM.png
    Screen Shot 2018-11-16 at 6.35.07 PM.png
    972.6 KB · Views: 200
  • Like
Reactions: TimothyR734
Good morning. Suddenly my MacBook 5.1 running the DP of Mojave 10.14.0 crashed (spinnig ball stopped spinning) and when rebooted my primary SSD with the booting partition with Mojave is not detected anymore. It was formattted as HFS++, nothing special done, there was no any sign of any potential damages... What can be an explanation for this, has anybody already seen such?
Thank you
What SSD have you been running on? An OCZ Vertex by any means? If so, this would be the second incident of this SSD dying, although mine died upon updating my unsupported MacBook Pro 8,1 to 10.14.1. Until I read your post I did not suspect Mojave to be the culprit but rather thought it is coincidental. It could still be, as a friends unsupported 17’’ did upgrade just fine on a Samsung SSD.

Both drives were parts of custom fusion drive configurations using the APFS Apple file system.

Could you provide additional information?
 
As related to my no display sleep no machine sleep issue.

The no display sleep would seem to be a control issue between the machine and the display and not process related.
 
  • Like
Reactions: TimothyR734
[doublepost=1542368094][/doublepost]Hello! I'm experiencing a strange behavior of my Mac mini 2010 (macmini4,1) with Mojave 10.14.1 patched with @dosdude1 patcher v1.2.3 after months of perfect working. Suddenly, after reboot, macOS 10.14.1 loading bar is stucked endlessly. I have tried installing on external and Macintosh HD drives, also reinstalling patches, forcing cache clearing, resetting the PRAM with command-option-P-R. After working well for some time soon suddenly on reboots again the loading bar is stucked >50% endlessly. PS: How can I try unpached recovery on a patched system? If I try to start it, system stops immediately with the forbidden sign.
[doublepost=1542368454][/doublepost]Hello! I'm experiencing a strange behavior of my Mac mini 2010 (macmini4,1) with Mojave 10.14.1 patched with @dosdude1 patcher v1.2.3 after months of perfect working. Suddenly, after reboot, macOS 10.14.1 loading bar is stucked endlessly. I have tried installing on external and Macintosh HD drives, also reinstalling patches, forcing cache clearing, resetting the PRAM with command-option-P-R. After working well for some time soon suddenly on reboots again the loading bar is stucked >50% endlessly. PS: How can I try unpached recovery on a patched system? If I try to start it, system stops immediately with the forbidden sign.

Can't fix it if we have no information on what's going wrong. Hold Command+V while you boot so we can get some more info on where it's sticking.
 
Partially correct: In system report (audio section) it was shown at any time, connectors plugged in or not.
Only in the system settings for audio input/output S/PDIF seems only to be available when an optical connector is plugged in. This was the case on MacBook Pro (with "miniTOSLink"), but different on Mac Pro having larger connectors for TOSLink and separate 3.5mm jacks for analog audio.
See screenshot (Mojave, MB 4,1) / photo (El Cap, MB 4,1).

Interesting. System report is not showing the Intel Audio section at all on my MBP 2012.
On my cMP 1,1 and 5,1 it's excactly as you say. S/PDIF is shown in audio system settings and the system report. I can't find a mini Toslink cable to check if the behaviour on the MBP is driver related (broken installation) or supposed to be like that. I just remembered that it only shows up if connected (like it does with headphones connected)

EDIT: My nMP 6,1 is not showing any S/PDIF either and it's suppose to support mini Toslink as well..
 
  • Like
Reactions: TimothyR734
Interesting. System report is not showing the Intel Audio section at all on my MBP 2012.
On my cMP 1,1 and 5,1 it's excactly as you say. S/PDIF is shown in audio system settings and the system report. I can't find a mini Toslink cable to check if the behaviour on the MBP is driver related (broken installation) or supposed to be like that. I just remembered that it only shows up if connected (like it does with headphones connected)

EDIT: My nMP 6,1 is not showing any S/PDIF either and it's suppose to support mini Toslink as well..
MacBook 5,2 - Shows in System Report in El Capitan but not in Mojave

El Capitan.png
 
Hi recently I get problem with wifi in mojave 10.14 so my wifi work but I cant connect to any of ssid so sometimes its lag searching over and over ssid s and unable to connect anymore im on macbook 5.2 mid 2009
[doublepost=1542380946][/doublepost]

@dosdude1

It appears you have a partial loaded Wifi Kext a/b/g, it should be 802.11 a/b/g/n

The kext you need is this IO80211Family.kext maybe also the stock Mojave one could work with your Wifi card.

Try to redo the Wifi Patch from the USB Mojave Post-Install, and "force cache rebuild" after.
 
This is an other problem in this case macbook wifi cant find ssid so its search again and again :(
Someone send me right kext for macbook 5.2 airport broadcom 43xx

Maybe you have installed some third party app that uses third party kext, anyway try @LuisN kext, but don't use kextwizard instead better with Terminal commands, after replaced yours:

sudo chmod -R 755 /System/Library/Extensions/
sudo chown -R 0:0 /System/Library/Extensions/
sudo kextcache -i /
sudo reboot
 
  • Like
Reactions: TimothyR734
Would love to test it and I'm quite sure I have a cable flying around somewhere..
Already turned the studio upside down and couldn't find it unfortunately. Maybe I will buy one tomorrow..
We´ve ordered 5 cables today from Amaze-off for our office use (yeah, we have to get some i.MX6 Linux board up and running and optical audio link is included in this task). Best way to test it seemed to connect it to our Macs - until I found out about Mojave driver issue now... Nevertheless, we´ll test it with El Cap and see how it´s supposed to run. Might give some hints about what to try with Mojave´s kexts.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.