Robert Posted May 19, 2016 Share Posted May 19, 2016 I've been using Fedora 23 as my primary OS for over a week now, with Gnome 3.18.2. Upon every reboot of the system it reverts to 100% maximum volume. I would normally work around this issue with my preset speaker volume, but the 100% volume is overloading the internal sound system so it crackles and breaks up on the speaker. Until I reset the Fedora/Gnome sound to about 80% it sounds awful no matter what the speaker volume is set too. Side note: I'll be going back to Ubuntu as my main system in a couple of days when my new graphics card (the old one replaced under warranty) arrives. I was unable to change my graphic settings in Ubuntu to a different backup graphic card I'm using while waiting so had to stop using Ubuntu. If the new card does the same I might be back here asking for help to get it to work. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 19, 2016 Share Posted May 19, 2016 Once you set the levels to what you like, run this as root to set the default audio level at boot: alsactl store 2 Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted May 19, 2016 Share Posted May 19, 2016 That will only work when using ALSA, of course. No help Fedora is using PulseAudio. Quote Link to comment Share on other sites More sharing options...
Robert Posted May 19, 2016 Author Share Posted May 19, 2016 I tried it anyway results: [robert@localhost ~]$ alsactl store alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists [robert@localhost ~]$ Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted May 19, 2016 Share Posted May 19, 2016 You must be root for that command to work, Robert. Quote Link to comment Share on other sites More sharing options...
Robert Posted May 19, 2016 Author Share Posted May 19, 2016 Now it says: robert is not in the sudoers file. This incident will be reported. I guess I should stop before the sound stops working completely or I get locked out. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 19, 2016 Share Posted May 19, 2016 That will only work when using ALSA, of course. No help Fedora is using PulseAudio. Most of the time, alsa works with pulse. It's not an either/or like i used to think. I actually use them together Quote Link to comment Share on other sites More sharing options...
Hedon James Posted May 19, 2016 Share Posted May 19, 2016 I always that ALSA was the base, acting on hardware; and PulseAudio was the UX layer that users were allowed to tinker with. Throw JACK into the mix and I tend to get lost....I just cross my fingers that the default config works fine! Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 19, 2016 Share Posted May 19, 2016 I always that ALSA was the base, acting on hardware; and PulseAudio was the UX layer that users were allowed to tinker with. Throw JACK into the mix and I tend to get lost....I just cross my fingers that the default config works fine! Correct. Alsa is built into the kernel and provides kernel level audio drivers whereas Pulse controls the sound. PulseAudio serves as a proxy to sound applications using existing kernel sound components like ALSA or OSS. https://wiki.archlin....php/PulseAudio Quote Link to comment Share on other sites More sharing options...
Robert Posted May 20, 2016 Author Share Posted May 20, 2016 I just booted up and it was at 80% so that command must have worked. 2 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 20, 2016 Share Posted May 20, 2016 I just booted up and it was at 80% so that command must have worked. Good deal 1 Quote Link to comment Share on other sites More sharing options...
Robert Posted May 20, 2016 Author Share Posted May 20, 2016 It didn't last. On another reboot volume was just a little bit higher. Next boot it jumped back to 100%. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 20, 2016 Share Posted May 20, 2016 It didn't last. On another reboot volume was just a little bit higher. Next boot it jumped back to 100%. Try going through some of the steps listed in this thread and see if it gets you anywhere and if not, post the configs and outputs from the commands here. Thanks Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted May 20, 2016 Share Posted May 20, 2016 It didn't last. On another reboot volume was just a little bit higher. Next boot it jumped back to 100%. Well, sat THUCKS! Quote Link to comment Share on other sites More sharing options...
Robert Posted May 21, 2016 Author Share Posted May 21, 2016 It's okay. Another boot and volume was at 80% where I left it. This is unpredictable. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.