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.
sometimes randomly when I turn on the Mac the load bar takes longer than normal and when it ends the keyboard doesn't work and I have to force the shutdown. Is this happening to someone else?

Yes, randomly on this machine "white macbook mid 2010", I noticed this even before Mojave announcement, so I'd exclude side-effects of patching, while instead I guess, at least on my machine, trackpad/keyboard are becoming faulty, probably a drop of water inside, however when it happens just power-off the macbook keeping pressed power button for 5 seconds, then power-on and they will work normally again.
 
One other observation I have from installing and flashing an EVGA Nvidia GTX 680 is that, for both the original PC and the flashed Mac ROMs, BootCamp runs the card as PCI-e v1.1 instead of v2.0. From the information floating around about the new boot firmware in 10.14.1, it appears that changes were made to solve this without requiring the physical R17 resistor mod to the graphics board.
 
  • Like
Reactions: TimothyR734
Yes, randomly on this machine "white macbook mid 2010", I noticed this even before Mojave announcement, so I'd exclude side-effects of patching, while instead I guess, at least on my machine, trackpad/keyboard are becoming faulty, probably a drop of water inside, however when it happens just power-off the macbook keeping pressed power button for 5 seconds, then power-on and they will work normally again.
On my Macbook 2009 Late only happens when turn on the mac sometimes but with High Sierra never happened.
 
  • Like
Reactions: TimothyR734
Yes, randomly on this machine "white macbook mid 2010", I noticed this even before Mojave announcement, so I'd exclude side-effects of patching, while instead I guess, at least on my machine, trackpad/keyboard are becoming faulty, probably a drop of water inside, however when it happens just power-off the macbook keeping pressed power button for 5 seconds, then power-on and they will work normally again.

Hello,

I have the same machine MB7,1 and I noticed also that trackpad/keyboard are becoming faulty before Mojave. Maybe since High Sierra 10.13.4...
I think we must try replacing Kexts from Elcapitan or from the firsts releases of High Sierra for those problems. What do you think ?
Thank you
 
On my Macbook 2009 Late only happens when turn on the mac sometimes but with High Sierra never happened.

Then probably Mojave patching side-effect, anyway I guess after a re-power-on they work regularly.
[doublepost=1539013554][/doublepost]
Hello,

I have the same machine MB7,1 and I noticed also that trackpad/keyboard are becoming faulty before Mojave. Maybe since High Sierra 10.13.4...
I think we must try replacing Kexts from Elcapitan or from the firsts releases of High Sierra for those problems. What do you think ?
Thank you

Maybe, but in my case I guess drinking near the m'book, caused some drops fallen into keyboard, sometimes I have the trackpad crazy, then just closing and re-opening the lid (sleep mode) and it responds normally, but you're right maybe some previous kext could give back more stability.
 
Then probably Mojave patching side-effect, anyway I guess after a re-power-on they work regularly.
[doublepost=1539013554][/doublepost]

Maybe, but in my case I guess drinking near the m'book, caused some drops fallen into keyboard, sometimes I have the trackpad crazy, then just closing and re-opening the lid (sleep mode) and it responds normally, but you're right maybe some previous kext could give back stability.

This also happened to me, sometimes it takes longer than normal and then mouse and keyboard doesn't work. But i saw that if you press once the power off/on button, display turns off and then if you re-press power off/on button and turn on display, then Keyboard and Mouse will work.

This happened to me also in HS.
 
OGNerd, post: 26632796, member: 965215"]He is using a HackBook, ie. different hardware.

ok, you do not want to or can not understand it, so you will not be able to update your final 10.14 to
beta 10.14.1 and .2.

Again, so after stopping the white loading bar, you can not continue,
then boot from the USB stick where Mojave Patcher is on it.

Then on the option "post install" and then up there "select device" to try another model.

Then select the patches at the bottom of the window, then Force reboot and then boot normally from Mojave, the 2nd phase of the installation will now be properly installed until the end.
 
  • Like
Reactions: TimothyR734
ok, you do not want to or can not understand it, so you will not be able to update your final 10.14 to
beta 10.14.1 and .2.

Again, so after stopping the white loading bar, you can not continue,
then boot from the USB stick where Mojave Patcher is on it.

Then on the option "post install" and then up there "select device" to try another model.

Then select the patches at the bottom of the window, then Force reboot and then boot normally from Mojave, the 2nd phase of the installation will now be properly installed until the end.

