My thoughts exactly lol.
@Vyzantion -- there is a Reduce Transparency option in Accessibility preferences if you like the "no acceleration" look. If you like the slowness rather than the look, you're insane. Could you give an explanation??
My thoughts exactly lol.
I am guessing that you already did manually what the patcher does automatically, or am I missing something? I doubt that there is an extra "code" in the new patcher.
For a moment I thought you had binary patched the .5 beta 4 CoreDisplay and that would have been great but not easy at all, anyway I always retain copies of original files I replace, so here is the stock .5 beta 4 CoreDisplay, you can simply notice that internally it is the current "untouched CoreDisplay" just checking this attached binary "date modified" comparing with your Mojave /usr/bin/ binaries "date modified", they match exactly with April 26th that is the last date available when apple developers officially compiled the current Mojave binaries.
Of course on the next .5 beta 5 Mojave release we expect that all the core binaries "date modified" will be recompiled during this month of May.
But keep in mind that for "unsupported Mac" the only working "CoreDisplays" are those taken from 10.14.4 or earlier, this one attached is only needed for "Mojave supported Mac" to bring the Metal Acceleration.
Very cool.Update time for the MB4,1 again.
New "hybrid" kexts in v1.3b contain newer/up to date components. Version numbering is shifted accordingly, see table/screenshot.
Get the full package here. Tested and working fine with 10.14.5b3.
View attachment 835381
Without the stress of hardware acceleration, it works even faster. My machine is fast enough, rarely lagging.My thoughts exactly lol.
@Vyzantion -- there is a Reduce Transparency option in Accessibility preferences if you like the "no acceleration" look. If you like the slowness rather than the look, you're insane. Could you give an explanation??
Since this is a Hackintosh, there could be several issues unrelated to our efforts and you might have more success posting somewhere like insanelymac. However, we can definitely look into it and see if our knowledge overlaps. The main problem here looks like the WindowServer crash. I'm not sure why that happens, though, since the installer BaseSystem typically runs without acceleration anyways.
There is all kinds of weirdness that can happen in the BaseSystem/recovery environments and it's tricky to troubleshoot. You might try a manual install of the package to a separate partition using Installer.app in High Sierra (I can walk you through this if necessary). Then we can debug a lot more effectively in the full system. Since your GPU is similar to the GeForce 8600, you'll probably eventually need to use our nVidia Tesla legacy graphics patch, but we'll deal with that once we get you booting without acceleration.
Hardware accelerated graphics does not cause any "stress" to the machine in any way... In fact, if anything, it RELIEVES "stress", as the video is being rendered by the GPU and not via software rendering, which puts a ton of extra load on your CPU, and makes the system run WAY hotter. Acceleration only makes the experience 100x better, as macOS is close to unusable without full hardware accelerated graphics.Without the stress of hardware acceleration, it works even faster. My machine is fast enough, rarely lagging.
@dosdude1 beat me to the point...Without the stress of hardware acceleration, it works even faster. My machine is fast enough, rarely lagging.
Apple Hardware Test found no problems on my MBP5,2 17" in two passes, including extended testing (but see below*).Thank you.
Did a /sbin/fsck -y on the internal disk in single-user mode. Looks good to me, but a screen photo is attached because of the four lines with handle_crypto_mount and apfs_keybag that I can't interprete.
Safari would not crash by itself and leave the system intact. I've only the KP report so far. Will continue using Safari and see what I get.
Just found back the DVDs delivered with my MBP 10 years ago!
Will try them now.
I do not plan to ever get an official Mac. As long as it is legal where I am, I shall stick to Hackintosh.@dosdude1 beat me to the point...
Sorry, but the whole point with hw (gpu based) acceleration is to offload most of the VERY compute intensive screen rendering ops to parallel processors like gpus - OpenGL does this well - Metal is even better as it is closer to the "metal" eliminating even more latency. This is even more of an issue for our old processors and architectures, hence why we focus on it here... Of course this depends on your use case, but you want to run Youtube, iTunes, LogicPro ,GarageBand and casually browse on any of the last four macOSes without acceleration...Good luck. As to getting a new Mac and disabling acceleration ... seriously ... just save you're hard earned $.
it should also be in your patch updater in your utilities folder
If this happened to me, I'd just restore the most recent backup I made before applying the patch.
That would put things straight again.
RATS !!!
My Mac mini 3,1 (Late 2009) had been running perfectly for the last 34 continuous days, under 10.14.4
UNTIL just moments ago,
AFTER I applied a legacy webcam update, that the Patch Updater prompted.
within 7 - 8 minutes, complete crash and reboot.
Came back and I'm typing this from the Mac mini
Error logs below
What Happened?…and can I reverse that last patch cause I know it will now continue to crash
Thank You
Hi,
I installed 10.14.4 via OTA, applied patches via usb and rebuild caches. My Imac 11.1 can't log in, it shows a gray screen and stays there without entering to the log in screen.
¿Any idea of what can I do?
Thank you guys
I meant that a full system restore would put things straight, not just picking and poking and hoping to get lucky.Makes sense. …and I have a time machine backup.
NOW
I just need the file path,
to exactly where the
Legacy iSight/Webcam Patch exists?
@ASentientBot I have a HackPro 5,1 system that I successfully upgraded with a patched Mojave install USB (patcher 1.3.0, Mojave 10.14.4). I have tried to reboot the very same HackPro 5,1 system with the very same patched Mojave installer USB and get the same trustd/locationd/WinowsServer/pluginkit endless boot loop that I experienced with my HackBookPro 7,1 (reported in post #14858). Nothing has changed about the HackPro 5,1 and nothing has changed about the patched USB installer.
What could be causing the patched USB installer to experience this problem after previously booting fine (and allowing me to upgrade the HackPro 5,1 to Mojave 10.14.4)? I suspect that if I figure this out, I'll know why the patched USB installer does not boot on my HackBookPro 7,1.
Thank you for your help.
Ahoy! If your Firefox Extentions went belly-up, do this -
Go to Firefox Preferences>Privacy and Security>Firefox Data Collection and Use>❎Allow Firefox to send technical and interaction data to Mozilla>❎Allow Firefox to install and run studies>❎Allow Firefox to make personalized extension recommendations. Takes about 10 minutes for Firefox Extensions to re-enable.
Turn those selections off later, the fix will stick. btw - at this writng there is no Mac v. 66.0.4, only Windows.
In your log, the legacy webcam patch kext isn't even loaded at all.
My mp3.1 connected to Apple LED Cinema Display needs the patch to get isight working. Uses the Cinema Display camera. So all slightly confusing! The update did not seem to affect my system.Infact, except any Mac/Macbook with an embedded LCD, every other Mac mini, Mac Pro don't have any internal USB iSight/Webcam hardware integrated, anyway there are two weird facts:
1) Why someone should accept and install a patch for an USB internal hardware (Webcam) that is not physically present?
I mean if can plug a USB printer, an external USB drive, then surely can plug also an external USB Webcam without any additional iSight patch.
2) Why "auto-patch updater" prompts a patch for a machine that doesn't have any internal webcam hardware?
Even if they seem not related in any way, I guess there is a minimum chance that a legacyiSight patch could cause a random KP on a non-targeted machine.