- This topic has 11 replies, 6 voices, and was last updated Oct 19-3:41 pm by dolphin_oracle.
- Posts
rek769I have a one day old install of Antix 23.
Two sound cards are detected and I use the HDA-Intel ACH as the default. When I try to set volume levels in alsamixer the headphone entry (which is where my external speakers are attached) mutes itself every 3 seconds and won’t un-mute without intervention.
The Master channel can be adjusted to 100% but will then reset to 36% after a couple of seconds.
When I try to set the Headphone channel volume manually, it will mute before I can get to 50%.
The sound icon in the system tray changes state as evidenced by animation of the different sound levels but alsamixer remains at zero even while that occurs.
Any ideas greatly appreciated.
PPC
I just congratulated you on your Gnucash thread, for updating to antiX 23, and now I read this… đ
I see you are using antiX-23_x64-full… You updated antiX, so the new Pipewire configuration is working, right? The full version uses Pipewire sound server. Did you toggle it off, in order to use alsamixer?
If you didn’t, and are still using Pipewire audio server, if you haven’t yet, update antiX and, just to be on the safe side, reboot.
Open pavucontrol (that Pipewire uses as GUI to manage volume, etc) and try to set audio output from there.
On my work desktop pc, my tiny columns are also plugged into the headphone entry- as long as pipewire is working (or I’, using pure alsa sound) I have sound, on my “HDA-Intel” sound card.EDIT: if pavucontrol does not open correctly (i.e. you are using alsa), or opens and says “dummy output”, use to newer “pipewire toogle” to make sure that pipewire is off and then turn it back on. If pavucontrol opens, but reports “dummy output”, there is something wrong, because it should recognize almost instantly your columns, plugged into the headphones jack – You can download the script over at https://www.antixforum.com/forums/topic/disabling-pipewire-in-antix-23/page/3/#post-120671 and if you read a couple of posts below that one, I explain how to replace the default old pipewire toggle with that newer version (that, if all goes well, very soon will be included in antiX).
P.
- This reply was modified 1 month, 2 weeks ago by PPC.
- This reply was modified 1 month, 2 weeks ago by PPC.
rek769I have always used ALSA up until now so it’s instinct to open the terminal and use alsamixer.
So, when I tried to open pavucontrol it faulted and threw an error message.
I then pkill-ed pipewire and restarted it. Pavucontrol then opened without issue, saw my sound card, and everything stabilized. I now have sound and it seems to be fine. I will post here again if something is amiss after next reboot.
Thanks for being “johnny-on-the-spot” and for the quick help!
abc-nix
If you want to continue using pipewire, please try editing .desktop-session/startup and change the pipewire-start entry with
pidof -q pipewire | pipewire &
and see if the issue persists after rebooting.Hopefully this issue can be fixed with the toggle_pipewire script or in the next point release.
I think that upgrading before installing antiX 23 full should already prevent the issue from occurring (because of an updated startup file), but we may need to test a bit more.
Brian MasinickIf you want to continue using pipewire, please try editing .desktop-session/startup and change the pipewire-start entry with
pidof -q pipewire | pipewire &
and see if the issue persists after rebooting.Hopefully this issue can be fixed with the toggle_pipewire script or in the next point release.
I think that upgrading before installing antiX 23 full should already prevent the issue from occurring (because of an updated startup file), but we may need to test a bit more.
@abc-nix
I think you are right.I upgraded and performed all of the prep and update steps before and after installing antiX 23. Sound started working with all browsers and anything else I tried. Also your subsequent scripts have worked for me; sorry that isn’t the case for everyone but hopefully the new tool and the incremental changes will allow individuals to easily move between the available options and result in even better results, not just for me but for the entire community.
Thanks for your diligence and expertise in this matter.
--
Brian Masinickrek769Upon reboot and before changing .desktop-session/startup, pavucontrol was not able to see my HDA-Intel ACH sound card. It was able see the built in monitor speakers as an HDMI card.
After making the change to .desktop-session/startup and rebooting a second time, the situation remains the same.
I also now, can not open the alsamixer.
Is there any way to disable pavucontrol / pipewire and revert to using ALSA again?
marcelocripeI think that upgrading before installing antiX 23 full should already prevent the issue from occurring (because of an updated startup file), but we may need to test a bit more.
The startup file is not updated when we update antiX 23 with the “Automatic Update” option.
Is there any way to disable pavucontrol / pipewire and revert to using ALSA again?
Test this https://www.antixforum.com/forums/topic/disabling-pipewire-in-antix-23/page/3/#post-120671.
As pointed out, you can test the script and fully disable pipewire.
Alternatively, if you want to give pipewire a last chance, make sure there is only one entry that starts pipewire in your startup file (the change I recommended in my last message).
If you want pipewire completely removed from the system, after disabling pipewire with the pipewire toggle, and make sure there are no entries in the startup file for pipewire, uninstall pipewire with:
sudo apt purge pipewire* wireplumberrek769Thanks for all the help and suggestions. I was able to toggle off pipewire with the script and now everything seems to be working as it was before with V21. I have to start the browser with “apulse” but otherwise all good. I left pipewire on board hoping that it all gets sorted and I can try using it again at some point. I also removed the volume icon as I could not get it to work properly and in place I am using Qasmixer.
- This reply was modified 1 month, 2 weeks ago by rek769.
I also removed the volume icon as I could not get it to work properly and in place I am using Qasmixer.
That, and the fact that initially pipewire worked perfectly for you (once you restarted it) but now refuses to work… points to me to the fact that something may be wrong with your audio settings.
I found that, at least running live, pipewire can be a strange beast, I many times have problems after suspending my desktop. One of the problems is that pipewire, in pavucontrol, says “Dummy output” and I have no audio. Toggling pipewire off and back on (on the fly, with the latest version of pipewire-toggle that I pointed you to) instantly solves that. On my installed system, on my extremely underpowered netbook, I had to manually restart volumeicon, because it refused to appear on the system tray… so I added volumeicon to my window manager’s startup file too (without removing it from the session.desktop start file)- still volumeicon refused to start automatically… After a recent updated, I restarted my system and… noticed I had 2 volumeicons on my system tray…
Pipewire is now much solid, with the latest configuration, and the latest version of it’s toggle GUI does allow me to solve any audio problem on the fly… If you are satisfied with using alsa, then stick with alsa… My advice? If you use alsa, edit your web browser’s .desktop file, so the Exec line includes the prefix apulse, so you can just click the program’s icon to start it…P.
rek769I eschew DEs so I generally use fluxbox…so apulse is simply prepended to the menu command that launches the browser…simple.
dolphin_oracleIf something like this happens again with pipewire, check to see if multiple instances of wireplumber are operating. That can cause all sorts of conflicts, including no audio at all. when working on getting pipewire running on mx, I ran into they cycling audio problem. almost always multiple entries of wireplumber.
- You must be logged in to reply to this topic.