Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.14 Mojave on Unsupported Macs Thread

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.
avz said:
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.
Click to expand...

Yes, I removed the 5beta4 coredisplay.framework and replaced it with the 10.14.4 version. It’s not so much extra code or anything like that, just to simplify it so it joins the other fixes that are part of the patcher automatically. Less chance for me to mess things up mainly.

jackluke said:
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.
Click to expand...

Sorry for the confusion on my wording, it was just a simple delete and replace I did with the core.display.framework.

Thank you for the 5beta 4 version, it is much appreciated.
When I did the update I used the 10.14.4 one for my 13” 2001 MBP 8.1 and it works very well with no issues at all so it should be fine with using the patcher too.
 
  • Like
Reactions: webg3 and jackluke
Interesting trivia:
The new 63kB iSight patch (popping up with patch updater these days) works as advertised on MB5,2 and does not change working setup of FaceTime on i.e. iMac 8,1.
Unfortunately, but no harm done, it does not bring FaceTime to MB4,1. USB on that machine still works after the patch.
Q: what components are changed by the patch?
 
  • Like
Reactions: jackluke and pkouame
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.

Bildschirmfoto 2019-05-05 um 14.04.10.jpg
 
  • Like
Reactions: TimothyR734, jackluke, webg3 and 3 others
ASentientBot said:
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??
Click to expand...
Without the stress of hardware acceleration, it works even faster. My machine is fast enough, rarely lagging.
 
ASentientBot said:
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.
Click to expand...

@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.
 
  • Like
Reactions: ASentientBot
Vyzantion said:
Without the stress of hardware acceleration, it works even faster. My machine is fast enough, rarely lagging.
Click to expand...
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.
 
  • Like
Reactions: bbfc, webg3, ASentientBot and 4 others
Vyzantion said:
Without the stress of hardware acceleration, it works even faster. My machine is fast enough, rarely lagging.
Click to expand...
@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 $.
 
  • Like
Reactions: webg3, jackluke, K two and 1 other person
hvds said:
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.
Click to expand...
Apple Hardware Test found no problems on my MBP5,2 17" in two passes, including extended testing (but see below*).

The DVD contained AHT version 3A175 from 2009. AHT started by holding D while powering-on with the DVD in the reader.

*Before the successful tests AHT found an error related I think to the temperature sensor of the battery (code 4SNS/1/40000000: TB3T-128.000). The battery I used was not original Apple, but an LMP P/N 9697. I still had the previous (Apple) battery which I had replaced unnecessarily when observing frequent spontaneous shutdowns last year; in fact they were due to a faulty capacitor C7771. Thanks again to @dosdude1 for the repair instructions!
After installing the Apple battery tests proceeded with no error.
 
Last edited:
  • Like
Reactions: pkouame and dosdude1
pkouame said:
@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 $.
Click to expand...
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 I read your earlier posts in this thread about Volume Control Patch and you are saying you must receive this patch after boot but I never receive it. How can I receive this patch? What should I do?
 
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







Anonymous UUID: 91C52A13-9320-8DAD-AAD7-B34E522125CD

Mon May 6 09:00:34 2019

*** Panic Report ***
panic(cpu 1 caller 0xffffff8002add16d): Kernel trap at 0xffffff7f841682f9, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffff802a91469117, CR3: 0x00000001f4135000, CR4: 0x00000000000026e0
RAX: 0x0000004000000100, RBX: 0x00000000000083e4, RCX: 0x00000000000003e4, RDX: 0x00000000031f0000
RSP: 0xffffff910fe72ff0, RBP: 0xffffff910fe730e0, RSI: 0xffffff8015634520, RDI: 0xffff802a914690ff
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000040000000, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffff8015540000, R15: 0x0000000040000000
RFL: 0x0000000000010286, RIP: 0xffffff7f841682f9, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0xffff802a91469117, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 1

