Ryzen 7000 Testing

[rexxver]

hotplug is working, one user in this thread has confirmed that hotplug is working.

but for me nothing works

It should be installed in the lowest slot. The card will not be lit in the rest of the slots.
In addition, the card was recognized irregularly. I gave up in the end.

 

[fabiosun]

new bios for upcoming AM5 CPU
for now it seems a bit problematic for Asus Hero:https://macos86.it/topic/6145-build-ryzen-9-7950x-asus-rog-x670e-hero/?do=findComment&comment=143724

in this thread you can find also opencore debug file

 

[CaseySJ]

new bios for upcoming AM5 CPU
for now it seems a bit problematic for Asus Hero:https://macos86.it/topic/6145-build-ryzen-9-7950x-asus-rog-x670e-hero/?do=findComment&comment=143724

in this thread you can find also opencore debug file

I haven’t been following the rumor mill on this. What new AM5 CPU is coming out? I understand that new Threadripper Pro AM5 will be announced in about a week, but may only be available to OEMs.

 

[fabiosun]

Hi it is for AM5 socket
check on Asus..they updated many bios, i think also the one of your Gene

AMD Confirms 2024 Launch For Ryzen 8000 Zen 5 Processors

AMD has apparently confirmed details of its next generation of Ryzen desktop processors plus new generation of APUs

www.forbes.com

 

[fabiosun]

 

[etorix]

I haven’t been following the rumor mill on this. What new AM5 CPU is coming out?

Ryzen 8000 with Zen 5 cores, in 2024 for desktops. And—you'll love that part…—hybrid architecture with a mix of Zen 5 and Zen 5c cores, at least for some mobile/console CPUs.

I understand that new Threadripper Pro AM5 will be announced in about a week, but may only be available to OEMs.

Probably "Lenovo exclusive" for 6 months or so before being available at retail, like the 5000WX.

 

[fabiosun]

@CaseySJ @Shaneee


sent also via DM a video @ExtremeXT to take a look when he has time to dedicate to this

Curious if it is only a my problem with hero and my config/EFI

 

[CaseySJ]

@CaseySJ @Shaneee


sent also via DM a video @ExtremeXT to take a look when he has time to dedicate to this

Curious if it is only a my problem with hero and my config/EFI

Ouch, looks like DSDT and many system SSDTs are failing to load.

Regarding DSDT, macOS cannot find: \_SB.PCI0.GPP7.UP00.DP60.XH00.RHUB.POT6

Do Windows and/or Linux work with this BIOS?

 

[fabiosun]

WIndows 11 is perfect
now i am creating a UBuntu USB live to see

 

[fabiosun]

Yep also ubuntu is working well

 

[CaseySJ]

WIndows 11 is perfect
now i am creating a UBuntu USB live to see

Yep also ubuntu is working well

In the past we created a patch for Gigabyte DSDT problems. Now for Asus it seems we may also need to create patches for DSDT and some system SSDTs.

I assume macOS boot process freezes shortly after those ACPI errors are displayed?

 

[fabiosun]

@CaseySJ this is verbose i see

maybe it is safe to wait to another bios release version if this problem will be confirmed also from others AM5 users

 

[Shaneee]

Looks like it possible your BIOS update has renamed some stuff. I remember this happening when using a full DSDT in the system which is why SSDTs were used more often.

 

[CaseySJ]

@CaseySJ this is verbose i see

maybe it is safe to wait to another bios release version if this problem will be confirmed also from others AM5 users

Can you post all of the ACPI tables? This can be done by using OpenCore.efi debug binary and setting config.plist -> Misc -> Debug -> SysReport to True. Then ACPI files will be in "SysReport" folder located in root folder of EFI partition.

 

[fabiosun]

Can you post all of the ACPI tables? This can be done by using OpenCore.efi debug binary and setting config.plist -> Misc -> Debug -> SysReport to True. Then ACPI files will be in "SysReport" folder located in root folder of EFI partition.
View attachment 12064

Here you go also with debug log
1602 good for all OS (osx, windows,Ubuntu)
1709 not good for OSX

 

[etorix]

