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
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 238 results

  1. 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
  2. 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​
  3. 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.
  4. 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!
  5. 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
  6. 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.
  7. 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!
  8. 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!
  9. 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
  10. 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
  11. Bom dia galera! Estou há uma semana tentando instalar mac OS 10.12 sierra processador AMD. Quando vou fazer bootable pelo Win32DiskImager ele chega até em uma frase, Using reloc block: yes.... e reinicia. Já no TransMac recebo a seguinte mensagem, This version of Mac OS X is not supported on this platform. Meu setup: PLACA MÃE: GIGABYTE 970A-UD3P PROCESSADOR: AMD FX-8350 MEMORIA RAM: 8GB 1866MHz DDR3 HYPERX PLACA DE VÍDEO: R9 380 4GB SDD: KINGSTON SUV300S37A 120GB HD: SAMSUNG HM500JJ 500GB
  12. Hi all, After realizing that Clover doesn't work on AMD Ryzen systems and the only solution is to use a closed-source fork, I set out to implement Ryzen support in Clover myself and share the results. The source can be found at https://github.com/shawnanastasio/Clover-Ryzen and I've attached a build to this post. I have confirmed that it boots on my Ryzen 7 1800X system, but I have not tried booting macOS yet. If anybody has a Ryzen hackintosh set up, I'd love to hear if it works for you. To try it out, just replace your current BOOT/BOOTX64.efi and CLOVER/CLOVERX64.efi with the attached build. Feedback is welcome! ============ Update 7/1/17: Add support for fractional multipliers (like 39.5). Link to download. ============ Old Downloads: Update 6/30/17: Fix max/min ratio detection as well as FSB detection. Link to download. Update 6/29/17: Add automatic CPU max/min ratio detection. Should resolve clock speed issues. Link to download. CLOVERX64.efi
  13. Hi guys..I sucessfully installed Sierra 10.12.5 & Windows as a DualBoot..Im interested in trying macOS High Sierra..Im using an AMD FX 8320 Processor..Do we know when the beta kernel will come out ?
  14. Hey guys, So here are my specs: Mobo: ASUS B150M-A CPU: i5-6500 Skylake GPU: ASUS STRIX R9 390 Monitor: Acer X34 Predator (3440x1440) OS: Dual boot Sierra and Windows 10 with Clover as bootloader I successfully got macOS Sierra running on my machine, but the resolution is wonky. Sierra won't properly recognize the R9 390. So, that being said, I want to accomplish either of two things: Either 1) Successfully use the R9 390 on Windows 10 and on Sierra with proper resolutions (Windows 10 works fine, just thought I'd mention that I do have it installed on a separate SSD in my machine) or 2) Use the R9 390 for Windows 10 and my iGPU (integrated graphics) for Sierra. My main use-case is developing using Xcode, so no intense gaming or graphics-heavy stuff going on. The thing is that I want to avoid having to swap monitor cables all the time. Current state: My machine starts up fine when I set the Boot GPU to the R9 390, but the resolution is incorrect. When I set the boot GPU to the integrated graphics, it doesn't start up at all, just goes to a blank screen. Any help is much appreciated.
  15. I have been trying to get iMessage working on my otherwise perfect Hackontosh. The problem is i cannot switch to clover due to exception 64 error and it's due to my motherboard which is super old it is a Asrock-VGS3-FX and I use a Amd Athlon x2 Black Edition OverClocked to Quad Core with 750 ti Graphics, Now with my specs out for the way I have tried file NVRAM I placed the kext in my Extra Folder and put the modules folder in the Extra Folder but with the filenvram.dylb in the extra folder the system will not boot and also had issues with yosemite I had filenvram in my extra folder when I was running yosemite but than I update to el captain but on yosemite I had no idea how to use file nvram and how to get iMessage working,
  16. ITzTravelInTime

    VoodooTSCSync Configurator

    Version 2.1

    2,014 downloads

    This app can be used to edit or create custom versions of the voodoo tsc sync kext, i have created it because i have seen many times peoples having troubles in finding the right version of voodoo tsc sync for their cpu, so i created a mac app that lets to edit or create a voodoo tsc kext and configure it for your system, i have included 3 ways to edit the kext: 1) configure using one of the existing templates (just chose one of the cpu models listed) 2) specifying the number of logical cores (threads) 3) manually editing the info.plist of the kext using the editor (still experimental, needs some improvements) This app uses a copy of the VoodooTSCSync in his Resourches folder, or you can open an existing version of VoodooTSC and edit it, there are some other useful features to discover, and new ideas are also welcome to improve this program, i know that with a plist editor you can do what this app does, but this is designed to be more user friendly than editing a plist file manually and just for accomplish the task of configuring this kext for your machines without looking on the web for that specific pre-configured version you need, just download this program and follow a few steps. Reference topic: VoodooTSCSync Configurator, create a custom version of voodoo tsc sync
  17. Hello, I purchased a hp laptop with Intel i7-6500U processor and a dedicated video card AMD R7 M440. I wanted to know if my pc is compatible with MacOS Sierra. Thank you P.S excuse my bad english
  18. So I have been trying to install OS X 10.10/10.11 and MacOS 10.12 on my main PC with no success. So I once got Sierra working couple of days ago without Graphical Acceleration but afterwards it didn't even boot at all. I read that I would be able to get the graphical acceleration on Yosemite so I thought I should give it a try. There's 2 pics what kind of error message I get when trying to boot to the installer. I think it's about my GPU but do you have any kind of suggestions that how could I at least boot into the installer and install the OS? Any kind of help would be appreciated. Specs: CPU FX-8350 Mobo: ASUS Crosshair V Formula-Z RAM: 16GB of Kingston HyperX DDR3 RAM GPU: XFX R7 260X ( I know it's not a very optimal card for this, but I've found out it's possible to get it working ) Tried using Clover but I got reboots so I started using Enoch.
  19. assassinale

    Rx 460 HDMI Audio

    hi everyone! I made an mackintosh with Sierra, an intel core i5 and an AMD rx 460. everything works fine, except for the HDMI Audio. i tried to use one of those SSDT file, I put the right one in "/Volumes/EFI/EFI/CLOVER/ACPI/patched/" but the HDMI audio don't work. How can I solve this? thank you.
  20. Hola buenas, Acabo de actualizar el sistema a esta versión y me ha dejado de funcionar correctamente la gráfica. El kext que utilizo para la ATI Radeon HD4890 es QE_CI Exotic Patch pero solo hay soporte para la versión 10.12.1 de macOS. ¿Alguien sabe si se puede modificar el kext para que funcione con la nueva versión?
  21. I have scoured the internet for an answer to this, but no luck. When I try to boot into my OS X El Capitan Virtual Machine, I get an error (Pictures Below). I have tried to reinstall VMware, reinstall the Virtual Machine. I have used the unlocker provided by someone else, and installed flags to the text file. But none has worked. Processor: AMD FX 8320E @ 3.20GHz Memory: 8GB DDR3 Below is my .VMX file. El Capitan VMX.txt
  22. Hello :D/ Any help is appreciated I need this hackintosh working ASAP cause my friend is an engineering student and needs working macOS for his semester studies. Compaq CQ60 207ee: - AMD Athlon X2 QL-62 dual core - Nvidia Gefore 8200 mg video card - Nvidia Chipset: Geforce 8200m - ATA 250 gb Hard Disk - Old bios with little options and without EFI I want to install Mavericks, tried almost all availabe kernels on the internet. I always get kernel panic with following abstracts: Invalid opcode 64bit, kernel trap type 14, Extensions in the backtrace: com.apple.driver.ACPIPlatform When using the kernels in the Niresh DMG, It says something like tsc_init: EFI not supported. Any help is really appreciated
  23. THIS TOPIC IS THE RESULT OF VARIUS SPLITTED POST FROM CLOVER GENERAL DISCUSSION THE MAIN GOAL OF THAT IS KEEP TRACK OF THE RESULT IN THE TEST AND MAYBE FIND POSSIBLE SOLUTION ON THE BOOT HANG WITH POLARIS CARDS WITHOUT THE HELP OF PRIMARY iGPU ALSO TO KEEP THE CLOVER GENERAL DISCUSSION TOPIC CLEAN... Other related topic: - AMD Polaris IDs on 10.12 Sierra - 10.12 Sierra AMD Framebuffer dump script ErmaC (November, 12 2016) Hi guys A question from a noob: it's about Clover support for Polaris graphics cards https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/ati.c (line 277) //Polaris { 0x67C0, 0x00000000, CHIP_FAMILY_HAWAII, "AMD Radeon Polaris 10", kNull }, { 0x67DF, 0x00000000, CHIP_FAMILY_HAWAII, "AMD Radeon RX480", kNull }, { 0x67E0, 0x00000000, CHIP_FAMILY_HAWAII, "AMD Radeon RX460", kNull }, { 0x67EF, 0x00000000, CHIP_FAMILY_HAWAII, "AMD Radeon RX460", kNull }, { 0x67FF, 0x00000000, CHIP_FAMILY_HAWAII, "AMD Radeon Polaris 11", Shouldn't we have CHIP_FAMILY_POLARIS instead of CHIP_FAMILY_HAWAII??? Or maybe CHIP_FAMILY_BAFFIN (for Polaris 11) and CHIP_FAMILY_ELLESMERE (for Polaris 10)??? Also, are you sure about RX460 with 0x67E0??? According to AMD and Linux Kernel Driver DataBase, there's no RX 460 with that device. Here, all known Polaris graphics cards device-ids
  24. Hello everyone, I'm having a strange problem with my OS X Yosemite installation. I'm using the Niresh Yosemite distro, and I'll put my specs in the bottom of the post. So my problem is, I installed OS X using the same distro about 2 times succesfully, but I messed up things post-installation which required me to re-install it. But after doing this a few times, the installation stopped working. I can still boot into the installation, but it halts at 14 minutes remaining. I've tried creating a new usb stick, but it doesn't change anything. The errors in the log are: "X /Volumes/OS X: missing CoreServices" "Container dmg is missing universal diagnostics" "Cannot connect to /var/run/systemkeychaincheck.socket: No such file or directory If anyone recognizes this problem or knows the solution, I'd be very grateful Specs: AMD A8 (Not supported but works anyway, same architecture as AMD Athlon I suppose?) AsRock a75m-HVS Some Radeon 7000 card that is supported 8GB RAM 320 GB harddrive
  25. I have an ESXi 6.0u2 on a 24 Core 65GB mem AMD Server. I have installed unlocker 208. I have tried from 10.3 through 10.12 OS X. The lower version can't get past the crossed out O and the higher versions fail right after the apple logo. I have tried the vmx change: smc.version = "0" I don't have a MAC to be able to create my own images. I have downloaded many of each version from torrents that claim to be bootable or install image. Has anyone got any version of OS X to work on a ESXi 6.0u2 with AMD processors? So frustrated.
×