Jump to content

Rocket88

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by Rocket88

  1. 17 hours ago, Driftwood said:

    @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

     

     

     

     

     

    I am using the Asrock (Intel AX200 WiFi and Bluetooth). 

     

    I tried the following:

     

    1.     Default BIOS settings with all USB, WiFi, and Bluetooth SSDTs and kexts disabled.

    Result: No Sleep, but shutdown works just fine.

    2.     Turned off Bluetooth and WiFi in the BIOS. All USB, WiFi, and Bluetooth SSDTs and kexts disabled.

    Result: Once again, no Sleep, but shutdown works just fine.

     

    In the past, I played around with turning off various USB controllers in the BIOS, and I could get sleep to work, but then I didn’t have any USB ports.

  2. 1 hour ago, Driftwood said:

    @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

     

     

     

     

    I have the same BIOS settings as you, with the exception that I am using version 1.70 because that is the latest official release. 1.73 beta gave me problems a few months ago when I tried it. I don't recall what the problem was though. If I recall, you have a version 1.74 that you somehow acquired.

    I also tried USBToolBox and it worked great for setting the ports, but I still could not get sleep to work for me.

     

    On a side note, I would like to thank all of you for your efforts. Without you guys, I would have an expensive machine that would only be good as a space heater (and running Windows). 😀

     

    • Like 1
    • whahahah 2
  3. On 9/9/2021 at 5:46 PM, Rox67er said:

    Amazing work guys, a bit quit from my side lately but all is well.

     

    Have been reading along with the new developments and I just update my opencore 0.6.8 to latest 0.7.3 and included the new minimised set of patches. Installed latest bios update and after some tweaks all working fine again and just installed latest Monterey Beta on my backup drive which was also painless. Everything working including WiFi / BT / Aquantia / handoff etc. (except still no sleep, wakes immediately just like previous OS versions)

     

     

     

    My sleep always works. For me, I had to set up my USB ports correctly.

    Attached are my settings for Asrock TRX40 Creator. Your case settings will be slightly different than mine.

     

    * Need Realtek audio port to be defined. Without this, your computer will attempt to sleep and then pop back on.

    * On power up, no Realtek audio. Requires 1 sleep to work. Wish I could figure this out.

    * My Logitech camera quits working after two sleeps. I have to unplug and replug to get it to work.

    * LED Controller port MUST NOT be defined to keep from getting Code 99 problem.

    SSDT-TRX40-USB-Port_R88.dsl.zip

    • Like 1
  4. 22 hours ago, Arrakis said:

    Successful installion of Monterey from BigSur 11.5.1.

    Update is scrolling without problems.

    I did the installation from the EFi posted above here with two changes in the kexts (AirportItlwm-Mont.kext, BlueToolFixup.kext) and delete of the IntelBluetoothInjector.kext

    WiFI and Bluetooth operational.

     

     

    No more ethernet connection.

    The I210 ethernet modules are more recognized while the kexts are included in the OS so in theory recognized natively.

    1736954278_Montereyethernet.thumb.png.cb62e61b5abc654988970dda1fb4a2c4.png

     

    I had to make a change to my Kernel patches to get ethernet to work under Monterey. I changed MaxKernel to 21.99.99.1363652488_ScreenShot2021-08-08at9_10_29AM.thumb.png.90fb53aef76b9705073aa474023ffb30.png

  5. Does Big Sur 11.5 Beta 2 support AMD 6900 XT version XTXH? (Device ID: 0x73af). After spending hours yesterday trying to figure out why my brand new shiny EXPENSIVE Sapphire Toxic Extreme Edition card did not work with Big Sur 11.4, I found someone on the TonyMacX86 site that had to reprogram the BIOS to get his 0x73af card to work. Apparently Apple only supports the a device ID of "0x73bf". Who would have known this? Anyway, in Big Sur 11.4, if I look at /System/Library/Extensions/AMDRadeonX6000.kext...Info.plist line 418, I see the line: <string>0x73A21002 0x73AB1002 0x73BF1002</string>. In Big Sur 11.5 has this file been updated? Any suggestions? I really, really, do not want to change my BIOS. Thanks for any advise you guys can give me.

  6. This is for iGPU and anyone who owns the ASRock TRX40 Creator. I have updated my USB Map to fix my ports. See kext included. Note: I disabled the LED Controller USB port because it causes problems. Also, I solved the problem of XHC0 ports moving around on reboots by duplicating the ports for each address (XHC0@60000000, 61xx, & 62xx) . Look at the info.plist for details in the kext file. For me, everything works fine, except for sleep.

    AH_USB-Map2.kext.zip

  7. I promised a few weeks ago that I would post my Mac mini (Apple Silicon) scores. Our AMD hacks blow it away, of course, but after using the Mac mini for almost a week, it just works. It is super quiet. No heat, no noise, sleep works, etc. The only thing that really disappointed me was the amount of time it took to run Cinebench 23, especially with one core. I don't do any video editing, so I have nothing to compare it against. 

    Screen Shot 2020-12-05 at 2.06.27 PM.png

    Screen Shot 2020-12-05 at 2.09.15 PM.png

    Screen Shot 2020-12-05 at 2.14.03 PM.png

    Screen Shot 2020-12-02 at 11.55.56 AM.png

    Screen Shot 2020-12-02 at 12.20.26 PM.png

    • Like 1
    • Thanks 1
    • +1 2
  8. 2 hours ago, shutterbug168 said:

    @Rocket88 Do you mind sharing your EFI/USBMap? Before my AMD hack died, it was working better than my X299 hack -- my Apple Watch could unlock my hack consistently (not so with my X299 hack).  But it wouldn't sleep: it would go to sleep but immediately wake up, and then repeat the cycle.  Yes, I have to enable CSM to make the hack work -- no idea on why but it didn't have any impact otherwise. Thanks!

     

    Here is my EFI. I have turned off verbose because it works for me, but you will probably want to turn it on. Good luck !!!!

    Rocket88 EFI.zip

    • +1 2
  9. 16 hours ago, shutterbug168 said:

    So, my Gigabyte Trx40 Designare MB died on me more than a week ago, and I still haven't heard back from Gigabyte.  Its support service is one of the worst if not the worse.  In the mean time, I had ordered an Asrock Trx40 Creator to get my hack back up (we have an Asrock Windows machine working very well in the office).  Do I need to modify my EFI (based on @Ploddles's shared EFI) much for the Asrock MB? Thanks!

     

    My Asrock TRX Creator has been running great once I fixed the MMIO Whitelist and configured the USB ports correctly. Before I configured USB, I would get a code 99 failure on boot approximately 30% of the time. Now USB works on all ports ALL of the time. I never had this much success with my X99 machine. The main problem that I have this this card is I cannot run DisplayPort unless I have CSM enabled. This is a minor inconvenience. Sleep does not work for me, but I think the problem is my Vega 64 video card, which I also use as a "space heater". 

  10. 26 minutes ago, meina222 said:

    Forgot to mention - I am not aware of anyone having above 4G enabled and having success with the Gigabyte TRX40 boards on this forum. Not sure about other brands. Could be wrong, but I have it off.

    Asrock Creator, Vega 64, LG38U99W: I have not been able to get this to work either with DisplayPort. For some reason with my configuration, DisplayPort will only work with CSM enabled and with my BIOS, CSM must be disabled for "Above 4G" to be enabled. I am extremely disappointed with this bios feature. The reason I am sticking with DisplayPort is my monitor will give me 75Hz frame rate. With HDMI, the frame rate goes down to 30Hz. 

  11. I have never been able to get sleep to work. As far a shutdown goes, with the correct MMIO whitelist, my shutdown works great. Make sure Energy Saver is set to "Prevent computer from sleeping automatically..."

    My main problem now is that I get a code 99 on my Asrock Creator when I power on my machine, even when I use windows.

  12. Super Simple Way to Make a MMIO Whitelist

     

    1. Copy OpenCore to the EFI section of a USB stick.

    2. Create a dummy file called USB_STICK.txt or anything else. This is so you can find your USB stick when you boot up. This file goes in the top directory, at the same level as the EFI folder.

    3. Copy EFI->OC->Tools->OpenShell.efi to EFI->BOOT and rename "This" OpenShell.efi to BOOTx64.efi

    4. Reboot and set up your BIOS in the configuration that you plan on using, i.e. Above 4G enabled or disabled. Video cards in the slot you plan on sticking with.

    5. Select the USB stick as your Boot Device.

    6. Type FS0: then dir. If you don’t see your USB_STICK.txt file, then type FS1:

    Keep changing volumes (FSx:) until you find your USB_STICK.txt file.

    7. Type memmap > memmap.txt

    8. Reboot and use memmap.txt with xcode to edit your MMIO entries 

     

    memmap.txt will look something like this:

    Type       Start            End              # Pages          Attributes

    BS_Code    0000000000000000-0000000000007FFF 0000000000000008 000000000000000F

    Available  0000000000008000-000000000003EFFF 0000000000000037 000000000000000F

    BS_Data    000000000003F000-000000000003FFFF 0000000000000001 000000000000000F

     

    Reserved   00000000AC000000-00000000AFFFFFFF 0000000000004000 000000000000000F

    MMIO       00000000B2500000-00000000B2580FFF 0000000000000081 8000000000000001

    MMIO       00000000B3580000-00000000B3600FFF 0000000000000081 8000000000000001

    MMIO       00000000E2100000-00000000E2280FFF 0000000000000181 8000000000000001

    MMIO       00000000FA180000-00000000FA200FFF 0000000000000081 8000000000000001

    MMIO       00000000FA300000-00000000FA3FFFFF 0000000000000100 8000000000000001

    MMIO       00000000FEA00000-00000000FEAFFFFF 0000000000000100 8000000000000001

    MMIO       00000000FEC00000-00000000FEC00FFF 0000000000000001 8000000000000001

    MMIO       00000000FEC10000-00000000FEC10FFF 0000000000000001 8000000000000001

    MMIO       00000000FED00000-00000000FED00FFF 0000000000000001 8000000000000001

    MMIO       00000000FED40000-00000000FED44FFF 0000000000000005 8000000000000001

    MMIO       00000000FED80000-00000000FED8FFFF 0000000000000010 8000000000000001

    MMIO       00000000FEDC2000-00000000FEDCFFFF 000000000000000E 8000000000000001

    MMIO       00000000FEDD4000-00000000FEDD5FFF 0000000000000002 8000000000000001

    MMIO       00000000FEE00000-00000000FEEFFFFF 0000000000000100 8000000000000001

    MMIO       00000000FF000000-00000000FFFFFFFF 0000000000001000 8000000000000001

    Reserved   000000204F200000-000000204FFFFFFF 0000000000000E00 000000000000000F

    MMIO       0000010000000000-00000100103FFFFF 0000000000010400 8000000000000001

    MMIO       000003CB90000000-000003CBA03FFFFF 0000000000010400 8000000000000001

    MMIO       000003CBC0000000-000003CBD03FFFFF 0000000000010400 8000000000000001

    MMIO       0000069750000000-00000697603FFFFF 0000000000010400 8000000000000001

     

    The only thing you care about is Start Address. Also xcode will let you use the hex value with a 0x in front. Based on what others have said, I think we only care about the 1st 15 MMIO values, not anything on page 10400. 

     

    image.png.cd1455ddbd1d86a7d6e3943c48c68802.png

    (The comment is incorrect, I cut & pasted it from ,  Driftwood EFI by mistake).

     

     

  13. 1 hour ago, fabiosun said:

    @Rocket88

    for 2)

    have you tested the latest kext for rtl8125?

    for3)

    it works if you do the above advised things (above in this thread I mean)

    also you have to revisit (imho) some of your bios settings..I mean CSM and 4g part and also npci part in config...

    4g off and the use of npci=0x2000 are often related

     

     

     

     

    I used something called LucyRTL8125. It did not work for me.

    As far as the CSM / Above4G / npci=0x2000 goes, I am wondering if it is a special feature of this motherboard mated to my Vega64. I did not have any issues with the Vega 64 in my X99 setup with or without CSM.

     

    If I have CSM disabled and I boot into windows, I cannot get to the BIOS screen, so it really looks like a motherboard issue.

     

     

  14. Attached is my latest EFI folder for the Asrock TRX40 Creator / Vega 64 . It is work in progress. I do not have the MMIO in yet. 

    Look at the readme file in the EFI__in_work folder. You will need to rename this folder EFI to use and you will need to add your serial number. I have been using the latest version of OpenCore Configurator.app with the project set to 0.61 debug. This latest version has worked pretty well for me.

    What works in this build:

    1. Damn fast. Just like the Mac that Apple has yet to build. 

    2. Bluetooth with the stock chipset. 

    3. 10G Ethernet

    4. All of the USB ports.  

    5. DisplayPort and HDMI, as well as sound from these ports. Note: DisplayPort only works if you set CSM to Enabled. This causes all of the icons and text to be enlarged when booting up. 

     

    What does not work:

    1. AX200 WiFi.

    2. RTL8125 ethernet

    3. Realtec Audio. I have to use the Sabrent USB Audio device. 

     

    I forgot to mention: I did not try this with Big Sur, yet.

     

     

     

    EFI___in_work.zip

×
×
  • 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.