mp = 0xffffff801541b880, phys = 0x1f6873880, prev (0xb: 0xffffc000-0x100000000)
vp = 0xffffff801a3d6458, phys = 0x1e9cc9458, prev (0xb: 0xffffc000-0x100000000)
0xffffff801541a000: aQAAAHEAAAB8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoPGouAIBAQAAIIIAgEAQMAYDAkGG0aLTgoMaP0QBMwACKQQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwMAeHwkHDgAmAAACCABYNCETAAAABAADYNAIAAEHAAAAAAAAAAAAAAAAAAAAAADwwtSA////AAAABAABAAAAAEAA/w8AAAAQAAAgAAAAAAAAIf////8/AAAAAFl+G2CTOjRye7IYoMJBFYC4QRUQbSYD4DgmA3ggZBVIJj4j0BlkFZCkQRUAEBAEABAQACBiXxVkZXZmL2RldgAAAgD/DwAAWQQAAAA7AQAAAAAh/////z8AAADAVmQV9h40FqCuQRUAEAAAAADg4O7u4ADu7u6ODgAAAMMADc7cIODgDufu4AUOBQ4BBCAAmwMOAQL8DzhN/Q84oABoGKNOMAcgAAgCAYy9OYDDBgEC/A84sAILEAAA
0xffffff801541b000: IUMAAAAAAgBgBwAAAgBkByAAAABoByAAAABsBwAAAgBwBwAAAgB0B/8PAAB4BwACAAB8ByAAAACABwEAAACEBwAAACHIB//////kBwBbyBQwCID///80CAIAAABQCP////98CECkQRWACID///+ECHgBQAOICID///+MCA0XAQCQCP////+kCKBwG4SoCH////+sCCBwYBWwCID///+0CIhO5xbACID////ECHhkPRrICID////MCGBjPRrQCID////UCLAdZBXYCID////cCKBrhRbgCID////kCMBrhRboCID////sCADQgATwCIAA3YD0CBAAAAD8CAAQAAAECQAAEAAICfxDRgcQCT61qAMYCRD3pQMgCb6OnQMoCf////8wCf///380CSq96/84Cf///388CQQAAAFACRkAAABECQHQgARMCWFwZnNUCS8AAABkCS9kZXZkDS9kaXNoDWsxczFsDQAA
0xffffff801541c000: iwAAAJMAAACfAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEICAGh8aCw4AJgAAAQoRSAwAAKgcKDQoNar9iDhhAyqoCjgIAgICAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAICAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKDxqLgBAQEAABCiEIBAEDAGAwJBhlGh04KDGT8AAgIAAioIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQttOA////AAAABAABAAAAAEAAAwAAAAAQAABZBAAAcAACAAAAACGAH2QVAwAAAEBXZBUAgUoiAAAAAsDMQRVApEEVBwAAAKBwG4QgcGAVYOOPFaBrVBxY6I8V8MJBFQSQkBQAAN2AAAAQAPxDRgfVFaYDBQAAAP////////9//P///////38GAAABGQAAAGFwZnMvcHJpdmF0ZS92YXIvdm0AL2Rldi9kaXNrMXMyAEC204D///8AAAAEAAEAAAAAQAADAAAAABAAAAAAACHA148VAwAAAECCjBU46I8VUgpWMeDWQRXQke+FIPYeGUDXNBoAoDoaEM1BFQgAUAQAAAgAAAQAAAACAAABAAAyGgAAAGF1dG9mcwAAL25ldAAAANDsDu7g7u7u7o79DgQA4ODgDu7u0O7g7m4ODgEOAYAQAALQ9T+AByAA/wP+P38DDjD3BwACAQjwP4BvDjgQCPA/gIMaAP//DTgggAQA
Backtrace (CPU 1), Frame : Return Address
0xffffff910fe72ac0 : 0xffffff80029af82d
0xffffff910fe72b10 : 0xffffff8002aeb795
0xffffff910fe72b50 : 0xffffff8002adcf4a
0xffffff910fe72bc0 : 0xffffff800295cae0
0xffffff910fe72be0 : 0xffffff80029af247
0xffffff910fe72d00 : 0xffffff80029af093
0xffffff910fe72d70 : 0xffffff8002add16d
0xffffff910fe72ee0 : 0xffffff800295cae0
0xffffff910fe72f00 : 0xffffff7f841682f9
0xffffff910fe730e0 : 0xffffff7f84175f9e
0xffffff910fe733c0 : 0xffffff7f84133d09
0xffffff910fe73410 : 0xffffff7f8413496c
0xffffff910fe736e0 : 0xffffff7f840dfeca
0xffffff910fe73860 : 0xffffff8002c3303f
0xffffff910fe738f0 : 0xffffff8002be70a4
0xffffff910fe73a30 : 0xffffff8002beb3a7
0xffffff910fe73ad0 : 0xffffff8002beac35
0xffffff910fe73c10 : 0xffffff8002beff03
0xffffff910fe73ca0 : 0xffffff7f840dcc36
0xffffff910fe73d10 : 0xffffff8002c30245
0xffffff910fe73d60 : 0xffffff7f8410eaa4
0xffffff910fe73da0 : 0xffffff8002bf8df3
0xffffff910fe73e50 : 0xffffff7f8410c1d8
0xffffff910fe73ea0 : 0xffffff8002c09e32
0xffffff910fe73ec0 : 0xffffff8002bf8a69
0xffffff910fe73f30 : 0xffffff8002c09d67
0xffffff910fe73f40 : 0xffffff8002fbb0ed
0xffffff910fe73fa0 : 0xffffff800295d2a6
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(945.250.134)[ED6CC0AB-28A7-3677-AC9F-762D613F91DA]@0xffffff7f840b9000->0xffffff7f841b9fff
dependency: com.apple.kec.corecrypto(1.0)[5AB8B6D3-C4F2-3457-A0D5-EB3A341EB22B]@0xffffff7f83b83000
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[AC061D0B-F4FF-34BB-9B05-9A9FC01DF807]@0xffffff7f84015000
dependency: com.apple.iokit.IOStorageFamily(2.1)[C322B8D1-C27F-3EFA-8A45-D7035ACC8D07]@0xffffff7f838b9000

