Jump to content

jamiethemorris

Members
  • Content Count

    1,046
  • Joined

  • Last visited

  • Days Won

    1

jamiethemorris last won the day on October 10 2013

jamiethemorris had the most liked content!

About jamiethemorris

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender
    Male
  • Location
    San Rafael, CA
  • Interests
    Music Production, Audio Engineering

Recent Profile Visitors

11,729 profile views
  1. jamiethemorris

    Mac'os Mojave 10.14.5 is OuT

    Supposedly 10.15 will have an API for writing device drivers... Not sure how reliable this source is though, and it doesn't necessarily mean Nvidia is going to suddenly start making drivers again https://www.idownloadblog.com/2019/04/22/macos-10-15-api-device-drivers/
  2. jamiethemorris

    10.12.6 post-install locks up near "HID: Legacy Shim 2"

    I know this is a really old thread, I've long since solved the issue, but I figured I would post my solution in case someone stumbles across this. In Later versions of Sierra and onward, Apple removed support for some SATA chipsets and older SSDs. So some of my drives were not being detected at all. The same problem would occur in High Sierra and Mojave. This is also causes multiple drives to say "I/O Error" Message in the installer and show up as uninitialized. In my case, since I was updating from Installer app, the drive got stuck here. These patches are necessary to detect the drives: fix IO error for 10.13, credit SunKi Name: AppleAHCIPort Find: 4585F60F 95C289C8 83E0FE66 85C9780F 84D2750B Replace: 89C883E0 FE6685C9 0F98C141 08CC9090 9090750B MatchOS: 10.13.x,10.14.x fix IO error 10.14 by vit9696 Name: AppleAHCIPort Find: 40600200 Replace: 00000000 MatchOS: 10.14.x fix hotplug for 10.13, credit SunKi Name: AppleAHCIPort Find: 89C82540 6002003D 40200000 750C81E1 BF7FFFFF 898B5101 0000 Replace: 90909090 90909090 90909090 90909090 90909090 90909090 9090 MatchOS: 10.13.x,10.14.x Not sure if the hotplug one is 100% necessary
  3. jamiethemorris

    Mac'os Mojave 10.14.5 is OuT

    Found a solution for the iTunes crashes that doesn't involve changing the SMBios. Using the following WhateverGreen boot flags eliminated the crashes for me: shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 https://www.insanelymac.com/forum/topic/338799-itunes-crashing-mojave-macos-10145-itunes-v1295/
  4. I think I figured it out, no iTunes crashes so far. Basically instead of changing the SMBios, we just need to tell AppleGVA.framework to use the configuration for a different board-id (in this case the iMacPro1,1). Use the following boot flags: shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 You need WhateverGreen for them to work. You may need to use shikigva=40 instead if you have an iGPU. Here's why/how this works.. According to the crash report, it's pretty clear that AppleGVA is the culprit if I scroll down to the actual crash: Thread 16 Crashed:: Dispatch queue: com.apple.FigASMF.InstanceManagement 0 com.apple.AppleGVAFramework 0x00007fff62ac2be3 0x7fff62a9f000 + 146403 1 com.apple.AppleGVAFramework 0x00007fff62abb318 0x7fff62a9f000 + 115480 2 com.apple.AppleGVAFramework 0x00007fff62af0a18 0x7fff62a9f000 + 334360 3 com.apple.AppleGVAFramework 0x00007fff62abad88 0x7fff62a9f000 + 114056 4 com.apple.MediaToolbox 0x00007fff572b1aaf 0x7fff56e0d000 + 4868783 5 libdispatch.dylib 0x00007fff7e82763d _dispatch_client_callout + 8 6 libdispatch.dylib 0x00007fff7e833129 _dispatch_lane_barrier_sync_invoke_and_complete + 60 7 com.apple.MediaToolbox 0x00007fff572b0dc3 0x7fff56e0d000 + 4865475 8 com.apple.MediaToolbox 0x00007fff572b0d17 0x7fff56e0d000 + 4865303 9 com.apple.MediaToolbox 0x00007fff571ee100 0x7fff56e0d000 + 4067584 10 libdispatch.dylib 0x00007fff7e82763d _dispatch_client_callout + 8 11 libdispatch.dylib 0x00007fff7e82d8e0 _dispatch_lane_serial_drain + 602 12 libdispatch.dylib 0x00007fff7e82e396 _dispatch_lane_invoke + 385 13 libdispatch.dylib 0x00007fff7e8366ed _dispatch_workloop_worker_thread + 598 14 libsystem_pthread.dylib 0x00007fff7ea67611 _pthread_wqthread + 421 15 libsystem_pthread.dylib 0x00007fff7ea673fd start_wqthread + 13 So we just need to use AppleGVA's settings for a known working SMBios instead of actually changing the SMBios. Explanation of the shiki boot flags bitmask can be found here: https://github.com/acidanthera/WhateverGreen/blob/master/WhateverGreen/kern_shiki.hpp shikigva=32 is the ReplaceBoardID flag, and needs to be followed by the shiki-id flag to specify the board id for AppleGVA. According to that link, AddExecutableWhitelist is required for iGPUs, which has a value of 8, so 8+32 would make the bitmask 40. So if you have an iGPU use shikigva=40 instead. I don't personally have an iGPU so I can't confirm whether or not that works. P.S. Preview and Quicklook for JPEGs still work fine since we aren't changing anything for AppleVPA.framework Worth noting: The bootflag is shikigva, not shikivga
  5. Oh ok, thank you. I actually already had that kext installed, was not aware they did the same thing. Thanks!
  6. Same problem here. I was reading some others that had the same issue on another forum were able to solve it by changing the SMBios, I'm hoping there's another solution because last time I did that I had to re-register a bunch of my software and my rig is working fine otherwise on 10.14.4. I assume it has something to do with the hardware decoding changes made to AMD cards. If I find a solution I'll report back here.
  7. jamiethemorris

    Mac'os Mojave 10.14.5 is OuT

    Anyone found another solution to the iTunes crashes besides changing the SMBios or know what actually causes that issue? Currently on MacPro6,1.
  8. jamiethemorris

    KernelAndKextPatches 10.13x,10.14.x,10.15.x X99

    What is the xcpm_bootstrap patch for? Is it still useful necessary? My X99 wouldn't boot with it enabled after the 10.14.5 update (Thank you pitrysha for your help!).
  9. Thank you for the reply, I disabled the xcpm_bootstrap kernel patch and it boots now. This is the patch in question for anyone wondering: xcpm_bootstrap © Pike R. Alpha (Haswell-E) Find: 89D804C4 3C227722 Replace: 89D804C1 3C227722 Does anyone know what this patch is actually for?
  10. jamiethemorris

    AptioMemoryFix

    Hi, I'm having a problem with my X99 build with the 10.14.5 update, which I think is related to AptioMemoryFix: https://www.insanelymac.com/forum/topic/338777-x99-classifed-update-from-10144-to-10145-stuck-on-end-randomseed/ It doesn't attempt to load the OS after it gets to "End RandomSeed." I suspect using one of the earlier AptioFix drivers would work but I would much prefer to use the newer driver. I'm not sure if there is something I need to change with my configuration or if something with the driver needs to be updated. Thank you! EDIT: Disregard, problem was related to the xcpm_bootstrap patch.
  11. Do you have a USB enclosure you can use to boot the drive externally? I had the same problem with my X99 in both later versions of High Sierra and all versions of Mojave (drives with this issue would also say "i/o error" when a usb installer was trying to locate them), and had to use this patch to get it to boot: AppleAHCI Port Find: 40600200 Replace: 00000000 Comment: fix IO error 10.14 by vit9696 Since your install has been working up to this point, I assume it's not that exact issue, but it might be a similar if something new needs to be patched in the AHCIPort kext. You could also try loading the previous version of the kext just to see if it boots.
  12. No luck after installing it from a real Mac.
  13. Hi, Tried running the update both through system prefs and the combo update and it stops right at "End RandomSeed," which I think is during the AptioMemoryFix driver initialization - doesn't attempt to actually boot the installer. I updated Clover beforehand. It looks like a memory mapping issue? But 10.14.4 and High Sierra work fine with AptioMemoryFix, so I'm not sure what would have changed. Drivers: ApfsDriverLoader, AptioMemoryFix, AudioDxe, CsmVideoDxe, DataHubDxe, FSInject, HFSPlus, NvmExpressDxe, SMCHelper Any ideas? I'm going to try the install from my Macbook and see if that does the trick.
  14. jamiethemorris

    Mac'os Mojave 10.14.5 is OuT

    Tried running the update through system prefs and it stops right at "End RandomSeed," which I think is during the aptiofix driver initialization - doesn't attempt to actually boot the installer. I updated Clover beforehand. Still boots fine into 10.14.4 on the same drive. Any suggestions? Should I just do the combo update? Edit: Specs are EVGA X99 Classified, 5960x, RX 590. Drivers: ApfsDriverLoader, AptioMemoryFix, AudioDxe, CsmVideoDxe, DataHubDxe, FSInject, HFSPlus, NvmExpressDxe, SMCHelper Edit 2: Tried the combo update, same issue.
  15. Hi guys, I'm kind of running out of ideas here. I've got a EVGA X99 Classified/5960x/GTX 980 build that's been stable on El Capitan for a few years now and I'm trying to test a fresh install of 10.12.6 on a separate drive. The installation was done from a real Mac and the Nvidia Web drivers are already installed. It typically freezes somewhere around "HID: Legacy Shim 2" which I'm guessing doesn't have any relevance to the actual issue. Sometimes I'll see a few more messages but it's typically right around there. I think it has something to do with USB? USB3 is disabled in the BIOS. Kexts being used (injected by Clover): FakeSMC (no plugins right now), Lilu, NullCPUPowerManagement, NvidiaGraphicsFixup, VoodooTSCSync (IOCPUNumber set to 15). Attached are my config and panic report. Panic report lists AppleUSBStorageCoexistentDriver as the last loaded kext. Panic photos: https://www.dropbox.com/s/mwqvqro4jio5ue0/jamiethemorris_panic1.jpeg?dl=0 https://www.dropbox.com/s/oq4u2moebw2xob6/jamiethemorris_panic2.jpeg?dl=0 P.S. I know my SMBIOS choice and lack of power management are not ideal but it's been working fine since Yosemite so I would think I'd be able to get it working on Sierra. Thank you in advance! config_Sierra.plist jamiethemorisX99_Panic_Mar11.txt EDIT: For whatever it's worth, on my El Capitan installation, these lines are right before the desktop appears - maybe it's graphics related? I tried booting with nv_disable=1 before but it didn't seem to make a difference.
×