Jump to content

MacFaulty

Members
  • Content count

    175
  • Joined

  • Last visited

About MacFaulty

  • Rank
    InsanelyNut
  • Birthday 09/01/1993

Contact Methods

  • Website URL
    http://woutsanders.com

Profile Information

  • Gender
    Male
  • Location
    Tulip & Cheese country
  • Interests
    Java, PHP, Ruby & Linux/Windows server management
  1. [HOW TO] Modification of AMD FB + Clover injection

    Hmm... This makes for some interesting stuff. I will do some more testing next week before I start to make false tickets lol Anyway, thanks for your help
  2. [HOW TO] Modification of AMD FB + Clover injection

    Thanks for the reply. I know that without injection nothing should happen, but why does he panic then? So if I boot without Injection is the kext still patched by Clover or not?
  3. [HOW TO] Modification of AMD FB + Clover injection

    A quick follow-up on post 175 (also posted by me): I did some testing with injecting and not and playing with framebuffers in Clover bootloader screen and there are some interesting things when I'm using my own patch: - No injection with Futomaki FB = OK (Card is recognized as a HD8970 in DPCIManager). - No injection with Baladi FB = Kernel Panic just after booting. - Injection + Baladi FB = Screen goes to standby mode (blinking LED on monitor). - Injection + Futomaki FB = Kernel Panic just after booting. I can also confirm that DP is working as well with option 1 above (DP -> HDMI converter, passive). The framebuffer column in DPCIManager when booting with option 1 above reads the following: ATY,AMD,RadeonFrameBuffer. This confirms that Baladi was not injected (as well as Futomaki??), because when booting with a injection and framebuffer (using Pavo's patch) I get ATY,Baladi in that column.
  4. [HOW TO] Modification of AMD FB + Clover injection

    Thanks for the reply. I do hope that AMD drivers are a) not altered, or b ) only improved . Otherwise it would mean a rollback :sigh:
  5. [HOW TO] Modification of AMD FB + Clover injection

    Hi there, Thanks for the quick response. This is with injectATI and explicitly setting the baladi framebuffer. Now, if I clear everything (no GFX patching) and leave the Clover defaults (InjectATI + Futomaki FB), the screen is black, but after replug it is stable (the known bug sort to speak). I wonder what I need to try to make it work...
  6. [HOW TO] Modification of AMD FB + Clover injection

    Hi all, I'm trying to patch my Sapphire R9 290X Tri-X O/C 4GB card, but the monitor goes to sleep after patching (I have only 1 Full HD monitor, so no multi-monitor setup and the monitor is plugged into the HDMI slot). I followed the guide to the letter and did exactly how it was explained. My graphics card has 4 connectors, but in the 8000Controller kext are only 2 framebuffers (baladi & exmoor) which are both defined as 6 connectors. I previously used the below patch in Yosemite with the Baladi FB which worked beautifully (credits to Pavo for his great patch work ). In El Capitan I can still boot with it, but I get image tearing on the screen (only when moving windows around). It does have QE/CI, just as it had in Yosemite. Color depth in System Profiler says CGSThirtyBitColor :S. I can also boot without any patches and injection, but then I need to replug the cable (screen is black, but not to sleep). Also, Clover sets the default framebuffer to Futomaki (but it doesn't is inside the 8000Controller?!). 00 08 00 00 04 02 00 00 00 01 02 00 22 05 02 03 00 04 00 00 04 03 00 00 00 01 01 01 12 04 01 01 00 04 00 00 04 03 00 00 00 01 02 00 21 03 02 02 04 00 00 00 14 02 00 00 00 01 03 00 11 02 03 04 00 04 00 00 04 03 00 00 00 01 05 00 10 00 05 05 00 02 00 00 04 02 00 00 00 01 04 01 10 00 04 06 --- The current Baladi framebuffer as it is present in the released El Capitan 10.11 is as follows: Personality: Baladi ConnectorInfo count in decimal: 6 Disk offset in decimal 1859712 0000000 00 04 00 00 04 03 00 00 00 01 03 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 01 00 11 02 01 01 0000020 00 04 00 00 04 03 00 00 00 01 02 00 21 03 02 02 0000030 00 04 00 00 04 03 00 00 00 01 04 00 22 05 04 04 0000040 00 04 00 00 04 03 00 00 00 01 05 00 10 00 05 05 0000050 00 04 00 00 04 03 00 00 00 01 06 00 20 01 06 06 0000060 Now, the output from both BIOS decoders are as follows: Redsock decoder: 285X0500.OU5: C67101 Hawaii XT A0 GDDR5 4GB 64Mx32 300e/150m Subsystem Vendor ID: 174b Subsystem ID: e285 Object Header Structure Size: 271 Connector Object Table Offset: 3e Router Object Table Offset: 0 Encoder Object Table Offset: ce 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 [4] which is [DVI_D] encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [4] which is [DVI_D] encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Radeon decoder: ATOM BIOS Rom: SubsystemVendorID: 0x174b SubsystemID: 0xe285 IOBaseAddress: 0x0000 Filename: 285X0500.OU5 BIOS Bootup Message: C67101 Hawaii XT A0 GDDR5 4GB 64Mx32 300e/150m PCI ID: 1002:67b0 Connector at index 0 Type [@offset 43532]: DisplayPort (10) Encoder [@offset 43536]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 43624]: 0x90, OSX senseid: 0x1 Connector at index 1 Type [@offset 43542]: HDMI-A (11) Encoder [@offset 43546]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 43651]: 0x92, OSX senseid: 0x3 Connector at index 2 Type [@offset 43552]: DVI-D (3) Encoder [@offset 43556]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 43678]: 0x93, OSX senseid: 0x4 Connector at index 3 Type [@offset 43562]: DVI-D (3) Encoder [@offset 43566]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 43705]: 0x95, OSX senseid: 0x6 The guide said to combine values from both BIOS decoder outputs, for me it looks like this: 12 04 01 01 //DP 22 05 02 03 //HDMI-A 11 02 05 04 //DVI-D #1 (top) 10 00 05 06 //DVI-D #2 (bottom) The constructed framebuffer in the end looks like this: 00 04 00 00 04 03 00 00 00 01 02 00 12 04 01 01 //DP 00 08 00 00 00 02 00 00 00 01 01 00 22 05 02 03 //HDMI-A 04 00 00 00 14 02 00 00 00 01 03 00 11 02 05 04 //DVI-DL 04 00 00 00 14 02 00 00 00 01 04 00 10 00 05 06 //DVI-DL I have put this in the ATIConnectorsData and ATIConnectorsPatch fields in Clover configuration like so: ATIConnectorsData: 000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606 ATIConnectorsPatch: 00040000040300000001020012040101000800000002000000010100220502030400000014020000000103001102050404000000140200000001040010000506 But when rebooting, the screen goes black and to standby mode. I must be doing something wrong (maybe I need to append the original 2 connectors or have the ordering wrong, I don't know), but I can't figure it out. If there is somebody who could help, that would be awesome! I have also attached my ROM just in case it is useful edit: typo 1002_67b0_e285174b.rom.zip
  7. R9 290X Help for mavericks

    Anybody tried to go to 10.11 as of today? I currently have it planned for this weekend to make the jump and will report here if there needs a 'fix' that is fixable by me . If anybody else already made the transition, please tell everybody here how it worked out for you. You will help many owners of Rx90X graphics cards. Thanks!
  8. R9 290X Help for mavericks

    Was anybody brave enough to test the current patch on the 10.10.3 update? I'll wait
  9. R9 290X Help for mavericks

    Quick question. If you are patching a framebuffer, will this patch need to be adjusted when a new version of the kext is included in an update? I'm using Clover and put the connectorsData in there. So, do you only need to patch the framebuffer once (only if the framebuffer stays in the driver and you keep the same graphics card, obviously)? Thanks
  10. R9 290X Help for mavericks

    One DVI-D port 'seems' to be working alright. I do wish that in 10.11 (or maybe next release is 11.00?) the driver will be covering more framebuffers though.
  11. R9 290X Help for mavericks

    If you mean HDMI audio. I do not use that. I only use HDMI video. I use ALC898 patch from toleda for working audio My screen is on HDMI, but does not have speakers. I am currently not in the need to get HDMI audio working as I cannot test it, but if there is anything you need from me, please do tell. I also finally came 'round to test the DP and that one (at least on my card) still needs to be re-plugged. DVI I cannot test, yet. HDMI works though on this card with the patch. Sorry for the confusion
  12. R9 290X Help for mavericks

    That's weird. Everything does work here (QE/CI etc) and I'm currently using the HDMI (video only).
  13. R9 290X Help for mavericks

    Okay then, there you go! Attachment added with the following included in the package: - Clover configuration (s/n etc. are masked). - IOReg dump from IORegistryExplorer v2.1. - Clover ACPI folder (original and patched DSDT, as well as the DSL file). Check my signature for hardware / software specs (it's the desktop one of course ). I hope that this information may help you. If you still need more information, don't hesitate to ask. files.zip
  14. R9 290X Help for mavericks

    Toleda, do you also want/need my current (working) configuration?
  15. R9 290X Help for mavericks

    I've got Clover patching-on-the-fly working. I am using rev. 3128 currently. I will post my config snippets later today with Pavo's patch. edit: Below are the relevant snippets. These snippets work on a Z77X-UD5H v1.0 board with a Sapphire Tri-X O/C R9 290X w/ 4GB VRAM (Hawaii XT Prototype). The switch on the card must be switched to UEFI mode to work properly (even then I recommend to run as much as possible in UEFI). I tested only HDMI at the moment, but will test DP soon as I have a converter for this. Tested on 10.10.2. This gives me no flickering or the need to replug my monitor. Only glitch is in second stage boot with the loading bar on bottom left, but that is a common issue and fine with me. edit 2: I updated the second code block, because AppleRTC patch has nothing to do with video patch (forgot to delete that thingy). Graphics section: <key>Graphics</key> <dict> <key>DualLink</key> <integer>1</integer> <key>FBName</key> <string>Baladi</string> <key>Inject</key> <dict> <key>ATI</key> <true/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>VRAM</key> <integer>4096</integer> <key>VideoPorts</key> <integer>4</integer> </dict> Kernel and Kext patches section: <key>KernelAndKextPatches</key> <dict> <key>ATIConnectorsController</key> <string>8000</string> <key>ATIConnectorsData</key> <string>000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606</string> <key>ATIConnectorsPatch</key> <string>000800000402000000010200220502030004000004030000000101011204010100040000040300000001020021030202040000001402000000010300110203040004000004030000000105001000050500020000040200000001040110000406</string> ... Any other 'regular' patches... </dict>
×