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.
That 10.14.2 fix never worked on the MB4,1. Interestingly, before the patch, F1/F2 summon up the brightness overlay icon, after patching, nothing happens any more.

About the 773kB CoreBrightness binary. Tried to patch, found the right offset but to no effect.
Can you provide your patched one, pls?
(Sidenote: There are two model_min offsets now: "BLR" (which has the right format to be the nightshift) and a "Harmony" - that seems new since 10.14.5?

"Harmony" model_min was already introduced from 10.13.6 security update that I patched too, I have to check better it seems I only included few model, and surely not MB4,1.

Anyway I find some similarities between HS 17G6030 and Mojave.

I mean this: https://support.apple.com/en-us/HT209635

But I don't advise to those who own a mac supported until El Capitan, to update their HighSierra patched, since there is an important firmware update.
 
  • Like
Reactions: Larsvonhier
Cannot get 10.14.4 to run reliably on a Mini3,1 early or late version, APFS or HFS+ SSD or SSHDD. Random KPs mostly in the Finder or Control Panel.

What models run on dot 4 as reliably as dot 3?

My MBP5,2 17" does run less reliably on .4 than on .3. But when using the 9600M GT GPU (instead of 9400M) and avoiding Safari (Firefox instead) I can work with it without problems. No problems in Finder or Control Panel.
 
My MacPro3.1 is running well on 14.4. I suspect that having a metal card helps. Also, I found 14.4 recognises the upgraded wifi/BT card so that is a bonus. I also have a MBAir 4.2 and that had no problems installing 14.4 but I do not use it much so have not given it a good workout yet.


No random KPs? One late Mini3,1 ran days on .4 and then KP'd repeatedly for no repeatable reason. Installations are never a problem with a dosdude1 patcher, btw.
[doublepost=1554395546][/doublepost]
how to fix system load on 100% all the time on macbook white 6.1 2009 / apfs on mechanical hdd / 10.14.5

MRT will run at full tilt for about 2 minutes after a new install or a new account, also Spotlight could be doing it's thing?
 
That 10.14.2 fix never worked on the MB4,1. Interestingly, before the patch, F1/F2 summon up the brightness overlay icon, after patching, nothing happens any more.

About the 773kB CoreBrightness binary. Tried to patch, found the right offset but to no effect.

EDIT:
The table has grown since 10.12.x - so I missed one byte (the last one for MacBooks). Did it again, works now! Attached file is patched for all types of min. "1.x" machines (iMac, MB, MBP etc.).

(Sidenote: There are two model_min offsets now: "BLR" (which has the right format to be the nightshift) and a "Harmony" - that seems new since 10.14.5?

Exactly! Almost no need to perform the "nm" and "xxd" just search from an hex editor inside the CoreBrightness binary this: 09 00 00 00 01 00 00 00 0D 00 00 00

Then if there are no other occurrences, you are on the right line (under which you can notice the Harmony hex code ffffff7f...) and then continue the pikeralpha method.

Those are surely the minimum model identified by apple, and 0D means number 13 that is identified by pikeralpha as iMac13,1 so putting as rightly you wrote 01 will catch a iMac1,1 that apparently doesn't have much sense, but it works.

Infact I noticed your correct patch here (I only highlight 3/7 but they are):

edit: here is mine, I've not added 01 to all, but tried to include the minimum possible capable night shift machine for each model they are 7.
 

Attachments

  • cb offsets.jpeg
    cb offsets.jpeg
    85.3 KB · Views: 155
  • CoreBrightness10145b.zip
    260.5 KB · Views: 149
Last edited:
No random KPs? One late Mini3,1 ran days on .4 and then KP'd repeatedly for no repeatable reason. Installations are never a problem with a dosdude1 patcher, btw.
[doublepost=1554395546][/doublepost]
Fingers crossed, no problem with mp3.1 yet which has been used every day since 14.4 released.

MRT will run at full tilt for about 2 minutes after a new install or a new account, also Spotlight could be doing it's thing?
 
Hi,
I’m also in the game of kernel panics with 10.14.4 :(

All the way from 10.14.0 to 10.14.3 everything was painless.
Yesterday I updated my MacBook Pro 6.2 15“ to 10.14.4 by using patcher v1.3 and installed through USB (not via Software Update)
Everything went without issues, but while running macOS crashed randomly but very often, also additionally during shut-down, not only in standard operation mode.
All needed patches are installed, graphics, iSight, backlight, … work flawlessly.

I reapplied the patches and forced a cache rebuild twice, seems to be unhelpful :(

Attached you find all the crash reports!

Hopefully this helps to find our common issue!
Any tips @dosdude1 @Larsvonhier @jackluke ?
 

Attachments

  • MBP6.2 Panics.zip
    29.7 KB · Views: 150
Spouse has the exact same Alum MB (MacBook5,1(13-inch, Aluminum, Late 2008) 2 GHz Intel Core 2 Duo, 8GB 1067 MHz DDR3, NVIDIA GeForce 9400M 256MB, except APFS 250GB SSD(Samsung EVO840)) on 10.14.3. Concur more reliable and more efficient than 10.13.6.

Will .4 be a reliable upgrade?
[doublepost=1554388121][/doublepost]Then, there is this - Mini3,1 display bliss.View attachment 830315

I have a partition with 10.14.4 on my MacBook5,1 and it is running very well and stable. No KP whatsoever. From what I understand the potential issues are mostly from 3rd party apps and I don't use that many of them.
 
Hi,
I’m also in the game of kernel panics with 10.14.4 :(

All the way from 10.14.0 to 10.14.3 everything was painless.
Yesterday I updated my MacBook Pro 6.2 15“ to 10.14.4 by using patcher v1.3 and installed through USB (not via Software Update)
Everything went without issues, but while running macOS crashed randomly but very often, also additionally during shut-down, not only in standard operation mode.
All needed patches are installed, graphics, iSight, backlight, … work flawlessly.

I reapplied the patches and forced a cache rebuild twice, seems to be unhelpful :(

Attached you find all the crash reports!

Hopefully this helps to find our common issue!
Any tips @dosdude1 @Larsvonhier @jackluke ?
I´d try to get rid of the kexts from AirParrot and Cisco (and eqMacDriver whatever that is). Test the system stability without them. Another source of info could be to run and log with the tool "Etrecheck".
 
  • Like
Reactions: jackluke
Hi,
I’m also in the game of kernel panics with 10.14.4 :(

All the way from 10.14.0 to 10.14.3 everything was painless.
Yesterday I updated my MacBook Pro 6.2 15“ to 10.14.4 by using patcher v1.3 and installed through USB (not via Software Update)
Everything went without issues, but while running macOS crashed randomly but very often, also additionally during shut-down, not only in standard operation mode.
All needed patches are installed, graphics, iSight, backlight, … work flawlessly.

I reapplied the patches and forced a cache rebuild twice, seems to be unhelpful :(

Attached you find all the crash reports!

Hopefully this helps to find our common issue!
Any tips @dosdude1 @Larsvonhier @jackluke ?

The fact that a simple screensaver as Flurry doesn't work while it does without OpenGL Acceleration, is a clear signal that something doesn't work properly on a patched 10.14.4 .

From 10.14.5 beta 1 I got no KPs and it's without OpenGL acceleration, I'm typing from there.
 
Hi,
I’m also in the game of kernel panics with 10.14.4 :(

All the way from 10.14.0 to 10.14.3 everything was painless.
Yesterday I updated my MacBook Pro 6.2 15“ to 10.14.4 by using patcher v1.3 and installed through USB (not via Software Update)
Everything went without issues, but while running macOS crashed randomly but very often, also additionally during shut-down, not only in standard operation mode.
All needed patches are installed, graphics, iSight, backlight, … work flawlessly.

I reapplied the patches and forced a cache rebuild twice, seems to be unhelpful :(

Attached you find all the crash reports!

Hopefully this helps to find our common issue!
Any tips @dosdude1 @Larsvonhier @jackluke ?
Try uninstalling air parrot. It has history of incompatibility in the past
 
  • Like
Reactions: Larsvonhier
@LuisN @Larsvonhier

I uninstalled the tools, but as I already assumed, it did not help!
Still several panics, like the attached ones :(

No pattern visible for me…
Any further ideas?
Etrecheck also shows no issues...
 

Attachments

  • Panics.zip
    8.6 KB · Views: 166
I didn't get an answer last time so I'll ask again: can I boot Mojave on an encrypted APFS filesystem on a MBP 5,1?

This is what's keeping me on HFS+.
 
That 10.14.2 fix never worked on the MB4,1. Interestingly, before the patch, F1/F2 summon up the brightness overlay icon, after patching, nothing happens any more.

About the 773kB CoreBrightness binary. Tried to patch, found the right offset but to no effect.

EDIT:
The table has grown since 10.12.x - so I missed one byte (the last one for MacBooks). Did it again, works now! Attached file is patched for all types of min. "1.x" machines (iMac, MB, MBP etc.).

(Sidenote: There are two model_min offsets now: "BLR" (which has the right format to be the nightshift) and a "Harmony" - that seems new since 10.14.5?


Are you saying this file will give me brightness control on the Macbook4,1? I'm on 10.14.3, does this work with that or only 10.14.4?
 
My MBP5,2 17" does run less reliably on .4 than on .3. But when using the 9600M GT GPU (instead of 9400M) and avoiding Safari (Firefox instead) I can work with it without problems. No problems in Finder or Control Panel.
Got your same model. Went back to .3 after a few days of random KPs. Zero KPs since. Staying here for a while.
 
Im thinking about buying a cheap iMac 2011 with Radeon GPU.
It is still running High Sierra and the Mojave patcher is not workin, because of die Radeon GPU.

Will it be possible to get the GPU working in the future or is it absolutely impossible to get this working at some time ?

I have a Macbook Pro 8,2 Early 2011, and my AMDRadeon GPU is failing, but still can give the "corderoy" graphics...so I am able to see enough in single user mode to run the NVRAM configuration command to disable it and run from the integrated Intel GPU. There are lots of posts here about how to disable the Radeon GPU. If dosdude ever releases his product to update the gpumux firmware I will likely bite on that, since it would be an easy HW fix that won't require the SW EFI /NVRAM to be reapplied in the event of an PRAM reset...making the AMDRadeon GPU disable permanent. I can say that 10.14.4 is running like a champ on my MBP...in fact, I don't think it's ever run better. My only complaint is that Remotix doesn't work anymore...Remotix team is supposedly looking at it...

Anyway, look around here for threads about disabling the AMDRadeon GPU... There's lots of info. As far as getting it working again...well good luck...it is a HW failure in the chip, which was never revised to fix...so any replacement would only manifest the issue again later. Best solution is to just disable it and go with the integrated Intel GPU.
 
  • Like
Reactions: Larsvonhier
Are you saying this file will give me brightness control on the Macbook4,1? I'm on 10.14.3, does this work with that or only 10.14.4?
No, unfortunately no brightness control possible at the moment on MB4,1 - not with any Mojave.
Still working to find a solution, but for me it´s a jungle of kext dependencies to resolve...
Best workaround is the combination of brightness slider and NoSleep.
 
  • Like
Reactions: jackluke
Spouse has the exact same Alum MB (MacBook5,1(13-inch, Aluminum, Late 2008) 2 GHz Intel Core 2 Duo, 8GB 1067 MHz DDR3, NVIDIA GeForce 9400M 256MB, except APFS 250GB SSD(Samsung EVO840)) on 10.14.3. Concur more reliable and more efficient than 10.13.6.

Will .4 be a reliable upgrade?
[doublepost=1554388121][/doublepost]Then, there is this - Mini3,1 display bliss.View attachment 830315

My spouse has the same machine. Tried 10.14.4 2x, and sporadic kernel panics killed it. Waiting to see if the team here figures it out. In the meantime, she is back on High Sierra.
 
Does anyone have 10.14.3 if so can you make a Mojave patcher I would gladly pay for it I am getting quite annoyed with the constant reboots on my iMac 9,1 I tried everything and all instructions to get it up and running and really hard I have no safe mode to boot into io kit error
I found following link:
https://linkcarry.com/?v=471
It might work for you
[doublepost=1554430239][/doublepost]
Cannot get 10.14.4 to run reliably on a Mini3,1 early or late version, APFS or HFS+ SSD or SSHDD. Random KPs mostly in the Finder or Control Panel.

What models run on dot 4 as reliably as dot 3?
Forget it, I have the same mini3,1. The crashes under 10.14.4 are random and do not apply to specific apps. You won't be able to figure it out. In the mean time I returned to 10.14.3. And boy it is working so great, as if 10.14.3 was created especially for mini3,1
 
Hi,
I’m also in the game of kernel panics with 10.14.4 :(

All the way from 10.14.0 to 10.14.3 everything was painless.
Yesterday I updated my MacBook Pro 6.2 15“ to 10.14.4 by using patcher v1.3 and installed through USB (not via Software Update)
Everything went without issues, but while running macOS crashed randomly but very often, also additionally during shut-down, not only in standard operation mode.
All needed patches are installed, graphics, iSight, backlight, … work flawlessly.

I reapplied the patches and forced a cache rebuild twice, seems to be unhelpful :(

Attached you find all the crash reports!

Hopefully this helps to find our common issue!
Any tips @dosdude1 @Larsvonhier @jackluke ?
Yes me too! It panics then restarts. Not all the time but a number of times. Only on my MacMini 3,1. My MacBook Pro 7,1 is solid.
 
I got partial accel with IntelHD, about Nvidia Tesla still got this:
Code:
kxld[com.apple.nvidia.classic.NVDAResmanTesla]: The following symbols are unresolved for this kext:
kxld[com.apple.nvidia.classic.NVDAResmanTesla]:     _VSLGestalt
Link failed (error code 5).
Prelink failed for com.apple.nvidia.classic.NVDAResmanTesla; omitting from prelinked kernel.
Can't use NVDAResmanTesla.kext - not linked.
Prelink failed for com.apple.GeForceTesla; omitting from prelinked kernel.
Can't use NVDAResmanTesla.kext - not linked.
Prelink failed for com.apple.nvidia.classic.NVDANV50HalTesla; omitting from prelinked kernel.

I guess @ASentientBot should check the "new" 10.13.6 build 17G6030: GeForceTesla* and NVDA*Tesla kext, maybe a refresh fix could work, don't know. At the moment on .5 only Video Framebuffer with Brightness Control but no sleep function.

Anyway to boot 10.14.5 beta1 from NvidiaTesla machine just try to use all the retro patches adding the .4 GPUWrangler.framework if you use NDRVShim.kext, instead remove or rename NDRVShim.kext if you want use .5 GPUWrangler.framework .

I just replaced the IOUSB*.kext , replaced telemetry.plugin with HS one, replaced AppleHDA.kext from HS , added the AppleIntelGraphicsHD*.kext from Sierra, and nothing else.

edit:
Just a note I guess those with an IntelHD3000 could achieve Video Acceleration on 10.14.5 beta1 using the stock IOAccelerator2D.plugin and IOAcceleratorFamily2.kext from .5 , and the IntelHD3000 kext from Sierra or those from HS by dosdude1.
The _VSLGestalt error is fixed by NDRVShim, no?

I'll get to work on .5 stuff for Tesla soon -- to be honest, I'm personally still on .3 on my primary system and I've been lazy recently. But I'll see if I can figure anything out.

Great work everybody! I have every hope that we can keep this effort going to 10.15 and beyond.
 
The fact that a simple screensaver as Flurry doesn't work while it does without OpenGL Acceleration, is a clear signal that something doesn't work properly on a patched 10.14.4 .

From 10.14.5 beta 1 I got no KPs and it's without OpenGL acceleration, I'm typing from there.

Just to add a few more data points on .4:

  • Yes, Flurry is hosed (grey screen) but all other similar (OpenGL) screensavers like Arabesque and Shell work great. So I think it may be a problem with Flurry. Did it work on .3? Don't remember. It's the only hosed screensaver
  • I even switched GPUs (in power settings) - no changes
  • Some folks reported problems with Safari on .4 - the release notes state that a jump from Safari 10.2 to 12.1 needs: defaults delete com.apple.Safari (but you'll lose your previous settings so be careful)
  • Have not installed any Patch Updater fixes (Night-Shift Siri or iSight) yet
  • Otherwise my .4 is pretty solid (accelerated) for almost a week now - no KPs at all. Note that my upgrade path may be different than most: from .2 -> software update straight to .4 -> post-install with dude's latest patcher 1.3. May or may not make a difference. I've tried not to tinker around with it too much while I run it through its paces.
My Test system: mbp 5,3 - dual NVidia GPUs - APFS on SSD
 
On my MacPro 3,1 with Mojave 10.4.4 patched by Dosdude1 method, I had sometimes kernel panics not happening under 10.4.3. It was suggested here that a faulty DIMM may be the cause. I have found now the culprit : the kernel panics happened only when I was using a Firewire CompactFlash Card Reader when taking out the CF Card !!!!! I changed the Reader to an USB one instead of the Firewire one and no more kernel panics now.................10.4.4 doesn't like Firewire anymore........
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.