Jump to content

Driftwood

Members
 View Profile  See their activity

  • Posts

    457

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Everything posted by Driftwood

  1. Driftwood
    @Rox67erand @Rocket88 Can you do an experiment. You're both using Broadcom like me (Apple wifi/BT native) yeah? Keep my S5 settings (like u saw above ^) in BIOS 1. Still in BIOS, switch off BT (On/Off) to Disabled, Save BIOS, Reboot and try Sleep / Shutdown. Note what happens. 2. In BIOS, Switch back on BT (On/Off) = Auto, and Switch off the Intel Wifi &AX200 to Disabled. Save BIOS, reboot and again try Sleep / Shutdown - again note what happens. 3. Now in BIOS switch both BT (On/Off = Disabled and Intel Wifi &AX200 to Disabled), Save BIOS, reboot and again try Sleep/Shutdown - noting anything. 4. In BIOS, now Switch both on to Enabled and save, reboot and try again taking note. Take note, and let me know what happens with Bluetooth and Wifi (ie test them on Desktop on & off for working) whilst the 4 above conditions are operative. ie are they still working. Remember to try both Shutdown & Sleep. I am interested to see what happens with your current varying EFI setups whilst the above are selected. Make sure you try each variable and when you instruct Sleep Mode, leave asleep for at least 5 minutes before waking. Thank you.
  2. Driftwood
    I wonder if the json file USBToolbox produces could be read in in such a way to make it all even easier for device naming/type assigning in SSDT. I kind of like the visual aspect of USBToolbox...
  3. Driftwood
    I know what you mean @iGPU "Bygone era" made me laugh 🙂
  4. Driftwood
    BIOS Im using is 1.70 CSM disabled and Above 4G on. Plus, that .bin I sent you all in earlier thread. Incidentally, Asrock Creator TRX40 users: here's the PCIEe layout. Note, Ive been told there is no sharing of PCIe M2 with SATA they are all independent.
  5. Driftwood
    Here's a typical USBToolbox edited screen in an earlier test inside Windows.exe version. Basically it shows your Controllers, Scans your ports, (you can use its guesses if u like) but best to plug in a USB3/2 or even USB C device into necessary ports, swap USB C plugs around to test speed throughput, switch off USB 2 Or USB3, isolate and unlink from a 'Companion' port, etc... https://github.com/USBToolBox Its really pretty good.
  6. Driftwood
    @Rocket88 and @Rox67er / Asrock Creator users. You're only going to get sleep/shutdown working with the S5 / BIOS settings. Please experiment with the following;- This is how I have them Turn on Onboard LED in S5 to =Disabled (in Onboard Devices Configuration screen) and in ACPI Configuration: PCI Devices Power On = Disabled USB Power Delivery in Soft Off State (S5) to =Enabled
  7. Driftwood
    Latest OpenCore 0.7.4 will fix the update to Beta 7 Monterey negating the need to switch SMBIOS or any silly hacks we've been doing! Here: https://github.com/dortania/build-repo/releases/download/OpenCorePkg-6107bc9/OpenCore-0.7.4-RELEASE.zip
  8. Driftwood
    Ive decided to ditch my USB map as each of my USB controllers are no bigger than 10 ports. Well under the 15 per controller. Tell me if Im wrong?! Everything works fine without!
  9. Driftwood
    Sorry this is what I used.... quickly generated a SMBIOS for the cause. Feel free to use any of this as I now no longer need. I actually used all of these numbers in my config just in case it balked. I dont think you'll need to use j160 as the Mac17,1 profile will get you into the install. So leave SecureBootModel on Disabled. I believe quite a few Intel users had to do the same as above, and sometimes they had to re-download a few times. I think if you download with the 17,1 profile booted you'll be good. Type: iMac17,1 Serial (SystemSerialNumber): C02Q7EYGGG7L Board Serial (MLB): C02533200GUGPF7UE SmUUID: 2D61C34C-61C7-4854-82DC-44DDBBA3DD34 Apple ROM: 98FE945C3654 You could actually use the above to download, then retry the install, and on 2nd reboot you enter your 7,1 profile.
  10. Driftwood
    Dell 8K at 60Hz on Monterey
  11. Driftwood
    Yeah 422 10-bit encodes will smack up the CPU%. Interestingly, Monterey is the first OSX to fully support Adaptive Sync. Display is much better on this 8K monitor
  12. Driftwood
    Hey @fabiosun did you manage to suss how you got yours working? Im taking you didn't use the iMacPro17,1 method? When I tried just the MacPro7,1 method it kept going on a continuous reboot loop on the second reboot. So was forced to use the 17,1 hack method. Also question for everybody, if running Quicktime movies/Apple TV / or FCPX (like here) how much of your CPU% in VTDecoderXPCService is being used? Over 300% playback and sometimes unto 1000% for FCPX encodes? I would be interested in hearing results. Actually Davinci shows less than half the cpu& time over FCPX doing the same video.
  13. Driftwood
    Nice to see Apple still supporting Firewire/RME Fireface800 in Monterey!
  14. Driftwood
    Big Sur 11.5.2 straight to Monterey Beta 12.06 and then onto beta 7. Strangely I could only download the installer with that cruddy old EFI with all the patches on (no j160 was used!) - Reduced patch EFI just wouldn't do it. And then switched half way thru install (2nd reboot) to reduced patch EFI. And we're in! Now lets do 7. Now to do the beta 7 update you have to change SMBIOS to iMacPro17,1 - reboot - get the update. download, Install (during install some users have managed to change SMBIOS back to = MacPro7,1 and get the install working), or, after first reboot switch to your OC usb stick with 7,1 SMBIOS on (which is what I did in the end). Anyways, here's the complete process I did:- 1/ Change config to iMacPro17,1 Now let it download... you shouldn't need to set j160 in SecureBootModel to download. 2/ Let it continue install... 3/ It will reboot to black install gauge... 4/ Next reboot (if you can, switch configs to your 7,1 SMBIOS on a separate USB stick ) or let it go on to 17,1 install. 5/. As soon as your in Beta 7, ensure SMBIOS is back to MacPro7,1 settings, reboot to check. Update NVRAM. We're in!
  15. Driftwood
    @fabiosun You mean the first three patches: enter 20 for 32 core patches? Yeah I know about those here. Ill update to 703 shortly... Here's current EFI: Driftwood BS1152 Current EFI.zip The whole exercise above was for Asrock owners to demonstrate that Shutdown should work simply by following the S5 power options settings of mine in BIOS. Whether BT is used or not.
  16. Driftwood
    I have the minimal set on my EFI. 🙂 Just need to update OC now from .701 to .703
  17. Driftwood
    Sorry all, I left in all patches for anybody using my EFI just in case they needed some, also (anyone reading) paste in serials/MLBs... Actually this EFI boots and works fine with all OC patches untouched for those who wondered! Hi @iGPU: My point was, in BIOS you can leave BT on at Enabled/disabled, but if you remove the AX200 Intel wireless card and exchange for a Mac friendly Brdcom one like I think all us Asrock Creator users seem to have done you can disable the AX200 in PBS section of BIOS. Then with all the S5 settings in my graphics set, Shutdown will work again. Re: Shutdown not working since update: I HAD everything working well (inc shutdown). until I recently updated to 11.5.2 Big Sur and updated my Catalina boot drive. Sleep worked with my USB settings kext but for some reason my Shutdown failed to. That was the point as other Asrock users had said their Shutdown didnt work under latest BS and Monterey. Also, my hunch is that TRX40 need no fixes for shutdown. Just use BIOS. I also think it would work without the USB kexts in my EFI (but didnt try). The reason I used the USBfixtool kext was to discover what I would need on for Monterey which distinctly requires the 15 port rule... running it under Windows allows you to discover which linked ports and types.... thats why I prefer it over others.
  18. Driftwood
    SUCCESS! SHUTDOWN / SLEEP with BIOS Control (All take note) *** NO ssdts Required **** PLUS, MY USB MAP for ASrock TRX40 Creator Users Plus, my EFI with the map inside (Tested under Big Sur 11.5.2 and OC 0.71 built with Pavo's GenX) So here's my EFI for Asrock TRX40 Creator motherboard users. This EFI shutsdown correctly (see BIOS settings) and has Sleep Power management. Other motherboard users should check their BIOS for matching settings. Driftwood EFI:Driftwood EFI Big Sur.zip My EFI has my own USBMap_D.kext requiring USBToolBox.kext. I DON'T like to use SSDTs as I dont require anything. Getting Shutdown to work was fun. After I thought long and hard about it, it HAD to be something to do with BIOS and/or maybe turning off Bluetooth. But then it was the Power management sections which took closer scrutiny... So see my screens below to check you have those settings enabled/disabled and matched to mine. Having turned the Bluetooth/on and off I dont think it was that. But Turn Onboard LED to S5 to =Disabled, and, USB Power Delivery in Soft Off State (S5) to =Enabled could be the reason why Shutdown works. You absolutely DON'T NEED FixShutdown-USB-SSDT.dsl OR _PTS to ZPTS Patch or any Clover style fix. FOR ASROCK CREATOR USERS ONLY: I've attached a BIOS .BIN file if any Asrock TRX40 Creator (with latest BIOS already installed) can load in as a profile (just copy it to a external USB disk and on BIOS Setup on the Memory Screen choose the Add the Profile from Disk and install my BIOS settings! My BIOS Profile: driftwood_BIOS.BIN.zip Here's the BIOS screens needed to get Shutdown working:- A video will be placed here soon proving shutdown and sleep.
  19. Driftwood
    Like you I hate the memory checks but am not inclined to use a kext to switch off the annoying notification. Would changing the RAM speed to 2933MHz help? What constitutes the memory check? The closest we can achieve is their top of the line machine with:- 28-core 1.5TB 2933MHz DDR4 ECC LR-DIMM or R-DIMM ? Is this still the more 'Mac Friendly' way of doing it or do you all use Restrict Events? https://dortania.github.io/OpenCore-Post-Install/universal/memory.html#mapping-our-memory I see using DMIDecode the Mac Pro 7,1 expects ALL memory slots to be filled so you have to incorporate some dud/fake populated slots.
  20. Driftwood
    *Defined using USB mapping kexts or ssdt Rocket88 means (ports either enabled or not) i dont define realtek audio or use the ALC kext as Im firewire, i dont define LED controller either with USBToolkit & myusbkext, I dont use ssdts at all. I have Above 4G enabled. Sleep works, even turns my firewire off. If you have windows define your usb ports and types with usbtoolkit (download windows.exe/zip from usbtoolkit beta site) - its easier than mac version plus you get to see all the linked ports and types and then jut enable 15 ports from the total available it finds. Remember usb3 counts as 2 ports. Also it helps to show which way round you should insert your usb-C cables should go to achieve maximum 10Gb/s rather than superpeed! IfI get a chance Ill upload a video demoing sleep in BS11.5.2. PS I dont use WEG.
  21. Driftwood
    One thing Ive noticed with Asrock TRX40 board is if you fully populate all PCI-E slots and all NVMEs, plus a few internal SATAs / SSDs, and even if you've USB set to 15 ports, you can get quite a few problems under Big Sur. I had three M2 nvme's (2x MP600s and a 8tb Rocket). The MP600s on Slot 1 and 2, Rocket on 3. I found Mac BS boot on SSD was very problematic with ethernet and firewire card not working or erratically when they did. If I pulled out the slot 2 MP600 m2 drive all seems perfect! So watch your PCIE resources... they soon add up and begin to cause problems. FIREWIRE+RME Fireface800/400 fix under Big Sur For anyone with problems getting Firewire and RME Fireface audio working under Big Sur (11.5.2) and onwards, you may find yourself reinstalling the RME drivers time and time again to combat crackling. You shouldn't have to. Simply install, 'Accept' Security and Privacy for the RME driver, reboot. On reboot, you may hear crackle on audio for the RME first time. However, the switch off RME, then Log Out current User, Switch on RME (wait until red light goes out) and Login again as your user (ie dont reboot), and the RME should reset (orange light and red light should be out, and only two nice green LEDs indicating everything is sweet). Music!
  22. Driftwood
    Have you tried defining with USBToolkit.kext. Using Windows. As you know, I have sleep. And I have Realtek Audio /ALC and LED Controller undefined in USB definitions. I use Above 4G. Also I dont bother with SSDTs
  23. Driftwood
    macOS 10.15.7 Catalina (19H1417) Security Update All good! Haha! 😉
  24. Driftwood
    Check MMIO as maybe change with Above 4G if I remember.
  25. Driftwood
    Have we got an upgrade from Big Sur to Monterey b3 working yet without having to do fresh. Hope you all well, been busy filming!
×
×
  • 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.