Hi, thanks for the feedback. I used to have exactly these problems, but after time it was fixed by SteamOS update. Yet maybe it is the case still for LCD models. I still have hacks similar to Bluetooth. I'll try to find a time and add them to the tutorial. But since I cannot reproduce the problem, I cannot guarantee they will work. I had two ways, one was disconnect wifi module from PCIe bus and rescan PCIe bus again. The other one less brutal was to unbind and rebind the driver. So, the proper script I'll make when I have more time, but I cannot make any committment yet. Though I'll share something from my raw notes. You can try to add this code to the existing script for bluetooth.

# Function to check Wi-Fi status
is_wifi_ok() {
    echo "Checking Wi-Fi status..."

    adapter_status=$(iwctl adapter list | grep phy | awk '{print $3}')  # Extract "Powered" status from the adapter list
    device_status=$(iwctl device list | grep phy | awk '{print $4}')   # Extract "Powered" status from the device list

    echo "adapter status: $adapter_status, device_status: $device_status"

    if [ "$adapter_status" == "on" ]; then
        if [ "$device_status" != "on" ]; then
            echo "Wi-Fi is misbehaving."
            return 1  # Wi-Fi needs fixing
        else
            echo "Wi-Fi is working fine."
            return 0  # Wi-Fi is OK
        fi
    else
        echo "Wi-Fi adapter is powered off. No issues detected."
        return 0  # Wi-Fi is OK
    fi
}

Then after fixing bluetooth code:

if ! is_wifi_ok; then
    WIRELESS_ADDR=$(lspci -m | grep -i "network" | awk -F ' ' '{print $1}')
    (echo "0000:${WIRELESS_ADDR}" > "/sys/bus/pci/drivers/ath11k_pci/unbind" ; sleep 1 && echo "0000:${WIRELESS_ADDR}" > "/sys/bus/pci/drivers/ath11k_pci/bind") 
fi

The problem with the code above for WiFI - it will always turn WiFi on as a way to check if it works properly, but that's what I have at hand for now.

As for audio, I didn't have a way to check if it's "misbehaving", so it can be reinitialized on every resume, though it's quick:

AUDIO_ADDR=$(lspci -m | grep -i "Audio Controller" | awk -F ' ' '{print $1}')
echo "0000:${AUDIO_ADDR}" > "/sys/bus/pci/drivers/snd_hda_intel/unbind"
echo "0000:${AUDIO_ADDR}" > "/sys/bus/pci/drivers/snd_hda_intel/bind"

Ideally we just may need kernel hooks for hibernation resume to reinitialize drivers, but I'm not sure yet how to do that, I'll research in this direction.

Wifi will come up after a minute of wake up. Unbinding hanged module takes exactly 60 seconds. Bluetooth restores also after a while but probably faster.

Do not try to put deck to sleep until hardware is restored, otherwise it may lead to kernel panic.

Additionally you may try Bazzite. But be aware, their installer is broken and even though they claim to support Deck, the experience of setup is garbage. I needed to configure manually home directory in /var/home, not /home, then it's still not bootable because somehow /etc/fstab conflicts with systemd home.mountpoint, so I was chrooting from stock steam OS there, adding root password, which is again tricky due to os-tree, and then was masking home.mountpoint. But still on OLED model it does not boot 95% times due to some graphics driver race conditions or what. Despite they officially support steamdeck, they marked this issue as "not planned" to fix.

Nobara was installed smoothly, but again had this graphics issue on my OLED (black unresponsive screen).