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.
Unfortunately i do not have installed it from dosdudes patcher. I had 10.14.0 before i updated, because it was said somewhere, that it should be safe to install any further updates.

Plus, i do not have an usb installer no more, but I can create a new usb installer with my friends macbook, that would be no problem i think. But we can handle that by tomorrow, thats why i had some hope, if i could do anything else for now.

You need the patcher (USB drive) to fix your OS.
 
  • Like
Reactions: TimothyR734
All you have to do is right-click the patch in the list, and select "Re-install". That will re-install the volume control patch.

That worked. Top. But it remains strange that the Volume Control does not work when you re-install ALL patches, but ONLY if you re-install just the Volume Control Patch.... Thx anyway.
 
  • Like
Reactions: TimothyR734
Found out today that the "legacy audio patch" either screws up the old S/PDIF digital I/O for sound or it is not patched correctly. The result is that even on machines that had this interface selectable under High Sierra the option for input/output is not available any more (and in system info it does not show any more). Only the mostly-used analog line-in/out is present. Is this reproducible on other machines as well (I tested it on MBP 4,1 / MPB 7,1) ?
Perhaps @dosdude1 has more info and insight why the old kext implant does not work fully? Some dependency might be missing.
 
  • Like
Reactions: ASentientBot
Found out today that the "legacy audio patch" either screws up the old S/PDIF digital I/O for sound or it is not patched correctly. The result is that even on machines that had this interface selectable under High Sierra the option for input/output is not available any more (and in system info it does not show any more). Only the mostly-used analog line-in/out is present. Is this reproducible on other machines as well (I tested it on MBP 4,1 / MPB 7,1) ?
Perhaps @dosdude1 has more info and insight why the old kext implant does not work fully? Some dependency might be missing.

I've already noticed that.
Unfortunately the audio is not fully functional.
I have a game: Age of Empires 3, It works perfectly in both High Sierra and Mojave, but the audio in Mojave is broken only in this game.
I noticed that things are missing in the audio kexts, so it does not work properly. I do not know how to solve this.
 
I've already noticed that.
Unfortunately the audio is not fully functional.
I have a game: Age of Empires 3, It works perfectly in both High Sierra and Mojave, but the audio in Mojave is broken only in this game.
I noticed that things are missing in the audio kexts, so it does not work properly. I do not know how to solve this.
Could someone with a working Mojave setup on Mac Pro 3,1 (or unmodified MP 4,1 and patched installer) please verify if TOSLink digital in/out for audio is working or at least shown in system info / audio section? I´d like to rule out different behaviour between miniTOSLink (i.e. on MacBooks) and TOSLink (on Mac Pro). Should only be connector type that´s different, not the audio path and kexts involved, but I´d like to be sure...
Thanks!
 
Could someone with a working Mojave setup on Mac Pro 3,1 (or unmodified MP 4,1 and patched installer) please verify if TOSLink digital in/out for audio is working or at least shown in system info / audio section? I´d like to rule out different behaviour between miniTOSLink (i.e. on MacBooks) and TOSLink (on Mac Pro). Should only be connector type that´s different, not the audio path and kexts involved, but I´d like to be sure...
Thanks!
MacPro 3,1 running 10.14.1
Screenshot 2018-11-14 at 17.43.34.png
Screenshot 2018-11-14 at 17.43.46.png
Screenshot 2018-11-14 at 18.38.06.png
 
Last edited:
Hi guys I installed mojave on macbook 5,2 mid 2009 and I have problem with trackpad! and touch to tap is not working with right click, so is there any way to enable "touch to tap" on it ? also I have problem with webcam not working anymore .

Alas, all that you are going to get from the 5,2 without replacing the touchpad with one from a later model, is the functionality of a two-button mouse (this is noted in the OP).

Additionally, even when replacing the 5 *USB* kexts in Mojave with those from from High Sierra or El Capitan, all you'll get is a very unstable (ie. not useable) camera.

Otherwise, Mojave on the 5,2 it is pretty much okay.
 
I had that distributed via Patch Updater, but it caused Bluetooth to stop working completely on some systems (that had working Bluetooth with Mojave to begin with). So I'm not sure what to do. It's not limited to specific machines either, in fact it seems to be completely random. For example, when I had initially pushed that patch, some MacBookPro8,1 users reported that it fixed their issue, while others reported that it made Bluetooth stop working completely. This is the same with all the machines (iMacs, MacBook Airs, Mac Minis, etc); some users said it worked on their system, others said it broke Bluetooth on the exact same system. I have no idea how to reliably distribute this patch.

