Jump to content

maleorderbride

Members
  • Content count

    607
  • Joined

  • Last visited

About maleorderbride

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender
    Male

Recent Profile Visitors

6,747 profile views
  1. maleorderbride

    WhatEverGreen Support Topic

    Hmmm..perhaps SMBIOS related as well. I'll mess around with it, but since adding a framebuffer fixes the issue...
  2. maleorderbride

    WhatEverGreen Support Topic

    This is on that X299 ASRock system, but I put in an RX 580 for testing since FCP X tends to work better with AMD cards. While OpenCL does work better with AMD, obviously this 264/265 encoding is unfortunate. The issue definitely exists. You can find other threads if you google for H264 or H265. Everyone solves it by injecting a FB, which again, makes it seem like an obvious thing to allow with WEG. On a real Mac system the AMD GPU is almost always paired with an Intel processor that has an IGPU.
  3. maleorderbride

    WhatEverGreen Support Topic

    OK, but FCPX and QT require an AMD framebuffer in order to export certain codecs. With WEG in place you get a system-wide freeze instead requiring me to add the framebuffer via SSDT instead.
  4. maleorderbride

    WhatEverGreen Support Topic

    Is there a boot-arg for WEG to set the AMD framebuffer? I can inject it via SSDT, but it seems like it would be an obvious nice to have for WEG.
  5. This is not working for me in 10.13.6. Anyone have an alternate find/replace?
  6. maleorderbride

    ThunderBolt Drivers

    I am using an ASUS X299 board for the first time (Sage), and my implementation of the patch worked with a few minor ACPI adjustments on this board. However, I noticed the USB 3.1 Bus was not present unless I booted with a USB 3.1 device plugged in. I know others had said they had this problem when using my SSDT. I fixed it by going into the BIOS and enabling "GPIO Force Power" and "ASPM" in the Thunderbolt section.
  7. maleorderbride

    Clover General discussion

    I have Clover 4392 installed and I am unable to boot in safe mode. I get the circle with a slash through it instead. I remember having issues with safe mode in previous Clover versions as well, but never really needed it to work until now. Should safe mode be working? Any tips on troubleshooting? Attached is a picture of the contents of my drivers64UEFI folder. This is on an ASRock X299 board running 10.13.4.
  8. maleorderbride

    ThunderBolt Drivers

    You are saying that thunderbolt hotplug works natively on your machine with no edits of any kind? I don't think that is the case as you would be the only person in the world to have this. It seems more likely you have other files or pieces still in place. It is quite possible this method simply will not work for your purposes. Note, this is "PCI hotplug" not actual native Thunderbolt hotplug, so it may not work here. Also, some devices do not support either thunderbolt hotplug, or do not support PCI hotplug. You would need to check in the Info.plist of your device kexts to see if they even contain IOPCITunnelCompatible=Yes, or perhaps other settings.
  9. maleorderbride

    (pre-release) macOS High Sierra 10.13.5

    H264 export in FCPX already works with Vega without iGPU. Just use an SSDT to inject Kamarang (for my Vega 64 anyway) instead of RadeonFB, plus Whatevergreen, and iMacPro1,1 SMBIOS. That works for me with FCPX in 10.13.4.
  10. maleorderbride

    ThunderBolt Drivers

    I took the values from PikerAlpha's blog, but I also posted where he derived them from (published APCI specs) that are freely accessible (page 4 or 5 of this thread). Copying the iMacPro makes the most sense to me, so why not try cutting the HS01/02, and change the 0x81 in the PLD's to 0x82. I'm not sure about the other values in the PLD buffer as the ACPI specs don't define what Piker chose to do there. The specs do offer other examples you could try though. Perhaps you should change your devices to match your actual ADR's found in a raw ACPI dump. My USB 3.1 device was at 0x00020000 so I inserted that device at DSB2 (the MacBookPro13,3 had the same pairing of 0x00020000 with DSB2 for it's 3.1), but perhaps your need to adjust the location or ADR? I allude to this in my original post, but this is just speculation on my part.
  11. maleorderbride

    ThunderBolt Drivers

    There are two version of the Gigabyte Alpine Ridge card with the same model number and name. The newer one uses JHL6540. Perhaps your TB devices are part of the equation. Do you have TB3 hard drive you can test with? Or are you using TB3->TB2 adapters here? The Apple one sucks, try the Akitio one if so.
  12. maleorderbride

    ThunderBolt Drivers

    IOreg says it is corrupted. Can you use the same version of IOreg you used on the previous post? I could open that. Whether or not an SSDT is "correct" is completely dependent on your motherboard, so that's why we need the IOreg with the SSDT loaded.
  13. maleorderbride

    ThunderBolt Drivers

    How can anyone help you if they can't see what effect the SSDT is having in your system? I see your old IOreg now, but it is useless since you aren't injecting any thunderbolt information. Follow the instructions again. Post just an IOreg with the SSDT installed.
  14. maleorderbride

    ThunderBolt Drivers

    You have quite a few things in your earlier post that one can download, but none appear to be your actual IOreg. Also, the Alpine Ridge card must be on the latest firmware, so make sure you are also at FW21. (requires Windows) Follow the instructions in my post to modify your own SSDT. Report back if hotplug is working or not, and attach an IOreg.
  15. maleorderbride

    ThunderBolt Drivers

    Are you on the latest firmware? 21 I believe. That screenshot looks valid, but I can't see if you have PCIHotplugCapable also set as One. You say you tried several "version" of the SSDT, but did you ever follow my instructions and modify your own to fit? It's quite easy. Do so and verify with an IOreg attached.
×