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. We made history here! Now Mountain Lion works on AMD Machines. The support is still limited to Phenom and FX-Series CPUs, but soon we'll have fixes for other CPU models ALL CPUS, but nVidia GPUs won't boot without either safe boot (-x) or disabling GeforceGA.plugin and GeforceGLDriver.bundle (thus no QE/CI - hopefully a fix will come soon). amd_kernel.zip -----> latest kernel: credits to Andy Vandjick! (Pag 74, post #1468) This kext is obligatory: you must install it before starting your machine: http://cl.ly/0o3s0d2c001A -----> AnVsCoreCrypto! No more need for any patched kext. Thanks to all that developed, tested, commented, helped to spread the news, to all who believed in what was deemed impossible. Success was our reward, and i'm very proud of it. Happy new year! EDIT: We have an IRC room for talking about development of a Mountain Lion working kernel for AMD and other unsupported CPUs. Join us! Server chat.osx86.hu, room #LegacyKernel Well, i suppose we're lucky for Apple's early release of its Mountain Lion kernel as open source. Thanks to this, a patched Atom kernel is already done, although it doesn't work on my little Atom netbook. Hopefuly, an AMD patched kernel will be around soon but, as everybody should know, this one will be a troublesome build. The AMD kernel for the now superseded Mac OSX Lion is very limited, to be kind. In most AMD machines, basic functionalities doen't even run, like - yes, believe it! - the Finder. It could be quite useless, but it's not, thanks to many alternatives and workarounds to be found at the community. The problem for AMD is that any patched kernel since Lion is strictly i386. To have access to 64 bit apps in an AMD Lion install, it's necessary a Buldozer CPU, since it has support for a key instruction set in OSX Lion, the ssse3 (please, don't confuse it with sse3). All other AMD processors should run strict 32-bit, forbidding crucial apps like the newer xcodes. A solution for this would be a sss3 emulator. Anyone willing or able to write? (silence) As i already knew. But even when some good-willing and capable-minded individual(s) do write the emulator, there's another issue: maybe Lion would be good to go with AMD, but Mountain Lion needs a 64-bit-only legacy kernel. And 64-bit legacy kernels equals instant reboots in AMD rigs in Lion, even on ssse3-capable Buldozer machines. You can try it for yourself, with a 64-bit patch of RAW x86 (boot with arch=x64_86): http://osx86.co/f100...687/page23.html The question: is it really needed to figure out why these problems plague Lion running on AMD to make AMD work under Mountain Lion? Or the behavior of 64-bit patches would be completely different in ML? Anyway, it seems obvious to me that a sss3 emulator is crucial, since the vast majority of AMD systems are non-Buldozer. So, there's an anxious waiting at AMD realm, to finally get an early update of AMD systems, to be shoulder to shoulder with Intel users.
  2. Rampage Dev

    Patched Framebuffer Repository

    about: This is a Repository for ATI and AMD patched Framebuffers. Here you will find a complete list of successfully patched framebuffers for ATI and AMD Graphics Cards. This is not a support page so do not post questions on this page. Start a new topic if you have questions. Thank you for your cooperation. Framebuffer Editing Guides: BCC9′s post that can be found here Alexander Martinez’s post that can be found here Mucha’s post that can be found here Posting Guidelines: The following are the posting guidelines for this page. Failure to follow set guidelines will mean that the patched framebuffer will not be posted on the first post. Thank you for your cooperation. Graphics Card Model: Graphics Card Manufacture Name: Graphics Card Manufacture Part Number: Fixed by: Patched Framebuffer:
  3. Mostly because of my partly success in making proper patch for all Radeon R9 270 Series GPU-s described in Radeon R9 270X FrameBuffer issue topic, but also because I see that many of you are still searching for some sort of help, I was coming to an idea to share some of my conclusions via this tutorial, in hope that it will resolve all of your current troubles. Once when you check this tutorial and you use it, you will understand better where is the problem and eventually, after you determinate what is what you will be able to fix it. It is important to say, that this tutorial is universal and it can be used for any AMD GPU. So lets start… Modifying the AMD driver is one of the advanced hacker's technique, however, recently with clover in combination, the whole process can be reduced to a decent minimum. This tutorial aims to discover what specific digits in the code do and basically to educate so that everyone can make necessary modification alone and w/o further assistant. All you need is a bit of good will and some patience. --------------------------------------------------------------------------------------------------------- Extracting ROM file - Step 1 involves extraction of the original ROM file from your graphics card. This could be done from Windows by applications such as GPU-Z or some other similar, or from Mac OS X via DPCIManager application. Extracted ROM file you’ll need to save and then switch again in your Mac OS X. --------------------------------------------------------------------------------------------------------- Finding proper FB - Step 2 involves finding proper frame buffer that can be used by your GPU. In order to do this properly, we will need a terminal and corresponding ATI FrameBuffers script. We need this one to extract FB code inside AMDXXXXControllers.kexts. Download ATI FrameBuffers php scripts by Pavo. Unpack the zip file on the desktop, then switch to terminal. Type php then simply drag the script in the terminal and press enter. What you’ll get is a long series of codes together with the exact names of the frame buffers inside certain AMD Controller kexts. Although by using this patching method we can modified any FB, it is recommended that you find the proper one for your GPU, which might already work with your card. The point with this is to locate those that contain the same number of connectors, so per example: My GPU has 4 connectors: 2xDVI, 1xHDMI and 1xDP - so this means that I need to use FB with 4 connectors. In the AMD personality dump file, just under the first line with FB name, we can find info that we need. Personality: Futomaki ConnectorInfo count in decimal: 4 So this means that I should check those FB-s first. Copy the code from the terminal in the Text Editor and save it on the desktop. Then take a look carefully extracted code, and write all frame buffers from the AMD Controller kext that drives your video card. For example, Radeon R9 270X that I’m using, is driven by AMD7000Controller.kext which containing the following list of frame buffers: MaguroS, Maguro, KaniS, Kani, Junsai, IkuraS, Ikura, OPM, Hamachi, Futomaki, Gari, Ebi, Dashimaki, Chutoro, Buri, Aji. For Radeon 6850HD it is necessary to look at the list of FB extracted from AMD6000Controller.kext, etc. ... Now that you have the names of FB-s you will need to determine which of them your card can use. The simplest way of doing this is Clover, although it is possible to do the same thing with Chameleon boot loader, but I'll be focusing exclusively this time on Clover. So open Clover Configurator and in the Graphics section of the FB Name field, type the first FB from your list. Then restart computer and reboot again in OS X. If all goes well, your graphics will work immediately (with or without GL quartz enabled), however, there are two more situations that may occur. First one is a situation where you will get a black screen, but the monitor will stays on. This also means that assigned FB works, but the connectors code inside dedicated AMD Controller kext is mismatched. In this situation pressing the ALT+CMD+Eject buttons on Apple keyboards and WIN+ALT+F12 on PC keyboards will simply sleep your computer. After waking from sleep your computer will activate the screen again. Basically, this is the one of the most common situation which requires further patching. In all other situations, most likely your monitor will automatically be switched off. This means that the assigned FB does not work, or another word that is not compatible with your GPU. In this situation my recommendation would be that you simply restart your computer. The best way to do that is to implement the software restart by pressing CTRL+CMD+Eject buttons on Apple keyboards or for PC keyboards that would be CRTL+ALT+F12, after which the computer will just restart immediately. By modifying Clover Boot options from its menu, where you can rename assigned FB or simply remove all enabled Graphics options that you are previously assigned, you will be able to re-boot OS X normally again. Basically, this is the part that will certainly take you some time before you discover which FB best suits to your card, but when you do this, you're ready for the next step. --------------------------------------------------------------------------------------------------------- FB Code Construction - Step 3 is the most important and involves modifying the original driver or more precisely, it considers changing hexadecimal values inside the driver that are defining the connector output signal from your graphic card. For this maneuver we will need correct values extracted from the existing ROM file, and that can be done through the two scripts: radeon_bios_decode and redsock_bios_decoder scripts. It is necessary to use both because they are giving different results. Basically only with both results we can collect all the necessary data that we need. Scripts can be used in a similar way. You’ll need to open the terminal, drag the first script in a terminal then press once space, than type < than once space again and now drag your ROM file in the terminal and simply hit Enter. The obtained result will look something like this (example R9 270X) localhost:~ Vladimir$ /Users/Vladimir/Developer/Ati\ Workbench/AMD\ Graphics\ tool/Radeon\ BIOS\ decoders/radeon_bios_decode < /Users/Vladimir/Developer/Ati\ Workbench/AMD\ Graphics\ tool/AMD\ BIOS/Pitcairn.rom radeon_bios_decode will give the following result: ATOM BIOS Rom: SubsystemVendorID: 0x148c SubsystemID: 0x2336 IOBaseAddress: 0x0000 Filename: E8B11LCC.HHW BIOS Bootup Message: C63101 CURACAO XT 2GB GDDR5 64Mx32 E8B11LCC.HHW 2013 PCI ID 1002: 6810 Connector at index 0 Type [offset 43522]: DisplayPort (10) Encoder [offset 43526]: INTERNAL_UNIPHY2 (0x21) i2cid [offset 43632]: 0x90, OSX senseid: 0x1 Connector at index 1 Type [offset 43532]: HDMI-A (11) Encoder [offset 43536]: INTERNAL_UNIPHY2 (0x21) i2cid [offset 43659]: 0x92, OSX senseid: 0x3 Connector at index 2 Type [offset 43542]: DVI-I (2) Encoder [offset 43546]: INTERNAL_UNIPHY (0x1e) i2cid [offset 43696]: 0x95, OSX senseid: 0x6 Connector at index 3 Type [offset 43552]: DVI-I (2) Encoder [offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [offset 43696]: 0x95, OSX senseid: 0x6 Connector at index 4 Type [offset 43562]: DVI-D (3) Encoder [offset 43566]: INTERNAL_UNIPHY1 (0x20) i2cid [offset 43723]: 0x94, OSX senseid: 0x5 redsock_bios_decoder will give the following result: E8B11LCC.HHW: C63101 CURACAO XT 2GB GDDR5 64Mx32 E8B11LCC.HHW 2013 Subsystem Vendor ID: 148c Subsystem ID: 2336 Object Header Structure Size: 355 Connector Object Table Offset: 48 Router Table Object Offset: 0 Encoder Object Table Offset: fd Display Path Table Offset: 12 Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true Connector Object Id [2] which is [DVI_I] encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [2] which is [DVI_I] encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 0x10 enc)] linkb: false Connector Object Id [4] which is [DVI_D] encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Copy and paste the results into Text Editor and save it. Then extract the following items from both results like in this example by following the color order: 01 [DISPLAY_PORT] redsock_bios_decoder : enc obj 0x21 transmitter 0x12 dual link 0x2 enc 0x4 radeon_bios_decode: Connector at index 0 Type [@offset 43522]: DisplayPort (10) Encoder [@offset 43526]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 43632]: 0x90, OSX senseid: 0x1 Code construction: 12 04 01 01 02 [HDMI_TYPE_A] redsock_bios_decoder : enc obj 0x21 transmitter 0x22 dual link 0x2 enc 0x5 radeon_bios_decode: Connector at index 1 Type [@offset 43532]: HDMI-A (11) Encoder [@offset 43536]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 43659]: 0x92, OSX senseid: 0x3 Code construction: 22 05 02 03 03 [DVI_I] redsock_bios_decoder : enc obj 0x1e transmitter 0x10 dual link 0x0 enc 0x0 radeon_bios_decode: Connector at index 2 Type [@offset 43542]: DVI-I (2) Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 43696]: 0x95, OSX senseid: 0x6 Code construction: 10 00 03 06 04 [DVI_I] redsock_bios_decoder : enc obj 0x15 transmitter 0x00 enc 0x10 radeon_bios_decode: Connector at index 3 Type [@offset 43552]: DVI-I (2) Encoder [@offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 43696]: 0x95, OSX senseid: 0x6 Code construction: 00 10 04 06 05 [DVI_D] redsock_bios_decoder : enc obj 0x20 transmitter 0x11 dual link 0x1 enc 0x2 radeon_bios_decode: Connector at index 4 Type [@offset 43562]: DVI-D (3) Encoder [@offset 43566]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 43723]: 0x94, OSX senseid: 0x5 Code construction: 11 02 05 05 Now let's look at the original source code extracted from the original driver for the FB Futomaki that activates R9 270X: Personality: Futomaki 10.9.2 ConnectorInfo count in decimal: 4 Disk offset in decimal 811280 00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 Each row represents definition for the one connector. In this case we have 4 of them. In order to better understand what is what I will separate first line from the code as an example: 00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 Divided into segments: 00 04 00 00 / Connector type 04 03 00 00 / ATY, ControlFlags 00 01 01 01 / Features 12 / Transmitter 04 / Encoder 04 / hotplug ID 01 / Sense ID What this means? First I’ll put the list of all types of connectors: Connector Type LVDS 0 × 00000002 = 02 00 00 00 Note: Laptop Monitor Connector Type DVIDL 0 × 00000004 = 04 00 00 00 Note: Dual Link DVI Connector Type VGA 0 × 00000010 = 10 00 00 00 Connector Type SV 0 × 00000080 = 08 00 00 00 Connector Type DP = 0 × 00000400 00 04 00 00 Connector Type HDMI 0 × 00000800 = 00 08 00 00 Connector Type DVISL 0 × 00000200 = 00 02 00 00 Note: Single Link DVI So now it's clear that first 4 pair of numbers represents the type of connector in the code: 00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 / Display Port 00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 / Display Port 04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 / DVI-D 00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 / HDMI Constructed FB is made this way, mostly due to the fact that Apple monitors are using DP as the primary connection and then we have beneath in order all others. In the vast majority of cases there, you will need to change only the last 4 digits, which are also the most important for proper connector injection, or eventually you will need to assign further a DVI-I (SL) connection for your monitor. In this case, it is basically a mandatory thing mostly because the original code does not have it. Therefore, we will need to change the second row from DP into DVI-SL. The initial input of first four pairs of digits we will need to change from 00 04 00 00 to 00 02 00 00, which is the proper input for DVI-SL. 00 02 00 00 Then follows the explanation of the second set of digits: 0×0002 : LVDS ControlFlag : 0×0040 and 0×0100 0×0004 : DVI ControlFlag : 0×0016, 0×0014, and 0×214 0×0010 : VGA ControlFlag : 0×0010 0×0080 : S-Video ControlFlag : 0×0002 0×0200 : DVI ControlFlag : 0×0014, 0×0214, and 0×0204 0×0400 : DisplayPort ControlFlag : 0×0100, 0×0104, 0×0304, 0×0604, and 0×0400 0×0800 : HDMI ControlFlag : 0×0200 0×1000 : DVI ControlFlag : 0×0016 Translated in to: Connector Type DP 04 03 00 00 Connector Type DP 04 03 00 00 Connector Type HDMI 00 02 00 00 Connector Type DVIDL 14 02 00 00 Connector Type_DVISL C 04 02 00 00 Connector Type_DVISL 04 02 00 00 From this example it is clear that in the modified row we should add further 04 02 00 00 according to the matched connector name. So after first 00 02 00 00 we will need to add the following 4 pair of digits 04 02 00 00 and all together it looks like this: 00 02 00 00 04 02 00 00 The following is the part that relates to the ATY,Features (hex digits): The first pair of numbers: 0 × 0002: LVDS * 0x09 = 09 0 × 0004: DVI 0x00 = 00 0 × 0010: VGA 0x00 = 00 0 × 0080: S-Video 0x04 = 04 0 × 0200: DVI 0x00 = 00 0 × 0400: Display Port 0 × 00 = 00 0 × 0800: HDMI 0 × 00 = 00 0 × 1000: DVI 0x00 = 00 The second pair of numbers: Use Internal * 0 × 01 = 01 Use RGB YUV On 0 × 04 = 04 Use Backlight * 0 × 08 = 08 Backlight Inverted 0 × 10 = 10 Use Clamshell 0 × 20 = 20 A third pair of numbers represents the order of connector activation 01 = first active connector 02 = second active connector 03 = third active connector etc. ... I suggest that you mark as first, connector raw that your monitor will use it as primary. The fourth two numbers are listed as Unknown: You can leave the same like in the original code (usually stands 01 or 00) or simply replace it with zeros - 00. I will in this demonstration left the original values: Finally, we add the following digits: 00 02 00 00 04 02 00 00 00 01 01 01 Last four digits simply rewrite from the above constructed table: 03 [DVI_I] redsock_bios_decoder : enc obj 0x1e transmitter 0x10 dual link 0x0 enc 0x0 radeon_bios_decode: Connector at index 2 Type [@offset 43542]: DVI-I (2) Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 43696]: 0x95, OSX senseid: 0x6 Code construction: 10 00 03 06 I will explain in short, what is what here, but that would not be important much anyway. The only one thing important it is the order of digits that we need to use and the patch will work. So here it is: Transmitter - the first two digits Encoder - the second two digits Hotplug ID - third two digits Sense ID - Fourth two digits --------------------------------------------------------------------------------------------- So that was detail explanation, however, we can simplify this procedure by using next basic code schematics per connector: LVDS / 02000000 40000000 08010000 / + (add your code construction) VGA / 10000000 10000000 00010000 / + (add your code construction) DP / 00040000 04030000 00010000 / + (add your code construction) DVI-SL / 00020000 04020000 00010000 / + (add your code construction) DVI-DL / 04000000 14020000 00010000 / + (add your code construction) HDMI / 00080000 00020000 00010000 / + (add your code construction) As you can see, all you have to do is to add the last 8 digits which you need to construct by yourself (see example above) Sierra is using additional digits in the code, so you'll need to add extra zero segments in front of your code construction and after it. Check example bellow: 00080000 00020000 00010000 00000000 + (add your code construction) 00000000 ----------------------------------------------------------------------------------------------- So this is it, and here we have final construction. 00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06 Except for the above modification, like I said, in most cases you will need to replace only the last four values: Original code: 00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 - DP 00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 - DP 04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 - DVI-DL 00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 - HDMI Modified code: 00 04 00 00 04 03 00 00 00 01 02 01 12 04 01 01 - DP 00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06 - DVI-I 04 00 00 00 14 02 00 00 00 01 03 00 11 02 05 05 - DVI-D 00 08 00 00 00 02 00 00 00 01 04 00 22 05 02 03 - HDMI With this, the whole thing is completed and you are now ready for the final step. --------------------------------------------------------------------------------------------------------- Clover Injection - Step 4 involves injection of the code and its activation. This can be done in several ways: kext patching by some hex tool or making the Binary patch, however, none of these methods are sufficiently elegant, mostly because in this case we will need to patch driver every time when we make system upgrade. Luckily we have a Clover, which is able to apply such modification "on the fly" which is ideal concept, or other words, this method represents a permanent solution that does not depend from the future system upgrades. Open Clover Configurator, and go to the Kernel & Kext patches. Click on the plus sign in the KextsToPatch field : Then type the name of the kext you want to patch, in this case this is AMD7000Controller. In the next field, enter the original hex code extracted from the driver, and next to it write a new one that you have created. Eventually, you can add notes in the next field (par example: Connectors patch) and that was it. You are ready for testing. If you are all done properly everything will work from the first attempt. If not you will need to work further on it. But if something goes wrong, you can always change the name of the FB or simply to uncheck the options that you have activated in the Graphics panel and thus everything will be back to its initial state. Decoders.zip ATI-framebuffers.zip
  4. I'll just clarify that this section isn't for "omg how to get mountain lion / lion / snow leopard running on AMD". The section is named "AMD Development". This basicly means that this section is dedicated to developing, not asking help. I know I've done this even by myself, but now it's kinda out of control, everyone asking about installing ML on AMD etc. The 3 threads (SL / L /ML) should be dedicated to development of kernels and other related stuff and reports of the developments, not asking "how to get it running i get error". If you need help with AMD on SL for example, you should post on the installation help or if you followed a tutorial, ask the tutorial thread. However, I do not suggest asking with PM, because then other people can't get the same information as easily, and it's not funny to see inbox full every minute. Also, if you need help with the test kernels for SL / L / ML, you can post on this thread, I'm sure there are people ready to help you with your errors. Let's just keep the "development" threads clean of the "spam" / stupid questions (even if there isn't any). For real-time help, download an IRC client and join us: chat.osx86.hu #LegacyKernel And when you get your build running, please post here! Thanks!
  5. As I see many novices in the forum ask "How to make my Radeon working? I have bad resolution, no QE/CI...." and so on. They come to the section and have no find an answer here because all Radeons are different and they don't know where else they read about this. I want to explain all steps needed for launching the Radeon family of videocards. Bootloader. I will speak about Clover because I maintain this bootloader to know recent hardware and modern OSX. Not sure if you will have the same result with other bootloaders. I am carefully checking the injecting of ATI card and correcting it times to times. I am also accessible for bug reports. OSX version. Older card require older system, newer cards require new system. ATIRadeon9000 is possible to launch under Tiger. ATIRadeonMobilityX1400 requires 10.5-10.6. See RadeonHD topic. As I see RadeonHD3xxx was successful only in 10.5 For new AMDRadeonHD7xxx there must be 10.8.3+ system. DeviceID. This must be the first question before asking about the card. You may know the device-id from Windows->DeviceManger->VideoCard.properties->compatibleIDs You may boot into system in safe mode (key -x) and see system profiler And you may boot into Clover GUI, press F2 and get preboot.log. Find here something like 2:709 0:000 PCI (00|01:00.00) : 1002 6758 class=030000 2:709 0:000 Found Radeon model=AMD Radeon HD 6670 Series It means my DeviceID=6758 (these are hex numbers) Then you must check that Apple's drivers support your DeviceID. If not then add it! For example HD7850 has DeviceID=6819. If we look into ATI7000Controller (AMD7000... in new systems) we find 6818 here but no 6819! I show you how to do this with terminal commands. Launch /Application/Utilities/Terminal.app. Type in opened window: cp /System/Library/Extensions/ATI7000Controller.kext/Contents/Info.plist ~/Desktop So you get a copy of the Info.plist on Desktop. Edit it with TextEdit. Change 68181002 -> 68191002. Don't edit this file directly in the system folder! Then copy back by terminal. Don't use finder to copy kexts! They will have wrong permissions in this case. sudo cp ~/Desktop/Info.plist /System/Library/Extensions/ATI7000Controller.kext/Contents/ sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/* Second command make sure next reboot the kext will use your edited info.plist. The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you. FakeID Since Clover revision 1971+ you may just inject new DeviceID into DSDT instead of correcting kexts. See instruction here. GraphicsEnabler or Injector OSX needs to know some properties (Model name, Family, etc...) that must be somehow injected at boot time. Yes, also real Macs got DeviceProperties string from firmware. Alternatives: 1. Set InjectATI=Yes in Clover (same as GE=y in Chameleon). 2. Use custom string made with gfxutil. For whom who knows. 3. Write _DSM into DSDT. You should know what to write. 4. Use some kext like ATY_init.kext or Natit.kext. If you are sure that the kext is for your card namely. I want to say that all this methods make the same thing. Differencies in their tuning. The Clover do this automatically for most known cards at this moment. Connectors. As you may see to start HD5000-7000 some strange names used: Pithecia, Orangutan, Elodea... What are they? They are configs for framebuffer. Predefined configs how connectors are solded for cards used in real Macs. Strange but these configs rear coincide with PC card. Usually gurus make advice "choose a framebuffer that most appropriate for your card". The chances 1:10. In most cases you may find a FB name that gives you main monitor working. Or nothing at all. Great respect to bcc9 who gives us a method to correct one of config to be exactly for you. See here. My retelling for Clover is here Success example in the thread in posts 44-52 Radeon Mobility I tested Clover's methods with two users having Mobility Radeon HD5470 and HD5650M. We found that full memory and QE/CI will be achieved if we set in Clover's config LoadVBios=Yes even thou no file with bios is provided. This is the key to make Radeon Mobility working! Other problem is bad gradients or artifacts. For this case Clover accept the key InjectEDID=Yes and sometimes you also need to inject CustomEDID. See Clover instructions for details. And my results. Gigabyte Radeon HD6670 <key>Graphics</key> <dict> <key>GraphicsInjector</key> <true/> <key>InjectEDID</key> <true/> <key>FBName</key> <string>Ipomoea</string> <key>LoadVBios</key> <false/> <key>VideoPorts</key> <integer>3</integer> <key>PatchVBios</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>6000</string> <key>ATIConnectorsData</key> <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string> <key>ATIConnectorsPatch</key> <string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string> VTX Radeon HD5570 <key>Graphics</key> <dict> <key>PatchVBios</key> <false/> <key>FBName</key> <string>Baboon</string> <key>VideoPorts</key> <string>3</string> <key>GraphicsInjector</key> <string>Yes</string> <key>LoadVBios</key> <string>No</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>5000</string> <key>ATIConnectorsData</key> <string>040000001400000000010000010201030008000000020000007100002205020110000000100000000001000000100002</string> <key>AppleRTC</key> <true/> <key>ATIConnectorsPatch</key> <string>040000001400000000010000010001040008000000020000007100002200020510000000100000000001000000000002</string> <key>AsusAICPUPM</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleAHCIPort</string> <key>Find</key> <data>RXh0ZXJuYWw=</data> <key>Replace</key> <data>SW50ZXJuYWw=</data> </dict> </array> </dict> See PatchVBios=No for this card "yes" leads to black screen. Use with precautions. A sample for Radeon R7 240 UPDATE for ElCapitan. It seems has more problems. My HD6670 is not working in ElCapitan OOB unlike Mavericks. I had to set FakeID=0x67401002 as correspond to real iMac12,2 and set this model in SMBIOS section. It related to GraphicsPM or GraphicsControl. Look these kexts to decide what you can do for your configuration. HighSierra requires change these kexts by version from Sierra 10.12.6 for Radeon HD6xxx AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext . for Radeon HD7xxx and up AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext . Black screen after wake problem resolved by follow method radeon_bios_decode.0.2.zip ati-personality.pl.0.15.zip ati-personality.pl.0.15a.zip
  6. 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
  7. 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
  8. OK well I'v sucseeded, i've installed leopard in virtualbox on amd the distro to use is kalyway.
  9. Well after 3 excruciatingly long days I have finally done it! I manged to get OSX 10.6.8 installed on my AMD machine but i'm still stuck in a few places... I am a super noob at this but good with tech work in general. I'm a Programmer/Web Developer/Hardware/Software Support guy by trade. hardware info: AMD FX4100 ATI HD5450 Gigabyte GA-880GM-UD2H So I used ModCD and a retail copy of 10.6.3 with the following flags: rd(0,0)/Extra/modbin_kernel arch=i386 legacy_kernel cpus=1 busratio=17 colors=32 GraphicsEnabler=No After a successful install I still couldn't get my machine to boot without a few flags: busratio=17 colors=32 UseKernelCache=No npci=0x2000 Once I finally reached the OS I did the following: Ran the Apple Combo Update for 10.6.8. Before rebooting installed legacy kernel AMD for 10.6.8 Ran Mulitbeast 3.10.x and installed all kexts, fixes, and ##### stuff Committed the second set of flags above to my org.chamelon.boot.plist Rebooted So the machine currently boots and runs but adding the ati5000injector.kext for my HD5450 to my Extras/Extensions folder causes the boot process to stall until it's removed. It seems to stall at the NvClockX loading process which i'm guessing is some sort of nvidia driver. Can I remove these drivers or is there a better way to get my ATI card to work? Can I fix my boot process so I don't have to use so many hardcoded flags to get it to start? Thanks in advance -Mike
  10. Hi, HELP!! haha System Specs are as follows: ASUS M4N98TD EVO Motherboard with Nvidia MCP78 and NF200 chip - VIA 1708S sound AMD 1090T X6 at 3.9GHz MSI GTX 660 Gaming 10de 11c0 8GB DDR3 1600mhz Ram I have successfully installed Snow Leopard but cant seem to update it past 10.6.3 without Kernel Panics, I also believe that support for the GTX 660 is not good. Using my snow leopard install, I created a Mountain Lion USB installer with the amd_kernel - using the boot flags: amd_kernel cpus=1 busratio=18 npci=0x2000 USBLegacyOff=Yes PCIRootUID=0 -v -f I managed to get the installer to run and install, it completed and said installation successful. I haven't been able to boot into the OS as yet however. All seems to be going well, with the kexts loading and SUCCESS coming up everywhere, then after macosx_swapon which is OK the loading seems to grind to a halt, it loads NVGK100Hal and also finds my Bluetooth dongle, assigns an internet address but just gets no further, it seems to be stuck just before it would normally say DSMOS has arrived.... Any ideas would be most gratefully received....Many Thanks
  11. There is an utility to analyze Radeon Video Bios http://www.phoronix.com/scan.php?page=article&item=amd_atombios_dumper&num=1 My compilation for OSX atomdis.zip Usage ./atomdis c0000.bin F >bios_info.txt where c0000.bin is an BIOS image obtained by Clover with F6. I expected someone found this utility useful.
  12. Fabio1971

    Nuovo Sub-forum per Installazione "AMD"

    Nuovo Sub-forum "AMD" In questa Nuova Sezione potete creare i vostri Topic su piattaforma "AMD" per Lion. Fabio
  13. GingerBraFace

    Installation success but can't boot. (fx-9590)

    I have successfully installed Mavericks (10.9.1 I think) to an internal 500gb HDD dedicated to Mavericks. I used myhack to make the installer and then copied a custom kernel onto to external drive. This is the kernel I used for the installation: http://www.insanelymac.com/forum/files/file/181-amd-109x/ I had to use the bootflags "GraphicsEnabler=No npci=0x2000" in order to boot the installer. But I can't boot the now installed Mavericks using the bootloader on the external drive I used to install it (the myHack one). I've tried various different bootflags with no success. I have also tried all the kernels I could find with no success. Is it a bootloader issue? Or am I doing something really stupid? My Specs: motherboard: sabertooth fx990 cpu: fx-9590 Graphics: GTX 760 RAM: 8GB (Cosair Vengance 1600MHz) HDDs (if relevant): 1TB Seagate Barracuda: Windows 8.1 2TB Seagate Barracuda: NTFS Space 500GB Western Digital Blue: Mavericks Even if you don't know a solution, any ideas are appreciated. Cheers!
  14. SAMEH209

    AMD 5570 HDMI Audio not working

    Hi all, I just installed Yosemite on my pc..everything is working fine till now except HDMI audio..it's not showing up in the "Output" in sound preferences..on-board is working fine. My specs are: M.B: Gigabyte G41MT-S2P VGA: AMD 5570 1GB connected to Samsung monitor through HDMI. RAM: 4GB Please help..Thanks!
  15. Whaka

    applications 32 bits crash

    hello, et oui... toujours entrain de me battre avec ce bon vieux leopard des neiges mais là, c'est sur amd (faut bien varier un peu ) alors, je résume en tres gros : la machine : HP DC5750 microtower. amd athlon 64 X2 4200+ chipset ATI 4 Go de ram en 10.6.8. la machine fonctionne assez bien (j'aurais d'autres questions, mais ce sera dans un autre sujet) j'ai donc un systeme qui démarre en full 64 bits, mais, les app 32 bits (ou en mode 32 bits) ne fonctionnent pas, elles plantent des le lancement. j'ai essayé avec 2 kernel, celui de anv et celui de nawcom, c'est pareil. j'ai essayé en elenvant 1 Go de ram : c'est pas mieux. j'ai essayer de patcher avec "amd_insn_patcher V2" : c'est pas mieux. voilà, donc est ce que c'est possible d'avoir un systeme full 64 bits qui soit fonctionnel avec ces kernel ? ou est ce qu'il existe une solution à ça ? j'ai un peu googlé, mais c'était pas tres fructueux... merci d'avance
  16. giofrida

    Disabling ATi Card through DSDT

    Hi everyone! I'm here to talk about disabling the discrete ATi Card through DSDT like disabling Nvidia Optimus. That's my situation: Intel HD Graphics (1ST Generation) - Full QE/CI + Resolutions ATi Radeon HD 5470M - Can't use it, my PC boots up with the integrated card. But I can use it with a BIOS mod (I don't want to do that, because there are some issues on Windows). Using Nvidia Optimus guides, I managed to reach a result: (Look at Core GPU Temperature) boot: after waking up my laptop from sleep: What I did Step 1 - Extract SSDTs from AIDA64 / Linux Step 2 - Find the SSDT table named "AmdTabl" (AMD Table) In this table I saw this method which should disable the card: Step 3 - Copy all the SSDT into your (pre-patched) DSDT Step 4 - Fix all the errors Step 5 - Make a new PINI method Method (PINI, 0, NotSerialized) { \_SB.PCI0.P0P2.PEGP._OFF () } and call it in _WAK method and in _DSM method in your IGPU device Now I need some help. Here for reference are all my tables and my final DSDT: dump.zip
  17. redheadturkey

    Possible to Hackintosh?

    My setup: Asus m4a79xtd Evo motherboard AMD Athlon II 3.2 ghz Rana processor, all four cores unlocked AMD 4600 HD graphics card Dynex network card (Runs off Realtek drivers) I am also running a Logitech g35 headset, but they have the driver software available for a mac, so not worried too much about that. I tried it before, with a distro, and it would get as far as booting to disc but then boot loop while trying to install. Clear instructions and links to all of the patches I might need would also be well appreciated, the use of the one distro I ifollowed the directions given and it still bootlooped me. Thanks. Edited to add: I am fairly tech savvy (I have rooted both mine and my husband's android phones and installed custom roms, no problem, and have also jailbroken my playstation portable and put custom firmare on it, if that is any indicator. XD) I just need to know *exactly* what I may be doing wrong so I can fix it. Also to add: I am going to bookmark that link, mod can delete dup post.
  18. Hello everyone. I have been trying to install os x Mavericks for a long time, but it gives me lot of problems so I came here to see if I could fix it somehow. Well, first of all I will give some information about the computer I'm trying to install it on: It's an Asus with uefi, EZ mode, 2001 version. Motherboard: A88XM-A CPU: AMD A4-6300 Dual core, 3,69 Ghz Internet: Realtek 8111G Sound: Realtek ALC887-VD Graphics: Integrated AMD Radeon HD graphics First, I tried with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], but it turned off as soon as it entered the apple logo screen. Then, I tried with Niresh. It installed, but the graphics were laggy and the internet, the sound, and well the graphics in general weren't working. I tried to install the kexts but didn't find them or either didn't know how to install them. And in addition, it gave me the boot 0 error. And now is when the real problem comes, I have tried using myhack. I have done all the proccess correctly, and now in the guide i've been following it says I have to replace the mach_kernel for a downloaded one that works for amd and mavericks. I have downloaded the os x mavericks installer from the Appstore but I belive it is the 10.9.5 version of it. Anyway, in case it was the 10.9.4 when I replace the kernel and rename it, after have intalled os x on the computer with amd, I then copied using the installer and the terminal, and removed the kernel from the hard disk, and then copied the one that works for it. Well, when I try to turn it on it suddenly turns off. I put it in verbose mode to see wheres the problem and it says: "Can't find mach_kernel" I have copied the commands and such correctly, and the names of the hard drive and USB too. I really don't know what to do. Thanks in advice, I'll be looking forward to hearing from you. If I break any forum rules please tell me and I will fix it, thanks again and greetings.
  19. I'm really a noob to this, so forgive me if I ask stupid questions. I really think I just need guidance that I'm heading in the right direction. I used Fuision71au's guide along with some others on the internet to get a Virtualbox VM up and running and imessage working using clover. I'd like to run this on more of my pc's including some AMD FX based ones. My thought was that I could boot the VM on intel, make the changes necessary for AMD and then copy it over to the AMD machine. My understanding is that I need to swap the kernel out for the AMD kernel. I have the kernel and I know it goes into /System/Library/Kernels. 1. I can't just copy the kernel in, because it tells me that the operation is not permitted. I've tried using csrutil disable booted into recovery but it doesn't stick. I'm not sure why. It reverts to enabled after reboot. Is there another way to get the Kernel copied over to /System/Library/Kernels ? 2. Assuming I can get the kernel copied over I believe I need to make some changes to config.plist. I've found this post but honestly, I'm not sure what these do. I'd like to understand what needs to be in config.plist in order to get the AMD kernel to work properly. Is there a good guide to what the AMD kernel options and requirements are? Am I on the right track? Is there any knowledge or guideance or silver bullet you could tell me to get this working? Any assistance is appreciated.
  20. I have written a tool to auto-patch cpuids and auto-decrypt system binaries on Mountain Lion and Lion. It is based on AutoAPBDecrypt but uses a launcher to elevate itself to admin rights. This way it can directly patch and replace the system binaries. Pre-built binaries for Mountain Lion and Lion are built. Source is, as usual, also included in the zip package. Make sure you do a Time Machine backup just to be safe. Enjoy AutoAMDTool.zip
  21. I'm trying to get Mountain Lion 10.8.3 to work on my AMD computer, but I get to this screen and am unsure of what to do: Below is the information of my system: CPU MAINBOARD SPD GRAPHICS If it makes any difference, I am using an SSD on C:\ Drive and a HDD on F:\
  22. theconnactic

    AMD - Geekbench scores

    Because there's no better way to measure our degree of success than seeing what the numbers say. Well, maybe not: real life user experience cannot be reduced to numbers only, but surely they matter. Post here your results. Let's show our fellow Intel hackintoshers how good an AMD machine can be! This one is not mine, but from Gilles:
  23. theconnactic

    [Need Help] Sleep issues

    Hello, everybody!! Thanks to this forum and the efforts of RAW X86, Bronzovka, AnV and others, who developed a working (32-bit, but working) lion legacy kernel, i have the latest OsX running on my machine, fine and stable. I installed it using Devout's experimental method. Now there's one last thing to solve, while its not possible to have 64-bit extensions (even Raw's kernel, whic offers support for 64-bit apps, is i386) or iCloud/facetime. What happens is this: when i put my computer to sleep, be by quick pressing once my power switch, be by clicking at the sleep option in the apple menu, the computer sleeps. In fact, it enters a coma, because it doesn't wake anymore, and i'm forced to reboot. Is there a solution? I'm running lion 10.7.4 (32-bit, with RAW's latest kernel) on an ECS A780LM-M2 motherboard and an Athlon II x2 250 (3.0 ghz) CPU. Any help will be much appreciated.
  24. I used Boot Disk Utility(http://adf.ly/1LHMts) to burn the Clover bootloader and Snow_Leopard_10.6.1-10.6.2_SSE2_SSE3_Intel_AMD_by_Hazard.iso onto my Lexar USB 16GB(I made two partition). When i try to boot into Hazard it showed soo many codes then it just stop,why does it do that?is there anyway to fix this? Here's a video to show you the problem:http://www.megafileupload.com/4Qc8/Clover_won_t_boot.mp4
×