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.
I am no expert but have been looking at this with the cMP after some other members commented on the high cpu use when playing 4k videos. Both my CMP3.1 and cMP5.1 will have up o 400% cpu use when playing a 4k 60 fps video made on an iPhone. On investigation it appears Mojave may be (solely?) using the Intel Quick Sync built into Sandybridge and later cpus and is not using dedicated graphic cards to encode/decode video. We are using old cpus now and Apple has moved on to rely on Quick Sync and is also using the T2 chip in its latest models. Although my cMP has a quite modern and capable card on Apple's recommended list (RX 580) Mojave makes no use of it for video decoding/encoding since 10.14.1. The fact that it is possible is that there was graphic card hardware acceleration in 10.14.0 but Apple took the decision to remove it on later versions so hardware decoding on the Radeon has been broken since 14.1. It was a little buggy on 14.0. So as the Xeon's do not have Quick Sync the decode/encode is purely reliant on software and cpu grunt. Streaming a 4k Ultra video via Safari/YouTube gives a VTDecoderXPCService CPU use of 32% but all is still pretty smooth.
The 5.1 Mac mini does have a Sandybridge cpu which implement version 1 of Intel's Quick Sync so there should be some H264/MPEG 2 hardware decoding. On my MacbbokAir 4.2 (also Sandybridge) playing the same YouTube 4K video resulted in a VTDecoderXPCService cpu use of 17% - but at half the output resolution of the cMP5.1 - so the question is does it use the hardware acceleration? I am not sure as H264/MPEG-4 and H262/MPEG-2 was not incorporated into Quick Sync until version 3, so the Sandybridge cannot decode these video streams. Playing lower resolution videos results in a cpu use around 11-14%. Playing the iPhone 4k 60 fps video cpu use ramped up to 160% and the fans started running at a higher speed which indicates the cpu is doing all the work. I am not familiar with twitch but have a look at the video codec they are using. If it is H265/MPEG-2 you might get some hardware decoding in from Quick Sync (v1). Any higher order codec will probably just use the cpu. Hope this helps. Does not solve the problem but I suspect we are having to accept that Apple is moving on and getting our older machines to keep up will become more of challenge.

I guess this explains quite well why I am so impressed with Mavericks in terms of 1080p video performance on my MacBook5,1.
 
APFS seems to work great for me. Good luck with HFS+.

Sure.

I did a lot of tests to determine the cause of the high CPU consumption of the process "Kernel_task". As I write previously, I have a Macbook 5.2 and other Macbook 5.1, both with mojave patcher and both with APFS file system in SSD disks. The Operating System was working, but since some months i noticed that both computers runs very slow. I have an iMac 7.1 with Mojave too, but formatted in HFS+ in a hybrid disk. The system in this computer runs smoothly. While I was writing my last post in this thread, i was thinking that the cause could be the file system (all three computers are configured in a similar way so this is one of the biggest difference between the iMac and the Macbooks).

So i made a time machine of the macbooks an I decided to format them in tho different ways. First I formatted the white macbook 5.2 with HFS+. The system was running perfect without restore the backup. So, then, I restored the backup. I have now the system as i was before the format, but in HFS+ instead of APFS. The macbook runs very well, and I didn't notice the problem of "Kernel_task".

So I formatted the other computer (macbook 5.1), but i formatted the disk in APFS. When the system starts, I can see some times the "kernel_task" growing up positions in the activity monitor, but it runs quite well. So I decided to restore the time machine. And when the computer restarted I could saw perfectly the "kernel_task" bug. The system was slow and "kernel_task" had an high cpu consumption. I decided to format this computer again with HFS+, and restored again the backup. Now the system runs smooth and I have not the "kernel_task" bug, so it seems that the problem is in the APFS file system.

As long as I have no solution to this problem I will leave these devices with HFS +. For me it is a problem, because while i being in HFS+ I will not have notices when there is any update of mojave.

I don't know if it is a bug of the APFS patch, a bug of the combination of APFS patch with Macbooks 5.x or it is a Mojave bug, but the problem exist.

Can anybody try some of this in this model of computers?
 
  • Like
