macOS 10.14 Mojave on Unsupported Macs Thread

[flyinmac]

Early 24-inch 2009 iMac9./ core2duo 2.66/1 8GB/1TB SSD (Electra G3)/ NVIDIA GeForce 9400 256 MB graphics.
iSight works.

Thank you. I might have to give it a try once I backup my High Sierra installation again.

 

[BookEmDanno]

Oh no, that's a shame. Wanted to try Group FaceTime.

That's exactly what I wanted to test as well.

 

[oscarodas]

Oh no, that's a shame. Wanted to try Group FaceTime.

I managed to install it on my iMac 27 2011

 

[jackluke]

But how I can do that?
Do you mean that i have to copy this folder/file System/Library/PrelinkedKernels/prelinkedkernel inside APFS recovery partition (where PlatformSupport.plist is it?)???
Sorry but with my english i don't understand somethings.

Yes, just that file "prelinkedkernel" inside your APFS Recovery (where PlatformSupport.plist is), you have to overwrite the one already there with yours Mojave one.

 

[lumos]

I have upgraded my MacPro 3,1 from High Sierra to Mojave.
The High Sierra FS was HFS+ with trimforce enable.
Later I converted it to APFS but now my Samsung EVO 850 Pro, does not have anymore the Trim Enabled (before, with High Sierra HFS+ was enabled).

Is this correct because APFS has its own trim function or I need to enable trim with a utility like Trime Ebabler https://cindori.org/trimenabler/?

Thanks

Any suggestion on this?

 

[gnubee]

vi / vim are the worlds best text editors when working from the command line inside of *nix type machines. This is a good read / reference if interested: http://shop.oreilly.com/product/9780596529833.do. Of course, the old timers say, real coders use sed to get the job done.

 

[Kaitozaki]

My imac is stuck after update, stays at apple logo with the loading bar full...i already tried with the latest 1.2.2 patch still not working...is the problem fixed? Using imac 2011 27"

 

[jackluke]

My imac is stuck after update, stays at apple logo with the loading bar full...i already tried with the latest 1.2.2 patch still not working...is the problem fixed? Using imac 2011 27"

Typical Corebrightness issue symptom try this: fix apple logo full progress bar
[doublepost=1538468418][/doublepost]

Any suggestion on this?

That app does the same of terminal command through a GUI, however terminal way is more effective:
sudo trimforce enable

 

[lumos]

Typical Corebrightness issue symptom try this: fix apple logo full progress bar
[doublepost=1538468418][/doublepost]

That app does the same of terminal command through a GUI, however terminal way is more effective:
sudo trimforce enable

I have tried many times with sudo trimforce enable, but the trim is always OFF.
For this reason I ask.
[doublepost=1538469351][/doublepost]

Typical Corebrightness issue symptom try this: fix apple logo full progress bar
[doublepost=1538468418][/doublepost]

That app does the same of terminal command through a GUI, however terminal way is more effective:
sudo trimforce enable

Never mind, I have tried in a different mode and now its work:

1. sudo su
2. trimforce enable

Instead sudo trimforce enable

Don't ask me why...

 

[arqueox]

It seems that Xcode command line points to another location, however at the moment one attempt could be booting from USB Mojave Installer, launch Terminal and try to replace the HItoolbox framework inside the Installer with the one installed into your Mojave disk, try this type in one line:

cp /Volumes/YourUSBInstallerLabel/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox /Volumes/YourMojaveDiskLabel/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/

edit:
I'm not sure it will 100% work, cause the HIToolbox size inside the USB Installer is 4,8 MB , while the stock Mojave one is 10,2 MB, however I guess it will work, they are from the same Mojave build.

edit2:
Don't do I'll test right now for you.

edit3:
I've done, using the HItoolBox 4,8 MB inside "USB Installer/Recovery" replacing the stock Mojave HIToolBox 10,2 MB works perfectly and it seems even faster.

Just tryed that and the error persists.... What the hell!?

 

[yeiyei0891]

Yes, just that file "prelinkedkernel" inside your APFS Recovery (where PlatformSupport.plist is), you have to overwrite the one already there with yours Mojave one.

I replaced the file in the path
/Volumes/Recovery/YourAPFSmainUUID/PlatformSupport.plist

with the file in the path
System/Library/PrelinkedKernels/prelinkedkernel

but it didn't work, the trackpad, mouse and keyboard are still frozen, I think the recovery menu is completely frozen.

 

