Jump to content
theconnactic

iCloud for AMD hackintoshes: a workaround.

71 posts in this topic

Recommended Posts

THE BEGINNING

 

As you folks can see in my signature, i'm an AMD hackintosher. That means that, some time in the past, i have the clever idea to invest some money on a cheap piece of hardware that nonetheless gave me lots of computational happiness, with (most of the times) little or no less performance compared to my friends' much pricier intel rigs, especially in day-to-day tasks. That means, unfortunately, that my times of hackintoshing have been giving me equal doses of fun and frustration, and all fun comes exclusively from OSX.

 

Everyone who frequently reads OSX86 forums know by now that AMD machines are at the bottom of the chain food in the mackintosh world. OSX running on AMD could be already a dead subject, if there wasn't very skilled people working very hard (Q: Wanna know what "hard" means? Write an on-the-fly sse3 emulator!) for it to be possible.

 

However, even with the talent and industriousness of those pro-AMD good people, well... sometimes the road comes to a dead end and that was kind of the case: the seventh iteration of OSX, Lion, added a new CPU instruction to the recipe, the ssse3 (believe, my friends, it is not just sse3 with one more "s"). This, by itself, put every AMD CPU but the newest ones, called Bulldozers or FX-Series, out of the party. Or that could have been the case, if we AMD user weren't so stubborn.

 

Slowly, heterodox solutions popped here and there to make Lion roar on AMD machines. Better saying, almost like that: running strictly 32-bit, even on the Bulldozer machines, without support to many cool features like iCloud (Oops, i say it!) or even the stock Finder, this Lion err... Meows. So that was the situation. While Intel users lived in the safe and confortable Palaces of Vanilla, we're from AMD side were left behind in the Wild Land of Doing It Ourselves.

 

INTO THE WILD

 

The famed and almost universally accepted theories of Charles Darwin, the Theory of Evolution of The Species and of natural selection proposes that, in the nature, only the fit survive and procreate. No, maybe that's what people usually think that Darwin stated, but anyway: the fact that we AMD hackintoshers have almost no support to make our machines work with the beloved OSX, except for a few good souls and great minds that develops cool things to support our hardware, this fact made us to either give up or read a lot and learn a lot: an authentic process of selection similar to the one that suposedly made the bacteria turn to plants, then to plants, than to, than to.

 

There are people at the Intel side of the mountain that cannot tell the user library from the system one, and lots of them had built their machines using that uni and multi pets. That is neither bias, nor intends to be an insult out of pure envy (but i concede that the envy exists indeed, at least inside me): the AMD users that were lazy, incompatible with computers or just wanted something to work effortlessly so they could work hard on anything else, these now are either using Windows again, changed to Intel or (the more intelligent choice) bought a Mac.

 

Indeed, a couple of months after the first useful AMD kernel for OSX Lion came out, a guy whose nickname is RAWX86 developed a kernel which made possible (for Bulldozer CPUs only, that's it) run Lion flawlessly, with 64-bit app support and all the small things. All the small things except the cloud-related ones. As always with AMD, with success comes frustration.

 

INTERLUDE

 

Besides my AMD desktop computer, i own a small and cheap Asus netbook, as you can also see in my signature. Like AMD, its Intel Atom CPU is not natively compatible with OSX and, even being supported for a while during the early Snow Leopard times, it's not any longer, and cannot run the vanilla kernel.

 

However, Intel is Intel and, when coupled with OSX, the happy ending can sometimes be troublesome to achieve, but is as certain as the success of a new Apple device: the patches work somewhat better, since the CPU supports the same instructions of all modern Intel processors, and has a very closely related architectural design.

 

Therefore, my little Asus can run versions of OSX as new as the last one, Mountain Lion 10.8.1. But not without its measure of woes: it was a real pain to get iCloud, FaceTime and other cloud features to work. Indeed, it ain't easy for anyone that runs a hackintosh and some indispensable steps must be accomplished for these features to be used:

 

1) You ought have a built-in ethernet working properly. I'm not saying just using the famed Chamaelon boot flag "EthernetBuiltIn=Yes". This, buddy, is not enough: you have to effectively configure your hardware so your LAN card is properly recognized by the OS, with a corrected kext loaded to it and assigned to the network interface assigned to en0. Do your homework!

 

