Jump to content

Search the Community: Showing results for tags 'amd'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • OSx86 Installation
    • Post-Installation
    • DSDT
    • Hardware Components and Drivers
    • Complete Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Categories

  • OSx86
  • Apple News

Found 520 results

  1. Weird display issues with gxt1060

    Hi, i recently set up High Sierra on my AMD computer with the help of the amdosx community (i actually used an installer just to confirm that something would work in the first place before i spend hours for nothing, i can and could have downloaded High Sierra the "legal" way). However the graphicscard is recognized properly, the 6gig are recognized and i have no artifacts and no screen tearing with the official nvidia webdriver, but unfortunally, dark colors have horizontal dark stripes in them and specific bright colors like on left bar of system windows such as settings do flicker like low fps. I only used the clover on the flash drive for now and i'd like if it's worth digging deeper of if i should just forget about it as it is a common nvidia problem on macOS. Would be amazing to know. Closer machine infos: * High Sierra (misses a recent minor patch as my network is veeeery slow and i got this nvidia issue anyway so i mainly jumped back to linux) * AMD fx8350 * Asus Sabertooth 990fx Ref. 2.0 * NVIDIA GeForce GTX 1060 6GB
  2. Hello, I am interested in building a Hackintosh using Threadripper. Could you please recommend good motherboard(s)? Is there one that is fully compatible with the Hackintosh?
  3. mac 10.13 high sierra Installation

    How to install macOS 10.13 High Sierra in Vmware Workstation 14 Pro on AMD Machine Unlocker cmd already installed for vmware workstation 14 vmx file edited...added smc.version="0" My System Specs AMD FX8120 8 Core Corsair Vengeance 32 GB DDR3 RAM Asus 990FX Sabertooth Motherboard Sandisk Ultra II 480 GB SSD SATA 3 Asus STRIX 960 GTX 4 GB DCU II Model Pixel Shader 5 DirectX 12 Support Virtual Machine Specs 16 GB RAM 2 processors and 4 cores = 8 core processor SATA hard drive 128 MB video memory
  4. macOS High sierra R9 380

    Last year i tried to install Sierra but after installing it keped booting to a black screen, now i want to try with high sierra but i dont know what i have to do to get this to work. I heard about the whatevergreen and lilu kexts but i dont know what to do with them, can anyone help me solving this? my pc specs Intel Core i5-4460 3.20 GHz with iGPU Intel HD Graphics 4600 Asus H81M-A 8GB RAM Kingston Hyper x 1600 mhz Asus Strix R9 380 4GB
  5. Still black boot with R290X on Sierra

    I have browsed thru all forums and all threads for this card but apparently my system is still something special. With some cumbersome effort (none of the simple one-click ##### and other USB-Installers methods ever worked for me) I managed to install Sierra 10.12.5. However when booting is nearly finsihed I get the famous black screen which can be recovered by quickly unplug/plug the DP monitor cable leading finally to a proper initialisation of my 290X. 1.) RadeoDeInit is on, without this patch the screens stays dark forever2.) Booting with iGFX never works for me, I always get memory allocation errors during boot until I disable the Intel graphics completely.3.) I am on Clover 4318, newer version do not make any differences. 4.) I am using a System Configuration for an Imac 14,2. Most other configs do not make difference either.I have not started again the nightmare of Framebuffer patching (as I remember from Yosemite) and I think it will not help as the card is recognised by Sierra but just not initialised.
  6. Hi all I currently use an NVidia 760 with four displays: 1 x 4K; 2 x 1920x1200; 1 x 1920x1080. This mostly works, but I am considering replacing it with an AMD GPU - likely a Radeon 7970 - for two reasons: I would like to add a fifth monitor, maybe even a sixth; I get small stutters and slowdowns with my NVidia, using both Native and NVidiaWeb drivers. It is a lot better than it was with my NVidia 980Ti, but it's still not perfectly smooth as it should be, especially when I have a full screen video playing while also doing UI movements like Swipe Left A Space or Mission Control. I have just been told that it should be possible to access all display outputs on an AMD 79XX GPU, possibly requiring a custom SSDT and/or radeonDeInit? I've only ever had one AMD GPU and that was 8 years ago so I am not experienced with them. My NVidia 980Ti has five outputs, but can only use four at once. But I believe AMD's EyeFinity does allow it to use them all as separate displays. Before I buy the GPU, I'd be most grateful if anyone could confirm that it should be possible to run five or six simultaneous displays on a card such as the ASUS HD 7970 DirectCU II (6 x DP outputs) or XFX AMD Radeon HD 7970 (2 x mini-DP; 1 x HDMI; 2 x DVI). With one display being 4K @ 60fps and the rest 1920x1200 or 1080P. I have Googled on this a while but haven't yet found anyone discussing connecting more than four monitors to an AMD Hack I did see that the late-2013 Mac Pro (which uses 2 x AMD FirePro GPUs) states it can support "up to 6 Thunderbolt displays". So I know the OS can do it, it's just a question of whether a particular GPU can, and in a Hack setup. Thanks very much TB
  7. Hi guys, i'm trying to help a friend of mine trying to install osx(possibly high sierra) on his pc with the following specs: Amd fx8350 Asrock 990fx extreme 3 8gb of fury Kingston ddr3 ram(2x4) Radeon hd 7950 128gb ssd( crucial m550) A couple of hdds I don't remember the brand(maybe a seagate barracuda and a dumb old disk for data) We tried to install it using the regular clover+high showers installer but we couldn't get it to reach the installer, then we tried osx-amd(don't know if i can talk about it there, sorry if i can't) and we still couldn't get to the installer. Is there a guide i can use to install osx in that machin, i tried to search in the forum but i couldn't find it.
  8. Hi Guys, I’m stuck with 3mb VRAM, and can’t get my screen resolution! I’ve tried to reinstall 18 times with different configurations but I can’t seem to get it right! PLEEEEASE HELP I really don’t know what to do now. I've tried Enoch but still no success! MY COMPUTER SPEC: System Model: HP EliteBook 8570p Processor: i7-3520M CPU @ 2.90GHz, 2901 Mhz, 2 Cores GPU: AMD Radeon HD 7570M RAM: 12GB​
  9. mITX Ryzen board advice

    Hi, I'm looking for a suggestion on a Ryzen motherboard in the mITX form factor that's most compatible with Hackintoshing High Sierra. Especially: - reliable multiple sleep / wake cycle must work without issues - USB2 and USB3 must be very reliable on peripherals and external discs - no kernel panics - M2 slot for Nvme drive - Wifi / Bluetooth on M2 PCI so to allow for swapping with original card otherwise with regret I'll have to switch to Intel..(
  10. I have the USB ports that are messy. It's even hard to explain what happens as it's not linear. At second wake from sleep USBs keyboard and mouse become unusable. If they're plugged on USB3 instead at second wake from sleep the PC...reboots itself. When I reboot at times USB keyb and mouse are not recognised. Front panel USB3 don't work. USB bluetooth after wake from sleep works really bad. Some USB3 drives get stuck while copying forcing a reboot. On Tonymac (sorry) some guy called pastrychef (moderator) tells the story of his build and how he fixed USB. He says Mr RehabMan in person suggests to create a custom SSDT for USBInjectAll.kext Now, being my machine AMD, some of what they suggest to do becomes difficult to process. All in all they say to forget your USBs are working fine unless: 1 you're lucky, 2 you fix them properly. I'm not lucky. Are there permanent fixes because I need sleep to work on my machine and I have all these troubles on USB that affect stability. Thanks all for your help.
  11. Hi all guys I need your help and I hope you can help me I took the road to install High Sierra on my new build and now I have some doubt / difficulty I do not know how to solve. My configuration: 8700K Asrock Z370 Professional Gaming i7 AMD RX580 Nitro+ 8GB First I created the usb pendrive and I used Clover with the following configurations: Bootflag: dart=0 -v Kext: Bios Setting: VT-d = Disabled Share Memory = 128MB IGPU Multi-Monitor = Enabled XHCI Hand-off = Enabled SMBIOS: iMac18,3 So far no problem, it started successfully, I initialized the hdd in APFS and I ran the installation. Once finished, it started and I made the first configuration successfully. At this point I configured Clover the same way as the installation: Bootflag: dart=0 disablegfxfirmware shikigva=4 -rad4200 darkwake=8 Devices: Graphics: Kernel and Kext Patches: SMBIOS: iMac18,3 Kext: I reboot and start without problems, but I know there is some problem to solve ... for example, the video card seems to recognize it but if I run a benchmark with "Novabench" I noticed that the GPU is recognized as 1GB: With "WhateverGreen.kext" and "RadeonDeInit=Disabled": || || || I tried to delete "WhateverGreen.kext" and "RadeonDeInit=Enabled" and I recognize the card differently but the same problem presents itself: || || || Why is it recognized by 1GB instead of 8GB? While on System Profiler is recognized by 8GB .... I'm doing something wrong? I tried to enable also "Hardware Encoding & HEVC Support" but I noticed a detail that I do not know if it's right or not (Hardware Info "MacX Video Converter Pro"): Without "WhateverGreen.kext" and "RadeonDeInit=Enabled": With "WhateverGreen.kext" and "RadeonDeInit=Disabled": [COMING SOON SCREENSHOT] Is it normal that this occurs? Which one is correct? I'm going completely in confusion I'm trying to figure out if I need to make any other changes to the system, if I add some other patches to make it work properly but I do not know where to check. I'm trying to configure the DSDT but DSDT Editor and MaciASL do not work, they do not open the DSDT.aml file generated by AIDA64. Do you know how to give me a hand? I'm banging my head for 2 days I thank you in advance for the help and I apologize for my english I hope I was clear
  12. High Sierra + AMD R7 370

    Ciao a tuttti Ho installato high sierra e fino a qui tutto ok Ho una scheda madrea Asus P6X58D Premium e la scheda video in oggetto Sapphire AMD R7 370 Non riesco a fargli riconoscere la scheda video ed ho aperto questo nuovo post per evitare di accavallarci su un post simile che è questo Ho cercato di seguire in parte i consigli del post di cui sopra ma l'hack info mi da questo output Gengik84 ==================================================================== Welcome...raffaele /Users/raffaele/Downloads/Hack_Info: line 895: bdmesg: command not found Password: 2017-12-28 16:14:54.159 AllowPasswordPref[808:33460] error == Error Domain=com.apple.LocalAuthentication Code=-6 "Biometry is not available on this device." UserInfo={NSLocalizedDescription=Biometry is not available on this device.} 2017-12-28 16:14:54.159 AllowPasswordPref[808:33460] Hardware Check err == -1 2017-12-28 16:14:54.184 AllowPasswordPref[808:33460] Is Network User? == 0 2017-12-28 16:18:10.822 system_profiler[760:35124] Terminating '/usr/sbin/system_profiler -nospawn -xml SPSerialATADataType -detailLevel full' because it did not respond. Sul web cmq ho trovato che si è riusciti a far riconoscere la mia scheda video ma anche seguendo ciò che c'è in giro non sono riuscito nell'intento Sicuramente sbaglio io qualcosa Vi ringrazio in anticipo per l'aiuto Ciao PS(ho allegato anche la cartella clover) CLOVER.zip
  13. I recently got an Asus X55U laptop with the following specs: AMD Brazos C-60 1Ghz CPU 4GB DDR3 120GB HDD AMD HD 6290 Graphics. I am trying to use the Sierra 10.12.5 raw file from the Olarila forum. I understand that I need to change the kernel on the installer USB to one that supports AMD processors, but I am not sure which kernel to use or how to replace it. If anyone can help me with this I would appreciate it. Thanks. EDIT: Also when I try to use the Sierra Zone distro with the included AMD kernel, I get Error loading kernel cache (0x9) when trying to boot into the installer. EDIT 2: Nevermind this post. I just read that your CPU needs SSE4.1 to run Sierra and the C-60 only had SSE4A. I'll try an older version and make a new post if necessary.
  14. Hi there guys! At the moment I try to get iMessage to work on Ryzentosh. iMessage Debug is giving out failed values: Gq3489ugfi: failed Fyp98tpgj: failed kbjfrfpoJU: failed oycqAZloTNDm: failed abKPld1EcMni: failed Is there a way to inject correct values with clover to get iMessage "maybe" to work. BTW: Thanks for Clover! It's so amazing.
  15. Thanks to B for the kernel version of the test, so more and more of the game player started to make the design industry software, for example: Adobe After Effects, Photoshop, Premiere, Illustrator, CINEMA, 4D and so on, but we also encountered "unexpected exit" collapse problem in the corresponding software, here we all work together, to find and solve problems the problem!
  16. MSI R9 270x Twin Frozr 2GB

    For sale, a MSI R9 270x Twin Frozr 2GB, immaculate condition, bought 5 months ago BNIB. I will be sending the invoice along with the GPU. I had no problem installing macOS El Capitan, Sierra & High Sierra with no patches whatsoever applied to the card. Price 130 euros, I can send photos if needed.
  17. I've recently acquired a kernel that Bronya has been developing and I had wished to test it out on my system. I assumed the process of updating the kernel would follow the steps outlined here So I booted via USB into my macOS, deleted the existing kernel at macOS/System/Library/Kernels and replaced with the new kernel file, then deleted the existing PrelinkedKernels file too. Next I ran Kext Utility, and when it finished I rebooted. Upon booting into macOS again via clover on the drive, I ran Kext Utility again, just to be safe. Now, however, I no longer have any sound devices once booted and I am experiencing very long boot times, noting "kextd wait appleacpicpu" at the end of boot (see attached screenshot) Did I actually update the kernel correctly? Did I miss a step, or screw something up along the way? Thanks
  18. Introduction With Whatevergreen.kext we already have a workaround for the AMD GPU wakeup issue which first arose with the release of El Capitan, but as a workaround is just a second class solution for a problem I decided to trace back the reason for the issue to it's origin and this post is the result of my research. As I used a R9 270X to do my research, which is the only AMD GPU I have, my patch has only been verified to work properly with this chip but according to the information sources I used, I have no reason to believe it won't work on other AMD GPU's too. In case there is still some uncertainty left in a particular point, I will mention this explicitly. Materials Used The Linux kernel sources of the Radeon driver in order to get a better understanding of the GPU's internals: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/radeon?h=next-20171013 A copy of the ACPI 6.0 specs in order to find out how to dump the chip's control register space. A disassembler, e.g. objdump in Terminal or the trial version of Hopper Disassembler. What I Did As it's been a well known fact that wakeup with AMD GPUs still works with El Capitan and Sierra provided you select the IGPU as primary GPU enabled CSM and use Legacy VBIOS of the AMD GPU in BIOS setup. I was wondering what is different with UEFI VBIOS and decided to I create dumps of the GPU's control register space while using Legacy VBIOS with CSM enabled and while using UEFI VBIOS with CSM disabled in order to find out. Comparing the register space contents it became obvious where the root of the problem lies and how it can be fixed with a DSDT patch. Technical Background Using Legacy VBIOS only the primary GPU is initialized by the VBIOS, i.e. only the IGPU is initialized while the AMD GPU is left untouched. When OS X boots up the framebuffer controller kext will find the AMD GPU in vanilla state, initialize it properly and wakeup will work as expected. That's also the reason why you have to blind boot in this configuration. Using UEFI VBIOS the AMD GPU will be initialized too, provided it has a display connected to one of it's ports. You'll see the BIOS splash screen and will be able to access the BIOS settings but unfortunately macOS's framebuffer controller kext will notice that the GPU has already been initialized and skips the basic setup so that the configuration made by the VBIOS will be used and this is the point where things start to go wrong because this configuration seems to be broken causing wakeup to fail. First of all you have to locate the AMD GPU in your DSDT. In my case it can be found at _SB.PCI0.PEG0.PEGP but it needs to be renamed to GFX0 for AppleGraphicsDevicePolicy.kext (AGDP) to work properly. This can be done manually or using a Clover patch (this is what I did) and I assume that this problem has been already solved before. The reason why I mention it explicitly here, is that you should be aware of it and don't get confused when your AMD GPU has a different name in the DSDT than in IORegistry. Second, we need to get access to the GPU's control register space. According to the Linux sources, PCI Base Address Register 2 (BAR2) is used to address the control register space on Radeon HD5000, HD6000 and HD7000 GPUs. It's a 64bit base address register but newer GPUs (BONAIRE and above, i.e. Radeon HD8000 and HD9xxx) are different as the use BAR5 instead of BAR2. Unlike BAR2, BAR5 is a 32bit base address register. On my R9 270X (PITCAIRN) BAR5 is zero so that I decided to use this as an indication to use BAR2 but I must confess that I haven't checked if it works for all supported GPUs too. In case my patch doesn't work for you, be aware that this might be a pitfall! The Radeon driver's source code tells us that the first display controller engine's registers can be found starting at offset 0x6800. It also tells us a lot about the meaning of the register contents. Using Legacy VBIOS my R9 270X's display controller engine's registers are still at their default values when macOS boots: 00006800 01 00 00 00 08 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | With UEFI VBIOS the display controller engine's registers look quite different. Using the Linux driver sources you can easily make sense out of these values and will discover that I've got a 4K display connected to my R9 270X which is configured to it's native resolution using 32 bits per pixel. 00006800 01 00 00 00 0a 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 0f 00 00 f4 00 00 00 |................| 00006820 f4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 0f 00 00 70 08 00 00 00 00 00 00 |........p.......| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | The rest was just a little bit of laborious work and trial and error, comparing register contents, understanding their meanings and see what happens when you reset these registers to their default values. If you try to play around with your GPU's control registers a little bit more, be prepared to get a garbled screen for a few seconds. After all I've managed to create a DSDT patch which fixes the wrong registers while preserving screen output during boot and, most important, solves the wakeup issue. The Patch Putting things together I created a DSDT patch to fix the incorrectly initialized registers. With this patch applied, I now have working wakeup with my R9 270X under Sierra (10.12.6) using UEFI VBIOS with CSM disabled in UEFI setup. No kext patches or additional kexts are needed anymore for sleep/wake to work properly with my R9 270X anymore. I can see the BIOS splash screen on my display and can access UEFI setup but the best of all is that there hasn't been a single wakeup issue since I applied this patch. Device (PEGP) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFFFFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } } In case you have in-detail questions or need AML code for debugging (code to dump BARs or to dump the GPUs control register space) please let me know. I'm willing to share all my information in order support further research. Below you can find the register dumps I created attached to this post. FAQ Do I still have to select the IGPU as the primary display? No. Although I haven't tried this on my own, user chh1 confirmed that this is no longer required when using the patch (please see http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/?do=findComment&comment=2519884). Nevertheless I still recommend to select the IGPU as primary as there is absolutely no reason not to do so, in particular as the IGPU will be unusable for multimedia acceleration on Haswell based systems when it's not the primary one (IGPU's dev id is different when it's not the primary one). ​When I boot into macOS I always end up with a black screen. Does your patch solve this problem too? No, it doesn't. This patch solves the wakeup issue, nothin more and nothing less. The black screen after boot is either the result of a connector problem (please create a connector patch for your graphics card using the well-known methods) or the result of a problem with AGPM as certain system definitions (in particular recent iMacs) select special configurations for graphics power management. In order to achieve proper operation of AGPM it is crucial that your GPUs have correct names in the DSDT matching those listed in the AGPM configuration for the system definition (IGPU for the Intel GPU and GFX0 for the AMD GPU on iMac15,1, iMac17,1 and iMac18,x). You may patch your DSDT manually or use a Clover DSDT-patch to fix the device names. Credits vit9696 for developing Whatevergreen.kext and pointing me to the right direction. RehabMan for developing ACPIDebug.kext The Linux Radeon driver kernel developers for providing me with the background information I needed. Legacy.bin.zip UEFI.bin.zip
  19. Buenas, hoy me acabo de topar con este video... (abajo link) en el cual el que sube el video dice que es una solución para no tener que usar IGPU con las tarjetas graficas de AMD RX 480 y RX 580 (que el dice que las ha probado), hay varios que han dicho que les ha funcionado pero no me queda claro si es solo para intel o también funciona para las hackintosh basadas en AMD, por eso hago la pregunta aquí (aunque también la hice en los comentarios del video) que si alguien lo ha probado para hackintosh AMD Video en cuestión: NOTA: no se si hice mi pregunta en el lugar adecuado, si ese es el caso espero disculpen y el admin lo mueva al lugar al que pertenece.
  20. Hi everybody! I need some help today: I’m trying to install Mac OS Sierra 10.12.5 on my friend’s laptop, which is an Acer Aspire 5250, but that’s quite a difficult task because it’s an AMD CPU. The model is AMD E-450 APU with Radeon HD Graphics (graphics model Radeon HD 6320). I need some help because I can’t boot the installer, when I select my USB from Clover, after the row of pluses in verbose mode instead of showing me all the booting commands it stucks on a black screen and the screen starts flickering along with a continuous beep sound and so I’m unable to get to the installer. Do I need a patched kernel or something else? Are you able to give me some help? Thanks!
  21. Hi everybody! I need some help today: I’m trying to install Mac OS Sierra 10.12.5 on my friend’s laptop, which is an Acer Aspire 5250, but that’s quite a difficult task because it’s an AMD CPU. The model is AMD E-450 APU with Radeon HD Graphics (graphics model Radeon HD 6320). I need some help because I can’t boot the installer, when I select my USB from Clover, after the row of pluses in verbose mode instead of showing me all the booting commands it stucks on a black screen and the screen starts flickering along with a continuous beep sound and so I’m unable to get to the installer. Do I need a patched kernel or something else? Are you able to give me some help? Thanks!
  22. I have: Intel Core i7 7700K 4.2 Ghz Gigabyte GA-Z270MX/Gaming 5 Samsung CF791 Series 34-Inch Curved Widescreen Monitor (C34F791) 3440x1440 4K Samsung U28E590D 28-Inch UHD LED-Lit Monitor with Freesync support 3840x2160 4K XFX AMD Radeon™ RX 580 8GB 256 Bit GDDR5 Graphics Card Both monitors are hooked up through Display Port Sierra works fine and I get full 4K off both monitors and everything works. However.... With High Sierra I can only boot into High Sierra with 1 of the monitors turned on. Whenever I turn on the 2 monitor everything freezes within High Sierra and screen goes gray. I can still see the desktop but can't click on anything. Anybody know what I can do to get both monitors working fully in 4K? Some Success ------------- After 2 days of constant testing with no luck. I think the problem has something to do with the AMD .kexts in S/L/E. When I copied the AMD .kexts from Sierra to High Sierra I got weird colors (red & blues flipped) and the 2nd monitor will go on and not lock up the computer Even though the method of copying kexts somewhat worked... It made the graphics choppy and everything was running slow (open windows and programs). Is there a FakeID (FB Name, NVCAP, VRAM, Video Ports, Display-cfg, ig-platform-id, BootDisplay) of some sort I can use in Clover to fix this? Kext? My clover config is attached if that helps anybody! Also... The 2 pictures attached are what happens. Boots with 1 monitor on. As soon as the 2nd monitor is turned on or plugged in... The working monitor goes black and everything stops responding. config.plist.zip
  23. Sapphire Radeon RX Vega 64 on macOS

    IF ANYBODY CAN HELP THAT WOULD BE GREAT!!! Just recently bought a: Sapphire Radeon RX VEGA 64 8GB ~ https://www.amazon.com/dp/B074HCCWW9/ Kinda new to the whole AMD graphics card on Hackintosh thing. Always used the nvidia cards and know how to do it that way. Does anybody know what I'm suppose to do in order for the mac to recognize the card the right way? Currently what is happening is mac OS is booting with my new AMD card but the graphics in the system profile is only showing Display 7MB and the resolution is at 1600x1200. The nvidia card I used to have was working fine with my 4K monitor and giving me 4K resolution when I booted the OS. What am I suppose to do? Is there something specific in Clover I need to do? FakeID or kext? Currently I am not using any boot flags of any sort, never had to with the nvidia card. I know people have said they been able to boot the Vega 64 cards OOB with no issues. Not having that type of luck. I attached the current clover config file I'm using, if that helps. config.plist.zip
  24. What works? Everything. Sleep/Wake, NVMe, Airport, Spotlight, AMD-graphics Config: ASUS Prime B250M-C µATX-board Intel Core i5 7500 (Kaby Lake) Gigabyte Radeon RX560 4GB Airport-compatible PCIe-Card for Wifi and Bluetooth (BCM943602CS) 2 NVMe drives: Samsung P961 with 1 TB and 256 GB Installed mac OS: 10.13.2 Clover: 4334 *Update 10.13.3* Added new config.plist and ssdt for AMD injection (config_amd_ssdt_10133.zip). With this config and Intel IGPU activated you'll get Metal2 (macOS GPUFamily1 v3). What did I do? Had to fake Skylake graphics or to prevent apps like iMovie or FinalCut from crashing. With Kabylake kexts loaded and IGPU as secondary graphics card, the computer will hard reset whenever the Intel GPU is utilised. Only Skylake kexts and activated IGPU will give you working Metal2 for the RX560. *Update 10.13.2* Since this update a new approach is advisable to get the RX560 up and running (works for 10.13.1 and GM as well). I've added a working SSDT and injector kext that gives you graphics and HDMI audio. Sleep works fine too if you add the DSDT I compiled. Credits go to @Toledo @Mork vom Ork and @Mieze because their work made this possible. *Update* I've added NEW config.plist and DSDT. For proper graphics power management you have to activate onboard graphics in BIOS but make PCIE the primary display. Furthermore you have to inject ig-platform-id 0x59120003 and let Clover patch GFX0 to IGPU. This is the only way to avoid crashes of iMovie, FinalCut or slowdowns after video playback. This may be the smoothest Hackintosh of my life. It is easier than Sierra install due to native support for most of the used hardware in High Sierra. Not much to do, using an up-to-date Clover version like 4184. Make sure you have apfs.efi in /Clover/drivers64UEFI/ on your EFI partition and that you delete EmuVariableUEFi.efi (downside: iMessage doesn't work without it). Somehow Rehabman's SSDT in /Clover/ACPI/patched helps avoiding crashes in iTunes. Needed kexts (on your EFI into /Clover/kexts/Other): FakeSMC, IntelMausiEthernet for ethernet, USBInjectAll and XHCI-200-series-injector for USB, Lilu and AppleALC for audio, Whatevergreen for AMD graphics, IntelGraphicsFixup and AMD9xxxControllerPatcher.kext. DSDT and SSDT go into EFI/Clover/ACPI/patched. config.plist.zip AMD9xxxControllerPatcher.kext.zip SSDT-HDMI-AMD-PEG0.aml.zip DSDT.aml.zip config_amd_ssdt_10133.zip
  25. R7 260x GPU in Sierra 10.12.6 / in any version of High Sierra ? I have this i7 7700K and asus rog z270e in my rig; So I can install Sierra/High Sierra on it using intel hd630 graphics, but I want to make use of the only gpu i have right now which is Sapphire R7 260x. And I dont know how to get it started in 10.12.6 / newer macOS? Already tried: Adding 0x66581002 in AMD8000 and 4000 kexts In Clover, you have to set: - FakeID / ATI = full ID (here: 0x66581002) - Inject / ATI = true - FixDisplay = true Configure your iGPU as primary graphics device in bios All these does not make it work, So Please let mw know if anybody can help!?
×