Looks like it possible your BIOS update has renamed some stuff. I remember this happening when using a full DSDT in the system which is why SSDTs were used more often.

Yup. The DSDT has been restructured.
Old version:

External (SB.PCI0.GP17.VGA_.AFN7, MethodObj) // 1 Arguments
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP60.XH00.RHUB.GPLD, MethodObj) // 2 Arguments

New version:

External (SB.PCI0, DeviceObj)
External (SB.PCI0.DADR, IntObj)
External (SB.PCI0.EBUS, IntObj)
External (SB.PCI0.FLG0, IntObj)
External (SB.PCI0.GP17, DeviceObj)
External (SB.PCI0.GP17.ACP_, DeviceObj)
External (SB.PCI0.GP17.AZAL, DeviceObj)
External (SB.PCI0.GP17.VGA_, DeviceObj)
External (SB.PCI0.GP17.XHC0, DeviceObj)
External (SB.PCI0.GP17.XHC1, DeviceObj)
External (SB.PCI0.GP18, DeviceObj)
External (SB.PCI0.GP19, DeviceObj)
External (SB.PCI0.GP19.XHC2, DeviceObj)
External (SB.PCI0.GPP0, DeviceObj)
External (SB.PCI0.GPP1, DeviceObj)
External (SB.PCI0.GPP1._ADR, IntObj)
External (SB.PCI0.GPP2, DeviceObj)
External (SB.PCI0.GPP3, DeviceObj)
External (SB.PCI0.GPP4, DeviceObj)
External (SB.PCI0.GPP5, DeviceObj)
External (SB.PCI0.GPP6, DeviceObj)
External (SB.PCI0.GPP7, DeviceObj)
External (SB.PCI0.GPP7._ADR, IntObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.UHBS, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6C1, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6C2, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6C3, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6C4, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6C5, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6C6, FieldUnitObj)
External (SB.PCI0.GPP7.UP00.DP40.UP00.DP00.WIFI.W6GS, FieldUnitObj)
External (SB.PCI0.GPP8, DeviceObj)
External (SB.PCI0.GPP9, DeviceObj)
External (SB.PCI0.GPPA, DeviceObj)
External (SB.PCI0.GPPB, DeviceObj)
External (SB.PCI0.GPPC, DeviceObj)
External (SB.PCI0.GPPD, DeviceObj)
External (SB.PCI0.GPPE, DeviceObj)
External (SB.PCI0.GPPF, DeviceObj)
External (SB.PCI0.GPPG, DeviceObj)
External (SB.PCI0.GPPH, DeviceObj)
External (SB.PCI0.M641, IntObj)

USB is now under GP17 and GP18; GPP7 has taken WiFi over. Need to re-do SSDTs for macOS.

Have you posted your current EFI somewhere?

 

[fabiosun]

Yup. The DSDT has been restructured.
Old version:

New version:

USB is now under GP17 and GP18; GPP7 has taken WiFi over. Need to re-do SSDTs for macOS.

Have you posted your current EFI somewhere?

i use only these two

 

[etorix]

On closer look, it's worse than I first thought. The USB objects under _SB.PCI0.GPP7.UPP0 which your SDDTs want still potentially exist under GPP7: In the new DSDT, their creation is now conditional upon various parameters (G002, G000, G003, G004). AMD may be preparing to introduce various tiers of CPUs with different capabilities.

And the first error in the screenshot is a failure to load the the DSDT itself. MacOS may have trouble with this conditional code.

 

[CaseySJ]

If the only error that is preventing DSDT from loading is due to the highlighted error...



... then the missing ACPI path \_SB_.PCI0.GPP7.UP00.DP60.XH00 is conditionally defined by this:

As we can see, there are 3 conditions:

    If (((G002 != 0x03) && ((G000 == One) && (
        G004 != 0x43FA1022))))

We could create an ACPI patch to change any or all of the conditions. Fortunately there are no other references to PCI0.GPP7.UP00.DP60, which means we don't have to worry about a conflicting device tree being created at the same path.

 

[fabiosun]

@CaseySJ have you update your Gene?

i am curious if it is a general problem or user problem!