Reactions: K two
I guess this explains quite well why I am so impressed with Mavericks in terms of 1080p video performance on my MacBook5,1.
Agreed, I do not really use my machines for high definition videos so did not notice any problems. I only started looking at the cpu loading in the activity monitor because some members reported stuttering videos. However, any one who uses their machines for encoding/decoding HD video work may want to review using Mojave. Unless their cpu has a decent version of Quick Sync (which works well) then they may be better off with a different Mac OS. For example you can still get good graphics drivers for Nvidia with High Sierra that gives you use of CUDA etc. I guess there is no incentive for Apple to develop the use of graphic card acceleration as there are only 2 present Macs that do not have Quick Sync. The cMP5.1 and iMac Pro. The iMac Pro has the T2 chip and also it is believed to be able to use the Vega card for encode/decode. That leaves the cMP5.1, that although is supported by Apple for Mojave has been somewhat ignored. The fact that the RX580 can be used as was shown with 10.14.0 and there are a few hacks around (although not perfect) to enable hardware encode/decode. Apparently the cMP5.1 with hardware encoding activated is impressive and can give many newer Macs a run for their money. Some have theorised this is why Apple has not enabled it - they would not do that would they?
 
Two questions:
1 - I have a EVGA GeForce GTX760 that did work with a Hackintosh Mojave 10.14.6. Do you think it would also work on a Mac Pro 2009 (Flashed to 5,1) Will work with a normal installation or would I need to use the installer by Dosdude?
2 - If I were to end up using the installer, would I be able to use Bootcamp? (I have never used it before so I don't have experience...I always could boot my Windows drive with clover)

Thank you!
 
Two questions:
1 - I have a EVGA GeForce GTX760 that did work with a Hackintosh Mojave 10.14.6. Do you think it would also work on a Mac Pro 2009 (Flashed to 5,1) Will work with a normal installation or would I need to use the installer by Dosdude?
2 - If I were to end up using the installer, would I be able to use Bootcamp? (I have never used it before so I don't have experience...I always could boot my Windows drive with clover)

Thank you!
1. Yes it should work on a installation from Apple’s App Store. You will not get a boot screen unless it is flashed with a Mac efi. However this will not stop you getting Mojave and if you use the full installer an upgrade of your rom to 144.0.0.0.0. Have a look here:
https://forums.macrumors.com/thread...-bootrom-upgrade-instructions-thread.2142418/
2. Not sure about boot camp and the installer but cannot see why it would not work. Should be ok if you go the full Apple installer way but have a search about using boot camp without a boot screen.
 
Will it ever be possible to boot into the recovery partition on a blacklisted or genuinely unsupported Mac with the DD1 patched Mohave install? Or is the patched USB installer itself now considered to be the "recovery partition" in this scenario?
I get the logic in that... But being that there are other things the recovery partition is useful for besides re-installing OSX...
 
  • Like
Reactions: K two
Will it ever be possible to boot into the recovery partition on a blacklisted or genuinely unsupported Mac with the DD1 patched Mohave install? Or is the patched USB installer itself now considered to be the "recovery partition" in this scenario?
I get the logic in that... But being that there are other things the recovery partition is useful for besides re-installing OSX...

I've found that reading page 415 of this thread is helpful in getting APFS recovery partition going.
 
  • Like
Reactions: roronl
Will it ever be possible to boot into the recovery partition on a blacklisted or genuinely unsupported Mac with the DD1 patched Mohave install? Or is the patched USB installer itself now considered to be the "recovery partition" in this scenario?
I get the logic in that... But being that there are other things the recovery partition is useful for besides re-installing OSX...
There really is no need for the Recovery partition, as anything it can do can be done from your bootable USB installer, with the added benefit of being able to do a re-install of the system.
 
I recently picked up a couple of older MB and MBP/PowerBook G4s, and even a Mac mini! Anyway, the newest ones of the bunch are three of them. Mid-2010 Poly Unibody MB, Mid-2010 MacBook Pro 13", and a Mid-2010 Mac mini. I put SSDs in all 3 of these systems and high Sierra and they run incredibly. Of course, me wanting to tinker with things, I am interested in this patch tool. I think that the guinea pig will be the poly MB. The other 2 I use in production environments and don't want to risk oddities. So, this machine is able to natively boot APFS, which from my understanding means that the patch tool only writes to the SSD. Am I correct in this assumption? I have searched around but cannot quite find the answer that I am looking for. I don't want to run it if it writes to the EFI chip on the motherboard. The standard patch tool for newer unsupported Macs just rights to the SSD, and disappears upon formatting should I want to revert to High Sierra? Is this correct? Thanks!
 
I recently picked up a couple of older MB and MBP/PowerBook G4s, and even a Mac mini! Anyway, the newest ones of the bunch are three of them. Mid-2010 Poly Unibody MB, Mid-2010 MacBook Pro 13", and a Mid-2010 Mac mini. I put SSDs in all 3 of these systems and high Sierra and they run incredibly. Of course, me wanting to tinker with things, I am interested in this patch tool. I think that the guinea pig will be the poly MB. The other 2 I use in production environments and don't want to risk oddities. So, this machine is able to natively boot APFS, which from my understanding means that the patch tool only writes to the SSD. Am I correct in this assumption? I have searched around but cannot quite find the answer that I am looking for. I don't want to run it if it writes to the EFI chip on the motherboard. The standard patch tool for newer unsupported Macs just rights to the SSD, and disappears upon formatting should I want to revert to High Sierra? Is this correct? Thanks!
Nothing is written to the EFI chip unless you use the EFI patcher program. The installer utility by @dosdude1 doesn't write anything in the EFI chip. They are two different programs and you're safe with the Mojave Patcher tool
 
  • Like
Reactions: Yiorlis59 and K two
First post here! this is my second run of the Patch, first, i sucessfuly updated a Macbook 5.2 (White, A1181 model). Now, i just managed to get it running on a iMac 9.1 (20-inch, Early 2009).

First, i would like to say thank you to @dosdude1 for this awesome patch and to give a huge extend of life to those macs, without you work, many people would not see the face of Mojave!

On my first run of the patch, the Macbook had a broken brightness slider, initially i fixed this by downloading Brightness Slider from the store, but then, a Patch Update fixed the brightness slider.

On this iMac i got the same issue, however, there seems to be no Patch update that fixes the slider

Is it possible to release the same fix to the iMac on the Patch Updater?

Thanks!
 
Will it ever be possible to boot into the recovery partition on a blacklisted or genuinely unsupported Mac with the DD1 patched Mohave install? Or is the patched USB installer itself now considered to be the "recovery partition" in this scenario?
I get the logic in that... But being that there are other things the recovery partition is useful for besides re-installing OSX...

Carbon Copy Cloner works perfectly to create a recovery partition. You have to boot to another drive with CCC installed, create the recovery partition, then run the USB patcher and ONLY select Recovery Partition Patch. Just tried it on a 10.14.3 HFS+ partition, worked first time with no issues. FYI I used the trial mode CCC for this, not even the full version.
 
  • Like
Reactions: roronl
Here on a MacPro 3,1 (10.14.6) getting a "complementary" update. It's safe to update? any instruction?
 

Attachments

  • Captura de pantalla 2019-08-26 a las 21.46.17.png
    Captura de pantalla 2019-08-26 a las 21.46.17.png
    101.7 KB · Views: 173
FYI, the 10.14.6 full installer from Apple has been updated to include today's supplemental update release and can be identified from its 14.6.04 version number compared to the 14.6.03 version number for the copy with the previous supplemental update. The Mojave Patcher creates a usable usb installer without issue although it can't download the current full installer which has to be done from a supported machine. As expected, the installed macOS shows up as 10.14.6 (18G95).
 
  • Like
Reactions: Eligos
I boot with the USB Installer and open the DiskUtility and choose the drive I want to convert to APFS but convert option is greyed out never been active. WHY? My system is HFS and I thought it will work on the recovery but when I choose recovery partition it never boots just giving me a prohibited sign error.

What can I do?
 
MacBook5,1 downloads 14.6.04 full installer straight from the App Store like a boss. I guess this is one of the many benefits of running Mojave on unsupported Mac. I would not be able to do it on High Sierra or any other Mac OS.

Screen Shot 2019-08-27 at 5.07.24 am.png


Screen Shot 2019-08-27 at 5.03.38 am.png

[doublepost=1566879820][/doublepost]
I boot with the USB Installer and open the DiskUtility and choose the drive I want to convert to APFS but convert option is greyed out never been active. WHY? My system is HFS and I thought it will work on the recovery but when I choose recovery partition it never boots just giving me a prohibited sign error.

What can I do?

Perhaps you need to unmount it first?
 
  • Like
Reactions: roronl and K two
First post here! this is my second run of the Patch, first, i sucessfuly updated a Macbook 5.2 (White, A1181 model). Now, i just managed to get it running on a iMac 9.1 (20-inch, Early 2009).

First, i would like to say thank you to @dosdude1 for this awesome patch and to give a huge extend of life to those macs, without you work, many people would not see the face of Mojave!

On my first run of the patch, the Macbook had a broken brightness slider, initially i fixed this by downloading Brightness Slider from the store, but then, a Patch Update fixed the brightness slider.

On this iMac i got the same issue, however, there seems to be no Patch update that fixes the slider

Is it possible to release the same fix to the iMac on the Patch Updater?

Thanks!
Just an update on that: I managed to fix the backlight on the iMac 9.1 by using the patch created by DD1 himself! Really great patch that works wonderfully, imo it should be released on the patch updater for future OS installs just like with Macbook 5.2, Many thanks again for the amazing patch DosDude1!

Also, fixed the white theme with bluesky, thanks really a lot for the tool Julian!

Long live to our forgotten macs!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.