[jackluke]

I replaced the file in the path
/Volumes/Recovery/YourAPFSmainUUID/PlatformSupport.plist

with the file in the path
System/Library/PrelinkedKernels/prelinkedkernel

but it didn't work, the trackpad, mouse and keyboard are still frozen, I think the recovery menu is completely frozen.

pre-edit:
Try, but I know only from Terminal, landing inside your APFS Recovery folder, type:
sudo touch prelinkedkernel

They are frozen cause IOUSB*** legacy kexts are missing from Mojave prelinkedkernel, however try to copy the "BaseSystem.dmg" from the Mojave Installer into the APFS Recovery, this should work.

 

[ZigMac]

First thing I need to know: Do you have graphics acceleration?

Let me Google what that is and I'll let you know

 

[jackluke]

Just tryed that and the error persists.... What the hell!?

But you can't boot to the Mojave GUI right ?
What's the last thing you did before that error occured?
I guess you have to re-install at this point.

 

[arqueox]

But you can't boot to the Mojave GUI right ?
What's the last thing you did before that error occured?
I guess you have to re-install at this point.

I have made a fresh install of the final Mojave version. Then, installed Xcode 10 and command line. That's the only thing I have done. And the error appears everytime. But, just tryed a Hitoolbox patched file and it worked on the system. LightMode works as expected from Github rules... but when I try to implement the .sh file on terminal, always gives me this error. Strange. It looks like the system search in the wrong place and says that In that specific place there is no such file or directory. Odd.

 

[yeiyei0891]

pre-edit:
Try, but I know only from Terminal, landing inside your APFS Recovery folder, type:
sudo touch prelinkedkernel

They are frozen cause IOUSB*** legacy kexts are missing from Mojave prelinkedkernel, however try to copy the "BaseSystem.dmg" from the Mojave Installer into the APFS Recovery, this should work.

I don't know what i have to do whit this you say:
Try, but I know only from Terminal, landing inside your APFS Recovery folder, type:
sudo touch prelinkedkernel

I tried replacing all files in:
/Volumes/Recovery/YourAPFSmainUUID/PlatformSupport.plist

with those in:
System / Library / PrelinkedKernels / prelinkedkernel

but it did not work either.

I tried replacing BaseSystem.dmg from Installer macOS Mojave.app and it did not work either.
This seems very complicated just to make the recovery work.

 

[jackluke]

I don't know what i have to do whit this you say:
Try, but I know only from Terminal, landing inside your APFS Recovery folder, type:
sudo touch prelinkedkernel

I tried replacing all files in:
/Volumes/Recovery/YourAPFSmainUUID/PlatformSupport.plist

with those in:
System / Library / PrelinkedKernels / prelinkedkernel

but it did not work either.

I tried replacing BaseSystem.dmg from Installer macOS Mojave.app and it did not work either.
This seems very complicated just to make the recovery work.

Agree, the fact is that APFS Recovery Container (even if HFS+) is a particular Recovery kind, however try to replace also the immutablekernel files from your Mojave into Recovery, to do that "sudo touch" command, you have to navigate from Terminal into the path:

diskutil list
diskutil mount diskXsY (where your Recovery disk is)
cd /Volumes/Recovery/YourAPFSmainUUID/
sudo touch prelinkedkernel

 

[yeiyei0891]

Agree, the fact is that APFS Recovery Container (even if HFS+) is a particular Recovery kind, however try to replace also the immutablekernel files from your Mojave into Recovery, to do that "sudo touch" command, you have to navigate from Terminal into the path:

diskutil list
diskutil mount diskXsY (where your Recovery disk is)
cd /Volumes/Recovery/YourAPFSmainUUID/
sudo touch prelinkedkernel

I tried writing that command in the terminal but it still doesn't work. Nothing has changed replacing files or with that command

 

[greymda]

hey guys

yesterday the updater said it has a new version of Night Shift patch, installed it and.. cannot boot on my macbook pro 5,5 anymore. at first macbook got slower, a lot of hang-ups and so on.
now it's a blinking folder with a question mark in it and that's it...

anyone else encountered such an issue?

 

[webg3]

pre-edit:
Try, but I know only from Terminal, landing inside your APFS Recovery folder, type:
sudo touch prelinkedkernel

They are frozen cause IOUSB*** legacy kexts are missing from Mojave prelinkedkernel, however try to copy the "BaseSystem.dmg" from the Mojave Installer into the APFS Recovery, this should work.

