I am seeing the exact same issue on a PC I just put together and loaded Fedora 43 Workstation on. If I hook the 3.5mm jack for the speakers (older Creative Pebbles) to the green port on the back panel it shows up just like OP’s when I try to test; however, if I plug the jack into the headphones port on the case (which is connected to the motherboard audio pins) it detects and works properly. I was also seeing some Dummy Output options with the line out connection in use, and not knowing what it meant, I selected one and this kicked me back to the login screen and gave me an unhelpful kernel alert.

In contrast, the speakers on my other PC, which is also running Fedora 43 Workstation, works fine off of the back panel. Both motherboards are using Realtek audio chips but it may not be the same version since one board is a B650 and one is a B550.

Curious to see what the solution ends up being but I also recently installed pavucontrol on the newer PC so I will try and set the speakers up using the line-out that way. If that doesn’t work I will migrate to bluetooth speakers or just leave things as is.

Good call. I think this post has definitely been worth the effort since you guys are giving me some ideas I wouldn’t have thought of otherwise. Thank you!

That is really interesting and I wouldn’t have considered doing that since I already replaced both of them with a fresh set. I guess only concern with the long term benefit of going down to a single stick would be giving up 16GB of RAM (since this is a 32 GB kit) and then I might get higher speed but I would also get lower bandwidth overall since I lose the dual channel benefit. Weighing that option vs running the dual mode with 32GB at a slightly lower speed makes for an interesting conundrum. I will test this option if I can’t get stable and error free performance from adjusting the SOC setting down. Thank you again.

Thanks for the feedback. I haven’t tried pulling one stick but I did replace them both so I figured that eliminated them from suspicion. I also tried manually adjusting all of the primary timings and the speed to see if the XMP defaults were just being applied wrong. I think the voltage settings are my most likely culprit in this case so at least I have another thing I can try which doesn’t involve a complete tear down and waiting another week for yet another part to get to me.

Thanks Shadow. I had never considered something like this and all of the other suggested fixes I found via forum posts pointed to the physical hardware being the most likely causes. I will try and manually set the SOC voltage tonight to a fixed value (since I am 100% it is set to Auto) and do some more testing.

Just out of curiosity, what voltage ended up working for your setup? From what I am reading in the linked post and a post which is linked within it, I could go lower (0.9200-0.9600; leaning towards 0.925 VDC) or higher to something like 1.1VDC, but one comment mentioned higher voltage can actually increase instability…ugh. Anyways, thank you for the reply and suggestion!