Jump to content

maleorderbride

Members
  • Content Count

    620
  • Joined

  • Last visited

1 Follower

About maleorderbride

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender
    Male

Recent Profile Visitors

6,985 profile views
  1. Anyone have a GTX 980 that won't do dual display at bootup with the last upteenth versions of the Nvidia web drivers? Any workaround other than using old web drivers? Right now I can connect the second after startup and all is well. 2x 2K displays via DP (also tried DVI). I'm using the latest version of Lilu and WEG. I've also tried injecting GPU information via SSDT (I need at least an SSDT since I have system definition MacPro6,1)
  2. maleorderbride

    ThunderBolt Drivers

    If it doesn't work in Windows even then I would assume you have a more fundamental problem than an SSDT will address. I'm pretty sure I've seen threads where others are using an Apple TB display successfully, but I can't be of any help. You've done already what I would recommend for MacOS. Your screenshot of the IOreg looks fine, so I would try getting it to work in Windows first. Perhaps a BIOS setting, or a different motherboard slot? Thunderbolt on a hackintosh is just PCI-e detection--not true Thunderbolt. So while those sections from the newer Mac models you are discussing certainly matter, they will need to be part of a completely different approach.
  3. maleorderbride

    ThunderBolt Drivers

    Are you are running a displayport connection from your video card to your TB3 card? You should look at my first post in this thread (first page) and make sure the SSDT you are using is for your ACPI addresses. You can't just assume an SSDT will work if it is for a different motherboard.
  4. maleorderbride

    ThunderBolt Drivers

    I can't reproduce this on my X299 system, but one of my older ASUS X99 (Deluxe II) systems shows the below with an old ASUS TB2 card. I attached two IOreg's, and the SSDT I am using is the same one I posted earlier with only the address modified for this board (to BR1A). BIOS settings do not matter beyond the card being Enabled and set to the right slot (PCIE 5 in my case). I was able to have this info show years ago and posted it in an old Thunderbolt thread that had similar goals to this one, but nothing further ever came of it in that thread. The second picture and IOreg is the same configuration but with UniqueID now enabled in the BIOS (instead of legacy). Thunderbolt still works. To do this yourself you must have a "Thunderbolt Bridge" device available in System Preferences->Network to have it appear this way in IOreg or System Profiler. AFAIK, this can only be generated during a fresh install in which you already have Thunderbolt enabled and a device connected. edit: I put in a Titan Ridge card and while I still am allowed to remove and re-add the "Thunderbolt Bridge" from Network I no longer can use UniqueID and nothing shows in System Profiler. I guess UniqueID is the only special piece here, and that old ASUS TB2 card could do it for whatever reason. Here are the relevant bits from Library/Preferences/SystemConfiguration/NetworkInterfaces.plist, perhaps someone else can spoof this network device or find something helpful with it. <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en3</string> <key>IOBuiltin</key> <true/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>3</integer> <key>IOMACAddress</key> <data> AgAAAAAB </data> <key>IOPathMatch</key> <string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/BR1A@1/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType2/IOThunderboltController/IOThunderboltLocalNode/AppleThunderboltIPService/AppleThunderboltIPPort/en3</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>UserDefinedName</key> <string>Thunderbolt 2</string> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en4</string> <key>IOBuiltin</key> <false/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>4</integer> <key>IOMACAddress</key> <data> rIejHH3p </data> <key>IOPathMatch</key> <string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/BR1A@1/IOPP/UPSB@0/IOPP/DSB3@3/IOPP/pci-bridge@0/IOPP/pci-bridge@0/IOPP/ethernet@0/BCM5701Enet/en4</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>UserDefinedName</key> <string>Thunderbolt Ethernet</string> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> Archive.zip
  5. maleorderbride

    H.264 and prohibited sign

    Try different version of AptioFix or AptioMemoryFix (only one can be installed at a time). You can find them in the Clover installer--just re-install on top and select a different option while removing the one that does not work.
  6. Get some help man. I said: "The 1080 Ti is still the fastest card for AE/Premiere, but obviously there is no 10.14 support yet (and if it does come then you would probably want a RTX 2xxx series card). An AMD card would make things easier though, and still be plenty fast in most cases." That's a direct quote from my first post in this thread. These are all factual statements. The 1080 Ti is the fastest card for Premiere & AE. If one wants to build a "bad ass video editing computer" then that would be the logical choice. I even specifically mention that an AMD is also a reasonable choice as it can be easier and still fast enough for most people. I'm not sure how accusing someone of being a "fanboy" is a relevant response to inconvenient facts. The GTX 1080 Ti has problems with OpenCL (use CUDA instead, of course), and no support in 10.14 at this time. However, it is grossly mistaken to say a GTX 1080 Ti has a "huge amount of problems." Just as you have been mistaken to say that only six cores of an i9 CPU work in MacOS, and just as you have been mistaken to say that an "A GTX card works the same as AMD for Premiere/AE, and even a bit less." You are clearly quite ignorant about hackintoshes, so I don't understand why you are here giving advice instead of reading the forum boards and perhaps learning something. I understand I hurt your feelings by critiquing your words harshly. Sorry about that.
  7. I would recommend a website that specializes in pro apps instead of one with a 15 minute ad by Linus for Blue Apron: https://www.pugetsystems.com/labs/articles/Premiere-Pro-CC-2018-NVIDIA-GeForce-vs-AMD-Radeon-Vega-1206/ The link to Linus you posted doesn't have Vega or GTX 10xx series cards in it. Why is that relevant in almost 2019? Anyway, a Vega 64 doesn't match a GTX 1080 Ti in anything compute (other than OpenCL vs OpenCL of course), so between worse all around performance and 37.5% less VRAM there isn't much to think about. As for how one might know that i9 2066 CPUs work fine with MacOS--you might try this very website that you are looking at right now. If you can't even run a search on InsanelyMac then I'm not sure why you think you should be giving advice to this guy.
  8. i9 CPUs work fine. Not sure where you are getting your info, but they worked pretty much since they day they came out.
  9. AfterEffects doesn't do well with more than ~12 cores. Premiere can use far more. Yes, you probably want to go with an i9, but will need some serious cooling. I'd recommend a 360mm AIO liquid cooler. Fractal design makes an inexpensive one, or Corsair of course. The 1080 Ti is still the fastest card for AE/Premiere, but obviously there is no 10.14 support yet (and if it does come then you would probably want a RTX 2xxx series card). An AMD card would make things easier though, and still be plenty fast in most cases. Most X299 motherboards work, but I would recommend ASRock if you don't need too many bells and whistles, or ASUS if you don't mind spending a bit more.
  10. maleorderbride

    Decompiled original Apple DSDTs

    Is there a Macmini8,1 dump anywhere?
  11. maleorderbride

    ThunderBolt Drivers

    There is little point in engaging in sustained conversation with KGP, obus. He rarely lets things like evidence interfere where his ego is concerned.
  12. maleorderbride

    ThunderBolt Drivers

    This method isn't a real Thunderbolt implementation, so I don't see any inherent value in blindly injecting Thunderbolt APCI information if doing so has no real-world effect. I think it is worth trying certainly, but not sticking to for no reason. Considering that the two posters above now have working wake from sleep with TB3 attached for the first time ever (instead of a KP as they did with your SSDT), I would think this would be a clear case of real world outcomes outweighing blind emulation. There is clearly some garbage in those 1650 lines I cut. I'm sorry that your rig still KPs on wake from sleep with TB3 attached, but if I had to hazard a guess as to why then it is likely because of the rest of your ACPI patches and SSDTs. Try removing all of your SSDTs except ones that injects USBX, XOSI, and XCPM. If it doesn't specifically add functionality, then get rid of it.
  13. maleorderbride

    ThunderBolt Drivers

    edit: There might be a problem with daisy-chaining multiple NVMe devices and then ejecting and re-inserting them. I'll need to do some more testing, but I imagine very few of you are doing that. Titan Ridge hotplug is working fine over here on both ASUS X299 Sage and ASRock x299 Killer board. As far as I can tell, it doesn't need anything special compared to Alpine Ridge or the ASRock TB3 AIC card I normally use. I can use any of those three TB3 cards with my same SSDT and they all display connected TB3 devices and allow me to hotplug and daisychain. I tested out the newer "no cable method" for hotplug and it works fine. My SSDT has ~1650 fewer lines of code versus KGP's, but still has working hotswap and thunderbolt detect. Some of these changes were the removal of cosmetic information, others seem to be for sleep (which I am not using), but many lines don't seem to have any real world effect. This is just my original SSDT with a few added lines. I did notice some weird behavior when mixing and matching USB 3.1 devices alongside TB3 devices, but that happens with KGP's SSDT as well. Namely, if you boot with a TB3 drive and a USB 3.1 drive connected then the USB 3.1 drive will not detect until you remove it and re-insert it. An easy workaround would be to put your USB 3.1 devices in an actual USB 3.1 port instead. The attached SSDT should work with any TB3 card so long as you change the ACPI address (guide in my original post on page 1) to reflect your actual motherboard address. This is set for RP05 right now and works without configuration for ASUS X299 Sage & ASRock Killer SLI/ac. From my testing, only three things are really necessary for any hotswap TB3 SSDT beyond the outlining of the bare devices. UPSB must contain: Return (Package (0x04) { "PCI-Thunderbolt", One, "USB Cable Attached", Package (0x01) { "False" } }) DSBO must contain: Return (Package (0x02) { "PCIHotplugCapable", One }) SSDT-TB3.aml.zip
  14. maleorderbride

    WhatEverGreen Support Topic

    Hmmm..perhaps SMBIOS related as well. I'll mess around with it, but since adding a framebuffer fixes the issue...
  15. 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.
×