Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

[gandem]

Oops, forgot to fix a typo. Please try attached version of the driver. Now colors will be back to RRGGBB.

That fixed it!

 

[Kalypso478]

This is very interesting. My issues were VERY similar in how they unfolded. I suspect that there's another piece to the puzzle on this. Once I eliminated my bad cable, I was able to re-establish a working internet connection in automatic mode, but only when directly attached to my router, which is still the case for me. Can you test the port in automatic when directly attached to the router? You'd probably have to re-locate it.

Unfortunately, no. My router is at the other end of my apartment, which is why I use the WLAN repeater. At the moment I don't have a cable long enough to connect the PC directly to the router.

 

[gandem]

Apparently the WD_Black SN850 has problems when installed alongside other NVMe and not placed in M2.1.

I have my Win10 volume on a SATA SSD, my SN850 in the top slot and I have the other 3 M.2 slots populated with Firecuda 530's in a soft raid setup on Mac. I have had no issues like you're describing, but I have only had my SN850 in the top slot.

 

[CaseySJ]

Another interesting observation:
I wrote in POST #322 that I had massive problems with the WD_Black SN850 NVMe.

I was able to reproduce the same problem now:
I installed the WD_Black SN 850 in an external Thunderbolt 3 enclosure and then installed MacOS 12.2 Monterey there without any problems. Now I wanted to replace the internal MacOS installation with the new one. The "old" MacOS installation was on a WD_Black SN 750 NVMe. This was in the M2.2 socket 3.
The existing Windows 11 installation (Samsung SSD 970 EV0) was in M.2.1.
Now I have exchanged the WD_Black SN750 for the WD_Black SN850 in socket M2.2 and the system crashes with an error when uploading.
Now I have swapped the Windows 11 installation from M2.1 for the WD_Black SN850 and installed the Samsung SSD 970 EVO in M2.2.
Now both macOS and Windows will boot without any problems!!!

Apparently the WD_Black SN850 has problems when installed alongside other NVMe and not placed in M2.1.

Interesting. It seems that when a PCIe 4.0 NVMe SSD is installed along with a PCIe 3.0 NVMe SSD, then the faster PCIe 4.0 device should be placed ahead of the PCIe 3.0 device. Hence:

Config 1: Correct

• M.2 Slot 1: PCIe 4.0
• M.2 Slot 2: PCIe 3.0
• M.2 Slot 3: PCIe 3.0

Config 2: Not correct

• M.2 Slot 1: PCIe 3.0
• M.2 Slot 2: PCIe 4.0 <-- 4 cannot come before 3

Config 3: Correct

• M.2 Slot 1: PCIe 4.0 <-- my system has WD SN850 PCIe 4
• M.2 Slot 2: PCIe 4.0 <-- my system has Sabrent Rocket PCIe 4
• M.2 Slot 3: PCIe 3.0 <-- my system does not have any other M.2 drives

 

[dehjomz]

Interesting. It seems that when a PCIe 4.0 NVMe SSD is installed along with a PCIe 3.0 NVMe SSD, then the faster PCIe 4.0 device should be placed ahead of the PCIe 3.0 device. Hence:

Config 1: Correct

• M.2 Slot 1: PCIe 4.0
• M.2 Slot 2: PCIe 3.0
• M.2 Slot 3: PCIe 3.0

Config 2: Not correct

• M.2 Slot 1: PCIe 3.0
• M.2 Slot 2: PCIe 4.0 <-- 4 cannot come before 3

Config 3: Correct

• M.2 Slot 1: PCIe 4.0 <-- my system has WD SN850 PCIe 4
• M.2 Slot 2: PCIe 4.0 <-- my system has Sabrent Rocket PCIe 4
• M.2 Slot 3: PCIe 3.0 <-- my system does not have any other M.2 drives

Quirky!! This and the Thunderbolt device behavior when the system is off... !!

 

[gandem]

Interesting. It seems that when a PCIe 4.0 NVMe SSD is installed along with a PCIe 3.0 NVMe SSD, then the faster PCIe 4.0 device should be placed ahead of the PCIe 3.0 device. Hence:

Config 1: Correct

• M.2 Slot 1: PCIe 4.0
• M.2 Slot 2: PCIe 3.0
• M.2 Slot 3: PCIe 3.0