That, alone, solve all App Store and iTunes Store issues, even for AMD hacks.

 

2) You must get a valid serial number, so the Apple servers think they're talking with a real Mac. Do you really thought the Cupertino Colossus wouldn't have its beautiful paradisiac garden just without any fences? But you can dodge them using a very cool app called Chamaleon Wizard - google is your friend! - to generate a file called smbios with a (hopefully) valid serial number. This, along the first step, should be enough for everyone to have the full array of Apple cloud features.

 

But is not. It was not enough for me and my little Atom CPU (speed-wise, it should be called Animal Traction, but does not matter, i love it, specially because it was very pocket-friendly). It was not enough for my AMD computer also, but let's left it aside for a while. I, frustrated and a little amused by the difficulty (remember that talk of natural selection) resorted to various additional, some of them quite unorthodox, like trying various versions of symbioses and an obscure method i found at a thread in Tonymac's, of getting a supposedly valid UUID (take a look: http://www.famkruith...et/uuid/uuidgen).

 

Not needed to say, nothing worked.

 

THE REAL CAGE OF THE LION

 

Most people that posts in OSX86 forums know meklort, right? Should exchange some words with him: the guy is a genius. He, alone, solved the iCloud issue for almost every Atom OSX computer. At least in Mountain Lion: i don't know if he's done something about it for Lion. Theoretically, it should work. He addressed the problem with a single and very reasonable insight: why apple should give all of the amazing features of OSX out with the open-source XNU kernel? Nah, it could be that way. Something will be missing, precisely that something that, among other things, makes iCloud and related goodies tick.

 

So he came out with his own patched kernel for 10.8: https://dl.dropbox.com/u/863180/kern...ocache.patched (if you have 10.8.1, try this one: mach_kernel_Atom 10.8.1(dev).zip). The patches weren't apllied to the source of the open-source XNU; instead, they were binary patches. And, pure magic, all started to shine: iCloud, FaceTime, iMessages, GameCenter. Pure joy. Of course they wouldn't have worked, the kernels, without following the steps mentioned before. Again, you have to do your homework!

 

Would his method work on AMD machines? Of course, meklort told me: once someone writes correctly the patches for AMD CPUs, they could with all certainty be applied as binary patches and should work. I guess it's not an easy task, tough - i, certainly, don't have the skill to do it, and no one showed up with something like that even until now.

 

But i was not prepared to give up yet!

 

MY WORKAROUND TO GET ICLOUD TO WORK ON MY AMD MACHINE

 

Are you still reading?

 

Good! You're a pure breed AMD hackintosher, not some uni/multipuppy lazy guy (okay, call me envious, and no offense at all to the puppies owners, they're great tools to get the work done).

 

Why did i talk so much about my atom experiences? Because from them, i learned enough to establish a realistic assessment of the facts, which are the following:

 

- On contrary of what most people think, these iCloud, FaceTime etc issues are indeed somewhat kernel related. Recently, i decided to reformat the disk of my netbook, erasing all partitions and letting only OSX installed. The problem was OSX wasn't in the first partition, so i decided to reinstall and restore my system from a time machine back up. I when i finished, i tried to do a call using FaceTime and, surprise!, it didn't let me log in. I forgot to put meklort's kernel back. When i did it, reboot and all went back to normal;

 

- I have to follow closely and carefully the basic steps of getting Apple's web-based services working; kernel tricks wouldn't suffice to achieve success;

 

- The critical moment for iCloud to work is not the log in, is the first log in. Is not without reason that Apple instructs you to set up iCloud, not just "sign up and sign in" like the way of the App Store. In that critical moment, something in your system files are optimized and changed, so Apple can offer you a better and more customized service. At this very moment, your computer is also checked if it's a genuine Apple-branded computer, not some fake thing. The evidence (circumstantial, i confess) is that my netbook is always "signed in" iCloud, even when it's offline (of course, in this case no data is exchanged, but it stays logged in anyway, because it's not really a log in).

 

Once we make through the first set up, i thought, we shouldn't bother anymore with kernels, serials and everything. But how to set up for the very first time, if our patched kernel is refused altogether?

 

That was the way i achieved that, and i can bet that will work for everyone. You'll have to use your friend's Mac/Intel hack/Atom hack with working iCloud, and will need a working network between it and your own computer. I assume you already followed the basic steps for Apple's web services and features:

 

1) On the Mac/Intel hack/Atom hack, create a new user account;

 

