You are not logged in.
Greetings, I have been dealing with a very annoying issue ever since I seemingly got this system for the first time (which was some months ago) but I never experienced it much before as I used a bluetooth headset. I'm running a rig of the following specs:
Ryzen 9 9900X
Giagabyte B650 AORUS ELITE AX ICE
RX 9070 (not the XT version)
The issue is simple. If I cold boot (i.e. the system isn't initially running and I start it), I'm able to log into my window manager and everything mostly works, but the audio on the monitor speakers don't work and say "Dummy Output". If I reboot the system, this gets fixed and I'm able to see "Vega XX HDMI/DP audio" or something along the same lines.
So, to summarize, a cold boot = no audio. Warm boot = yes audio.
Audio:
Message: No device data found.
API: ALSA v: k7.0.12-zen1-1-zen status: kernel-api
Server-1: PipeWire v: 1.6.6 status: activeThis issue does not appear for my integrated GPU, which is able to initialize audio right from a cold boot. I've tried doing the following:
On BIOS:
* disable "fast boot"
* forcefully disable integrated GPU as well as the HD audio controller (which seems to pertain only to the integrated gpu)
Inside linux (I use Niri):
* restarted pipewire and wireplumber after logging in
* tried rescanning the PCIe bus
Outside Linux:
* Funnily, the issue even appears on Linux mint if I do a cold boot, so it's not really specific to Arch.
I would like to test out any other possible software-side workarounds or solutions before I deem that it's really a hardware-side issue. Can anyone please help?
I am indeed on a newer kernel 7.0.12-zen1-1-zen and have the following mesa version:
GPU0:
apiVersion = 1.4.348
driverVersion = 26.1.2
vendorID = 0x1002
deviceID = 0x7550
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon RX 9070 (RADV GFX1201)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 26.1.2-arch1.2Offline
Stuff like that is can often be tied to the UEFI version, how up to date are you there?
Online
Thanks for the suggestion. I found that my BIOS version was released about a year and a half ago. I updated my BIOS, but sadly, the issue still persists.
I was thinking I could probably instead have my Linux system detect if it's cold starting and do a hot-start immediately.
Offline
Mhm... when on a fixed boot where it works, try running an explicit
sudo alsactl store, does that help a subsequent cold boot?
Online