Config 2: Not correct

• M.2 Slot 1: PCIe 3.0
• M.2 Slot 2: PCIe 4.0 <-- 4 cannot come before 3

Config 3: Correct

• M.2 Slot 1: PCIe 4.0 <-- my system has WD SN850 PCIe 4
• M.2 Slot 2: PCIe 4.0 <-- my system has Sabrent Rocket PCIe 4
• M.2 Slot 3: PCIe 3.0 <-- my system does not have any other M.2 drives

What if you change the PCIe settings in BIOS from Auto and manually set it to PCIe 3?

 

[dehjomz]

I believe your cooler uses Addressable RGB LEDs that are connected to one or more of the three 5V 3-pin ARGB headers. Those headers are called argb1, argb2, and argb3. So please try:

# ARGB header 1 (top edge of motherboard):
% liquidctl set argb1 color static ff0000

# ARGB header 2 (bottom edge):
% liquidctl set argb2 color static 00ff00

# ARGB header 3 (bottom edge):
% liquidctl set argb3 color static 0000ff

Note that setting dynamic color modes such as Rainbow, Spectrum, Fading, etc. will apply to all channels.

Also please try a modified version of aura_led.py attached below. Simply copy it to:

/usr/local/Cellar/liquidctl/1.8.1/libexec/lib/python3.10/site-packages/liquidctl/driver

Do both 12V and 5V LEDs still work?

Things I notice:
1) You are credited in the driver! How cool.
2) if a kraken cooler or nzxt rgb device is installed, they are natively recognized by liquidctl. As such, when trying to control argb per the commands in your post, liquid fails with the following message:

'Error: too many devices, filter or select one (see: liquidctl --help)'

In this case, we can match to the device name and let liquidctl control asus alone instead of nzxt.
So Command becomes: 'liquidctl -m asus set argb2 color static 00ff00'

3) While the command works to control the color on the selected port, the lights on the other ports go out.
So by default, all ports are set to rainbow. However, when running liquidctl on port 3 (argb3), the lights on the other two ports go out. Not sure this should happen. They should remain in the mode they were in until specifically programmed by the user. Just a suggestion.

Otherwise, real cool that we can use python to extend liquidctl for Asus Aura. I can imagine a GUI wrapper around liquidctl (with buttons and color pickers and such) to control RGB. I just need to find the time to code it.

Edit: another observation, once the aura led controller is programmed by liquidctl, the settings survive a reboot and even a soft power off. I didn't cold boot to see what happens.

 

[ummario]

Awesome, ready to begin!

• Have you already copied the two Aura LED files as mentioned in this post?
• If so, please try these commands ('%' is just the prompt character, do not type it):

% liquidctl list

% liquidctl initialize

# set color to static red
% liquidctl set rgb color static ff0000

# set color to static green
% liquidctl set rgb color static 00ff00

# set color to static blue
% liquidctl set rgb color static 0000ff

# turn LEDs off
% liquidctl set rgb color off

• Because your case comes with its own controller, it may be necessary to switch it to "motherboard control" first.

It works! You are a genius my friend!

The only side note Is that I'm getting different colours from the ones you wrote above and previous post (maybe a typo from you or something is wrong.) Here's what I get when I enter:

liquidctl set sync color static ff0000 - turns on blue (instead of red) edit: Turns on red
liquidctl set sync color static 00ff00 - turns on green (ok)
liquidctl set sync color static 0000ff - turns on Red (instead of blue) edit: Turns on blue
liquidctl set sync color static 00ffff - Turns on Yellow (instead of cyan) edit:Turns on cyan
liquidctl set sync color off - turns off
liquidctl set sync color rainbow - Turns on rainbow
liquidctl set sync color static ff00ff - turns on purple

Good Job!

Will you make a table with the different colours we can try?

EDIT - Only later noticed that you changed to new file. Now all colours are Ok!

 

[gandem]

It works! You are a genius my friend!

The only side note Is that I'm getting different colours from the ones you wrote above and previous post (maybe a typo from you or something is wrong.) Here's what I get when I enter:

Try the one linked here.

 

[ummario]

Try the one linked here.

Thanks I forgot this last post!

edit - Now the colours works fine!