2) Set up iCloud for this user account;

 

3) Log both this computer and your computer at the same network;

 

4) Start the migration assistant (/Applications/ Utilities/ Migration Assistant) in your computer. When prompted to chose which kind of migration, chose "from a Mac";

 

5) Since both computers are in the same network, you should see the other computer, select it;

 

6) Start the migration assistant in the Mac/Intel hack/Atom hack. When prompted to chose which kind of migration, chose "to a Mac";

 

7) Select your computer from the Mac/Intel hack/Atom hack;

 

8) A passcode will appear on your computer; check the Mac/Intel hack/Atom hack, will appear there too. If they match, hit continue;

 

9) When prompted to chose which files to migrate from the Mac/Intel hack/Atom hack, select under "users" the user you just created to set iCloud, and select "settings";

 

10) When it ends, congratulations: you have iCloud working on your AMD hackintosh, like i do. Reboot it, and don't forget to erase the user account you created in your friend's computer.

 

Attention!

 

The method works for iCloud, but not for FaceTime!

 

Apparently, FaceTime does make a live login every time, and every time the kernel is checked. Why am i saying that? First of all, it doesn't work in my AMD. Second, remember when i formatted my Atom netbook and forgot to change the kernel? FaceTime (and Messages also) would not connect. But my iCloud account, previously set up, was working flawlessly. If someone gets a workaround for it, post here.

Share this post


Link to post
Share on other sites
Advertisement

Alternative methods: if you have a spare hard disk, or have the possibility of take your own HD out of your computer (desktops only!), and have your own/your friend's intel machine available, you can follow the previous steps before the step 1) (notice they're harder than the proposed one, since you're going to boot in another hardware environment and it could not be possible, with the caveat, depending on the method you use, that you screw your own system):

 

a ) install OSX on your HD (if you take your own OSX HD to do it, simply boot it with the vanilla kernel - you remembered to make a back up of it, right?), create an user account (use your own in your system HD) and follow all the interlude steps. Then set up iCloud, disconnect the HD, connect to your own PC (if you used your main HD, remember to boot with the correct kernel);

 

b ) proceed to step 1) of the workaround.

 

APPENDIX 1: if you have a Mac or a iCloud enabled hack, and a spare HD, or can use your main HD to do it, you simply do a CCC/SuperDuper cloning, connect the HD to the AMD Machine, boot with the correct AMD Kernel and proceed to the interlude steps.

 

APPENDIX 2: If your Intel machine or the Intel machine you're using to perform alternative method a) is already a hack with fully working iCloud, you can simply migrate the user (if the machine is of somebody else, you'll have to create one and set up your own iCloud first) to your own connected HD after install OSX on it (if you bring up your own main HD, you don't need to instal OSX, of course :)).

Share this post


Link to post
Share on other sites

Hey theconnatic, couple quick questions for you in regards to setting up iCloud:

 

1. Can this be achieved using OSX set up in a virtual box?

2. Would this work if the account created on the intel Hack is running Mountain Lion, and my AMD machine is running Lion?

Share this post


Link to post
Share on other sites

Basically, I've been trying to Hackintosh every Intel PC in the house for the last couple days (3 of 'em) with no luck (I think my spare hard drive is shot), and I figured a virtual box would be easier to set up on an existing Windows 8 install than trying to fully hackintosh the machines. So the machine from where I want to import the account from.

Share this post


Link to post
Share on other sites

Honestly, i tried only once: it didn't work, i gave up. Let me now if they (FaceTime and iMessage) work for you, though.

 

No iMessage for Lion, but I'll definitely test FaceTime. Waiting for a day off so I can bring my desktop to a buddy's house. The {censored} has an i5 and a setup that works like a dream lol

 

***EDIT*** I got one of the intel machines in the house Hac'd! Merging accounts as we speak, I'll let you know how it goes, and how FaceTime works out.

