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 237 results

  1. 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
  2. So the source has just been released. https://opensource.apple.com/release/os-x-1010/ With this release I want to do things a bit different: Topic ONLY for releases of kernels, this will make it easier to find kernels in the forum. Topic ONLY for the testing of a kernel, when a release of a kernel gets posted on the other topic inform this topic of the release and post findings here. I am also thinking of posting a topic on the building of each kernel release listing the: Dependancies Kernel Version Post the diffs for each release. Let me know if that would be something the testers would be keen on having.
  3. I installed everything nice and easy and can boot into OS X 10.6 easily by using the -x boot flag. However, without it I can only get passed the apple splash only to be hit with an ugly glitched looking black and grey screen. However, I can boot without any flags using the ModCD. The screen resolution no matter how I boot it is whack, just can't see the finder bar. So I just need help figuring ot what is going on. I have the impression that it is a graphics card error, but my GPU is recognized completely by the system. My specs: GATEWAY GT5228 -Chipset: NVIDIA GeForce 6100 -Graphics: ATI Radeon HD 4600 -CPU: AMD Athlon 64 X2 4200+ -RAM: 2GB DDR2 I want to also add that I used SnowLeo for the installation and used the following options in 'Customize' (note, I did not take out in memory or my GPU during installation): -Azaila audio -ATI_init -Chameleon R5 -AMD Patch -Chocolate Kernel -FakeSMC -PlatformUUID -AppleTRL8169(LAN) -LegacyApplePIIXATA Any help is much appreciated I am also willing to reinstall if you suggest it.
  4. 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
  5. Tino2

    Hd 7750 Powercolor 1Gb

    Hello Members I got a Problem with the 7750 1Gb Powercolor, my System runs with Clover Bootloader. Without Injection KernelPanic Without Fake ID KernelPanic With Fake ID and Injecton Boot possible The Framebuffer gets loaded, but i have no Signals at the Displayport/HDMi/Dvi Port IoReg shows wrong device ID 0x0000 Shows Framebuffer chosen in Clover (tried Aji, Buri, Dashimaki etc) Tried also a DSDT edit but no success so far, if someone has an Idea i would like to hear it please. In the Attachment is the IoReg and Dsdt if someone needs them. If there is a Guide im pleased to know about it, but google gave so far no Solutions. System: Ga-H87N-Wifi, i7 4770s, HD 7750, 250Gb SSD, Mavericks 10.9.2 IoReg + DSDT.zip
  6. 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.
  7. 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
  8. 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
  9. 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
  10. After installtion of Yosemite 10.10.5 on my AMD PC , the system runs smooth and perfect, with the latest kernel 10.10.5_SSEPlus_V3, but i have following issues, which needs your help to be fixed. Sorry, i am bloody new in this sector. 1. how can i boot from HDD instead of USB Stick? Enoch is currently installed on USB 2. which bootlader can be installed also? Best one? Enoch, etc... ? 2. how to insert bootflag into bootloader to start automaticlly with these flags, instead of entering flags every boot? 3. Sound is not working -- any kext or etc...? --> Realtek 4. no network -- any kext or etc...? --> 100 mbit/s Realtek My System: AMD Phenom II X6 T1090 ASRock Mainboard 8GB RAM Nvidia GTX560 WD 500GB
  11. 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
  12. Hello. Need some help with this problem. On clover booting stuck at "Root device UUID IS (some letters)" Here's my machine Motherboard:asus m5a97 (UEFI supported); Procesor: AMD Athlon II x4 640; Graphics: sapphire radeon r9 270 (non x); Here config.plist I used. What should I do? Please help. Second week I trying to fix this error. And my Kernel. config.plist-GE=Yes-ATI.zip
  13. 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.
  14. 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!
  15. 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
  16. 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:
  17. LolfaceMC

    Multiple Displays HD6850-Framebuffer

    Hi, Help please!!! I have 3 vga moniters and I want to use at least 2 on my hackintosh. I use a dvi-vga adapter for my main display and I plugged my other monitor to the vga slot in the motherboard. This works in windows because I enabled "Enable Vga" in the BIOS. I tried some of the stuff on here http://legacy.tonymacx86.com/viewtopic.php?t=46392 but it desnt work. I cant use the other dvi port because it is a different kind of DVI port. Specs: GIGABYTE ATI Radeon HD6850 1GB DDR5 2DVI/HDMI/DisplayPort PCI-Express Video Card GV-R685OC-1GD Intel Core i5-2500K Quad-Core Processor 3.3 GHz 6 MB Cache LGA 1155 - BX80623I52500K Gigabyte Intel Z68 ATX DDR3 2133 LGA 1155 Motherboards GA-Z68X-UD3H-B3 THANKS!
  18. 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!
  19. 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.
  20. benbc7

    AMD Hackintosh

    can someone please help me with my HP Omni 100 5155 ive tryed iPC and iAtkos and some form of Chameleon and every single time i start to boot from the install disk it gets stuck on "still waiting for root device" sata is set to AHCI and everything, ive tryed many different tips and none of them have done anything
  21. Because I have some problem with my screen .. I'm re-doing the kext for Mavericks Need GraphicEnabler=yes and AtiConfig=Hoolock Because I have re-mapped the Hoolock only.. Need to sleep Have fun PS : this is for people want two screens with a good resolution. the problem at the start is I have just one monitor detected .. Now I have my two screens detected with the good resolution 1920*1080. Connected to HDMI and the first DVI on top.. AMD5000Controller.kext.zip
  22. iProCr4ftr

    AMD Cool 'n' Quiet

    Hello, Is there a way to get AMD Cool 'n' Quiet/auto downclocking working on an OS X Mavericks hackintosh? This is because I do not want my Hackintosh to drain electricity by running at its max clock speed all of the time. I am running a M5A78L-M LX3 motherboard, with an AMD Phenom II X4. Many thanks
  23. Hi there. Today, I wanted to install Yosemite 10.10.5 (Niresh for AMD of course) on my second PC. After hours of hard work, it was mainly stable and I installed Chameleon. After a reboot, the bootup gets stuck at "iobluetoothhcicontroller missing bluetooth controller transport". Yes, I looked around in the internet for a fix, but all I found was a fix for Intel. But im an AMD user. So, I'm asking you guys now, how can I fix this? A friend told me I should use a diffrent kernel. But I have no Idea how to install a new kernel. BTW, because of this error, I can't boot into OSX so I cant change anything! I hope that one of you got a solution for this! My specs: OS Version: Yosemite 10.10.5 (Niresh) CPU: AMD A8 5600K Mainboard: Biostar A58MD
×