14 points ·
If that works, something with the PipeWire state might be weird. Tried deleting pipewire/wireplumber in `~/.local/state` followed by a reboot (or restarting pipewire and wireplumber). That should reset it.
u/Max_P — Max-P
Joined
Just some Internet guy
He/him/them 🏳️🌈
- IRC: Max-P on libera.chat
- Matrix: @max-p:max-p.me
Posts
- [Solved!] Swapped nvme from old deck into new deck, now headphones don't work · 36 points · 37 comments
- Problems with connecting to a stereo receiver? · 5 points · 11 comments
Comments
4 points ·
You could try having the HDMI input selected on the receiver before plugging it in, in case there's some EDID fuckery going on and it might pass it through that way. There might be some info dumped in `dmesg` as well that could help troubleshoot what it's not liking about. Computers try to be smart and output a supported resolution whereas a lot of AV equipment just outputs whatever it wants without checking.
If it is an EDID problem, there's ways to override it for the port so you could dump your TV's, then force it to use that one even when plugged into the receiver. Or you can use a generic 1080p/4K one.
Failing that, if your receiver and TV support eARC, I guess plugging directly into the TV and have the TV feed the receiver is an option.