I don't have updated yet to 10.14.1 but I guess I understood why this "method" works, probably this time the version upgrade "10.14.1 beta 2" puts into the "Temporary Installer" folder its new Mojave "unpatched" prelinkedkernel without using the current one in your machine, while installing the patches "in the middle" you will obtain a re-builded custom prelinkedkernel so the Installer will be able to continue its process until the end. As known everything revolves around prelinkedkernel.
 
  • Like
Reactions: TimothyR734
I installed Mac os mojave on a 20011 MacBook pro but no option for screen brightness... The sound keys work but not the brightness keys or in settings is no option
 
  • Like
Reactions: TimothyR734
I don't have updated yet to 10.14.1 but I guess I understood why this "method" works, probably this time the version upgrade "10.14.1 beta 2" puts into the "Temporary Installer" folder its new Mojave "unpatched" prelinkedkernel without using the current one in your machine, while installing the patches "in the middle" you will obtain a re-builded custom prelinkedkernel so the Installer will be able to continue its process until the end. As known everything revolves around prelinkedkernel.
This is impossible. I have installed it from the terminal which has no temporary files and it doesn’t work after patching it.
 
  • Like
Reactions: TimothyR734
This is impossible. I have installed it from the terminal which has no temporary files and it doesn’t work after patching it.

Every minor version upgrade contains a new "kernel" that means new troubles for unsupported systems, using the previous kernel should work. Anyway I don't understand "installed from Terminal" you mean from a Terminal you typed:

pkgutil --expand packagename.pkg /Volumes/Mojavelabel/

or something like

sudo installer -pkg packagename.pkg -target /Volumes/Mojavelabel/
 
Last edited:
Every minor version upgrade contains a new "kernel" that means new troubles for unsupported systems, using the previous kernel should work. Anyway I don't understand
They are replaced after applying the patches. However, it still won’t boot. I have tired this like 4 times and it never worked. I tried installing it from terminal now instead of system preferences but still no luck.
[doublepost=1539019339][/doublepost]
Every minor version upgrade contains a new "kernel" that means new troubles for unsupported systems, using the previous kernel should work. Anyway I don't understand "installed from Terminal" you mean from a Terminal you typed:

pkgutil --expand packagename.pkg /Volumes/Mojavelabel/

or something like

sudo installer -pkg packagename.pkg -target /Volumes/Mojavelabel/
I used softwareupdate -install.
 
  • Like
Reactions: TimothyR734
They are replaced after applying the patches. However, it still won’t boot. I have tired this like 4 times and it never worked. I tried installing it from terminal now instead of system preferences but still no luck.
[doublepost=1539019339][/doublepost]
I used softwareupdate -install.

Probably the other commands are more effective, anyway there is no doubt that new system versions bring new platform incompatibility, so possibly some new patches could be needed.

I guess you should try to Rebuild the prelinkedkernel cache before the 10.14.1 Installer can place its new Mojave kernel into your Mojave /System/Library/Kernels

it's just my supposition, nothing else.
 
Then probably Mojave patching side-effect, anyway I guess after a re-power-on they work regularly.
[doublepost=1539013554][/doublepost]

Maybe, but in my case I guess drinking near the m'book, caused some drops fallen into keyboard, sometimes I have the trackpad crazy, then just closing and re-opening the lid (sleep mode) and it responds normally, but you're right maybe some previous kext could give back more stability.
Those times when the keyboard doesn't work when ends the load (longer than usual) the mac is in the login screen and I have to force the shutdown by pressing the power button.

Yes, after re-boot all works again. But this must be a mojave patcher issue. I guess, because with High Sierra never had that problem.
 
  • Like
Reactions: TimothyR734
Then probably Mojave patching side-effect, anyway I guess after a re-power-on they work regularly.
[doublepost=1539013554][/doublepost]

Maybe, but in my case I guess drinking near the m'book, caused some drops fallen into keyboard, sometimes I have the trackpad crazy, then just closing and re-opening the lid (sleep mode) and it responds normally, but you're right maybe some previous kext could give back more stability.
Do you know which kext we have to test ?
Thank you
 
I don't have updated yet to 10.14.1 but I guess I understood why this "method" works, probably this time the version upgrade "10.14.1 beta 2" puts into the "Temporary Installer" folder its new Mojave "unpatched" prelinkedkernel without using the current one in your machine, while installing the patches "in the middle" you will obtain a re-builded custom prelinkedkernel so the Installer will be able to continue its process until the end. As known everything revolves around prelinkedkernel.

