Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I've gotten a ton, but they literally give NO info on what's causing the issue. Always a random last loaded process, and the usual list of loaded kernel extensions. Nothing more.
Oh dear god please Brazil win, we can't possibly have England win, they will never shut up about it, they keep reminding us at any opportunity that they won in 1966, 52 flipping years ago.
Would we be able to strip all the kexts and slowly add them back in until we find the culprit?
_____
These kernel panics are also quite noticeable on a MacBookPro6,1 17" mid-2010.
Is the procedure alluded to using the discrete GPU disabler reversible (in case the kexts or 10.14 itself gets better)? If so, how?
It is (from developer 2 to developer 3). But if you have public beta 1, then you have to wait until public beta 2 is available). Just note that developer 2 = public 1.
Already tried something similar, I copied all the kexts from the installer (which WILL boot just fine) into a full OS, set perms as necessary and rebuilt kextcache, and it still did the same thing. This indicates it's some userland framework causing the issue, finding which ones is going to be quite difficult.
[QUOTE = "G5-PowerLifter, post: 26215787, member: 1069294"] Come on guys stop speaking south american [/ QUOTE]
That's alright. Gave me a chance to turn on the option of "translation" on Chrome.
It did work, although I am not sure if the translation was accurate or not. Looks like it was.
Mahalo (Hawaiian for Thank You)
That's alright. Gave me a chance to turn on the option of "translation" on Chrome.
It did work, although I am not sure if the translation was accurate or not. Looks like it was.
Mahalo (Hawaiian for Thank You)
Last edited:
With them
I have the same feeling it’s a framework. Guess we could start with the install or recovery disk frameworks and see how many are left.
I agree it will be painstaking and will take awhile.
Maybe if we list all of the possible frameworks thst it could be we could get a group of people to work on it. Help carry the load.
I have the same feeling it’s a framework. Guess we could start with the install or recovery disk frameworks and see how many are left.
I agree it will be painstaking and will take awhile.
Maybe if we list all of the possible frameworks thst it could be we could get a group of people to work on it. Help carry the load.
Ola boa noite fiz toda instalacao mas em APFS nao funciona somente em mac os extended procede isso desde ja muito obrigado
Hello good night I did all installation but in APFS it does not work only on mac the extended proceed this way already thank you very much
Hello I have the same Mac model I am running macos Mojave so the sound is not working. I tried many options but the problem persists. Could you help me please? Thanks
Well, I found that these frameworks are intertwined and has lot of new dependencies....and, yeah finding the culprit/culprits will be difficult.
Just to lower the list, I think someone needs to concentrate on frameworks that are on Mojave but not in HS....but that list alone I think is large...Just a thought
Last edited:
I just tried to update my Early 2011 15 inch MacBook Pro to Mojave using the Patcher tool. I followed all the directions pretty closely and the installation process seemed to go by without a hitch. But at the very end of the process, after my computer Restarted, I got the No Exit symbol upon startup. Does anyone know what I can do to fix this? I do have a Time Machine backup so it's not really the end of the world, plus this laptop is not my daily driver. However, I would like to fix the problem and get Mojave running on this machine. Any help?
Try installing the latest "trunk" build of Chromium, which likely has already been fixed for Mojave:
https://chromium.woolyss.com/
click on the top one, where "Installer" is highlighted in blue.
If it works (fixes were in fact implemented), then you can expect those fixes to make it "downstream" into Chrome stable in about 1-2 months. (!) No wonder it doesn't work on Chrome stable/Official Build...
Chromium is super extra incredibly bleeding edge and lacks the "Widevine" DRM monster (no netflix, hulu), "Pepper" Flash (so no adobe flash/shockwave) and any other proprietary code/codecs like h.264, so it will play Youtube perfectly fine (if it has been fixed for Mojave) but some other websites will break. Youtube by default uses VP9, so it is unaffected by the uninclusion of proprietary codecs.
It does not auto-update. Chrome Canary is a few days behind, so test Chromium first.
[doublepost=1530847521][/doublepost]
You betcha, just do a
find /System/Library/Frameworks -name '*.framework' and a
find /System/Library/PrivateFrameworks -name '*.framework'
on both HS and Mojave and then run a diff between the two output file lists.
(the -name is to find nested frameworks within another one, so to get a complete list)
Attachments on DP1 are broken for me, and I haven't yet updated, so if someone could run those commands on Mojave and High Sierra and /usr/bin/diff the two outputs and post that, it would be a great help.
Last edited:
Yes, I did... after seeing the No Exit symbol I had to force Shut Down, and held down Option whilst the computer restarted. Then I clicked on the Post Install patch and ran it. After it installed a few things, a Reboot button popped up and then I clicked on that. The computer restarted but I'm still seeing the No Exit symbol
Last edited:
Ah, you probably installed to an APFS partition... I still need to modify the tool to properly patch that. In the meantime, you can either erase and install to an HFS formatted volume, or just run the following in Terminal:Yes, I did... after seeing the No Exit symbol I had to force Shut Down, and held down Option whilst the computer restarted. Then I clicked on the Post Install patch and ran it. After it installed a few things, a Reboot button popped up and then I clicked on that. The computer restarted but I'm still seeing the No Exit symbol
sudo nvram boot-args=-no_compat_check
(leave off sudo if running from the installer drive or singleuser mode.)
Yes, it was installed to an APFS drive. Followed your instructions (erase and install) and now at least I can boot up properly without the No Exit sign, thank you! I am getting some glitches, where the graphics 'ripple' in instead of automatically appearing. Is this expected behavior? Or is there a way to fix that? Should I run the Post Install patch?
You have an AMD GPU, and as stated in the OP, acceleration doesn't work on those yet. That's what happens in OS X when you have no video acceleration.
Right, I ran the Post Install patch and at least I'm not seeing the ripple effect anymore, that's cool.. THANK YOU so much for helping with the installation by the way! I'm typing this reply on my MBP right now
At least that is progress? So how again did you boot into the OS, I want to get this done! I have weeks free, so I can get some things done
I believe you misunderstood. By "it still did the same thing", he means that it still crashes. I've tried the same.
Also done some screwing around with disabling different LaunchDaemons. No progress yet. But I agree with @dosdude1 that it's not kext-related.
Yup! At least my machine is running
The problem in the beginning was that my System Drive was formatted to the AFPS format. I did an Erase and Install to the the Mac OS Journaled HFS format. Then I was able to reinstall Mojave correctly. After that, I ran the Post Install patcher for good measure because I was seeing some graphic glitches.. now those glitches are gone. There is a very slight lag graphic wise throughout the entire system, but it's expected since my machine is non-Metal.
Hi
Experimented with Mojave Patcher.
I'm trying to get a GeForce GTX 260.
Also copied a file about which parrotgeek1 wrote - /System/Library/Frameworks/coredisplay.frameworkfrom 10.14 beta 1.
The result is identical.
I tried all patches of models in Mojave Patcher.
For patches under imac11.2, imac11.3, imac12.1, macbookair4.1, macbookair4.2, macbookpro6.1, macbookpro6.2, macmini5.1, macmini5.2, macmini5.3 - the result is bad.
Unless on patches from laptops that were started both monitors, but the second monitor went duplicating.
For patches under imac11.1, imac12.2, macbookpro8.1-8.3, macpro4.1 - the most successful result at the moment:
namely to define 2 monitors, the resolution on the second monitor is also identical, on the first 1024x720;
and only on these patches after the login screen allows to log into the system, but after almost complete initialization of the system hangs tightly, also the top bar menu as if it is not active and darkened.
Also I want to note that the system runs without any correct drivers and everything works there, only friezes and artifacts.
NVDANV50HalTesla is loaded without errors, only as I understood the identification of the NDRVShim load can not be determined.
My system Hackintosh - identify imac11,1.
Intel i5-750 3Ghz (Overlocking)
GeForce GTX 260
MSI P55-CD53
SSD Kingston 240GB
Successfully run macOS 10.13.5.
Help me, please.
Experimented with Mojave Patcher.
I'm trying to get a GeForce GTX 260.
Also copied a file about which parrotgeek1 wrote - /System/Library/Frameworks/coredisplay.frameworkfrom 10.14 beta 1.
The result is identical.
I tried all patches of models in Mojave Patcher.
For patches under imac11.2, imac11.3, imac12.1, macbookair4.1, macbookair4.2, macbookpro6.1, macbookpro6.2, macmini5.1, macmini5.2, macmini5.3 - the result is bad.
Unless on patches from laptops that were started both monitors, but the second monitor went duplicating.
For patches under imac11.1, imac12.2, macbookpro8.1-8.3, macpro4.1 - the most successful result at the moment:
namely to define 2 monitors, the resolution on the second monitor is also identical, on the first 1024x720;
and only on these patches after the login screen allows to log into the system, but after almost complete initialization of the system hangs tightly, also the top bar menu as if it is not active and darkened.
Also I want to note that the system runs without any correct drivers and everything works there, only friezes and artifacts.
NVDANV50HalTesla is loaded without errors, only as I understood the identification of the NDRVShim load can not be determined.
My system Hackintosh - identify imac11,1.
Intel i5-750 3Ghz (Overlocking)
GeForce GTX 260
MSI P55-CD53
SSD Kingston 240GB
Successfully run macOS 10.13.5.
Help me, please.