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 I am pretty new with installing MacOSX, i will start with that i am able to run,install, and get it worked on Virtual Machine successfully MacOSX Snow Leopard. Problem is, i cant get it done as a normal install on my hardware for some reason it stuck. I did tried, ModCD + snowleopard_10a432_userdvd(retail DVD, converted from DMG to ISO, Burned by IMGBURN with 8x speed) on virtual box it does worked. When i tried to boot it normally selecting DVD as a first bootable device. I got stuck on: And it freezes so i cannot continue at all. Also tried EFI legancy boot disk to boot it up to install retail DVD. and got: So again i cannot do nothing. My specs are as shown on pictures: http://imageshack.us...myspeccpuz.png/ And Processor Supports: http://imageshack.us...alizationc.jpg/ Could anyone help me solve this? What distro should i try go get it worked? Thanks for any answers.. Hope i don't need to change hardware... Edit: Added Quotes.
  2. hzhjy123

    AMD Kernel

    Version 10.8.x

    4,152 downloads

    Support topic for the kernel is here http://www.insanelymac.com/forum/topic/281450-mountain-lion-kernel-testing-on-amd-dont-ask-help-here-use-the-help-topic/ The kernel is RC4 by Bronzovka. I think that it is the best AMD Kernel at the moment. Advantages: 1. Faster than Andy's kernels (less than 30s) 2. Running stable 3. SSSE3 issue has already been solved But the kernel still has a few glitches. We will strive for it!
  3. iProCr4ftr

    AMD Processors - nForce 630a without AHCI

    Hello, I have a motherboard (ASUS M4N68TM_LE_V2) which has the nForce 630a chipset (for AMD processors). As is the theme with nForce chipset motherboards, there is no option to select AHCI, only the default IDE mode or RAID, as seen in the following image: http://i.imgur.com/hsoGtdo.jpg I know that RAID implies AHCI, however, no matter if I am in the default or RAID mode, I still can't get to the Mac OS X Mountain Lion Installer, due to the "Still waiting for root device error". This image shows the error that I see: http://i.imgur.com/xY1qe0r.jpg The boot flags which I use are: -x -v npci=0x3000 (I use npci=0x3000 in order to get around the [PCI Configuration Begin] error) No matter if I run it using -x or not, it still won't work. I have tried 5/6 different nForce ATA kexts, to no avail, and tried Verdant's Support Pack, which didn't seem work for me either. What would you suggest? What do you think is the problem? Also to note, I have Mac OS X Mountain Lion on a USB drive, using Andy Vandjick's 10.8.2 AMD kernel. I am using Chameleon the bootloader. Thank you.
  4. 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.
  5. jatomusic87

    HP ENVY AMD

    I am excited to start on my OSX endeavors with the community here. First I will start with my build: HP ENVY m6-1205dx AMD a10-4600m Quadcore AMD Radeon HD 7660G Some multi DVD drive(does it matter?) Realyek PCIe gigabit controller Atheros wireless AR9485 I dont know what sound chipset or USB3.0 OR USB2.0 Will post when i find out! Now I'm sure you are face palming and saying, AMD! No! But i believe it will just make this project more fun to tinker with! I have decent knowledge of computers, but not of OSX underlings, can get around just fine with the OS since i have to for work (work at some place that fixes computers with a synonym for "nerd posse") So! This is were i am at, i have Niresh 10.8.2 and have gotten to boot to disk etc I have tried the amd boot option with -v verbose but it seems to not load the amd kernel in niresh, after some digging i found the "Kernel Cache"=\amd and the unit just restarts So i tried also amd hp -v and it appears to try and load but it just freezes no indication of loading after 30min of sitting idle on black screen So finally to my question Anyone have any other boot command ideas to push me in the right direction I was wondering just like i found out on niresh the amd boot option was "Kernel Cache"=\amd any one know what the hp boot options actually does? would love to manually enter both amd and hp boot options to see if i can tinker with those and make it to another screen past black Thanks for the help! Oh and if this is not the right sub forum to post in, please point me to the right one to create a topic Thank you all! Happy Hackintoshing! John
  6. Ok so I'm looking for a little help with my Lion install. Here's the story: I've been running 10.6.7 on my AMD machine for the better part of a year with absolutely no issues. I mainly use my HackPro for video editing in Final Cut Pro X, so when the first AMD kernels were released with 32bit support only, I had to stay away (FCPX is 64bit only). Not until recently have I started working on installing Lion & Mountain Lion. And so far, I just can't win With Mountain Lion, I had graphic corruption caused by the amd_kernel. Understandable, I told myself, and decided to roll back to 10.7 and give that a shot, as I heard there were several working kernels with full graphic support for my HD 5750. I was able to get up and running in no time at all, found working kexts for my graphics and network, sleep is working with no issues, shutdown/restart, the whole nine yards. I'm able to boot in full 64bit mode or 32bit/64bit userland, and FCPX opens and runs perfectly well. Here's the issue: Any sound that I play on my machine starts off with a brief stutter. Video sources such as YouTube and Netflix play fine after the stutter goes away, which is well and fine. The problem I'm having is when I'm playing video in Plex Media Center, or when I've opened a project in FCPX and start playback, the video is behind the audio, falling completely out of sync. It seems like the video is playing in slow motion, and the audio is playing at full speed. I have had no issues whatsoever with audio up until this point. I use a Tascam USB audio device, which works in 32bit only, and I've used VoodooHDA to enable my on board audio. With either device, the audio issue is the same. I've tried using busratio=15 as a boot flag, I tried enabling/disabling SSE2 in VoodooHDA prefs, I've tried creating and compiling a DSDT (never used one before, and couldn't find any patches for the one I made...), and nothing seems to be helping. I've also tried a number of different kernels to no avail. I'm tired of being stuck on Snow Leopard. I'm trying and trying to get this working so that I can use it as my full time OS, but I just can't seem to shake the issues. If it's not one thing, it's another. ***EDIT: I also have an nVidia GTX 550 ti, GT430 8300GS on hand if they would make the Lion process any easier. Thanks again.***
  7. After a painful waste of all my last weekend trying to patch AppleHDA for the Via-VT1705 codec of my motherboard, with the help of Mirone, a very experienced person when patching HDA is concerned, we had to gave up: we finally hit a brick wall, where no advancement was being done. The research we made for the patch, yet ending in failure, revealed a important caveat: almost all guides for binary and DSDT patches aiming a full working AppleHDA are meant for Intel chipset motherboards (there are in fact a few resources for nVidia chipsets). We AMD users have been left at the mercy of VoodooHDA development. While VoodooHDA surely works (in fact, i have to use it to finally have onboard audio), this is far far from an optimal solution: there are lots of reports of poor quality sound, noise and system instability. VoodooHDA, if it doesn't enable our HDMI ports out of the box, won't enable it at all, and Intel users on Mountain Lion can always resort to many DSDT edition guides for HDMI fix, even without working onboard audio. That's not possible yet for us AMD users: the overwhelming majority of the DSDT patches available in the scene today doesn't blend well if our motherboards. In ATI chipset-based boards, southbridge and northbridge schemes appear in a completely different manner. With Lion, the situation is even worse: the successful DSDT patch, by itself, is not enough - AppleHDA must be properly recognizing and working with the onboard codec. But then again, many AMD-based boards, specially cheaper ones, use strange codecs, for which no support is provided. We deserve better! So i think it's time to start AppleHDA and DSDT development targeting specifically our needs. My resultant after these days of hard work and research, is attached. It still fails to enable AppleHDA sound and HDMI audio, but at least it loads the kext, and both AppleHDA (HDEF) and HDMI audio (HDAU) appear in IOReg. I made this DSDT replacing the SBAZ@14,2 entry by Toleda's HDEF DSDT patch, but keeping the original address instead of 1B. I added also the basic discrete graphics edit by Toleda, and renamed another SBAZ entry to HDEF. Then Apianti of projectosx cleaned it from warning and remarks. Mirone also made some edited DSDTs, trying to help me to have native audio, but since his DSDTs didn't perform quite well, i decided to attach my own: DSDT.zip Mirone also made various binpatched kexts for my Via-VT1705 codec. Here's some links, if you want to play with them (all credits go straight to him, if some of them succeeds to give audio as is: he worked alone, and working hard, to "boldly go where no man has gone before"): http://cl.ly/1w0n2D3M1Y0A http://www.sendspace.com/file/nh8oc8 http://www.sendspace.com/file/7ji0tz http://www.sendspace.com/file/vvdzfj - his DSDTs are also attached in these links. Tools recommended: - DSDT Editor: http://www.insanelym...ttach_id=110472 (credits to El Coniglio) - Ubuntu Live USB for CODEC dumps: http://www.ubuntu.co...tick-on-mac-osx - Hex Fiend or any hex editor of your choice: http://ridiculousfish.com/hexfiend/ - IORegistryExplorer (affectionally called "IOReg"): http://www.osx86.net...ryexplorer.html - Kext Utility: http://www.osx86.net....8_edition.html (credits to cVaD) - DPCIManager: http://sourceforge.net/projects/dpcimanager/ (credits to SJ_UnderWater) - Radeon Bios Decode: http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=90340 (credits to bcc9) All tools work in OSX. Let's start? Notice that it's not expected that any of this files works at all: they're meant only as starting ground for R&D, and as guidelines for what to try (or not to try). Many thanks to Mirone, Toleda and Apianti. Best regards!
  8. [AMD] 10.7.3 Guide - Experimental Only Guide Revision 003 - 20042012 Written by Devout CHANGES are in Green. Introduction Welcome to the tutorial to get your 10.7.3 running. Before we start, I'd like to make it clear that this tutorial is based on a kernel that is still being developed, and future changes to the tutorial will occur. Additionally, not everything works right now so you'll just have to see if your machine is supported and that you want to see if it's capable of running Lion. Please do not install this if you're planning to use the machine a lot, as there are still problems with applications crashing, and I don't want you to be frustrated. Use my Snow Leopard Guide if you need a reliable machine (link in FAQ). It's currently impossible to install Lion using your AMD machine, unless if it's a distribution. Please use Methods 1 to 3, depending on what access of hardware you have. Additionally, these range from being easy (1) to hard (3). The Retail Lion installation requires an Intel processor, and you won't be able to bypass this on an AMD machine, hence you might need to use Methods 2 or 3. Installation - Setup Method 1 - Easy Required: 10.7.3 DMG from Mac App Store + Existing Intel Hackintosh or Mac Hardware Using your exisiting Intel hackintosh machine running Snow Leopard 10.6.6 + or real Macintosh hardware, Install 10.7.3 Retail DMG to an external harddrive OR take your your exisiting hard drive and connect it to your machine using an external exclosure if needed. Once it's installed successfully move on to STEP 1. (Follow directly, don't restart, reboot). Method 2 - Moderate Required: iATKOS L2, ShowAllFiles, Existing Snow Leopard Using your existing AMD Machine running Snow Leopard. Mount iATKOS L2 DMG, and let it verify. Once verified, you'll need to ShowAllFiles, before you can see the contents of the DMG. Once ShowAllFiles has been enabled, open the DMG. Locate: System/Installation/Packages/OSInstall.mkpg and open the file. This is the Lion Installer, continue till you can customize the install. Make sure you select the correct Installation Harddrive, as you need to be careful you're not reinstalling over Snow Leopard or other important partitions. Customize the installation, however you like. Not much of this will matter, leave the default selected items. Additionally you can untick Bootloader, if you want it to be a bootable USB (Scroll down for this). Install any network/sound drivers you need. Let the installation continue and install, let it finish, and you'll have Lion installed. Once it's successfully installed move on to STEP 1. (Follow directly, don't restart, reboot). Method 3 - Hard Required: iATKOS L2, iHazard 10.6.2, ShowAllFiles, Existing Snow Leopard Download VirtualBox https://www.virtualbox.org/, and install. Download iHazard 10.6.2 ISO. Create a VirtualBox Profile and configure profile, making sure you untick Special EFI, and then load iHazard 10 6 2 ISO. Run the Virtual Profile you created and install 10.6.2. Once successfully Installed, restart. Try and run Snow Leopard with the following Bootflags: -v arch=i386 If it works, proceed. (If not, reply to topic). Remove iHazard 10.6.2 ISO from the Virtual Profile. Attach iATKOS L2 DMG to the Virtual Profile, and open it up from within Snow Leopard. iATKOS should come up. You'll need to ShowAllFiles, before you can see the contents of the iATKOS. Once ShowAllFiles has been enabled, open iATKOS. Locate: System/Installation/Packages/OSInstall.mkpg and open the file. This is the Lion Installer, continue till you can customize the install. Make sure you select the correct Installation Harddrive, as you need to be careful you're not reinstalling over Snow Leopard or other important partitions. Customize the installation, however you like. Not much of this will matter, leave the default selected items. Additionally you can untick Bootloader, if you want it to be a bootable USB (Click here for that). Install any network/sound drivers you need. Let the installation continue and install, let it finish, and you'll have Lion installed. Once it's successfully installed move on to STEP 1. (Follow directly, don't restart, reboot). STEP 1: If you've enabled ShowAllFiles yet, do so now. Open the root of the freshly Installed Lion. Replace the hidden (but shown up) mach_kernel with the one from here. (http://www.osx86.net...md!!!!!!!!.html) (Use V4). STEP 2: Install Chameleon using Chameleon Wizard on the harddrive. Additionally, you can choose to install this on a USB stick so you have a bootable USB. STEP 3: Reboot and configure your BIOS and make sure the drive that the partition is on is set as AHCI. Reboot to save your BIOS settings and you should be in Chameleon. (If you created a bootable USB with Chameleon, make sure you use Boot Priorty for your USB to load before Hard drive or press F8 (button varies), to boot the USB directly first). Type in the bootflags -legacy -v arch=i386 npci=0x3000 Step 4: It should load, and you'll be greeted with the Welcome Screen. You've now got a running machine of Lion! Proceed to install graphical, wireless and sound drivers if they're not already working. (If you used iATKOS L2, upgrade to 10.7.3 through combo updater and then replace mach_kernel and finder again, or you'll need to use another Mac or MacDrive to replace these files). Confirm your motherboard processor! BY REPLYING! CONFIRMED motherboards + processors list Motherboards Asus M2N32-SLI Asus M2N68 AM-SE2 Asus M4785TD-M EVO Asus M5A78L-M LX v2 AsRock N68-S3 MSI 870A-G46 Processors AMD Phenom II X2 550 Black Edition AMD Phenom II X3 450 Black Edition AMD Phenom II X4 955 AMD Athlon II X2 250 AMD Athlon II X2 5400+ BE AMD Athlon II X2 7550 AMD Athlon II x4 640 FAQ. Q. Do I need to replace mach_kernel if I update Lion? Yes, you'll need to do this if you're coming from iATKOS 10.7.2 to 10.7.3. You'll need to do it for future updates as well as 10.7.3. Q. Is it possible to replace mach_kernel and finder in Windows? Yes, with MacDrive. Q. I get stuck at "AppleUSBOHCI::CheckSleepCapability - OHCI Controller will be unloaded across sleep" in verbose mode. Make sure your hard drive is set to AHCI mode in BIOS. Q. I get stuck on [PCI Configuration Begin]? Make sure your use either npci=0x2000 or npci=0x3000. Q. I get stuck after [PCI Configuration Begin] or RTC: Only Single Ram Bank (128 bytes) or FakeSMC? Your motherboard has problems with USB Legacy so unplug the keyboard and mouse and see if you can boot, unplug them after you press enter after inserting your boot flags in Chameleon, you can also try by adding the bootflag: USBLegacyOff=Yes Q. Finder doesn't work? The kernel is only capable of 32 bit mode, meaning you'll need to use the Lion DP2 Finder which can be downloaded here. Replace System/Core Services/Finder.app. You'll need to replace this everytime you update Lion to a newer version. Q. -v Sometimes it doesn't load? Stuck after DMOS has arrived. It freezes sometimes, you'll need to use -x bootflag to run safe mode. Q. Does iCloud work? My Ethernet is en0, deleted Network Interfaces.plist, but still doesn't work? iCloud/Facetime doesn't work with self-compiled kernels. Appstore will work with EthernetBuiltIn=Yes bootflag. Q. Why do applications stop opening after X minutes? (Typically 10). Kernel bug, should be fixed in the future. READ BELOW FOR TIPS! The reason why applications are not functioning after 10 minutes is because Xpchelper has a bug and it's sending a lot of information to ReportCrash and it's basically nuking the system, hence system core services applications don't work after a while. You can remove ReportCrash in (sys/lib/coreserv/reportcrash) Force Quit XPCHELPER everytime you launch a system core service application like Safari, App Store, Calender, FaceTime etc. ​It won't fix it, and it will still stop working, but this prolongs the availability of opening applications and using your system for more varied tasks. Q. Do you have a Snow Leopard Guide? Yes!, you can find it here (AMD): http://www.insanelym...howtopic=253767 Bootable USB Open Charmeleon Wizard Install Charmeleon latest build to your USB stick Once completed it's ready to be used. IMPORTANT!=(When using this to boot you will need to press enter so it loads mach_kernel into the userframe before it can load futher, it'll tell you to press any key to continue because mach_kernel is not found, but once you type bootflags and try to load again, it'll work.)
  9. I made new kext as an addition to HWSensors v3.3. Compatibility with OS 10.6 - 10.10 Currently it show only CPU temperature. May be later I make voltage and frequencies. Voluntaries welcomed. I am not sure with kozlek's project compatibility. Test with precations. (kozlek's version is not newer. It is a branch with own enumeration) Manual testing without installation: sudo -s chown -R root:wheel ~/Downloads/AmdCPUMonitor.kext chmod -R 755 ~/Downloads/AmdCPUMonitor.kext kextutil -v ~/Downloads/AmdCPUMonitor.kext This kext v1.0 AmdCPUMonitor.kext.zip Other files in the project (don't install all of them! For example you don't need IntelCPUMonitor) FakeSMC_plugins_746.zip New FakeSMC with Illumination version in System Profiler and no warnings in kernel.log FakeSMC.kext_Illumination.zip Minimum set includes FakeSMC+HWInfo Recommended installation (I have no installer so I propose you will use Terminal.app) sudo -s cp -r -v ~/Downloads/HWSensors/AmdCPUMonitor.kext /System/Library/Extensions/ and so on for all kexts that will have a sense for you ACPIMonitor.kext - for devices in DSDT. Only for advanced users! AmdCPUMonitor.kext - temperature for AMD CPU Andigilog.kext - for andigilog chip. Found on some Intel motherboard AnalogDevices.kext - for chips like ADT7470-7475 F718x.kext - for Fintek chip FakeSMC.kext - obligatory for any Hackintosh GeforceSensor.kext - for new NVidia Geforce cards HWInfo.kext - if you use Clover bootloader ICHSMBus.kext - an addition for Andigilog.kext IntelCPUMonitor.kext - temperature, voltage and frequencies for Intel CPU up to Haswell ITEIT87x.kext - for ITE chip, found on most Gigabyte motherboards NuvotonNCT677x.kext - for Nuvotone chip, found on new ASUS motherboards NVClockX.kext - for old NVidia cards PC8739x.kext - for NSC chip, found on Dell Inspiron only RadeonMonitor.kext - for Radeon videocard HD4000+ W836x.kext - for Winbond chips found on old ASUS motherboards X3100.kext - for Intel X3100 (GM965 chip) Monitor application to be used HWMonitor.app_731.zip New version andigilog.kext supports EMC6D103 chip. Advantages: - no spam in system.log - CPU usage only 0.1% - no panics - supported wide range of chips. Sources are available here https://www.assembla.com/code/fakesmc/subversion/nodes/738/HWSensors
  10. Introduction: After seeing a lot of people having trouble getting the Radeon HD5450 working with Mavericks, I decided to make a guide. The card works perfectly without any graphics enabler as long as the proper device ids are in place. Guides made for Mountain Lion are obsolete because Apple changed the kext names. --- The are two ways to get the HD5450 to work properly in Mavericks: 1- Injecting a compatible fake-id (in this case, 68E01002) via DSDT. This has the advantage of using Apple's stock kexts and thus no need to re-patch kexts with every system update. 2- Adding your specific device-id to the appropriate kexts. This is probably easier, but you'll have to redo it everytime you update the system. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1- Inject a compatible fake-id via DSDT. (Recommended if you have the skills) All you need is to add the following code in the appropriate location in your DSDT (usually under PEG0, PEGP, or P0P1). PS. With this method you *must* use the original unmodified kexts. Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "device-id", Buffer (0x04) { 0xE0, 0x68, 0x00, 0x00 }, "ATY,DeviceID", Buffer (0x02) { 0xE0, 0x68 }, "vendor-id", Buffer (0x04) { 0x02, 0x10, 0x00, 0x00 }, "ATY,VendorID", Buffer (0x02) { 0x02, 0x10 }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "@0,AAPL,boot-display", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 } }) } } 2- Add the device id of your GPU to the appropriate kexts. Add your device-id to the cedar section of the AMDRadeonX3000.kext and anywhere in the AMD5000Controller.kext - Go to /System/Library/Extensions/ - Copy AMDRadeonX3000.kext and AMD5000Controller.kext to your desktop - Right click on the AMD5000Controller.kext and click show contents. - Open the info.plist (using TextEdit or any plist editor) - Find the IOPCIMatch key and you'll see many device-ids - Change any of those device-ids with yours (eg. 68981002 -> 68F91002) - Save (make sure you don't change file extension) - Right click on the AMDRadeonX3000.kext and click show contents. - Open info.plist - Find the AMDCedarGraphicsAccelerator - Under IOPCIMatch, change 68E01002 to 68F91002 - Save Use Kext Wizard to reinstall the modified kexts. =============================================================================================================== Further Considerations: 1- Power Management a- I use MacPro3,1 smbios to avoid loading AGPM and my temperature and performance are very acceptable. b- You can experiment with different smbios (mainly iMac11,2 and 11,1) which will load AGPM. 2- Framebuffers: a- You can either use the Eulemur or the Generic framebuffer. My tests show no performance difference. b- Eulemur breaks sleep with DVI and HDMI monitors. VGA works fine though! c- Clover and Chameleon will automatically set framebuffer to Eulemur so I strongly recommend you disable the graphics injector features. 3- VESA modes (aka. boot resolution) a- Chameleon's resolution module can patch the vbios and give you full resolution during boot. b- Clover's built-in vbios patcher works perfectly too. c- VGA does not work in either case. The bootloader fails to read the EDID to obtain the optimal resolution. 4- Clover: a- Clover's graphics injector has the ability to inject a fake id b- As stated before, the injector automatically set framebuffer to Eulemur and thus breaks sleep.
  11. Hello! Does anyone know if R9 285 or R9 280 work OOB in Yosemite?I know for sure that R9 280X does,but I'm not sure about these two cards..I haven't found many topics in which they are mentioned, and I want to be sure that HDMI and DVI work OOB..has anyone tested them?I don't want to buy a graphics card and then have to return it and buy another one..
  12. Version 1.3

    5,678 downloads

    AMD Radeon GPU pack is a post-installation tool specifically designed for Clover boot loader. The tool contains patches and injectors for various AMD Radeon graphic cards, but also additional plugins for MacPro3,1 and MacPro6,1 SMBIOS specifications and Sandy Bridge CPU-s. How it works: The tool will add just a few FB code lines for proper GPU activation in Clover config.plist file (ATI Connectors Data, ATI Connectors Patch & ATI Connectors Controller). • Be advised that patches depend on card manufacturers. • The list of patches and injectors are based on certain GPU models and extracted ROM files from them. • Injectors from this tool will work on most models, but not on all of them. • That’s because certain GPU cards from the same series using the slightly different firmware. Injectors & patches: AMD Radeon HD 6450 (device id - 0x6779) AMD Radeon HD 6790 (device id - 0x673E) AMD Radeon HD 6850 (device id - 0x6739) AMD Radeon HD 6870 (device id - 0x6738) AMD Radeon HD 7730 (device id - 0x6837) AMD Radeon HD 7870 (device id - 0x6818) AMD Radeon R9 270 (device id - 0x6811) AMD Radeon R9 270X (device id - 0x6810) AMD Radeon R9 280X (device id - 0x6798) AMD Radeon R9 290X (device id - 0x67B0)
  13. 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
×