Any software update that craps out due to unsupported boot ROM updates is highly suspect because you simply don't know how much of the software update installation resides on the other side of the boot ROM upgrade step. IMHO, in the past when folks were able to get failed High Sierra updates to run after tweaking with Onyx, they were just lucky.
 
This also happened to me, sometimes it takes longer than normal and then mouse and keyboard doesn't work. But i saw that if you press once the power off/on button, display turns off and then if you re-press power off/on button and turn on display, then Keyboard and Mouse will work.

This happened to me also in HS.
I'll try that the next time.
High Sierra was supported in your Mac? In my MacBook was officially supported and never happens this.
 
  • Like
Reactions: TimothyR734
Any software update that craps out due to unsupported boot ROM updates is highly suspect because you simply don't know how much of the software update installation resides on the other side of the boot ROM upgrade step. IMHO, in the past when folks were able to get failed High Sierra updates to run after tweaking with Onyx, they were just lucky.
Is there a way we can ignore the boot rom update and not install it?
 
  • Like
Reactions: TimothyR734
Do you know which kext we have to test ?
Thank you

Apart the 5 IOUSB***.kext perhaps there are others involved:

AppleHIDKeyboard.kext
AppleHIDMouse.kext
AppleMultitouchDriver.kext
AppleUSBMultitouch.kext
AppleUSBTopCase.kext

But I really don't know exactly them.

I am only 100% sure that the 5 IOUSB***.kext are needed to make them working.
 
  • Like
Reactions: TimothyR734
Agree weird problem, however any time I open a 32bit app from Mojave I get a warning of incompatibility "app is not optimized", and that link me here: https://support.apple.com/en-us/HT208436

Yes, most probably is one (or more) of your extra kexts, boot in safe move and check the extensions loaded from System_Information--Software--Extensions and watch the "Loaded" tab set in order by "Yes", and check if you have also third party apps or usb dongles that installed third-party framework.

I found the difference between kexts in safe mode and full mode. The following 56 kexts are NOT loaded in safe mode. That's a lot of kexts to remove for trail error. Any idea which ones could be responsible for blocking 32 bit apps to load in full mode?

Code:
/Library/Extensions/intelhaxm.kext
/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.kext
/System/Library/Extensions/AppleStorageDrivers.kext/Contents/PlugIns/AppleUSBStorageCoexistentDriver.kext
/System/Library/Extensions/AppleUSBTopCase.kext/Contents/PlugIns/AppleUSBTCKeyEventDriver.kext
/System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext
/System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBUHCIPCI.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/DspFuncLib.kext
/System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothSerialManager.kext
/System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext
/System/Library/Extensions/IOTimeSyncFamily.kext/Contents/PlugIns/IOgPTPPlugin.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/IOHDAFamily.kext
/System/Library/Extensions/IOTimeSyncFamily.kext/Contents/PlugIns/IOgPTPPlugin.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/IOHDAFamily.kext
/System/Library/Extensions/AppleUSBCDC.kext
/System/Library/Extensions/AppleXsanScheme.kext
/System/Library/Extensions/AudioAUUC.kext
/System/Library/Extensions/CUDA.kext
/System/Library/Extensions/eficheck.kext
/System/Library/Extensions/GeForceTesla.kext
/System/Library/Extensions/IOAudioFamily.kext
/System/Library/Extensions/IOFireWireIP.kext
/System/Library/Extensions/IOFireWireIP.kext
/System/Library/Extensions/IOSerialFamily.kext
/System/Library/Extensions/vecLib.kext
/System/Library/Extensions/pmtelemetry.kext
/System/Library/Extensions/OSvKernDSPLib.kext
/System/Library/Extensions/NVDAStartup.kext
/System/Library/Extensions/NVDAResmanTesla.kext
/System/Library/Extensions/NVDANV50HalTesla.kext
/System/Library/Extensions/NDRVShim.kext
/System/Library/Extensions/msdosfs.kext
/System/Library/Extensions/Libm.kext
/System/Library/Extensions/IOUserEthernet.kext
/System/Library/Extensions/IOUSBMassStorageClass.kext
/System/Library/Extensions/IOSlowAdaptiveClockingFamily.kext
/System/Library/Extensions/AppleUSBAudio.kext
/System/Library/Extensions/AppleUpstreamUserClient.kext
/System/Library/Extensions/AppleSSE.kext
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/AppleSMCPDRC.kext
/System/Library/Extensions/AppleSMCLMU.kext
/System/Library/Extensions/AppleOSXWatchdog.kext
/System/Library/Extensions/AppleMikeyHIDDriver.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleMikeyDriver.kext
/System/Library/Extensions/AppleIntelSlowAdaptiveClocking.kext
/System/Library/Extensions/AppleIntelHDGraphics.kext
/System/Library/Extensions/AppleHV.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHardwareConfigDriver.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAController.kext
/System/Library/Extensions/AppleHDA.kext
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext
/System/Library/Extensions/AppleFIVRDriver.kext
/System/Library/Extensions/AppleFileUtil.kext
/System/Library/Extensions/AppleFileSystemDriver.kext
/System/Library/Extensions/AppleBacklight.kext
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AGDCPluginDisplayMetrics.kext
 
  • Like
