Jump to content

DaGr8Gatzby

Members
  • Content count

    49
  • Joined

  • Last visited

About DaGr8Gatzby

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,220 profile views
  1. Just to bump this thread, I was able to get Mojave up and running but it took quite some work. I had to do the following: 1. Fix my broken Arch install (glibc fail with Pacman) 2. Compile a custom version of qemu (checked out tag v2.12.0) 3. Compiled a custom OVMF with EPT Read Only tables disabled. I had to reach out for a patch on this code. Patch worked. 4. Install Mojave as usual. I am not redirecting graphics as I intend to do some kernel debugging work and it is not needed. However, redirecting should work fine as usual. Latest clover works.
  2. I believe this is what is preventing iMessage from working. Glad I am not the only one that has come to this conclusion. Let's get this more visibility. These variables are in various Frameworks. Can you do the following to get a list? I'll do this when I get home. egrep -Ria "Gq3489ugfi|Fyp98tpgj|kbjfrfpoJU|oycqAZloTNDm|abKPld1EcMni" /System/Library Let's start getting a list. Possible kernel calls to these processes are not generating values. I do not believe nvram command will insert these. There are located in IOPower plane as well, which I believe are mirror copies of IODeviceTree entries. Not certain. Let's hack.
  3. DaGr8Gatzby

    Ryzen 5 1600 and Asrock AB350 Pro4

    Are you saying you were able to get iMessage to work? I have a vested interest in this as I am not able to get my iMessage to connect . Facetime working as well?
  4. We need to get some serious resources devoted to getting iMessage to work. Shaneee, as always, great work man! Does your kernel work with dtrace?
  5. I get this for iMessage Debug: Model: iMac14,2 Board-id: Mac-27ADBB7B4CEE8E61 SerialNumber: REDACTED Hardware UUID: REDACTED System-ID: REDACTED ROM: REDACTED BoardSerialNumber: REDACTED Gq3489ugfi: failed Fyp98tpgj: failed kbjfrfpoJU: failed oycqAZloTNDm: failed abKPld1EcMni: failed Then Could not sign in to iMessage. Error occurred during activation. Try again.
  6. Serious question. Anyone have iMessage working?
  7. @shaneee, possible to update github with your latest? Would like to try a custom compile this holiday weekend. Also, would anyone be adverse to centrally hosting compiled kernels for testing? Thanks!
  8. All, I don't want to derail this thread. I feel like I've been alienating a lot of people actually. Is there anyway we can get a kernel compilation tutorial with all code fixes going on Github? I don't know if this is against policy so I'll leave it to the mods to figure out. However, it would be nice if we had a centralized location with bug fixes that we can just run git clone on, compile, and then test. I'm very interested in getting Ryzen working smoothy. Please feel free to PM me on this matter if you would like to take this offline. Bronya/Shanee/Gigamaxx have done a great job, as well as all the of the other devs who have made the tools for facilitating this. Thanks goes out to all of them. It's time we take some of the load off of them.
  9. I will try this today when I get home. I did notice that if I open Photo booth, I need to disconnect/reconnect my camera, but facetime does seem to work seamlessly with this. I've relocated my USB hub to the USB 3.0 port I have and it seems to have to gotten around the issue. My USB Audio is still flaky, but input works from the camera. Noted --- Dual Boot Win10/Sierra 10.12.6 ASRock AB350M‑HDV Samsung Pro 960 - 512 GB
  10. did not work. Did a fresh install to ensure we were good. Ran USB fix. Nothing. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <dict> <key>ATI</key> <false/> <key>Firewire</key> <false/> <key>HDA</key> <false/> <key>HDMI</key> <false/> <key>IDE</key> <false/> <key>IntelGFX</key> <false/> <key>LAN</key> <false/> <key>LPC</key> <false/> <key>NVidia</key> <false/> <key>SATA</key> <false/> <key>SmBUS</key> <false/> <key>USB</key> <true/> <key>WIFI</key> <false/> </dict> </dict> <key>SSDT</key> <dict> <key>DropOem</key> <false/> <key>Generate</key> <dict> <key>CStates</key> <false/> <key>PStates</key> <false/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>-v npci=0x3000 nvda_drv=1 kext-dev-mode=1 debug=0x100 busratio=36 USBBusFix=Yes</string> <key>Debug</key> <false/> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Legacy</key> <string>LegacyBiosDefault</string> <key>Secure</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <string>Yes</string> </dict> <key>CPU</key> <dict> <key>UseARTFrequency</key> <false/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <string>Detect</string> <key>ResetHDA</key> <true/> </dict> <key>FakeID</key> <dict> <key>ATI</key> <string>0x0</string> <key>IMEI</key> <string>0x0</string> <key>IntelGFX</key> <string>0x0</string> <key>LAN</key> <string>0x0</string> <key>NVidia</key> <string>0x0</string> <key>SATA</key> <string>0x0</string> <key>WIFI</key> <string>0x0</string> <key>XHCI</key> <string>0x0</string> </dict> <key>USB</key> <dict> <key>FixOwnership</key> <false/> <key>Inject</key> <false/> </dict> </dict> <key>DisableDrivers</key> <array> <string>Nothing</string> </array> <key>GUI</key> <dict> <key>ConsoleMode</key> <string>Max</string> <key>Hide</key> <array> <string>Recovery HD</string> </array> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <true/> <key>Mirror</key> <false/> <key>Speed</key> <integer>8</integer> </dict> <key>ScreenResolution</key> <string>2560x2048</string> <key>Theme</key> <string>embedded</string> </dict> <key>Graphics</key> <dict> <key>FBName</key> <string>Futomaki</string> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>NvidiaSingle</key> <false/> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleIntelCPUPM</key> <false/> <key>AppleRTC</key> <true/> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>KernelHaswellE</key> <false/> <key>KernelLapic</key> <false/> <key>KernelPm</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>IONVMeFamily IONameMatch</string> <key>Disabled</key> <false/> <key>Find</key> <data> PHN0cmluZz5wY2kxNDRkLGE4MDQ8L3N0cmluZz4= </data> <key>InfoPlistPatch</key> <true/> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> PHN0cmluZz5wY2kxNDRkLGE4MDI8L3N0cmluZz4= </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#1</string> <key>Disabled</key> <false/> <key>Find</key> <data> ibPoAgAAweAMBQAQAACJgw== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> ibPoAgAAweAJBQAQAACJgw== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#2</string> <key>Disabled</key> <false/> <key>Find</key> <data> D7aMiIIAAACD+QwPhTIBAA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> D7aMiIIAAACD+QkPhTIBAA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#3</string> <key>Disabled</key> <false/> <key>Find</key> <data> AMeDpAAAAAAQAABIi0gISA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> AMeDpAAAAAACAABIi0gISA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#4</string> <key>Disabled</key> <false/> <key>Find</key> <data> SYnGTYX2dGFBwecMSWP/vg== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> SYnGTYX2dGFBwecJSWP/vg== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#5</string> <key>Disabled</key> <false/> <key>Find</key> <data> hv8PAABIwegMD7cPgeH/Dw== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> hv8PAABIwegJD7cPgeH/Dw== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#6_7</string> <key>Disabled</key> <false/> <key>Find</key> <data> icGB4f8PAABIAdFIgfn/DwAAdzs= </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> icGB4f8BAABIAdFIgfn/AQAAdzs= </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#8</string> <key>Disabled</key> <false/> <key>Find</key> <data> SYHF/w8AAEnB7QxJiwQkSA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> SYHF/w8AAEnB7QlJiwQkSA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#9_10</string> <key>Disabled</key> <false/> <key>Find</key> <data> BgIAAEyNuAAQAABMiflIgeEA8P//SYmGGgEAAEmJjiIB AABBvAAQAABJKfQ= </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> BgIAAEyNuAACAABMiflIgeEA8P//SYmGGgEAAEmJjiIB AABBvAACAABJKfQ= </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#11</string> <key>Disabled</key> <false/> <key>Find</key> <data> AABJiY4iAQAAugAQAABIKQ== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> AABJiY4iAQAAugACAABIKQ== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#12</string> <key>Disabled</key> <false/> <key>Find</key> <data> yAAAAEkp17gAEAAATYskJA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> yAAAAEkp17gAAgAATYskJA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#13</string> <key>Disabled</key> <false/> <key>Find</key> <data> 4b+AQBUGTYnWugAQAABFMQ== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> 4b+AQBUGTYnWugACAABFMQ== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#14</string> <key>Disabled</key> <false/> <key>Find</key> <data> iWTY+EmBxAAQAABJgccA8A== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> iWTY+EmBxAACAABJgccA8A== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#15</string> <key>Disabled</key> <false/> <key>Find</key> <data> Bf8PAABIwegMZvfB/w8PlQ== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> Bf8PAABIwegJZvfB/w8PlQ== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#16</string> <key>Disabled</key> <false/> <key>Find</key> <data> weIIQQ+2wcHgDEQJ0EQJwA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> weIIQQ+2wcHgCUQJ0EQJwA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#17</string> <key>Disabled</key> <false/> <key>Find</key> <data> RYTJD5XAD7bAweAMRAnYRA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> RYTJD5XAD7bAweAJRAnYRA== </data> </dict> <dict> <key>Comment</key> <string>change 15 port limit to 26 in XHCI kext (100-series)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g72M/v//EA== </data> <key>Name</key> <string>AppleUSBXHCIPCI</string> <key>Replace</key> <data> g72M/v//Gw== </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>MLB</key> <string>C02K1JM0F693FE</string> <key>ROM</key> <data> APtUC4oE </data> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>08/08/2017</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>IM142.88Z.0122.B00.1708080739</string> <key>Board-ID</key> <string>Mac-27ADBB7B4CEE8E61</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardSerialNumber</key> <string>D25431902OPF64VFB</string> <key>BoardType</key> <integer>10</integer> <key>BoardVersion</key> <string>iMac14,2</string> <key>ChassisAssetTag</key> <string>iMac-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>0x0D</string> <key>Family</key> <string>iMac</string> <key>FirmwareFeatures</key> <string>0xE00FE137</string> <key>FirmwareFeaturesMask</key> <string>0xFF1FFF3F</string> <key>LocationInChassis</key> <string>Part Component</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <false/> <key>PlatformFeature</key> <string>0x01</string> <key>ProductName</key> <string>iMac14,2</string> <key>SerialNumber</key> <string>D25N52IHF8JC</string> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>CustomUUID</key> <string>CC8DEDB5-B109-46DD-8C58-292970203AEB</string> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist>
  11. Tried this on my Ryzen 1700. Timer is too fast. Videos play like I have FFx10 on them. No sound from USB.. Boots to desktop though.
  12. Quick question, how do I test this kernel? Every time I've placed a new kernel in here, I am unable to recreate prelinked, so I kill my system.
  13. Anyone having problems with USB ports? I ran Shanee fixUsb script and it appeared that it populated USB information under System Report. I plugged in my Logitech C920, the entry updates, but for some reason, it doesn't come on. Same issue if I Plug a USB drive in. No detection of the drive done. I have a USB 2.0 HUB and my peripherals connected via that HUB work.
  14. DaGr8Gatzby

    Ryzen Clover Installation Guide macOS Sierra

    Quick question: I had problems with Nvidia drivers previously on my virtual machine. It required a recompile of Clover due to FSB parameter being ignored. Has anyone tried playing with FSB in clover to get Nvidia drivers up to speed? I definitely do not want to buy Vega simply for this, as I don't require it, but if it comes down to it, so be it.
  15. Hello All. I recently decided to attempt this foray into AMD Hackintoshing and ran into lots of snags. Fortunately, I ran into a lot of similar issues as I did have a KVM virtual machine install of Sierra with hardware redirection as my daily driver, so I was used to the headaches My installation method differed just a bit. I realized a lot of problems people are having are booting into the installer. I decided to forego all of this and go via an alternate installation method. Lots of people are saying to perform an install with an SSD and then just insert it into your machine. However, I only have an NVMe Samsung Pro 960 so my options were a bit limited. Here is the installation method I performed: 1. As a proof of concept, I decided to perform a target install of Sierra on a USB drive. I have a 12 inch macbook I can use to achieve this, but this can also be done via VMWare as long as you are writing to USB. 2. Ensure USB drive is bootable by holding down option, and selecting Name of macOS install that resides on external drive. Once you have confirmed you can boot on regular intel hardware, move on. 3. Boot into your normal environment (intel/VM) and run RyzenPatcher python script and specify the USB drive as the target volume. 4. Install clover on ESP/EFI partition of USB drive and replace with the clover distribution that is provided in USB Installer file in gigamaxx's tutorial 5. Insert USB drive into Ryzen box, and boot clover from USB Drive. If it detects the macOS install on your USB Stick, it should boot. 6. Select macOS install on the USB drive. 7. Ensure desktop fully initializes. If you can use the install on the USB drive, then your proof of concept is complete. I used this as a live CD environment to get Sierra install complete on my NVMe drive. ----- These steps were done after I confirmed my USB drive live environment worked: 8. Grabbed all kexts to ensure my hardware was fully accounted for. I placed all in S/L/E and ran kext wizard/repaired perms. I was able to get my live CD environment to recognize my NVMe drive as well as my RealTek NIC. 9. Grabbed Sierra Install from App store (This may not be necessary) 10. mounted InstallESD.dmg. 11. Here is where I hit a snag. I realized that if I were to reboot and specify the target partition, it would not boot due to missing Ryzen Kernel. I realized there must be a way to simulate an OS install without actually running the installer. I looked and noticed there were 5 PKGs. I formatted the target partition on my NVMe drive (One that also houses my exFAT data and Win10 install) and did the following: installer OSInstall.mpkg --target /Volumes/TARGET_VOLUME -verbose Verbose is important as you will have no indication of what is happening. You should see the following in your prompt: Starting OSInstall #### (with repeating hash marks) Ensure this completes. This silently unpackages the files necessary for the OS to run. 12. Ran RyzenPatcher against the target partition on NVME drive. 13. Insert Ethernet/NVMe kexts on /S/L/E of Target partition. Run kext wizard. 14. Copy aMD prelinked kernel just in case and AMD kernel. 15. Reboot. I was able to do the above steps in one go entirely from my Live CD environment. I also extracted the pkgs to an exFAT data partition once my live CD found my NVMe drive. This sped up install substantially. I'm having problems with audio and slow Nvidia performance, but overall this does work.
×