Jump to content
theconnactic

Mavericks kernel testing on AMD (formerly Mountain Lion kernel testing on AMD)

6,477 posts in this topic

Recommended Posts

 

:)

 

hello spakk, 
 
why develop a kernel 13.2 beta? it would be wiser to wait for the official release 10.9.2 Maveriks to continue, beta kernel changes can still happen so the best solution may be to wait for the official version that the coders working on it.
 
the Maveriks Version 10.9.0/1 works perfectly on AMD and has nothing to envy to the vanilla version for Intel. The Haswell processors (Intel) encounter more problems than AMD CPU is a little history of the biter !   :)

 

I think you're right Gils, mavericks works very well so far on AMD processors.

I'm not quite sure if the OPCODE problem will also come in the official version too.?

 

Edit:

also mavericks 10.9.2 version 13C59 works very well with last amd kernel by Andy and sinetek but with Replace System.kext and Sandbox.kext from 10.9

Edited by spakk

Share this post


Link to post
Share on other sites
Advertisement

:)

 

profitons de nos PC AMD qui fonctionnent à merveille , même mon Sempron reprend vie sous OS X Maveriks   :) je penses que sous M 10.9.2 il fonctionnera à merveille aussi :) même un Pentium HT ne fonctionne pas aussi bien  :rolleyes:

 

enjoy our PC AMD that work wonderfully, even my life again Sempron OS X Maveriks :) I think it will work under 10.9.2 M perfectly too :) even a Pentium HT does not work as well

 

245230Capturedcran20140217020112.png

 

with small HD 5450  :D

 

257138Capturedcran20090317040113.png

 

 

948278Capturedcran20090317040305.png

 

 

 

 

http://www.youtube.com/watch?feature=player_detailpage&v=PkMWetiJCFA

Share this post


Link to post
Share on other sites

quick Q for whom have FX processors like FX 8350 

do you have any problem (Crashes or glitches or colour changes ) on any programs specially on latest  GFX programs 

as i think on upgrading cpu to FX8350

thanks :)

Share this post


Link to post
Share on other sites

quick Q for whom have FX processors like FX 8350 

do you have any problem (Crashes or glitches or colour changes ) on any programs specially on latest  GFX programs 

as i think on upgrading cpu to FX8350

thanks :)

@ Mohamed, if you want to buy a new CPU, then I would wait a little until the FX9590 is slightly cheaper, though it costs a few bucks more but then you have a super CPU :)

http://geizhals.de/amd-fx-9590-fd9590fhhkwof-a973468.html

 

I use a CPU: Phenom II X6 1100T, CPU is not overclocking.

So far I have not had a Crasch, all music and sound programs and the remaining Adobe programs run on my hardware without any problems and my graphics card works almost perfectly

 

 

FX 9590 Test

Edited by spakk

Share this post


Link to post
Share on other sites

@ Mohamed, if you want to buy a new CPU, then I would wait a little until the FX9590 is slightly cheaper, though it costs a few bucks more but then you have a super CPU :)

http://geizhals.de/amd-fx-9590-fd9590fhhkwof-a973468.html

 

I use a CPU: Phenom II X6 1100T, CPU is not overclocking.

So far I have not had a Crasch, all music and sound programs and the remaining Adobe programs run on my hardware without any problems.

the problem on final cut pro :/

and feel to some extent that cpu doesn't works with its full power because of instruction limitation

so want to update for instructions and and upgrade for performance 

about fx9590 it is too expensive now and see on power consummation  don't know if it will work normally on my motherboard !!

Share this post


Link to post
Share on other sites

the problem on final cut pro :/

and feel to some extent that cpu doesn't works with its full power because of instruction limitation

so want to update for instructions and and upgrade for performance 

about fx9590 it is too expensive now and see on power consummation  don't know if it will work normally on my motherboard !!

I do not know why there is such a massive problem?

I think that that the optimization of the DSDT.aml and the selection of drivers are essential for the good Performences and Kompetabilität. I do not know. :unsure:

the problem on final cut pro :/

and feel to some extent that cpu doesn't works with its full power because of instruction limitation

so want to update for instructions and and upgrade for performance 

about fx9590 it is too expensive now and see on power consummation  don't know if it will work normally on my motherboard !!

I do not know why there is such a massive problem?

I think that that the optimization of the DSDT.aml and the selection of drivers are essential for the good Performences and Kompetabilität. I do not know. :unsure:

Edit:

 

I had massive problems with system crashes during the entire Mountain Lion kernel-development phase but since mavericks everything OK

 

 

Edit:

 

The fact is that your and my motherboard can work max. with FX 8350. I can not take the FX 9590 my Board is GA-990 FXA-UD3 with Rev. 1.2. only the next Gigabyte Generation Rev. 4.0 or the GA 990 FXA-UD5/UD7 in Rev. 3.0 can work with the current consumption of the FX 9370 or FX 9590 together.

Edited by spakk

Share this post


Link to post
Share on other sites

Edit:

I am very satisfied at the moment, so I'll continue to work with my current hardware and still do not buy new hardware.