Reactions: jackluke
I found the difference between kexts in safe mode and full mode. The following 56 kexts are NOT loaded in safe mode. That's a lot of kexts to remove for trail error. Any idea which ones could be responsible for blocking 32 bit apps to load in full mode?

Code:
/Library/Extensions/intelhaxm.kext
/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.kext
/System/Library/Extensions/AppleStorageDrivers.kext/Contents/PlugIns/AppleUSBStorageCoexistentDriver.kext
/System/Library/Extensions/AppleUSBTopCase.kext/Contents/PlugIns/AppleUSBTCKeyEventDriver.kext
/System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext
/System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBUHCIPCI.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/DspFuncLib.kext
/System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothSerialManager.kext
/System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext
/System/Library/Extensions/IOTimeSyncFamily.kext/Contents/PlugIns/IOgPTPPlugin.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/IOHDAFamily.kext
/System/Library/Extensions/IOTimeSyncFamily.kext/Contents/PlugIns/IOgPTPPlugin.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/IOHDAFamily.kext
/System/Library/Extensions/AppleUSBCDC.kext
/System/Library/Extensions/AppleXsanScheme.kext
/System/Library/Extensions/AudioAUUC.kext
/System/Library/Extensions/CUDA.kext
/System/Library/Extensions/eficheck.kext
/System/Library/Extensions/GeForceTesla.kext
/System/Library/Extensions/IOAudioFamily.kext
/System/Library/Extensions/IOFireWireIP.kext
/System/Library/Extensions/IOFireWireIP.kext
/System/Library/Extensions/IOSerialFamily.kext
/System/Library/Extensions/vecLib.kext
/System/Library/Extensions/pmtelemetry.kext
/System/Library/Extensions/OSvKernDSPLib.kext
/System/Library/Extensions/NVDAStartup.kext
/System/Library/Extensions/NVDAResmanTesla.kext
/System/Library/Extensions/NVDANV50HalTesla.kext
/System/Library/Extensions/NDRVShim.kext
/System/Library/Extensions/msdosfs.kext
/System/Library/Extensions/Libm.kext
/System/Library/Extensions/IOUserEthernet.kext
/System/Library/Extensions/IOUSBMassStorageClass.kext
/System/Library/Extensions/IOSlowAdaptiveClockingFamily.kext
/System/Library/Extensions/AppleUSBAudio.kext
/System/Library/Extensions/AppleUpstreamUserClient.kext
/System/Library/Extensions/AppleSSE.kext
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/AppleSMCPDRC.kext
/System/Library/Extensions/AppleSMCLMU.kext
/System/Library/Extensions/AppleOSXWatchdog.kext
/System/Library/Extensions/AppleMikeyHIDDriver.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleMikeyDriver.kext
/System/Library/Extensions/AppleIntelSlowAdaptiveClocking.kext
/System/Library/Extensions/AppleIntelHDGraphics.kext
/System/Library/Extensions/AppleHV.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHardwareConfigDriver.kext
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAController.kext
/System/Library/Extensions/AppleHDA.kext
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext
/System/Library/Extensions/AppleFIVRDriver.kext
/System/Library/Extensions/AppleFileUtil.kext
/System/Library/Extensions/AppleFileSystemDriver.kext
/System/Library/Extensions/AppleBacklight.kext
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AGDCPluginDisplayMetrics.kext
AppleOSXWatchdog sounds interesting.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.