Exactly the same issue on my MacBook5.1. Bluetooth (at least Audio) was working prior to the Patch Updater. I tried the solution of copying some other kext but it did not solve the issue.
The bluetooth module is available and responsive but after a connexion, a timeout occurs few second later.
I can see some error in the Console when trying to Connect

rejecting read of { com.apple.Bluetooth, kCFPreferencesAnyUser, kCFPreferencesCurrentHost, no container, managed: 0 } from process 76 because accessing preferences outside an application's container requires user-preference-read or file-read-data sandbox access
Couldn't read values in CFPrefsPlistSource<0x7f8de2c3b750> (Domain: com.apple.Bluetooth, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): accessing preferences outside an application's container requires user-preference-read or file-read-data sandbox access
 
No problem on a MP 3,1 and I use digital all day every day.

Screenshot 2018-11-15 08.08.31.png
Screenshot 2018-11-15 08.08.41.png



Found out today that the "legacy audio patch" either screws up the old S/PDIF digital I/O for sound or it is not patched correctly. The result is that even on machines that had this interface selectable under High Sierra the option for input/output is not available any more (and in system info it does not show any more). Only the mostly-used analog line-in/out is present. Is this reproducible on other machines as well (I tested it on MBP 4,1 / MPB 7,1) ?
Perhaps @dosdude1 has more info and insight why the old kext implant does not work fully? Some dependency might be missing.
 
  • Like
Reactions: TimothyR734
Updated my MacPro 3.1. All was fine. A few days later it won't sleep and I cant use hot corners to turn off the screen. I restored a HS backup and upgraded again but same issue not screen sleep or machine sleep. When I select sleep from the menu a few seconds later I get a chime from the built in speaker.

Re applied all the patches, reset NVRAM, SMC, turned off all bluetooth.

If I boot from the HS backup, sleep is fine.
 
  • Like
Reactions: TimothyR734
Updated my MacPro 3.1. All was fine. A few days later it won't sleep and I cant use hot corners to turn off the screen. I restored a HS backup and upgraded again but same issue not screen sleep or machine sleep. When I select sleep from the menu a few seconds later I get a chime from the built in speaker.

Re applied all the patches, reset NVRAM, SMC, turned off all bluetooth.

If I boot from the HS backup, sleep is fine.

Did you try running the ONYX app ???? I had this problem once and it was solved after running Onyx.
 
  • Like
Reactions: TimothyR734
On my post above i do not have access to high sierra bluetooth kexts so how can i fix this ?
Hi there. Have a Mac pro 3.1 which had bluetooth issues with both mojave 14.0 and 14.1. Replacing these kexts helped solve the problem. Both version 6.07 from High Sierra. however the issue seems to be fairly random as dosdude explained.
 

Attachments

  • IOBluetoothFamily.kext.zip
    2.4 MB · Views: 204
  • IOBluetoothHIDDriver.kext.zip
    66.5 KB · Views: 195
Hi there. Have a Mac pro 3.1 which had bluetooth issues with both mojave 14.0 and 14.1. Replacing these kexts helped solve the problem. Both version 6.07 from High Sierra. however the issue seems to be fairly random as dosdude explained.
i just did this deleted old emptied trash added these and still no bluetooth.

I have a Mac Mini 2011 server if this helps any.
 
  • Like
Reactions: TimothyR734
Hi guys I have problem with my home wifi with odd issue okey let me describe it , I have a home wifi and I use it with all my devices without any problem but when I try to connect with my macbook unfortunately unable to discover SSID on mac but when I Start my android phone hotspot and once when I connect with mac to this hotspot then I can find my home SSID in macbook this is too strange.
 
  • Like
Reactions: TimothyR734
i just did this deleted old emptied trash added these and still no bluetooth.

I have a Mac Mini 2011 server if this helps any.
Did you fix permissions on the new kexts and then clear the kext cache? If not then running these commands using terminal is required if you replace kexts.

sudo chmod -R 755 /System/Library/Extensions/IOBluetoothFamily.kext

sudo chmod -R 755 /System/Library/Extensions/IOBluetoothHIDDriver.kext

sudo chown -R 0:0 /System/Library/Extensions/IOBluetoothFamily.kext

sudo chown -R 0:0 /System/Library/Extensions/IOBluetoothHIDDriver.kext

sudo kextcache -system-prelinked-kernel

Wait for the last command to finish fully then reboot your machine.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.