Jump to content
InsanelyMac Forum

chiefsalami

Members
  • Content count

    105
  • Joined

  • Last visited

About chiefsalami

  • Rank
    InsanelyMac Geek
  1. chiefsalami

    replace 10.11 AMD graphics kexts with 10.10?

    Hello all, I have a non-supported graphics card (FirePro W7100, Tonga architecture) that I have made work pretty well in 10.10 Yosemite by using Clover (modified deviceID definition in the source code) and adding the device ID to AMD9000Controller / AMDRadeonX4000 kexts. Seems like it is using the default RadeonFramebuffer kext personality, so all ports and resolutions work fine without any tweaking. However, making the same edits in 10.11 do not work. If I add device ID to BOTH kexts, it will not load the desktop. Freezes at boot just prior to going to desktop. If I add it only to AMD9000Controller.kext, I can get into the desktop, but performance is very poor. Artifacts, black areas on screen, very slow refresh rate, etc. If I replace the 10.11 kexts with the ones from 10.10, it results in the same situation as editing both kexts - cannot reach the desktop. If I just replace the Info.plist files, same thing. What would it take to be able to use the 10.10 kexts in 10.11? I am able to get everything else working in El Capitan except for the graphics. Anyone have a guide for doing something like this? Generally, I have not had a problem in the past by using kexts from an older OS version, but I have never done it for graphics kexts before.
  2. Greatly appreciate the OP for this! I am now able to get most of my machine working, especially the 1150 audio that I just could not get working with any other method, including all of the toleda utilities. However, one major issue is that after waking from sleep, the USB stops working. No mouse movement, no keyboard input. End up having to do a hard shutdown. Any solution for this? My mobo is an Asrock X99M, with a 5820k. And as a related issue (probably because of the unsupported CPU, whether I use fakecpuid or not), I have not been able to get virtualization (VMWare, Parallels) to work. Virtual machines run ridiculously slow or crash out upon bootup. Anyone else experienced this? Is there a workaround? Thanks!
  3. chiefsalami

    [HOW TO] Modification of AMD FB + Clover injection

    Yes, that is how I am injecting. The default injection through Clover (Baladi) works better, but whether I inject the default FB or my modified one, nothing ever shows on ioreg besides AMDFramebuffer.
  4. chiefsalami

    [HOW TO] Modification of AMD FB + Clover injection

    Guys, how do I "force" the computer to use a particular framebuffer? I am using an unsupported video card (AMD FirePro W7100), and patching kexts in order to have it work. I have added the device ID to AMD9000Controller, and am injecting connector info with Clover. I am starting with the Basset framebuffer and editing the connector data using this guide, and also injecting with Clover. I can see that when I make changes to the connector info in the personality, it affects my output to the monitor. In other words, I can get different displays (I have two connected via DP), but not both, to work based on what I use for the connector info, but no matter what, when I run ioreg I don't see the Basset framebuffer being used. If I don't inject a framebuffer, OS X properly detects my two connected displays, but with all kinds of artifacts and stuttering. No matter what, whether I inject the framebuffer or not, whether the displays work correctly or not, I only see AMDFramebuffer being used. Never Basset or anything else. Can anyone tell me how to force the framebuffer to be used, instead of the default? I'm on El Capitan 10.11.1, latest Clover, running either MacPro6,1 or iMac15,1 SMBIOS (doesn't appear to make a difference)
  5. chiefsalami

    Radeon R9 270X framebuffer issue

    Guys, how do I "force" the computer to use a particular framebuffer? I am using an unsupported video card (AMD FirePro W7100), and patching kexts in order to have it work. I have added the device ID to AMD9000Controller, and am injecting connector info with Clover. I am starting with the Basset framebuffer and editing the connector data using this guide, and also injecting with Clover. I can see that when I make changes to the connector info in the personality, it affects my output to the monitor. In other words, I can get different displays (I have two connected via DP), but not both, to work based on what I use for the connector info, but no matter what, when I run ioreg I don't see the Basset framebuffer being used. If I don't inject a framebuffer, OS X properly detects my two connected displays, but with all kinds of artifacts and stuttering. No matter what, whether I inject the framebuffer or not, whether the displays work correctly or not, I only see AMDFramebuffer being used. Never Basset or anything else. Can anyone tell me how to force the framebuffer to be used, instead of the default? I'm on El Capitan 10.11.1, latest Clover, running either MacPro6,1 or iMac15,1 SMBIOS (doesn't appear to make a difference)
  6. chiefsalami

    Clover General discussion

    Sorry about the link. I realize that solution is only cosmetic, which is why I would rather not change it that way. Do you know what the source of that info is, so I can change it there? No, I was having a problem too. Use .git
  7. chiefsalami

    Clover General discussion

    Took me a while to get Clover compiled, but eventually got it and installed. Clover now correctly recognizes the FirePro on bootup. El Cap just refuses to work (black screen) after adding my ID to the correct kexts... installed Yosemite and it works great. Minor flicker when first loading the desktop, but then no issues, really. However, About This Mac and System Report show the graphics card as an "AMD R9 xxx". What is the source of this info? I'd rather change a kext somewhere as opposed to editing OS screens, as described here: Thanks again for the great support!
  8. chiefsalami

    Clover General discussion

    I'll take a look ASAP. Thanks for the quick support!
  9. chiefsalami

    Clover General discussion

    I was wondering how graphic device detection/injection is done in Clover. For example, I have a Firepro W7100 8GB PCI-E card that is detected as a Radeon 4xxx (don't remember exactly) by clover based on the device/vendor ID. It didn't work at all, but I patched AMDRadeonX4000.kext to add my deviceID and modified a framebuffer for the port information described in another guide. I add the FakeID (although I don't have to, since it is correctly detecting the device ID) and also specify the modded frambuffer in the Graphics settings in Clover. By doing this, I can get into the desktop and have at least one display working, but with flickering and poor performance. However, Clover still incorrectly detects my video card no matter what settings I put, and therefore Mac 10.11 also gets the wrong information (shown as Radeon 7MB). Where is the database that Clover uses to populate the card information based on the device ID? How is it done, and how can I change it so that it picks up the information for my card? I'm determined to make this card work fully in OS X, and I'm getting there... device ID is 692b, vendor 1002
  10. chiefsalami

    Using 10.5 kext for 10.6?

    I GOT IT!!!! I had to use kexthelper b7. It was the only way the drivers were successfully installed. I went through the installation of 10.6 over a USB drive (put the stock hard drive in a SATA-USB enclosure) and then booted from that installation while still plugged into the USB port. Then I installed the 10.5 kext using kexthelper onto the 10.6 installation. Pulled the hard drive out of the USB enclosure, installed it back onto the internal SATA connector, and rebooted. Voila! It worked! Just thought some others might benefit from my experience. Now I'm working on getting the system updated to 10.3.... fingers crossed
  11. chiefsalami

    Using 10.5 kext for 10.6?

    I have done both of these - adding the kext to the install image and rebuilding the Extensions.mkext file, as well as trying to install to the hard drive over USB and then copying the kext to my install image. The hard drive is seen by almost any install image while it's plugged in via USB, but once I remove it and install it on the internal SATA controller, it is no longer seen (including by the install image). Only the ideneb 10.5 installer sees it, and can generate a working installation. Copying the kext over to a 10.6 install doesn't work, because the kext that makes the SATA controller work is a 10.5 kext. I cannot get 10.6 to recognize the controller by trying to use this kext. So my question is how can I get 10.6 to use the 10.5 kext? Is there something about the format of the kexts, the Extensions.mkext, or something else that is different between the two operating systems? What do I need to do?
  12. Folks, I have only ONE working kext for my SATA controller in my machine, and it happens to be part of the ideneb 10.5 installation. Is there a way for me to modify my 10.6 installation disc to include this kext and have it work as it does for 10.5? The setup utility will not even recognize my hard drive in 10.6, whereas in the ideneb 10.5 it will. Simply copying the kext into the correct location and rebuilding Extensions.mkext does not help. The hard drive is still not seen during the installation setup. Does this make sense what I'm asking?
  13. I have a motherboard with an SiS 5513 SATA controller, but it is essentially a SATA to IDE controller (the physical drive itself is SATA, but the system will see it as an IDE drive). I have the PCIID (1039, 5513) for the controller, now I'm just trying to get it working so that my Snow Leopard installation finds the hard drive that's connected. The installation disc will not even see any drive connected. Says there are no SATA and no ATA devices. I'm OK with editing a kext file to put in the PCIID to have the system recognize the controller (and therefore the drive), but which one do I put this into? Can someone help me in getting my installation to recognize my drive? I'm starting from a 10.6 install disc.
  14. chiefsalami

    Corrupted Intel iMac Firmware

    You need to try that restoration CD that Apple released. It will burn a CD that will re-flash your firmware and should fix it. You have to reboot and hold down the C key on the keyboard for it to boot off the CD and start the process.
×