I have installed a new SAS controller on my machine. No other changes.
Suddenly I noticed that the audio volume control in Plasma 5 got broken:
Right clicking that and then Audio volume settings gives:
Interestingly I am able to play audio. I just can’t control the volume.
Any ideas how to fix that?
Use pavucontrol or the veromix widget.
Note there are only settings on that screen if you have a program playing sound
I can’t find what veromix widget is and pavucontrol gives:
also I run this as user:
# start-pulseaudio-x11
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
veromix is from the KDE repo.
Have you run initrd to register the new hardware??
I have never heard about it and so far everything worked perfectly. Do I really need additional software to run the same hardware?
Have you run initrd to register the new hardware??
I have rebooted several times. Does that mean I have? All hardware actually works fine. The problem is missing software control of audio volume.
No just rebooting is not enough to discover new hardware. initrd will force a new hardware scan
You don’t need veromix but I like it better the the default volume control. It messes with pulse better IMO. In any case the problem is obviously with Pulse
Oops should be mkinitrd
Then how do you explain the new hardware is working fine? I hope you can clarify.
You don’t need veromix but I like it better the the default volume control. It messes with pulse better IMO. In any case the problem is obviously with Pulse
I will try to find veromix.
Can you explain how to do what you suggest?
Ok, I installed vermomix but I can’t find a way to use it. How do I do that?
Another thing: Going to System settings > Multimedia I see this:
Previously I could see more stuff in there (I am using SB Audigy2).
Also going to YaST > Sound gives me:
I have no idea why a second SB Audigy appears but when I try to configure it with Quick automatic setup I am getting:
Just for info: I don’t use the sound card of the motherboard. I have always used the SB Audigy.
Ok, I fixed it myself:
diff ~/.config/pulse/default.pa /etc/pulse/default.pa
33c33
< load-module module-stream-restore restore_device=false
---
> load-module module-stream-restore
...
I have no idea how what this line does and how it has changed in the local default.pa but after making it the same as in the /etc/pulse version and logging in again everything works like before.
So nothing to do with veromix or mkinitrd.
Dammit… broken again.
I simply plugged my Bluetooth dongle in the USB port and re-logged in. Even removing the dongle and rebooting didn’t help.
This time there is no difference in the default.pa files though.
Any ideas what is going on?
Renamed ~/.config/pulse/default.pa to backup.pa, logged out, then in - everything works.
Renamed backup.pa to default.pa, logout again, login - everything works.
Weird.
Maybe it will hold this time but to discover new hardware just as root run mkinitrd
Done. Here is the output:
http://paste.opensuse.org/f0eb026b
And… after rebooting it is broken again.