Well folks, welcome to Mohave 10.14.6 beta testing that Apple released today.
At this rate I'd expect a Mojave 10.14.7 and even .8 as Leopard/SL times.
I don't think to follow this .6 betas, maybe directly jump to 10.15 .
Well folks, welcome to Mohave 10.14.6 beta testing that Apple released today.
Yes I did - my hybrid patches don't fix that yet. Dunno why.Hi everybody,
Has anyone observed this little bug with Hybrid transparency? Or do not I have the right versions of CoreUI, HIToolbox and CoreDisplay.framework
I used CoreDisplay.framework v99.14 (1 238 313 bytes) and CoreDisplay.framework v99.14 (1 232 165 bytes)
CoreUI and HIToolbox Hybrid-18E226
View attachment 837132 View attachment 837133
If I put back original HIToolbox (saved) I have the ugly gray menu bar but strange thing, I still have transparency with the Finder.
View attachment 837134
For information, I made this manipulation on MBP5,3 and iMac8,1 with the same result on both machines
By the way, which version of macOS are you run-in? If it's any variant of .5, hybrid transparency patches are not available yet (soon). Some report that .4 versions of Hybrid patches work well with .5, but it's not a tested or supported configuration, so just be aware of that. Thanks.Hi everybody,
Has anyone observed this little bug with Hybrid transparency? Or do not I have the right versions of CoreUI, HIToolbox and CoreDisplay.framework
I used CoreDisplay.framework v99.14 (1 238 313 bytes) and CoreDisplay.framework v99.14 (1 232 165 bytes)
CoreUI and HIToolbox Hybrid-18E226
View attachment 837132 View attachment 837133
If I put back original HIToolbox (saved) I have the ugly gray menu bar but strange thing, I still have transparency with the Finder.
View attachment 837134
For information, I made this manipulation on MBP5,3 and iMac8,1 with the same result on both machines
.4 hybrid patches work well with 10.14.5 and 10.14.6 beta 1 so far I posted screenshots when I updated my iMac and MacBookYes I did - my hybrid patches don't fix that yet. Dunno why.
HIToolbox affects all things menubar - so restoring the original version will undo those fixes. No correlation to CoreUI but a legitimate configuration if you don't want to muck with the menubar (or don't care for the Dark mode side effects)
CoreDisplay is not part of my Hybrid patch approach. No linked effect that I know of (yet). It IS necessary for graphics acceleration from 10.4.4 onwards (as @ASentientBot discovered)
[doublepost=1557954850][/doublepost]Hmmm a new .6 beta with NO release notes. I hate those...
https://developer.apple.com/documen...notes/macos_mojave_10_14_6_beta_release_notes
Wonder what changes are being snuck in...
[doublepost=1557955276][/doublepost]
By the way, which version of macOS are you run-in? If it's any variant of .5, hybrid transparency patches are not available yet (soon). Some report that .4 versions of Hybrid patches work well with .5, but it's not a tested or supported configuration, so just be aware of that. Thanks.
Mmm, interesting Alphascorp.Good evening @upipes
I have the same thing with my Radeon HD 5870 under El Capitan
View attachment 837204
You can do a PRAM reset to get it back to the integrated GPU (if not, then SMC reset... I honestly cannot remember which). Not sure why the switch from dGPU back to integrated does not work as expected.
Just re-install the Legacy Video Card Patch using Patch Updater, and that should restore that functionality.
if I remember right last year 10.13.6 final came out the same time the first beta of macOS Mojave about 2 weeks after the event in JuneAt this rate I'd expect a Mojave 10.14.7 and even .8 as Leopard/SL times.
I don't think to follow this .6 betas, maybe directly jump to 10.15 .
@dosdude1https://forums.macrumors.com/members/dosdude1.669685/ Any idea how to fix the the CCFL backlight on my 17" MacBookPro4,1 that stopped working after my OTA upgrade from 10.14.3 to 10.14.5 followed by running macOS Mojave Patcher post install ???
Do I have to re-run your CCFL Backlight Control Patch (bkltpatch10.14.2 referenced in post #11156) that I successfully ran following my 10.14.2 installation? Or do I need an updated bkltpatch10.14.5 for macOS 10.14.5 ?
Yes, just go ahead and re-run that patch. It still causes kernel panics for some users (and I haven't been able to figure out why), so I haven't included it with any of my tools. The 10.14.2 version should work just the same on later versions.@dosdude1 Any idea how to fix the the CCFL backlight on my 17" MacBookPro4,1 that stopped working after my OTA upgrade from 10.14.3 to 10.14.5 followed by running macOS Mojave Patcher post install ???
Do I have to re-run your CCFL Backlight Control Patch (bkltpatch10.14.2 referenced in post #11156) that I successfully ran following my 10.14.2 installation? Or do I need an updated bkltpatch10.14.5 for macOS 10.14.5 ?
My 10.14.5 Status Update:
Downloaded dosdude1 patcher v1.3.2 today. Created a new USB Flash drive Installer with 10.14.5
27in iMac 11,1 running 10.14.4 - booted to flash drive, installed, rebooted, patched, rebooted. Everything A-OK! No issues whatsover. Works like a charm.
Macbook Pro 8,2 w/broken AMD dGPU running 10.14.4
Followed the same process as for my iMac. Turns out the install deleted my /System/Library/Extensions-off directory.
I use the loginhook / AMDRadeonX3000.kext load/unload + AMD6000.kext Info.plist FWB_CFG=3 method to keep my AMD dGPU disabled and still have brightness buttons + sleep + clamshell mode working. (I posted the method details I found a while back in this thread... I've found that cannot use the dosdude1 dGPU disable patch without losing brightness buttons and sleep functions...at least that was the case for 10.14.3 and 10.14.4).
Anyway, after patching with the tool (v1.3.2), my MBP went into a bootloop. So I went back to CLI Single user mode, recreated the System/Library/Extensions-off directory, and moved the AMDRadeonX3000.kext out of /System/Library/Extensions over to the Extensions-off directory. "touched" the Extensions directory and rebooted. SUCCESS! (This was good news, since it means I can use the updated 10.14.5 AMDRadeonX3000.kext, and not have to revert to a prior version. The 10.14.5 version appears to work fine with the loginhook load/unload hack.)
I then checked the AMD6000.kext info.plist and found the FWB_CFG was back to 0. Copied AMD6000.kext out of /System/Library/Extensions, updated the copy info.plist to FWB_CFG value "3" (as is needed), deleted the AMD6000.kext version in System/Library/Extensions, and replaced it with my modified version. Reboot. SUCESS!
Continuity Activation tool: Had to uninstall, reinstall, and then re-do the board-ID patching. Working now!
My only issue is the MBP iSight camera doesn't work now. I think I need to go back to the non-dosdude1 patched version. But I can't remember which .kext that is for the legacy iSight patch? Anybody know? I had it working fine in both 10.14.3 and 10.14.4....
Otherwise, I'm back to "normal" on the MBP and everything else is working well! THANK YOU ALL! THANK YOU dosdude1!
Unlike 10.14.0-3, in 10.14.4-5, USB/keyboard/touchpad actually works OOB on MacBook7,1 which is nVidia MCP89 based. Not sure if this applies to other machines, but it is kind of cool (and shocking, for Apple!) that the OS actually got more compatible again.It adds IOKit entries for each of the unsupported Mac models for their USB controller and bus power specifications. Without it, USB 1.1 (USBOHCI) functionality will not work at all, which causes non-functional USB on machines that initialize their USB bus in OHCI mode on POST (MCP79/89-based machines and older), and weird USB port power issues on newer machines (that POST with the bus in USB2.0 (EHCI) mode).
Yes, just go ahead and re-run that patch. It still causes kernel panics for some users (and I haven't been able to figure out why), so I haven't included it with any of my tools. The 10.14.2 version should work just the same on later versions.
I just did the upgrade from 14.4 to 14.5. With the 1.3.2 patcher version and repatched with APFS patch auto selected. On a MacPro 3.1
After the reboot the boot screen appears and hangs about halfway. Is this just a case of waiting (it's there for about half an hour now) or is there something else wrong. Or should I try something else. Normally somewhere in this excellent thread the answer is there , this time round my search skills let me down, thanks in advance for any tips.
And many thanks too the people who developed this awesome little tool.
Still works fine on two of my MBs: MBP4,1 and MB5,2.Yes, just go ahead and re-run that patch. It still causes kernel panics for some users (and I haven't been able to figure out why), so I haven't included it with any of my tools. The 10.14.2 version should work just the same on later versions.
Your video card is working properly. The line that says there is no driver is about the audio controller. This is for using audio over HDMI. Having no driver here is normal for Mac OS.Flacko, I understand. I want to say thank you again for your patience with me. This is a bit tricky for a beginner, and plus English is not my language. So I consider this update a total success! LOL
Now, I'll be focusing on finding the way to get a much better performance from the GTX680. I do video often, and time is gold!
There is one thing I've found on System Profile that makes me feel curious. As you see on the screenshot, the blue checked line, says no driver for the nVidia Card... but it has a driver on the upper line... weird, isn't it?
You can just re-install a copy of macOS using your Mojave Patcher USB drive, then apply post-install patches. When released, I hadn't realized that update would cause issues on 10.14.2 and older. It's been fixed now though, and won't cause issues on any Mojave version.installed a graphics driver update (mid 2010 iMac) from the patcher on the machine from dosdude and now I can start in single user mode only. The startup gets to the end of the bar and just hangs. If I boot with:
mvram boot-args=“-x -v -f” or without the -f I get a message about Iopresentmenttransactionstate I believe it is and then every process crashing with a “too many corpses being created” message
Is there any way to back this patch out or am I screwed?
You can just re-install a copy of macOS using your Mojave Patcher USB drive, then apply post-install patches. When released, I hadn't realized that update would cause issues on 10.14.2 and older. It's been fixed now though, and won't cause issues on any Mojave version.