Ryzen 7000 Testing

[CaseySJ]

Aura LED controller via liquidctl:

% liquidctl list
Device #0: AsusTek Aura LED Controller (experimental)

% liquidctl status
AsusTek Aura LED Controller (experimental)
├── ARGB channels: 2      
└──  RGB channels: 1      

# set all channels to green
% liquidctl -m Aura set sync color static 00FF00

# set all channels to cyan
% liquidctl -m Aura set sync color static 00FFFF

# set all channels to purple
% liquidctl -m Aura set sync color static FF00FF

 

[CaseySJ]

Odd about the BIOS reset... Maybe the CMOS battery is faulty? Try re-seating it.

Windows 11 is also installed on this system, and reboots normally.

And can you send an IOReg dump?

IOReg attached for Big Sur

 

[ExtremeXT]

Windows 11 is also installed on this system, and reboots normally.


IOReg attached for Big Sur

Try enabling DisableRtcChecksum, known issue for Intel systems but not for AMD (CMOS reset).

 

[PoMpIs]

I add my last EFI...

In a few hours I have to disassemble the Ryzen, because I had already processed the return, and in 24 hours they come to pick it up and when the Intel 13000 are launched they send me one.....Probably a 13900KF .. the iGPU is just annoying

I always try new processors when they are released

I keep reading you guys... you have a very high knowledge in hackitnosh..

 

[CaseySJ]

Try enabling DisableRtcChecksum, known issue for Intel systems but not for AMD (CMOS reset).

I've tried it both ways. Will check if my Thunderbolt SSDT is causing issues.

 

[CaseySJ]

I add my last EFI...

In a few hours I have to disassemble the Ryzen, because I had already processed the return, and in 24 hours they come to pick it up and when the Intel 13000 are launched they send me one.....Probably a 13900KF .. the iGPU is just annoying

I always try new processors when they are released

I keep reading you guys... you have a very high knowledge in hackitnosh..

Thanks -- I'm going to compare notes.

Are you using Default BIOS parameters other than the under-volt options?

 

[PoMpIs]

Thanks -- I'm going to compare notes.

Are you using Default BIOS parameters other than the under-volt options?

If I have several options changed..

I get a TXT from the bios in a few minutes

 

[ExtremeXT]

I've tried it both ways. Will check if my Thunderbolt SSDT is causing issues.

Fixing RTC write issues | OpenCore Post-Install

Try this.

 

[PoMpIs]

Here I leave the TXT of the bios as it is now and it works quite well for me in Ventura

 

[ExtremeXT]

Windows 11 is also installed on this system, and reboots normally.


IOReg attached for Big Sur

IOReg is corrupted...

 

[CaseySJ]

IOReg is corrupted...
View attachment 7773

Aarg, will check shortly. Stepped out for coffee!

 

[CaseySJ]

IOReg is corrupted...
View attachment 7773

Aarg, will check shortly. Stepped out for coffee!

The file is okay -- just downloaded and tested on another system.

It is zipped, so need to decompress.

 

[ExtremeXT]

The file is okay -- just downloaded and tested on another system.

It is zipped, so need to decompress.

Which IORegistryExplorer version did you use to dump it?

 

[Pabo]

** Some Updates **

• I decided to assemble the system yesterday and started with Big Sur 11.6. No issues getting the O/S to install
  • AMD Ryzen 7 7700X 8-core 16-thread CPU
  • Asus Crosshair X670E Gene mATX board
  • G.SKill DDR5 memory (not EXPO)
  • BeQuiet! Pure Loop 2 FX 240mm liquid AIO cooler
  • PowerColor Radeon RX 5700XT GPU
• BIOS 0705 (latest)
• Big Sur is installed on SATA SSD mounted to an internal SATA port; will install NVMe SSD later
• iGPU disabled via SSDT
• Just completed the USB port map:
  • Aura LED controller enabled (see post below for liquidctl effects)
  • Realtek ALC4080 USB audio enabled
  • Intel Bluetooth enabled
  • Intel WiFi enabled
• Thunderbolt SSDT modified for this board, but no luck yet connecting Thunderbolt components; haven't spent much time on this yet
• Components that work:
  • Intel i225-V Ethernet port works out of the box
  • Intel WiFi and Intel Bluetooth both work properly with OpenIntelWireless drivers
    • Not using BCM94360NG or Fenvi FV-T919 at this time
  • USB 2, USB 3 Type A, USB 3 Type C ports all working

Issues / To-Do:

• Audio is occasionally choppy regardless of (a) Realtek 4080, (b) HDMI/DP output, (c) external USB DAC/Amp
• Disabling NB Azalia didn't seem to help, but will try again
• Each reboot causes a BIOS alert, requiring me to enter BIOS and Save/Exit
  • Fortunately all default BIOS parameters are compatible, but still need to figure this out
• Will work on sleep/wake soon

View attachment 7765View attachment 7766

What SATA SSD did you use ?

 

[CaseySJ]

Which IORegistryExplorer version did you use to dump it?

Version 3.0.2. Click here to download.

 

[CaseySJ]

What SATA SSD did you use ?

I'm using a simple Silicon Power A55 256GB SATA SSD.

 

[CaseySJ]

Basic Thunderbolt is okay when peripherals are connected before boot -- will test hot-plug with a modified SSDT shortly.

 

[ExtremeXT]

@CaseySJ
Can you try booting Monterey too?
Also, is the audio really bad? Try Speedkeeper.

 

[CaseySJ]

@CaseySJ
Can you try booting Monterey too?
Also, is the audio really bad? Try Speedkeeper.

Will work on RtcMemoryFixup momentarily.

Audio garbling/static frequency depends on the source, roughly as follows:

• Playing video from YouTube -- garble/static about 5-7 seconds apart
• Streaming music from Apple Music (subscription) -- virtually continuous
• Playing music through external USB DAC and Amp -- virtually continuous
  • I have a separate DAC with its own ESS Sabre chip connected to a separate headphone amp; both are powered by an external linear power supply; DAC is connected to computer via USB port

Will work on Monterey soon. I'm trying to stabilize Big Sur as much as possible before proceeding. This allows me to better keep track of variables.

 

[etorix]

Same here, z690 has working sleep on some boards, I just want one with two 5.0 m.2 slots.

Alder Lake CPU have "only" 20 PCIe lanes, compared with 24 for Ryzen 7000 (16+2*4). So you're out of luck, unless a manufacturer decides on a weird splitting of these lanes instead of the intended 16+4.