Share this post


Link to post
Share on other sites

@ Mohamed, if you want to buy a new CPU, then I would wait a little until the FX9590 is slightly cheaper, though it costs a few bucks more but then you have a super CPU :)

http://geizhals.de/amd-fx-9590-fd9590fhhkwof-a973468.html

 

I use a CPU: Phenom II X6 1100T, CPU is not overclocking.

So far I have not had a Crasch, all music and sound programs and the remaining Adobe programs run on my hardware without any problems and my graphics card works almost perfectly

 

 

FX 9590 Test

 

:)

 

bah  !!! le test est complètement faussé  :shock:  j'ai un FX 8350 et un Xeon E3-1245 v2 ( i7 3770) et je te garantie que le FX est plus puissant que le Xeon , rien que dans le test x264 , le FX 8350 est plus rapide en réalité que le Xeon avec Handbrake (300 fps pour le FX et 200 fps pour le xeon , donc , j'ose imaginer que le reste des tests sont faux .

 

http://www.cpubenchmark.net/high_end_cpus.html

 

le i5 4670k est quand même très loin derrière un FX 8350  :hysterical: :hysterical: :hysterical:

 

 

bah! the test is completely distorted  :shock:  I have a 8350 FX and Xeon E3-1245 v2 (i7 3770) and I will guarantee that the FX is more powerful than the Xeon, nothing in the x264 test, the FX 8350 is actually faster than the Xeon with Handbrake (300 fps to 200 fps and the FX for xeon, so I imagine that the rest of the tests are false.

 

http://www.cpubenchmark.net/high_end_cpus.html

 

the i5 4670k still far behind FX 8350 :hysterical: :hysterical: :hysterical:

Share this post


Link to post
Share on other sites

Thanks to our development here on Insaneleymac, now can AMD recorded better sales figures, and we get nothing for development. I ask for a donation to our account: :cry::bye::whistle: :whistle:

Edited by spakk

Share this post


Link to post
Share on other sites

:)

 

regardes le Xeon E3-1245 v2 vs FX 8350 dans une machine virtuelle (win7/Parallels9) 8 threads activé en test multitache , le résultat est sans appelle ;)

 

look at the Xeon E3-1245 v2 vs FX 8350 in a virtual machine (win7/Parallels9) 8 threads activated multitasking test, the result is called  ;)

 

kernel vanilla for Intel and kernel Bronya v7 for FX 8350 :)    with 3 MV active

 

 

Share this post


Link to post
Share on other sites

Only problem whit AMD CPU is that some APPs like Photoshop CC (Black And White, some 3D Stuff. . .etc),Ilustrator CC (ALL) are not working, and there is no more Open Source for OS X 10.9+ releases.

 

I am waiting for my next salary and i am buying i7. . .

Share this post


Link to post
Share on other sites

Only problem whit AMD CPU is that some APPs like Photoshop CC (Black And White, some 3D Stuff. . .etc),Ilustrator CC (ALL) are not working, and there is no more Open Source for OS X 10.9+ releases.

 

I am waiting for my next salary and i am buying i7. . .

 

Is it bad that I knew nothing about that? I started PS CC to see if B&W worked, and it crashed! I was like..... :wallbash:

Share this post


Link to post
Share on other sites

test the structure of my Extra folder, compare the information and try to be adjusted in accordance with your data, maybe it can help you to solve your problems.

Share this post


Link to post
Share on other sites

Hi,

 

I read through all 200+ pages of the forum to try and figure out what I should do. I am running Niresh 10.9 (no updates applied yet) I have an A8 cpu, but it hangs at times. Not sure if this kernal was meant to address the A8 series. I also own a FM2A55M-DGS V2 motherboard that haS been a bit of pain to get it up and running. Not sure if this solution would provide me with a bit of a speed boost or resolve the hangs. 

Share this post


Link to post
Share on other sites

Hi,

 

I read through all 200+ pages of the forum to try and figure out what I should do. I am running Niresh 10.9 (no updates applied yet) I have an A8 cpu, but it hangs at times. Not sure if this kernal was meant to address the A8 series. I also own a FM2A55M-DGS V2 motherboard that haS been a bit of pain to get it up and running. Not sure if this solution would provide me with a bit of a speed boost or resolve the hangs. 

===>   FM2A55M-DGS V2

I think that you're better download the original Mavericks app from appel store and then install via MyHack

but first of all:

• you need to test it, install SystemInfo.app and thus is check your hardware compatibility.

• Then look for the correct chipset drivers for your hardware.

• If it does not boot, then you may need to edit the chipset driver with your VEN-ID and DEV-ID , found by SystemInfo.app

• But the most important is bios settings: set AHCI to Enabled, set the boot medium (USB Stick) on the first place.

• then you should try to boot with diveres boot flags

 

here you no one can say which kernel you can take special so that your system will boot, try the last 5 - 6 test kernels eventually will boot your system

 

Good Luck! B)

Share this post


Link to post
Share on other sites

Apple released update 10.9.2! Build 13C64

