I have tried putting my High Sierra disk back in and still see the scrolling text. Thank you for your help!
I will also see a scrolling text if I don't do this. Please post a screenshot of your Startup Disk Preference Pane.
I have tried putting my High Sierra disk back in and still see the scrolling text. Thank you for your help!
@netsrot39
Excuse my ignorance please, but I cannot get this to work.
I tried copying everything, from the raw view of the Bluesky.sh file, all 443 lines of code/script,
into Terminal,
But it does not make any changes to light mode.
Can you please detail the exact steps needed, to use this code/script in terminal, so I too can use light mode on my late 2009 Mac mini under 10.14.6
Perhaps I should not be using terminal but something else.
Thank you
If the script doesn’t detect the resources folder, then it will download them automatically. This is the recommended method of installation since updates can be made without needing to download new versions manually. If you prefer to have the resources included, you can download the .zip from the releases page, that one includes both the .sh script, and the resources folder. Download the .sh script for the automatic download version.So here is how I did it:
1. Download the files from here as a zip file (https://github.com/rmc-team/bluesky) and unzip it to a new folder
2. Download the following file https://github.com/rmc-team/bluesky-resources/archive/master.zip and unzip the "resources" directory to the previous created folder that has the main shell script in it
-> The directory should look like this (see attached image)
3. Open Terminal, type sudo and then drag and drop BlueSky.sh and hit enter
4. Follow the install routine and when asked select "5 - Install both patches"
After the automatic restart everything should work and the graphic glitches should be gone.
Are you sure you patched the right hardware...?
I don't recall MBP6,2 has 640m... only 330m...
Sweet! that worked awesome! Thank you so much for the help I appreciate it!Hi shadowcatz23, I am assuming you are trying to remove the scrolling text at start up caused by the APFS software patch. If so try this:
To remove the verbose output you will need to mount the efi drive. To find which one it is use:
sudo diskutil list
This will display your drives and you can identify the efi partition. In my case it is disk0s1. Then mount this partition:
sudo diskutil mount disk0s1
After a moment the efi drive should appear on your desktop. You can then use finder to delete the following: apfs.efi, /BOOT/BOOTX64.EFI and startup.nsh.
Here ya go!I will also see a scrolling text if I don't do this. Please post a screenshot of your Startup Disk Preference Pane.
View attachment 854148
[doublepost=1566503106][/doublepost]
Sweet! that worked awesome! Thank you so much for the help I appreciate it!
[doublepost=1566503216][/doublepost]
Here ya go!
Sorry that bothered you, but I did at least want to provide answers to the questions I was asked.Flacko already advised you of a solution from the page 228 of this thread but technically it is not necessary to get rid of the verbose boot. Glad that something has worked for you in the end.
Sorry that bothered you, but I did at least want to provide answers to the questions I was asked.
I notice a bug in my laptops running mojave patcher. I don't know if the bug is caused by the patch or the original Mojave OS (I only have unsupported laptops).
I notice that the "kernel_task" is consuming a lot of resources in "Activity monitor". See the image attached.
During this high consumption of "kernel_task", the system is very slow. Is very evident at boot (the system delay a lot of time to be operative).
I have a macbook 5.1 and a 5.2. Both have a very similar hardware and both have the same problem. May be a driver problem? I have an iMac 7.1 too with mojave patcher and I have not this problem. This laptops have windows 10 installed too, and i not notice the system slow at boot or during the use of windows 10, so i think that is a problem with Mojave or the patcher (@dosdude1 says in a previous post that some computers can have a sensor damaged, but i think that if my sensors were damaged, windows 10 may run as slow as mojave does, Isn't it?)
Other diference between the laptops and my iMac is that the laptops have APFS and the imac have HFS.
Anybody have this models with Mojave patcher and notice the same problem? Can anybody see the "activity monitor" and tell us if the "kernel_task" ins consuming high resources? Anybody have a solution for this?
Thanks
It most likely your hardware as Mojave is a perfection on my MacBook5,1(as well as Catalina Beta 6). "Kernel_task" consumes less resources than Activity Monitor itself(most of the time). I hope you are using good quality SSD's with plenty of free space available in your machines.
I have SSD's in both computers and botht SSD's works well. I have enought free space too.
Today i tryed to format the Mojave partition. When the installation was completed, the problem dissapear, so it might be a software problem. I made a change: Now i will use NFS instead of APFS. I'm restoring the time machine backup in the computer. When it finished i can see if the problem persists or the problem is related to APFS (I think that it must be the problem).
@dosdude1
It would be great if we can get an option to install a 100 % original System. Like you added in the catalina patcher for debugging.
A lot of people use the patcher to install on supported macs, too.
As it is less complicated...
It is... Just don't apply post-install patches and it is a 100% stock install.@dosdude1
It would be great if we can get an option to install a 100 % original System. Like you added in the catalina patcher for debugging.
A lot of people use the patcher to install on supported macs, too.
As it is less complicated...
Did you apply the post-install patches using an installer volume created with Mojave Patcher version 1.3.2 or later, as instructed?I'm sure I did everything right. Mojave 10.14.5 installed perfectly on Mac Pro 3,1 and worked without issue for two months save for a few graphics anomalies like the search field not being visible in Outlook.
I referred to the following from the updates section found at http://dosdude1.com/mojave/#updates:
10.14.6 can be updated normally via Software Update if using an APFS volume, and will need to be patched using an installer volume created with Mojave Patcher version 1.3.2 or later after installing.
I updated via Software Update and now the machine auto reboots after the progress bar on the boot screen is a little more than half complete. It never transitions to the Black boot screen with the white apple logo to complete the boot sequence.
Any suggestions?
I assumed that this was to be done after the update from within Mojave. Do I need to boot from the the drive I originally used to install?Did you apply the post-install patches using an installer volume created with Mojave Patcher version 1.3.2 or later, as instructed?
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.So nothing about no hardware video acceleration?