Delete all data from Recovery and try to recreate it on MacBook Pro 7.1 but it did not work, it continues with a forbidden symbol when pressing CMD + R

I created a new container named Recovery by Disk Utility and I cloned the patched pendrive, it occupied 8GB, I would like to delete the Recovery container (default) that has been empty, already tried anyway and does not leave, it is only as an unwanted entry, without any serventia.

 

[lumos]

I have only one problem left after the update of my MacPro 3,1 from HS.
My LED Cinema Display iSight does not work, the green led turno on but there is no image.
I have not the Virtual Box app installed, anyway I have VMWare, I don't think the Virtual Box solution can be researched for VMWare.
There is other workarounds or fix for the iSight?

 

[webg3]

I have only one problem left after the update of my MacPro 3,1 from HS.
My LED Cinema Display iSight does not work, the green led turno on but there is no image.
I have not the Virtual Box app installed, anyway I have VMWare, I don't think the Virtual Box solution can be researched for VMWare.
There is other workarounds or fix for the iSight?

IOUSB*** legacy kexts

 

[yeiyei0891]

Delete all data from Recovery and try to recreate it on MacBook Pro 7.1 but it did not work, it continues with a forbidden symbol when pressing CMD + R

I created a new container named Recovery by Disk Utility and I cloned the patched pendrive, it occupied 8GB, I would like to delete the Recovery container (default) that has been empty, already tried anyway and does not leave, it is only as an unwanted entry, without any serventia.

How have you cloned it?

 

[webg3]

How have you cloned it?

CCC (Carbon Copy Cloner) 5.1.5

 

[lupine]

Trying to get up and running on a Mac Pro 2008, but I'm having all kinds of grief with the video card. I have a Mac-flashed 7950 on board (which would show the boot screen), and the whole system worked fine with High Sierra and dosdude1's patch. So I figured I'd upgrade.

The initial upgrade appeared to go well. No errors during the initial install, got all the way through to the reboot. Then no boot screen. No display at all. Holding option on boot doesn't seem to let me choose to boot from the install USB, though I tried bless'ing it from SSH with no success either.

From SSH, I can watch /var/log/system.log which shows that WindowServer is repeatedly crashing. I had a look at the crash file for this, and it shows the following (abridged):

Process:               WindowServer [2338]
Path:                  /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier:            WindowServer
Version:               600.00 (336.80.6)
System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [2338]

Application Specific Information:
StartTime:2018-10-02 20:14:22
GPU:AMD
MetalDevice for accelerator(0x0): 0x7fbb7f409ec8 (MTLDevice: 0x7fbb8305be00)
MetalDevice for accelerator(0x343b): 0x7fbb7f719808 (MTLDevice: 0x7fbb8305be00)
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/NRP5@5/IOPP/PXS1@0/ATY,Hamachi@0/AMDFramebufferSI

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.AMDRadeonX4000GLDriver    0x000000014dac0089 glrATI_SI_InitMiscTextureInfo + 177
1   com.apple.AMDRadeonX4000GLDriver    0x000000014daf9d46 glrATI_SI_InitHardwareContext + 270
2   com.apple.AMDRadeonX4000GLDriver    0x000000014daab365 glrInitializeContext + 26
3   libGPUSupportMercury.dylib        0x00007fff497524a5 gldCreateContext + 1221
4   GLEngine                          0x00007fff37e06959 gliCreateContextWithShared + 691
5   com.apple.SkyLight                0x00007fff53cfb5ac slglsCreateContext + 247
6   com.apple.SkyLight                0x00007fff53dfeed9 initialize_display_context + 1794
7   com.apple.SkyLight                0x00007fff53dfe674 CGXInitializeGL + 18
8   com.apple.SkyLight                0x00007fff53e01613 WSInitialize + 3359
9   com.apple.SkyLight                0x00007fff53e960ae SLXServer + 1138
10  WindowServer                      0x000000010b15e4cc 0x10b15d000 + 5324
11  libdyld.dylib                     0x00007fff5adee085 start + 1

So it's crashing deep inside the driver for the display. But I don't think that explains why I've lost my boot screen. Did the installer try to update my display's BIOS? I've tried flicking the alternate bios switch on the card with no success.

Anybody else had any experience with this combination? Is there any way to get back to a working mac? Still have my 2016 MBP daily driver, but it'd be nice to get a desktop back too (or at least to a working state so I could sell it...)