Successfully install it and boot with kernel from Савва v.2. Also need to change kexts: applematch, corecrypto, applematch, system with kexts from 10.9.1

Share this post


Link to post
Share on other sites

Apple released update 10.9.2! Build 13C64

Successfully install it and boot with kernel from Савва v.2. Also need to change kexts: applematch, corecrypto, applematch, system with kexts from 10.9.1

 

After the update, a rollback of System.kext and Sandbox.kext of 10.9 is sufficient. Then your system will boot normally.

Share this post


Link to post
Share on other sites

After the update, a rollback of System.kext and Sandbox.kext of 10.9 is sufficient. Then your system will boot normally.

 

Hi. I rolled back those ketxts and using Савва's Kernel. after updating but I have not been able to boot at all and verbose isn't giving me much indication on what's the problem.

Does anyone know exactly which kexts the 10.9.2 update updates/replaces?

Thanks.

Share this post


Link to post
Share on other sites

Hi. I rolled back those ketxts and using Савва's Kernel. after updating but I have not been able to boot at all and verbose isn't giving me much indication on what's the problem.

Does anyone know exactly which kexts the 10.9.2 update updates/replaces?

Thanks.

 

Yeah, mine is pretty unstable after the update. I'm using Bronya's RC8 kernel, and I rolled back the System.kext and Sandbox.kext, but it gets very sluggish after I get to the login screen. Mine keeps crashing back to the login screen. Safe Boot is my only option right now.

Share this post


Link to post
Share on other sites

Thank god I waited before going on with the update. :D I also heard that 7000 cards also stop working after the update. It reads the AMD Radeon 4000 kexts instead. And having a 7870 card, it would be unfortunate if I did.

Share this post


Link to post
Share on other sites

Yeah, mine is pretty unstable after the update. I'm using Bronya's RC8 kernel, and I rolled back the System.kext and Sandbox.kext, but it gets very sluggish after I get to the login screen. Mine keeps crashing back to the login screen. Safe Boot is my only option right now.

disregard my previous post. I got it to work but I'm using Савва v.2 kernel (was previously using the one on the first post) and everything seems to be working fine, not sluggish or unstable for me at all. in my case i did only require the kexts spakk mentioned and any kernel seems to be working fine for me. (need to repair disk permissions with Disk Utility not kext wizard, but do rebuild the kext cache with wizard)

 

btw any kernel makes the clock go fast on my system so far, is there a work around or do I just have to wait for a better kernel?

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 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
    • By marras
      Hi, I've an old machine (see the signature) that I want to use for xcode , when I'm too lazy to take my macbook pro. I tried install Sierra, and worked surprisingly well, but sadly it doesn't support the latest version of xcode. I tried to update to High Sierra, but in the first boot everything goes black. So I tried a clean install, and had the same result. Tried Mojave with the telemetry plugin hack (as I've not SSSE 4.2), and the installation went smooth, but in the first login, I've a mouse pointer (which moves!) over a blinking screen, gray and black, and seems stuck. Tried several SMBIOS, changing the Display port, HDMI, LILU with WhateverGreen, but with these 2 the verbose freezes pretty soon (if needed I can make a screenshot). So I know that this card should work OOB, but I've also seen that several people had this problem, but honestly I didn't figured it out how to continue. My pc doesn't have any integrated gpu.
      Please help me, I'm stuck!
      Thank you
    • By gusbemacbe
      Hello,
       
      I am a former user of MacBook and Mac mini. Both died. One in 2014 and another last year.  I will think of giving my Hackintosh-compatible laptop to my brother that I purchased years ago, because he wants to play more than one computer, so he is a Twitch/YouTube streamer and a hardcore gamer and I will not need to lend him many times. If he wants, from my former laptop I will take only one 240GB SSD Samsung Evo with installed Arch Linux and leave one 500GB HDD for him. In the future, I will purchase a new Alienware laptop.
       
      As I got newly graduated, I moved to a new super PC with AMD Ryzen™ 7 2700X CPU and with NVIDIA GeForce™ 1660 Ti GPU. More details, you can see my signature below, that provides the complete details. I own an external SSD m.2 2280 with installed Windows 10.
       
      I will reconsider purchasing 4th drive – an external 480GB SSD m.2 2280 SATA WD Green 545MB/s or an external 1TB SSD SATA WD Green 545MB/s – for installing Hackintosh. But purchasing, I need to make sure.
       
      1. Is it worth to install Hackintosh on an external SSD m.2 2280? If I partition two partitions, one for Insansely's MyHack/Chameleon/Clover and another for Hackintosh and my new super-PC boot is natively BIOS and Grub, is it worth? Maybe I will try to install reFind on Arch Linux to replace the Grub if it is worth.
      2. I know that it will run on macOS High Sierra, Mojave and Catalina, but if I need Metal 2 to run the latest version of Sketch (the which I own an original licence) and of other apps the which I own original licences? Is NVIDIA GeForce™ 1660 Ti compatible with Metal 2?
      3. Since it be an external SSD, will I able to run Hackintosh as a portable OS in other computers?
       
       
×