Need help with Ryzen 7700X & Gigabyte X670E

[ManuelB]

which settings were made in Opencore ?

 

[CaseySJ]

@CaseySJ I still have a bioreg here, now after the restart Wlan is fine again because I'm trying to go to sleep again...do the bioreg files differ?

Stop its Gone

@ManuelB

I know English is not your native language, but the last two posts are difficult for me to understand.

Let's try this:

• Select Sleep from Apple menu (not "hibernate")
• Does the system enter sleep and stay asleep?
• Or does it wake up immediately?
• If it goes to sleep, can you wake it by pressing a key on keyboard?
  • NOTE: We have to press a key two times to wake the computer, like this:
    • When computer is sleep, press a key on keyboard (do not use Bluetooth keyboard at this time, but Logitech wireless keyboard is okay)
    • Now wait about 5 seconds
    • Then press another key on keyboard
    • Does the computer wake up?

 

[ManuelB]

@XtremeXT

 

[ExtremeXT]

I told you that's not needed anymore.. Sorry for the confusion... Try what Casey said.

 

[ManuelB]

@CaseySJ So it goes into sleep mode until I wake it up, but then it doesn't really go up and I've pressed and tested it several times

 

[ManuelB]

@XtremeXT I had already done that before, thought maybe you could see some information there that you could use sorry

 

[CaseySJ]

@CaseySJ So it goes into sleep mode until I wake it up, but then it doesn't really go up and I've pressed and tested it several times

Interesting. So it does not wake from sleep. We faced similar problem when working on Intel Alder Lake, where Gigabyte board would reboot when waking from sleep. The problem was fixed by patching one of the ACPI tables.

There is one ACPI table in your board that still fails to load. I can fix the problem shortly with a new patch.

There is no guarantee this will fix wake from sleep because we already know that one of the _PRW methods in DSDT had to be disabled. PRW means “Power Resources for Wake”.

 

[ExtremeXT]

Hmm, the other user's Gigabyte motherboard with the exact same ACPI patches works fine with sleep and wake, you sure it's not something else?

 

[CaseySJ]

Hmm, the other user's Gigabyte motherboard with the exact same ACPI patches works fine with sleep and wake, you sure it's not something else?

It may turn out to be something else, but we can start by ruling out the easy things first.

 

[CaseySJ]

Hmm, the other user's Gigabyte motherboard with the exact same ACPI patches works fine with sleep and wake, you sure it's not something else?

Do you know if the other Gigabyte user's SSDT-9 is failing to load? In the boot log below, table EXTGPP00 is defined in SSDT-9.

(AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
(AppleACPIPlatform) (SSDT:EXTGPP00) while loading table
(AppleACPIPlatform) (20160930/tbxfload-319)
(AppleACPIPlatform) ACPI Error:
(AppleACPIPlatform) 1 table load failures, 22 successful

There is a redefinition of GPE line-level event _L08 which is responsible for waking up several PCI bridges. The version in DSDT is currently used, but the version in SSDT-9 is not -- because the entire SSDT-9 is rejected at boot time.

I can fix this by moving all of _L08 from DSDT into SSDT-9 and renaming the DSDT's method to XL08, but if the other user experiences the same problem with EXTGPP00 and does not have sleep/wake issues, then we can move on to something else.

 

[ExtremeXT]

Do you know if the other Gigabyte user's SSDT-9 is failing to load. In the boot log below, table EXTFPP00 is defined in SSDT-9.

(AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
(AppleACPIPlatform) (SSDT:EXTGPP00) while loading table
(AppleACPIPlatform) (20160930/tbxfload-319)
(AppleACPIPlatform) ACPI Error:
(AppleACPIPlatform) 1 table load failures, 22 successful

There is a redefinition of GPE line-level event _L08 which is responsible for waking up several PCI bridges. The version in DSDT is currently used, but the version in SSDT-9 is not -- because the entire SSDT-9 is rejected at boot time.

I can fix this by moving all of _L08 from DSDT into SSDT-9 and renaming the DSDT's method to XL08, but if the other user experiences the same problem with EXTGPP00 and does not have sleep/wake issues, then we can move on to something else.

View attachment 8582

Yes, the other user also has an error related to _GPE, I'll ask for a kernel log to see if it's the same SSDT.

 

[ManuelB]

@CaseySJ Just wait a little like 10 minutes I already had a working idle state but through all the trying, what can I say, it doesn't work anymore I'm trying to restore this state

 

[CaseySJ]

@ManuelB,

If wake-from-sleep is still a problem, we can try this procedure...

We can look at the sleep log even if the computer does not wake properly from sleep. The procedure has to be done exactly as described below. It may be a good idea to print these steps on paper.

• Boot the computer and select Sleep from the Apple menu
• Wait until computer is asleep
• Let it sleep for about 30 to 60 seconds -- we want to make sure it does not auto-wake within the first minute
• Now press a key to wake it up
• Wait 10 seconds
• Did the monitor turn on?
• If not, press another key on keyboard
• Did the monitor turn on?
• If not, wait 20-30 seconds
• Now press and hold the power button until computer shuts down (do not press "reset" -- we must do a shutdown)
• Look at the time on your watch or phone. Write down the time -- CALL THIS TIME "A"
• Press power button to turn the computer on
• Start Ventura and log in
• Open Terminal from the Applications --> Utilities folder
• Now look at your watch or phone again. What time is it? -- CALL THIS TIME "B"
• What is the difference between TIME A and TIME B in minutes? -- CALL THIS X (minutes)
• Now type this command, but replace 10 with the actual number X followed by m (for minutes)
  • If X was 5, then replace 10m with 5m

log show --last 10m > ~/Documents/LargeBootLog.txt

• And finally, type this command:

pmset -g log > ~/Documents/SleepLog.txt

• There will be two new files in Documents folder called LargeBootLog.txt and SleepLog.txt
• Press compress and post both of them

 

[ManuelB]

@CaseySJ I already had a working state of rest, but all the attempts are no longer possible. I would just like to try to restore this state

 

[ManuelB]

@Casey I can't shut down the computer with the power button, only switch it off completely, I've just tried it

 

[CaseySJ]

@CaseySJ I already had a working state of rest, but all the attempts are no longer possible. I would just like to try to restore this state

To try and restore to old state, have you tried disabling both UTBMap.kext and USBToolBox.kext?

Another option is to test/verify the new UTBMap like this:

• Connect a USB Type C device to each USB Type C port, one by one, to make sure it connects and works
• Safely eject the device before moving it to the next port
• Then connect a USB Type A device to each USB Type A port, one by one, to make sure it connects and works
• Safely eject the device before moving it to the next port

 

[ManuelB]

@CaseySJ Ok, let's do it right away, I'm still testing... please have a look at post 235/236, I sent the iioreg 4 there and I was in hibernation, maybe you can find the difference there

 

[ExtremeXT]

You could try the latest UTBMap that you made from Windows which you posted above.

 

[ManuelB]

@CaseySJ the USBmap kext and tool kext are disabled all the time

 

[ManuelB]

@CaseySJ & ExtremeXT. I have now tried the USBMap Wlan works just like the ssdt's. I have now tested all usb connections, they are all recognized type c and usb 2.0 and 3.0

 

[ExtremeXT]

@CaseySJ & ExtremeXT. I have now tried the USBMap Wlan works just like the ssdt's. I have now tested all usb connections, they are all recognized type c and usb 2.0 and 3.0

So the problem is fixed? Which map did you use?