Share this post


Link to post
Share on other sites

Can someone confirm that the migration takes a long time to transfer the settings? I selected just a few and i'm thinkin its stucked. Just don't want to cancel it and it seems that i don't have this option i'll need to force close it :wacko:

 

Edit:

 

Well, i force closed the process on both computers, log out on the amd hackintosh and Boom Shakalaka! The new account was there with full iCloud Support, thanks for the workaround theconnactic.

Edited by juliomoreira

Share this post


Link to post
Share on other sites

Can someone confirm that the migration takes a long time to transfer the settings? I selected just a few and i'm thinkin its stucked. Just don't want to cancel it and it seems that i don't have this option i'll need to force close it :wacko:

 

Edit:

 

Well, i force closed the process on both computers, log out on the amd hackintosh and Boom Shakalaka! The new account was there with full iCloud Support, thanks for the workaround theconnactic.

 

Where did yours get stuck at? I left mine running about six hours ago and just got home to find it still sitting on ten minutes remaining.. I wanna cancel it but I don't want to start all over again if I don't have to...

Share this post


Link to post
Share on other sites

 

 

Where did yours get stuck at? I left mine running about six hours ago and just got home to find it still sitting on ten minutes remaining.. I wanna cancel it but I don't want to start all over again if I don't have to...

 

I cannot remember exactly, but i think was on "less than one minute remaining" so i felt safe to close it, just clicked the close button... I guess six hours is enough time to it, even with low rate transfer it shouldnt take too long, so i think you should close. If it didnt work, try migrating only the settings for the new user and dont select anything else...

 

Edit:

 

Just to clarify it if you ended up well, find my mac will only "work" if you have a recovery partition, wich as i know can only be achieved using an script to create it, as it is only created with standard installation in real macs.

Edited by juliomoreira

Share this post


Link to post
Share on other sites

Ok so I went ahead and closed it out, the account wasn't transferred successfully. So, I got smart and moved my desktop into the front office where the other Hack is plugged into the modem directly. With both Hacks on plugged into the same box, the transfer took less than thirty seconds and is working perfectly!

 

@theconnatic I can confirm FaceTime doesn't work still. When I launched it, it said FaceTime is off, so I switched it on and tried to sign in, and it was not able to verify. Not too big of a deal, as I usually FaceTime from my iPhone anyways. Just wanted to see if it would work!

 

Thanks again for the guide! Worked like a charm :)

Share this post


Link to post
Share on other sites

Mountain Lion users: GameCenter.app works flawlessly here, but i don't know if it was actually working before the workaround was applied. Can someone who didn't apply it yet confirm if it does or doesn't work without the fix? Thank you.

 

All the best!

Share this post


Link to post
Share on other sites
Mountain Lion users: GameCenter.app works flawlessly here, but i don't know if it was actually working before the workaround was applied. Can someone who didn't apply it yet confirm if it does or doesn't work without the fix? Thank you.

 

All the best!

 

If i get the time needed i'll do a clean install and report it back ;)

Share this post


Link to post
Share on other sites

Mountain Lion users: GameCenter.app works flawlessly here, but i don't know if it was actually working before the workaround was applied. Can someone who didn't apply it yet confirm if it does or doesn't work without the fix? Thank you.

 

All the best!

 

Soon as the kernel gets fixed for graphics corruption I'll be back to testing Mountain Lion... For now, I'm staying on Lion :)

Share this post


Link to post
Share on other sites

Hey guys, as i've promised did a clean 10.8 install today and i can confirm it does not inherited the icloud problems. The only custom kexts it loaded was chameleon default fakesmc and the one for my atheros integrated ethernet beside that and the safeboot -x bootflag nothing was changed so i think we can assume that Game Center works OOB with latest ANV kernel.

 

Cheers...

Share this post


Link to post
Share on other sites

