Jump to content

Driftwood

Members
 View Profile  See their activity

  • Posts

    457

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Everything posted by Driftwood

  1. Driftwood
    FireWire. I use slot 2 or 4. Works out of the box. For kicks. Try & install RMEs fireface800 card drivers and let me know if FireWire works with your audio device. I know u don't have this audio unit but it might install an Apple happy kext.
  2. Driftwood
    @fabiosun How about you make a TRX40 Discord channel for this group/AMDOSX as the growing army of users is testament to the groundbreaking work you and the rest of us have done here.
  3. Driftwood
    We've been there with this test a few days ago I thought! On Discord we all agreed (and Algrey) that its pointless using UpdateDataHub as timing is shot! Its all over the place. And as you saw, anything below 64KhZ (48K, 44k and 32k) is lagged and cracklin' to hell! Higher timings like 96k and 192k on my firewire were fine... however, it will latency correct timings every few minutes at these settings I later discovered. Summary: Its a no go for anything related to timing in OSX. As Pavo has spelt out. If you use it for rendering or cpu 'speedup' things look great but probably will error. If there was a way to harness TSC better and to use this, then Im sure Algrey and others are looking it it.
  4. Driftwood
    I spoke to Asrock weeks ago, there is no chance of Thunderbolt support on this board. This was there response: Hello, Our TRX40 models have no header for a Thunderbolt add-in card. No way to add Thunderbolt support to these boards, sorry. Kind regards, ASRock Support ASRock Europe B.V. Bijsterhuizen 1111 6546AR Nijmegen The Netherlands
  5. Driftwood
    I dont know about the Cheetah Xpress but a lot of bridged firewire cards have been problematic in Proxmox (maybe iGPU can comment about Bare metal) but my LSI643 card (single chip NOT bridged) works great and has done for years in other builds. I guess you could look at enabling SIP (csrutil Enable) when installing it, and check to see if it supports the current OSX you are using. Use Recovery Mode to properly enable SIP.
  6. Driftwood
    Which ones? Nice to be up and running so quickly with these new patches... must go away more often!
  7. Driftwood
    https://9to5mac.com/2020/08/30/imac-2020-lines-screen-glitch/ The 5700XT has been proving problematic for Apple iMac users too.
  8. Driftwood
    Back from filming... well, you fellas have been busy with Beta 7 BS... Time to give it a go for kicks! Any advice for us Asrock n rollers?
  9. Driftwood
    /System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a > AGDCDiagnoseTRX40_a.txt 2>&1
  10. Driftwood
    Hi mate, Im away from computer atm as filming. Sleep works with Cat Above 4G and I think I had S5 on. All MMIO is YES apart from last four which is No, like you now have. Havent tried converting my M2 Catalina drive over to BM yet as wanted to leave it as Proxmox just in case (and probably till BS is working better). I have Cat BM and BS BM installed on separate SSD satas.
  11. Driftwood
    99 error? Check BIOS for correct boot up devices... if all fails refresh the 99? Or could be a problem related to PCI-E devices.
  12. Driftwood
    He's probably from TonyMac bless him!!!!
  13. Driftwood
    Handbrake is so fast at software cpu encoding. 🙂 That's x265 for you! Was that HEVC 10-bit 420? or the 12-bit setting? In this pic below, here's my rec2020 HDR PQ output variables if anyone needs them! Load up Activity Monitor just to watch those cores fly! 🙂 Now try the same test and same variables with Compressor, Media Encoder or Davinci. They crawl!
  14. Driftwood
    As I said in previous posts most of the new Adobe beta apps will not need the patch too. Only Photoshop (no beta as of yet) and Illustrator beta are in need of patching.
  15. Driftwood
    On an open quest to discover common traits of our MMIO addresses in our boards HPET always keeps cropping up for address 0xFED00000 "The BIOS often sets up the HPET incorrectly in the ACPI, initializing it correctly only in Intel 8253 mode. If the ACPI is not set up correctly the OS cannot list the HPET. And the BIOS and OS developers don't see the need to get Real Time support. So the HPET is only there to satisfy the system's high speed needs. If the HPET is set up correctly in the ACPI from BIOS then the ACPI MMIO page of the first HPET chip should be at 0xFED00000 and the second HPET at page 0xFED80000" WIKIPEDIA So I started investigating the other MMIO addresses to find any common values out there in webworld as nobody seems to know what they relate to! Therefore we have in our debug of my Asrock TRX40 Creator an estimate of what these values mean:- child 0 MMIO devirt 0xCB100000 - AppleACPIPCI PCI Bridge Peg 0 child 1 MMIO devirt 0xD7180000 - Registered nosave memory ? child 2 MMIO devirt 0xE3180000 - Registered nosave memory ? child 3 MMIO devirt 0xE3300000 - device interrupt (10?) memory child 4 MMIO devirt 0xEF100000 - device interrupt(20?)memory child 5 MMIO devirt 0xFEA00000 - device interrupt (e.g. interrupt 16 at device 0.0 on pci4) child 6 MMIO devirt 0xFEC00000 - RTMPTable IOAPIC (The address in the physical address space of the I/O APIC. If set to zero, the default address 0xFEC00000 is assumed) child 7 MMIO devirt 0xFEC10000 - IOAPIC child 8 MMIO devirt 0xFED00000 - HPET1 child 9 MMIO devirt 0xFED40000 - Trusted Platform Module (TPM) ? child 10 MMIO devirt 0xFED80000 - AMD ACPI MMIO address / General Purpose Input Output (GPIO) address (Southbridge?) / HPET2 child 11 MMIO devirt 0xFEDC2000 - Reserved no save memory ? child 12 - MMIO devirt 0xFEDD4000 - Reserved ? child 13 - MMIO devirt 0xFEE00000 - LAPIC - LAPIC registers are usually placed on address 0xFEE00000, and I/O APIC registers on address 0xFEС00000 child 14 - MMIO devirt 0xFF000000 - Int Mask Child 15 - MMIO devirt 0x10000000000 acpipci0 pcimem Child 16 - MMIO devirt 0x2BF40000000 acpipci3 pcimem Child 17 - MMIO devirt 0x47E80000000 acpipci2 pcimem Child 18 - MMIO devirt 0x63DC0000000 acpipci1 pcimem As you can see in the device interrupt areas these memory addresses are probably going to change between motherboards and devices on the PCI/PCIe lane. Anyways, research goes on... please dont take the above as gospel! Interesting PROBE of Asrock TRX40 Creator under Linux here: https://linux-hardware.org/index.php?probe=724cb22da0
  16. Driftwood
    Yeah, its a memory address error. Damn! thought I was onto something for a minute. In Catalina I hadn't fixed an error from the other week on that address. Thats from using BSS so long! Hopefully soon Algrey can nail down what these addresses relate to.
  17. Driftwood
    Interesting. I just swapped out my BMD 4K Monitor PCIe card for the 8K Decklink card and MMIO has changed to a skip 0 even though its YES in config. Which means, that slot 2 where I regularly swap round these two cards is using a hex address 0xE3300000 (child 3 out of 0 to 18) . The 100 pages for that address if I look further down could (I say could) indicate then that the next 100 page address is my Firewire card is seen at slot 4 on xFEA00000 (another 0x100 pages, 0x8000000000000001). With 4K Decklink 0xE3300000 (0x100 pages, 0x8000000000000001) skip 1 With 8K Decklin card devirt 0xE3300000 (0x100 pages, 0x8000000000000001) skip 0 I need to do some more tests... as it could be address error.
  18. Driftwood
    So Im probably not going to see any improvements on mine unless I get power table DSDT and GPU water-cooling which is making you improve back to Proxmox? Actually do you mind posting your latest config for me to analyse? There may well be something I have forgotten to do. Thanks @iGPU Did you check your debug boot log to seee if anything changed in the hex addresses for MMIO?
  19. Driftwood
    Adobe Apps Patch LINK. As a reminder for the group ALL Adobe BETA products now work without patching EXCEPT Photoshop and Illustrator. These Adobe Creative Cloud (2020) patches will do everything for current releases, but soon you wont need to do all of CC hopefully on final release (lets hope they do'nt recompile the Release candidates!). https://gist.github.com/naveenkrdy/26760ac5135deed6d0bb8902f6ceb6bd
  20. Driftwood
    @dtek Aquantia shouldn't need anything. Its supported by Apple. Shouldn't need to add anything for it. The Intel 10G should need a kext I believe, I replaced my wifi pic card like others here to Broadcom Mac compatible.
  21. Driftwood
    Big Sur Bare Metal Candle Test (Not as Quick As Proxmox, however we are using a patched dylib library replacing BMDs own to get Davinci Resolve working under Big Sur / AMD bare metal - and AMD BM is not supported under Mac from Davinci.. But even with the patch, it's still very acceptable. * On Proxmox I was getting apx 34fps on 66 Blur Nodes, Here around 20-24fps at moment of screen grab. Had a load of background apps going on if that didn't help. Test is available from here: https://www.liftgammagain.com/forum/index.php?threads/resolve-standard-candle-benchmark.3718/. (top three links in comment 1 of thread) Free Version of Davinci Resolve available here from BMD: https://www.blackmagicdesign.com/uk/support/ (see latest downloads, bottom left hand pane of browser) Davinci Patch For AMD: AMD-Davinci-Fix .zip (from iGPU link)
  22. Driftwood
    @iGPU Yeah I saw he had a number of misfortunes. Tragedy. Think it was Macpato on Discord who said he went back to Apple. Who knows, but we miss him.
  23. Driftwood
    @dtek Do u have this in BIOS? Or equivalent? I enabled S5 Soft off for USB wakeup and it seems it guarantees it in BS BM. Havent tried the others yet...
  24. Driftwood
    Now PikerAlpha is a legend... works for Apple now I heard! Oh, and there you are @fabiosun all over the comments! :-) I used to read his stuff. One of the best gurus around. :-) So we're back to looking for 0x3f Boy! Havent times moved on @fabiosun ?
  25. Driftwood
    Either. The methodology is exactly the same. If you set Above 4G on in BIOS, it may (or may not ) have different MMIO values found in your debug file. I think most of us with lots of devices inside our computers have it Enabled (and csm disabled in BIOS) See the blue highlighted bits here highlighted from the OC debut? The hex values are;- e.g.See straight after the text 'MMIO devirt' you'll see the first one - 0xCB100000 So enter this in Hackintools calc (or any hex to dec calculator) and it will give you the decimal value like in the example below (e.g. Hex to decimal value in mine = 3406823424) , then enter that Decimal value into a child under 'mmiowhitelist' in 'Booter' section of Config.plist. Do it for each hex to decimal value on each line (theres 19) from your OpenCore debug .txt and put each decimal equivalent into a new numbered child going up from 0 all the way to 18. You dont need to do 15-18 though as theyre not used. If you leave 15-18 in , make sure their boolean values are set to NO. Here's where the 'Childs' go see 0 the first one and so on... Download a config.plist of ours to see how we did it. But dont copy our values as yours might be different. Just make sure all 0 to 14 are Boolean = YES. For example in this graphic - I'm sure @iGPU exampled all this a few pages back in this thread if you want a clear and concise methodology!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.