I haven’t booted into my Endeavour system in a while. When I did a couple days ago there were, of course, a lot of updates - including kernel and the post-Atlantis updates. After doing this, my audio volume is VERY low. I have set all audio channels to max in pavucontrol and alsamixer (on the Pipewire device and the actual sound card) and it’s still very quiet. It was working great before the update. An issue with pipewire maybe? An update to the sound chip driver? I have onboard Intel HDA.
I even did a fresh install from the liveusb and I’m having the same issue. If I boot into Windows I have ear-splitting volume. I have noted this from within the liveusb environment, XFCE, and KDE with a fresh install.
Anyone else notice something like this? Any suggestions?
Welcome to the forum! Or your first post after using eos for a while
Was this with the old iso or Atlantis?
Could you try booting in current and lts kernel?
The rest of the audio problem you describe should not be related to pipewire change on the new iso if you just updated your system from the previous August iso. To my understanding eos was still using pulseaudio, and the update would just update pulseaudio and not automatically install pipewire.
I downloaded the latest iso and have the problem in the live environment as well as a fresh install from the new iso.
Previously, I did a system update which introduced the issue. But since I have done a fresh install, I don’t have logs and can’t back out packages. Your note about pipewire is good - I saw the issue after an update, and if pipewire had not replaced pulse at that time, then we’re looking at something else. Soundcard driver? Something else in the kernel?
Ok, here’s something fun. In all this dual-booting, reinstalling, etc., I never had shut down the computer completely. Once I did and booted right back into Endeavour, the sound is at normal levels now. I have heard of other dual-boot issues where if you go from Windows into Linux, the hardware may be left in a certain state that causes problems. I’ll keep an eye on it, but at least for me, this seems like a workaround… when going from Windows to Linux, shut down the machine completely and boot directly into Linux.