Just for curiosity i tried to import a user that was imported from a real mac to a mountain lion installation on another partition to my current lion installation, the workaround seems to work as well but for some reason even with the applications folder unselected it messed up some stock applications such as calendar and mail. But again, this workaround works even from another system version, in this case from 10.8.3 to 10.7.5.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By D3s0lat0r
      Greetings to the Forum,
      i recently followed a guide on hackintosh,and also i am complete noob in this field.
      all is working great, as i am using macpeets codec with layout id=18 cause i like to manually switch to my headphones.
      only one thing doesnt work and its my mic. I tried all the layout ids but no luck.
      i am using ASROCK Fatal1ty b450 k4 with amd r5 2600.
      wich has alc 892.
      Can you please help me? Thank you very much
    • By BlitzPanzer
      Catalina 10.15.3, OC 0.5.5

      Follow the OpenCore AMD Vanilla Guide, everything works fine iMessage, Siri, FaceTime, Continuity, Airdrop, Audio, WiFi
      But here is the problem
      Once I restart or shutdown and reboot, I will have kernel panic, so i have to reboot once again, then no more kernel panic, straight back to the system.
      Down below are the 3 kernel panic reports I got after I am back to the system, also provided specs, kexts, drivers and config.plist I used.
      Please someone help me with the problem
      Thanks in advanced   

      System Specs
      CPU: Ryzen R5 3600
      MOBO: MSI B450 Mortar Max
      RAM: Kingston HyperX Fury 16GB*2 3200MHz DDR4
      SSD: Kingston A2000 500GB NVMe PCIe
      GPU: Gigabyte RX 570 Gaming 4G v2.0
      PCIe: BCM943602CS Kexts:
      AppleALC
      AppleMCEReporterDisabler
      BrcmBluetoothInjector
      BrcmPatchRAM3
      HDMIAudio
      Lilu
      MacProMemoryNotificationDisabler
      NightShiftUnlocker
      NVMeFix
      RealtekRTL8111
      VirtualSMC
      WhateverGreen Drivers:
      ApfsDriverLoader
      AppleUsbKbDxe
      FwRuntimeServices
      VBoxHfs config.plist:
      https://drive.google.com/file/d/1M22Tvn7W-Zf_b_-J52oLcfjECj5qAcp6/view

      Kernel Panic Report 1
      panic(cpu 0 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9f212fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffffa3ce87c000, CR3: 0x00000000263ba000, CR4: 0x00000000003406e0 RAX: 0xffffffa3ce87c000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffffa3ce75bb60, RBP: 0xffffffa3ce75bb80, RSI: 0xffffff806d3141c0, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805cc7c900, R13: 0xffffff835806f000, R14: 0x0000000000000000, R15: 0xffffff8068d2da50 RFL: 0x0000000000010246, RIP: 0xffffff7f9f212fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffffa3ce87c000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffffa3ce75b5c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffffa3ce75b610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffffa3ce75b650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffffa3ce75b6a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75b6c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffffa3ce75b7c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffffa3ce75b810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffffa3ce75b880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffffa3ce75ba00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffffa3ce75ba50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75ba70 : 0xffffff7f9f212fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffffa3ce75bb80 : 0xffffff7f9f24a795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffffa3ce75bba0 : 0xffffff7f9f212ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffffa3ce75bbe0 : 0xffffff7f9f2325c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffffa3ce75bc30 : 0xffffff7f9f1b8adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffffa3ce75bc70 : 0xffffff7f9f1b64be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffffa3ce75bd00 : 0xffffff7f9f128534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffffa3ce75bd80 : 0xffffff7f9f1b488e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffffa3ce75bde0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffffa3ce75be40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffffa3ce75bef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffffa3ce75bf50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffffa3ce75bfa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000->0xffffff7f9f1b2fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c185000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c228000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9f1b3000->0xffffff7f9f6f7fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 47565362999  
      Kernel Panic Report 2
      panic(cpu 10 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9e629fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d25d2000, CR3: 0x0000000029068000, CR4: 0x00000000003406e0 RAX: 0xffffff83d25d2000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d14c3b60, RBP: 0xffffff83d14c3b80, RSI: 0xffffff805f6adb80, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805fba2580, R13: 0xffffff835b02e000, R14: 0x0000000000000000, R15: 0xffffff80631191e0 RFL: 0x0000000000010246, RIP: 0xffffff7f9e629fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff83d25d2000, Error code: 0x0000000000000002, Fault CPU: 0xa, PL: 0, VF: 1 Backtrace (CPU 10), Frame : Return Address 0xffffff83d14c35c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d14c3610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d14c3650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d14c36a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c36c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d14c37c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d14c3810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffff83d14c3880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d14c3a00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d14c3a50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c3a70 : 0xffffff7f9e629fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d14c3b80 : 0xffffff7f9e661795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d14c3ba0 : 0xffffff7f9e629ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d14c3be0 : 0xffffff7f9e6495c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d14c3c30 : 0xffffff7f9e5cfadb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d14c3c70 : 0xffffff7f9e5cd4be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d14c3d00 : 0xffffff7f9e52a534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d14c3d80 : 0xffffff7f9e5cb88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d14c3de0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d14c3e40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d14c3ef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d14c3f50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d14c3fa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000->0xffffff7f9e5b5fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c3f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c09f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9e5ca000->0xffffff7f9eb0efff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 38416992755  
      Kernel Panic Report 3
      panic(cpu 8 caller 0xffffff801da652fa): Kernel trap at 0xffffff7fa084dfe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d44cd000, CR3: 0x000000002b260000, CR4: 0x00000000003406e0 RAX: 0xffffff83d44cd000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d319bb60, RBP: 0xffffff83d319bb80, RSI: 0xffffff8066659c00, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff8061f35280, R13: 0xffffff835d231000, R14: 0x0000000000000000, R15: 0xffffff806189db90 RFL: 0x0000000000010246, RIP: 0xffffff7fa084dfe3, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0xffffff83d44cd000, Error code: 0x0000000000000002, Fault CPU: 0x8, PL: 0, VF: 1 Backtrace (CPU 8), Frame : Return Address 0xffffff83d319b5c0 : 0xffffff801d93bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d319b610 : 0xffffff801da734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d319b650 : 0xffffff801da64f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d319b6a0 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319b6c0 : 0xffffff801d93b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d319b7c0 : 0xffffff801d93b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d319b810 : 0xffffff801e0d2aa9 mach_kernel : _panic + 0x61 0xffffff83d319b880 : 0xffffff801da652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d319ba00 : 0xffffff801da64ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d319ba50 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319ba70 : 0xffffff7fa084dfe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d319bb80 : 0xffffff7fa0885795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d319bba0 : 0xffffff7fa084def0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d319bbe0 : 0xffffff7fa086d5c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d319bc30 : 0xffffff7fa07f3adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d319bc70 : 0xffffff7fa07f14be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d319bd00 : 0xffffff7fa074e534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d319bd80 : 0xffffff7fa07ef88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d319bde0 : 0xffffff801e01b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d319be40 : 0xffffff801e01adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d319bef0 : 0xffffff801e01a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d319bf50 : 0xffffff801e01c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d319bfa0 : 0xffffff801d8e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000->0xffffff7fa07d9fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9e5f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9e29f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7fa07ee000->0xffffff7fa0d32fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001d600000 Kernel text base: 0xffffff801d800000 __HIB text base: 0xffffff801d700000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 27776834167  
      config.plist
    • By NoEnd
      Hi team,
       
      I'm looking for the best route to achieve this upgrade, so I have been stuck with HS since Nvidia drivers stopped being supported on newer MacOS releases. Now I'm having an AMD 5700 xt on the way and want to plan the upgrade properly. I have added some information below and questions that might help with your recommendation.
       
      Current GPU 1080 ti with Nvidia webdrivers installed. So should I uninstall the webdriver before adding the new GPU? Clover is being used and EFI attached. Any kext must be removed? or parameters adjusted MacOS HS 10.13.6, should I upgrade before using the new GPU? CPU: 9900K Motherboard:ROG MAXIMUS XI HERO (WI-FI) Dual Monitors I have a Time machine backup, Do you recommend a fresh install? and If I did, will I be able to restore my data/apps as-is?  
      Please let yourself free to explore further aspects to considers.
      EFI-20200204.zip
    • By neoskateur
      Hello team!

      I have a small issue wiith my RX580 MSI on High Sierra, only one DP is working, no hdmi... Any clue?

      Supermicro X8DTL-6F
      2 x Xeon X5650
      RX580 MSI
×