Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Vlada. last won the day on January 21 2014

Vlada. had the most liked content!

1 Follower

About Vlada.

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
  • Location

Recent Profile Visitors

6,324 profile views
  1. Care to share how did you do that? I have some Core 2 Duo E4500 cpu in my old computer, so I would appreciate if you leave here instructions for the method that you use to do that!
  2. Vlada.

    [HOW TO] Modification of AMD FB + Clover injection

    Well, it seems that all those old scripts are not working anymore from some reason. However, I will attach the AMD personality dump from El Capitan, because it's not that much different. For your card FB is Futomaki and the code for it from El Capitan 10.11.5 version is next: Futomaki (4) @ 0x1cc5d0 DP, DP, DDVI, HDMI 00040000 04030000 00010101 12040401 00040000 04030000 00010201 22050502 04000000 14020000 00010300 00000606 00080000 04020000 00010400 11020103 If you check my first post you will find explanation that Sierra is using additional digits in the code, so all you need to do is 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 in short the original code for Futomaki will be the next: Futomaki (4) @ 0x1cc5d0 DP, DP, DDVI, HDMI 00040000 04030000 00010101 00000000 12040401 00000000 00040000 04030000 00010201 00000000 22050502 00000000 04000000 14020000 00010300 00000000 00000606 00000000 00080000 04020000 00010400 00000000 11020103 00000000 Obviously someone from Apple is inventing the hot water with this... anyway, this is the current situation under the Sierra. So all you need to do is to change the 8 digits between zero segments at the end of the code line with your construction and you are good to go. And if I'm correct, that would be the same code construction that I was using for R9 270X which was my previous GPU card. So I was using the next code construction: [DISPLAY_PORT] 12 04 01 01 [HDMI_TYPE_A] 22 05 02 03 [DVI_I] 10 00 03 06 [DVI_I] 00 10 04 06 [DVI_D] 11 02 05 05 00040000040300000001000012040101 00020000040200000001000110000306 04000000140000000001000111020505 00080000040200000001000022050203 And this one is for Sierra: 000400000403000000010000000000001204010100000000 000200000402000000010001000000001000030600000000 040000001400000000010001000000001102050500000000 000800000402000000010000000000002205020300000000 But as I said, for R9 270 you will need to patch device id digits in plist files inside the AMD7000controller and AMDRadeonX4000 kexts. So for that you can use let's say binary patch: sudo perl -pi -e 's|\x36\x38\x31\x30|\x36\x38\x31\x31|g' /System/Library/Extensions/AMD7000Controller.kext/Contents/Info.plist sudo perl -pi -e 's|\x36\x38\x31\x30|\x36\x38\x31\x31|g' /System/Library/Extensions/AMDRadeonX4000.kext/Contents/Info.plist All in all, this is it in short... AMD personality dump from Mac OS X 10.11.5.zip
  3. Vlada.

    [HOW TO] Modification of AMD FB + Clover injection

    It's been a while since I was doing this, so I'm a bit rusty. Well, I see now from my old AMD Radeon R9 patching tool that you need to make those changes on both kexts: AMD7000controller and AMDRadeonX4000.
  4. Vlada.

    [HOW TO] Modification of AMD FB + Clover injection

    Hmm... strange that fakeid doesn't work. Well, if my suggestion doesn't work and fake id doesn't work too, then you should manually make changes in the AMD7000Controller.kext. Make a copy of AMD7000Controller.kext on desktop, then open the info.plist file inside the kext and find 0x68101002 hex then replace those numbers with 0x68111002 and reinstall the kext again. That's not the perfect solution, but it'll do the job until you find the best one.
  5. Vlada.

    [HOW TO] Modification of AMD FB + Clover injection

    For R9 270 you need to add additional patch, because it using device id that is not supported by Apple. Open Clover Configurator and load your config.plist file. In KextsToPatch field you need to make a new entry, and then type next: Name > AMD7000Controller Find Hex > 0x68101002 Replace Hex > 0x68111002 Info Plist patch > Yes (check it) That should do the trick, alongside with the FB patch that you can make by using this guide.
  6. Vlada.

    [HOW TO] Modification of AMD FB + Clover injection

    Check the first post because everything is explained there!!! Basically you need this: 02000000 40000000 08010000 / LVDS + (add your code construction) 10000000 10000000 00010000 / VGA + (add your code construction) 00040000 04030000 00010000 / DP + (add your code construction) 00020000 04020000 00010000 / DVI-SL + (add your code construction) 04000000 14020000 00010000 / DVI-DL + (add your code construction) 00080000 00020000 00010000 / HDMI + (add your code construction) When you finish with code construction, translate whole code in single line and add it in kexttopatch field in Clover Configurator. [EDIT] Sierra is using additional digits in the code, so you'll need to add those extra zero segments in front of your code construction and after it. Check example bellow: 00080000 00020000 00010000 00000000 + (add your code construction) 00000000
  7. Vlada.

    Radeon R9 270X framebuffer issue

    Unfortunately, I am not able to do that mostly due the fact that I'm not using AMD GPU anymore. There is another topic that I was started during that period where I was explained whole procedure step by step, so I suggest you to check it, if you didn't already. [HOW TO] Modification of AMD FB + Clover injection
  8. Vlada.

    Patched Framebuffer Repository

    Here are FB patches that I was using for construction of AMD Radeon GPU Injector tool: FB patch based on Sapphire HD6450 1GB / 100322L (device id - 0x6779) Personality: Ipomoea 000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002 patch: 040000001402000000010000100002040008000004020000000100002103010210000000100000000001000000100301 FB patch based on MSI HD6790 1GB / R6790-2PM2D1GD5 (device id - 0x673E) Device id changes: 0x67381002 >>> 0x673E1002 Personality: Bulrushes 000400000403000000010000110201010004000004030000000100002103020200040000040300000001000012040303000400000403000000010000220504040004000004030000000100001000050500040000040300000001000020010606 patch: 000400000403000000010000120401010004000004030000000100002205020200080000040200000001000011020304040000001402000000010000110204060002000004020000000100001000050500020000040200000001000000100605 FB patch based on Asus Radeon EAH6850 1GB / DC/2DIS/1GD5/V2 (device id - 0x6739) Personality: Duckweed 00040000040300000001000012040401000400000403000000010000220505020008000004020000000100001102030400020000140200000001000000000605 patch: 00040000040300000001000012040401000800000002000000010000220506040002000004000000000100001102010604000000140200000001000010000305 FB patch based on Asus Radeon EAH6870 1GB / DC/2DI2S/1GD5 (device id - 0x6738) Personality: Gibba 0004000004030000000100001204050100040000040300000001000022050402000800000402000000010000110206040002000014020000000100000000030504000000040200000001000011020103 patch: 0004000004030000000100001204040100040000040300000001000022050502000800000402000000010000110206040002000014020000000100000000030504000000040200000001000011020106 FB patch based on MSI HD7730 1GB / R7730-1GD5V1 (device id - 0x6837) Device id changes: 0x68391002 >>> 0x68371002 Personality: Dashimaki 00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103 patch 00020000040200000001000010000304000200000402000000010000001004040008000000020000000100002205020500040000040300000001000012040102 FB patch based on Asus HD7870 2GB / HD7870-DC2-2GD5-V2 (device id - 0x6818) Personality: Futomaki 00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103 patch 00040000040300000001030012040101000400000403000000010400220502020400000014020000000101001000040600080000000200000001020011020303 FB patch based on PowerColor PCS+ R9 270X 2GB / AXR9 270X 2GBD5-PPDHE (device id - 0x6810) Personality: Futomaki 00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103 patch 00020000040200000001000010000306040000001402000000010000110205050008000000020000000100002205020300040000040300000001000012040101 FB patch based on Gigabyte R9 280X 3GB / GV-R928XOC-3GD/F60 (device id - 0x6798) Personality: Futomaki 00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103 patch 00020000040200000001000010000406000800000002000000010000110203040004000004030000000100001204010100040000040300000001000022050202 FB patch based on Sapphire Vapor R9 290X 8GB / 100361-8GVXSR (device id - 0x67B0) Personality: Baladi 000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606 patch 000800000402000000010200220502030004000004030000000101011204010100040000040300000001020021030202040000001402000000010300110203040004000004030000000105001000050500020000040200000001040110000406
  9. That's unfortunate! Seems to me like that our best option would be, switching to NVIDIA... Obviously, not a very popular move, but after all, it is a sort of solution...
  10. Ok, here my report. I'm using latest Clover, where I have set Futomaki FB patch as primary since that's the one which works properly with my card. I add another line in the field kexttopatch for Maguro, for DVI-I patch, and later also for DVI-D patch because Maguro is single connector FB. But that is not important, because when I boot in El Capitan with Maguro FB, my monitor shuts down, which means that dedicated FB is not working. Also, I switch SMBIOS from MP6,1 to MP3,1 then to iMac14,2 and finally iMac12,2. None of this works. Same thing happens with FB-s which have LVDS connectors. However, I didn't check binary patch, but that's the smallest chance. Previously I was tested latest Ozmosis via USB shell boot method in combination with Futomaki FB, same thing - wake won't work. And I was trying to fix the problem by changing various things inside the plist files for AMD7000Controller.kext, AppleGraphicsPowerManagement.kext and AppleGraphicsDevicePolicy.kext AppleGraphicsControl.kext is important and AppleGraphicsDeviceControl.kext inside the plugins folder. The other kexts from plugins folder can be removed and the graphics will work properly except, of course wake from sleep. So I tried that option too... I'm running out of options. It would be nice to see what you did till now, because that perhaps can give me an idea to try something else.
  11. It’s not that… No matter what I do and which SMBIOS I use, Maguro (but also several others from the list) refuses to work. Besides, from Macandreas report, we can see that MacPro5, 1 and MacPro6, 1 should work, and I'm also using Radeon R9 270X. However, on my machine that is not the case...
  12. You probably won't get much with that. Maguro doesn't work in my case or at least not with the FB patch for DVI 1080p monitor. But, I didn't check HDMI and DP outputs. According to the reports, it seems that Maguro only works with 4k Monitors, or perhaps system w/o IGPU, or both... All in all, I’m getting tired of this AMD graphics mess.
  13. @macandrea - I don’t know for 4K resolution because I don’t have such monitor so I can't test it, but on 1080p everything is working properly in my case with Futomaki FB. Also, you probably won’t be able to use any FB which has LVDS connectors in combination with MP6,1 definition, so you should stick to those with DP, DDVI and HDMI, because they are probably most compatible. I will leave here ATY personality dump from 10.11.2, for those who want to make further tests. @Mieze - When IGPU is first booting device (master) and PEGP is second (slave), everything is working properly, so you basically confirmed what I said 15 days ago. Two things more: I don’t think that current DSDT patches that we using had anything with this GPU problem, because nothing indicates that, but also, UEFI boot is not to much important option, because I am using legacy boot and as I said in that combination on my machine everything is working properly too. All in all, what you got is more a kind of workaround solution, but I guess that is better than nothing. So it’s good to know that is possible to make it work with HDMI adapter, like you did... Nevertheless, we should continue to search another solution. ATY personality dump 10.11.2.zip
  14. Well, I said that the anomaly stays even when IGPU is removed from the DSDT and the system completely. This clearly indicates that the problem is not in IGPU but in AMD drivers, or more precisely in AMDRadeonX3000 & 4000 kexts, and in AppleGraphicsControl.kext too. If we discover where is the problem on the code level, I think that we will be able to fix it... However, It'll take time, that's for sure.
  15. OK, since you mention this I’d like to clarify a few things… I’m not sure for that Intel GOP driver that you mentioned, but I know that my R9 270X have a GOP partition inside the firmware. Also, I am using a Clover legacy boot variation, although I have UEFI BIOS, but because of certain Clover boot option graphics issues, I don't like to use it. So in short, the wake is working in my case under the Clover legacy boot variation, but only when the IGPU is set in BIOS as a first device. And again, I'm using SMBIOS for MP6,1.