BSD process name corresponding to current thread: launchd
Boot args: kext-dev-mode=1 -no_compat_check

Mac OS version:
18E226

Kernel version:
Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64
Kernel UUID: 4170BF94-38B6-364F-A1B0-2F7C2C30F9A9
Kernel slide: 0x0000000002600000
Kernel text base: 0xffffff8002800000
__HIB text base: 0xffffff8002700000
System model name: Macmini3,1 (Mac-F22C86C8)

System uptime in nanoseconds: 1113139408085
last loaded kext at 294968093552: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f83d49000, size 69632)
loaded kexts:
com.AmbrosiaSW.AudioSupport 4.1.4
com.logmein.driver.LogMeInSoundDriver 411.2.11
com.Cycling74.driver.Soundflower 1.5.3
com.makemkv.kext.daspi 1
com.parrotgeek.NDRVShim 1
com.parrotgeek.SIPManager 1
com.plantronics.driver.PlantronicsDriverShield 4.3
com.apple.filesystems.msdosfs 1.10
com.apple.filesystems.smbfs 3.3.2
com.apple.fileutil 20.036.15
com.apple.driver.AppleTopCaseHIDEventDriver 138.3
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AppleGraphicsDevicePolicy 3.30.14
com.apple.AGDCPluginDisplayMetrics 3.30.14
com.apple.driver.AGPM 110.25.2
com.apple.driver.ApplePlatformEnabler 2.7.0d0
com.apple.driver.AppleHDAHardwareConfigDriver 281.52
com.apple.driver.AppleHDA 281.52
com.apple.driver.AppleHV 1
com.apple.driver.AppleUpstreamUserClient 3.6.5
com.apple.driver.AppleMCCSControl 1.5.6
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.iokit.IOBluetoothSerialManager 6.0.11f4
com.apple.driver.pmtelemetry 1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.GeForceTesla 10.0.4
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleLPC 3.1
com.apple.nvidia.NVDAStartup 12.0.0
com.apple.driver.MaxTranserSizeOverrideDriver 456.250.6
com.apple.iokit.IOBluetoothUSBDFU 6.0.11f4
com.apple.driver.AppleIRController 354
com.apple.driver.Oxford_Semi 456.250.6
com.apple.driver.IOFireWireSerialBusProtocolSansPhysicalUnit 456.250.6
com.apple.driver.StorageLynx 456.250.6
com.apple.driver.LSI_FW_500 456.250.6
com.apple.driver.initioFWBridge 456.250.6
com.apple.driver.AppleFireWireStorage 456.250.6
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.driver.AppleVirtIO 2.1.3
com.apple.filesystems.hfs.kext 407.200.4
com.apple.iokit.SCSITaskUserClient 408.250.3
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleSystemPolicy 1.0
com.apple.filesystems.apfs 945.250.134
com.apple.private.KextAudit 1.0
com.apple.driver.AirPort.Brcm4331 800.21.31
com.apple.driver.AirPort.Brcm4360 1400.1.1
com.apple.driver.AppleFWOHCI 5.6.0
com.apple.driver.AppleAHCIPort 329.200.2
com.apple.nvenet 2.0.22
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 6.1
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 6.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 220.0.0
com.apple.nke.applicationfirewall 190
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 220.0.0
com.apple.driver.AppleBluetoothHIDKeyboard 208
com.apple.driver.AppleHIDKeyboard 208
com.apple.driver.AppleMultitouchDriver 2440.7
com.apple.driver.AppleInputDeviceSupport 2440.2
com.apple.kext.triggers 1.0
com.apple.driver.AppleHSBluetoothDriver 138.3
com.apple.driver.IOBluetoothHIDDriver 6.0.11f4
com.apple.driver.AppleGraphicsControl 3.30.14
com.apple.driver.DspFuncLib 281.52
com.apple.kext.OSvKernDSPLib 528
com.apple.iokit.IOAVBFamily 740.1
com.apple.plugin.IOgPTPPlugin 740.2
com.apple.iokit.IOEthernetAVBController 1.1.0
com.apple.iokit.IOSkywalkFamily 1
com.apple.driver.AppleSMBusController 1.0.18d1
com.apple.driver.AppleSSE 1.0
com.apple.iokit.IOSurface 255.4.2
com.apple.AppleGPUWrangler 3.30.14
com.apple.AppleGraphicsDeviceControl 3.30.14
com.apple.nvidia.classic.NVDANV50HalTesla 10.0.4
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.iokit.IOFireWireIP 2.3.0
com.apple.nvidia.classic.NVDAResmanTesla 10.0.4
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleHDAController 281.52
com.apple.iokit.IOHDAFamily 281.52
com.apple.driver.IOPlatformPluginFamily 6.0.0d8
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.iokit.IONDRVSupport 530.51
com.apple.iokit.IOGraphicsFamily 530.60
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.11f4
com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.11f4
com.apple.iokit.IOBluetoothHostControllerTransport 6.0.11f4
com.apple.iokit.IOBluetoothFamily 6.0.11f4
com.apple.driver.usb.AppleUSBHub 1.2
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.5.1
com.apple.iokit.IOFireWireSBP2 4.3.3
com.apple.driver.AppleUSBAudio 315.6
com.apple.driver.usb.IOUSBHostHIDDevice 1.2
com.apple.iokit.IOAudioFamily 206.5
com.apple.vecLib.kext 1.2.0
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2
com.apple.iokit.IOSerialFamily 11
com.apple.iokit.IOSCSIMultimediaCommandsDevice 408.250.3
com.apple.iokit.IOBDStorageFamily 1.8
com.apple.iokit.IODVDStorageFamily 1.8
com.apple.iokit.IOCDStorageFamily 1.8
com.apple.filesystems.hfs.encodings.kext 1
com.apple.iokit.IOAHCISerialATAPI 267.50.1
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IOAHCIBlockStorage 301.250.5
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.driver.corecapture 1.0.4
com.apple.iokit.IOFireWireFamily 4.7.3
com.apple.iokit.IOAHCIFamily 288
com.apple.driver.AppleUSBMergeNub 900.4.1
com.apple.driver.usb.AppleUSBOHCIPCI 1.2
com.apple.driver.usb.AppleUSBOHCI 1.2
com.apple.driver.usb.AppleUSBEHCIPCI 1.2
com.apple.driver.usb.AppleUSBEHCI 1.2
com.apple.driver.NVSMU 2.2.9
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.quarantine 3
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 493.0.0
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleUSBTDM 456.250.6
com.apple.driver.AppleMobileFileIntegrity 1



EOF
Model: Macmini3,1, BootROM MM31.00AD.B00, 2 processors, Intel Core 2 Duo, 2.53 GHz, 8 GB, SMC 1.35f1
Graphics: kHW_NVidiaGeForce9400Item, NVIDIA GeForce 9400, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x857F, 0x483634353155363446373036364700000000
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x857F, 0x483634353155363446373036364700000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Bluetooth: Version 6.0.11f4, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 840 EVO 500GB, 500.11 GB
Serial ATA Device: OPTIARC DVD RW AD-5670S
USB Device: USB Bus
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: IR Receiver
USB Device: USB 2.0 Bus
USB Device: CanoScan
USB Device: Canon CAPT USB Device
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Miscellaneous Device
USB Device: ImageMate CF
USB Device: OWC Express USB 3.0
FireWire Device: Passport III, WD, Up to 800 Mb/sec
Thunderbolt Bus:
 
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.
 
jbarley said:
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.
Click to expand...

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?
 
BuffyzDead said:
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
Click to expand...

In your log, the legacy webcam patch kext isn't even loaded at all.
 
  • Like
Reactions: jackluke, K two, Larsvonhier and 3 others
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
 
  • Like
Reactions: K two
swheel said:
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
Click to expand...

Do NVRAM reset. Turn-on iMac, hold comand-option-p-r. Let it bong twice. Then, hold down option key, select boot drive w/ arrow key. Return.
 
deeveedee said:
@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.
Click to expand...

@ASentientBot - I'm on track to figuring out the failed boot of the USB installer. Don't waste your time with this. I will return with an update when I have the solution.
 
  • Like
Reactions: ASentientBot
K two said:
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.
Click to expand...

As much as I like Firefox(and all its useful extensions), I must admit that it is way too hard on my old hardware resources, so after the extensions went belly-up I saw it as an opportunity to get rid of it. And I am very glad I did, the system works much better and cooler with Safari/Safari Technology Preview(I also reduced the RAM from 8GB to 4GB as its plenty for my use). In order to replace some extensions I discovered some very good command line tools.
 
  • Like
Reactions: ASentientBot
parrotgeek1 said:
In your log, the legacy webcam patch kext isn't even loaded at all.
Click to expand...

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.
 
  • Like
Reactions: LuisN
jackluke said:
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.
Click to expand...
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.
 
  • Like
Reactions: jackluke
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back