Low sound volume on Lenovo laptop under Fedora Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionSetting maximum volumeHow to have CoreAudio from Mac to Linux/Unix?How do I make Wheezy see my sound card?How to troubleshoot audio problems / issues in Arch?Sound is very low (almost not audible) from primary sound card, Debian 8, pulse audiolow volume in ALSA soundDistortion At High Volume On Headphonesgentoo alsa pulseaudio - alsa mixer works; aplay straight to hw:1,0 works; aplay to any of configured PCM does not workUbuntu: No sound from speakers, headphones jack detected even when no headphones are connectedBluetooth Headset volume too low (only in arch)Multiple problems with alsamixer after opening up laptop (no problems in other OSs)
Can a new player join a group only when a new campaign starts?
Why didn't Eitri join the fight?
How do I make this wiring inside cabinet safer? (Pic)
An adverb for when you're not exaggerating
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
Chinese Seal on silk painting - what does it mean?
Is there any way for the UK Prime Minister to make a motion directly dependent on Government confidence?
Wu formula for manifolds with boundary
Maximum summed powersets with non-adjacent items
Can you use the Shield Master feat to shove someone before you make an attack by using a Readied action?
Is "Reachable Object" really an NP-complete problem?
When the Haste spell ends on a creature, do attackers have advantage against that creature?
Did MS DOS itself ever use blinking text?
What does できなさすぎる means?
Generate an RGB colour grid
Amount of permutations on an NxNxN Rubik's Cube
What is the meaning of the new sigil in Game of Thrones Season 8 intro?
Delete nth line from bottom
How to compare two different files line by line in unix?
What is homebrew?
What do you call the main part of a joke?
How does the math work when buying airline miles?
When a candle burns, why does the top of wick glow if bottom of flame is hottest?
Is there a kind of relay only consumes power when switching?
Low sound volume on Lenovo laptop under Fedora
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionSetting maximum volumeHow to have CoreAudio from Mac to Linux/Unix?How do I make Wheezy see my sound card?How to troubleshoot audio problems / issues in Arch?Sound is very low (almost not audible) from primary sound card, Debian 8, pulse audiolow volume in ALSA soundDistortion At High Volume On Headphonesgentoo alsa pulseaudio - alsa mixer works; aplay straight to hw:1,0 works; aplay to any of configured PCM does not workUbuntu: No sound from speakers, headphones jack detected even when no headphones are connectedBluetooth Headset volume too low (only in arch)Multiple problems with alsamixer after opening up laptop (no problems in other OSs)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm having trouble hearing anything at all under Fedora 16 on this Lenovo T520. Everything in alsamixer is at 100% (both pulseaudio and card). I installed Windows 7 on the laptop to check if the same issue is present on windows, and it's not.
Does anyone know how to deal with this? I've been annoyed by this problem for almost a year, but now with the heat wave on the east coast, I have to run my AC at full blast and I can't hear anything with the AC on.
Under audacity I can get definitely get high volume out of my speakers by just mixing up the sound volume. Is there a way to run a software amplifier between PulseAudio and alsa to crank up the volume or is there something that can be done in alsactl.conf to get the card to normalize the sound volume scale at a lower point? Since this laptop is quite common among Linux users, I would hope that someone has come up with a solution.
fedora alsa pulseaudio
|
show 3 more comments
I'm having trouble hearing anything at all under Fedora 16 on this Lenovo T520. Everything in alsamixer is at 100% (both pulseaudio and card). I installed Windows 7 on the laptop to check if the same issue is present on windows, and it's not.
Does anyone know how to deal with this? I've been annoyed by this problem for almost a year, but now with the heat wave on the east coast, I have to run my AC at full blast and I can't hear anything with the AC on.
Under audacity I can get definitely get high volume out of my speakers by just mixing up the sound volume. Is there a way to run a software amplifier between PulseAudio and alsa to crank up the volume or is there something that can be done in alsactl.conf to get the card to normalize the sound volume scale at a lower point? Since this laptop is quite common among Linux users, I would hope that someone has come up with a solution.
fedora alsa pulseaudio
Or try a different kernel version? -- bugzilla.altlinux.org/show_bug.cgi?id=23705
– imz -- Ivan Zakharyaschev
Dec 14 '12 at 8:59
Did you ever tried alsamixer through command line? some time GUIs doesn't work properly! I had same problem on my dell laptop which solved by justify PCM column to 100%.
– hassan_noori
Jan 5 '13 at 9:01
Perhaps volume turned down with some physical wheel thingy? Happened to me once...
– vonbrand
Feb 4 '13 at 18:48
Do you use fedora 16 default (gnome)? Did you trygnome-control-center sound
and maxing out the volume-bar at the bottom?
– xx4h
Feb 12 '13 at 19:54
funny, i have an identical setup (520/F16) with no sound issues
– amphibient
Mar 23 '13 at 2:34
|
show 3 more comments
I'm having trouble hearing anything at all under Fedora 16 on this Lenovo T520. Everything in alsamixer is at 100% (both pulseaudio and card). I installed Windows 7 on the laptop to check if the same issue is present on windows, and it's not.
Does anyone know how to deal with this? I've been annoyed by this problem for almost a year, but now with the heat wave on the east coast, I have to run my AC at full blast and I can't hear anything with the AC on.
Under audacity I can get definitely get high volume out of my speakers by just mixing up the sound volume. Is there a way to run a software amplifier between PulseAudio and alsa to crank up the volume or is there something that can be done in alsactl.conf to get the card to normalize the sound volume scale at a lower point? Since this laptop is quite common among Linux users, I would hope that someone has come up with a solution.
fedora alsa pulseaudio
I'm having trouble hearing anything at all under Fedora 16 on this Lenovo T520. Everything in alsamixer is at 100% (both pulseaudio and card). I installed Windows 7 on the laptop to check if the same issue is present on windows, and it's not.
Does anyone know how to deal with this? I've been annoyed by this problem for almost a year, but now with the heat wave on the east coast, I have to run my AC at full blast and I can't hear anything with the AC on.
Under audacity I can get definitely get high volume out of my speakers by just mixing up the sound volume. Is there a way to run a software amplifier between PulseAudio and alsa to crank up the volume or is there something that can be done in alsactl.conf to get the card to normalize the sound volume scale at a lower point? Since this laptop is quite common among Linux users, I would hope that someone has come up with a solution.
fedora alsa pulseaudio
fedora alsa pulseaudio
edited Oct 1 '13 at 22:21
mattdm
29.1k1372117
29.1k1372117
asked Jul 8 '12 at 0:15
eofeof
50145
50145
Or try a different kernel version? -- bugzilla.altlinux.org/show_bug.cgi?id=23705
– imz -- Ivan Zakharyaschev
Dec 14 '12 at 8:59
Did you ever tried alsamixer through command line? some time GUIs doesn't work properly! I had same problem on my dell laptop which solved by justify PCM column to 100%.
– hassan_noori
Jan 5 '13 at 9:01
Perhaps volume turned down with some physical wheel thingy? Happened to me once...
– vonbrand
Feb 4 '13 at 18:48
Do you use fedora 16 default (gnome)? Did you trygnome-control-center sound
and maxing out the volume-bar at the bottom?
– xx4h
Feb 12 '13 at 19:54
funny, i have an identical setup (520/F16) with no sound issues
– amphibient
Mar 23 '13 at 2:34
|
show 3 more comments
Or try a different kernel version? -- bugzilla.altlinux.org/show_bug.cgi?id=23705
– imz -- Ivan Zakharyaschev
Dec 14 '12 at 8:59
Did you ever tried alsamixer through command line? some time GUIs doesn't work properly! I had same problem on my dell laptop which solved by justify PCM column to 100%.
– hassan_noori
Jan 5 '13 at 9:01
Perhaps volume turned down with some physical wheel thingy? Happened to me once...
– vonbrand
Feb 4 '13 at 18:48
Do you use fedora 16 default (gnome)? Did you trygnome-control-center sound
and maxing out the volume-bar at the bottom?
– xx4h
Feb 12 '13 at 19:54
funny, i have an identical setup (520/F16) with no sound issues
– amphibient
Mar 23 '13 at 2:34
Or try a different kernel version? -- bugzilla.altlinux.org/show_bug.cgi?id=23705
– imz -- Ivan Zakharyaschev
Dec 14 '12 at 8:59
Or try a different kernel version? -- bugzilla.altlinux.org/show_bug.cgi?id=23705
– imz -- Ivan Zakharyaschev
Dec 14 '12 at 8:59
Did you ever tried alsamixer through command line? some time GUIs doesn't work properly! I had same problem on my dell laptop which solved by justify PCM column to 100%.
– hassan_noori
Jan 5 '13 at 9:01
Did you ever tried alsamixer through command line? some time GUIs doesn't work properly! I had same problem on my dell laptop which solved by justify PCM column to 100%.
– hassan_noori
Jan 5 '13 at 9:01
Perhaps volume turned down with some physical wheel thingy? Happened to me once...
– vonbrand
Feb 4 '13 at 18:48
Perhaps volume turned down with some physical wheel thingy? Happened to me once...
– vonbrand
Feb 4 '13 at 18:48
Do you use fedora 16 default (gnome)? Did you try
gnome-control-center sound
and maxing out the volume-bar at the bottom?– xx4h
Feb 12 '13 at 19:54
Do you use fedora 16 default (gnome)? Did you try
gnome-control-center sound
and maxing out the volume-bar at the bottom?– xx4h
Feb 12 '13 at 19:54
funny, i have an identical setup (520/F16) with no sound issues
– amphibient
Mar 23 '13 at 2:34
funny, i have an identical setup (520/F16) with no sound issues
– amphibient
Mar 23 '13 at 2:34
|
show 3 more comments
4 Answers
4
active
oldest
votes
I've done this in the past and have had pretty good success with boosting the volume up. The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%.
However with the steps below should remain "sticky" from reboot to reboot.
Turning up the volume
If you right click on the speaker applet and select sound preferences you'll bring up this dialog.
confirming and saving changes
Turn the volume all the way up to 150%. Once it's been turned up you can close this dialog. If you go to a shell and type the command amixer
you can confirm this:
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 98304 [150%] [on]
Front Right: Playback 98304 [150%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [off]
Front Right: Capture 65536 [100%] [off]
If you then run this command you can save this state out so that the next time you restart your system, it will be the default.
# saves settings
$ sudo alsactl store
# confirm file's created
$ ls -l /etc/asound.state
-rw-r--r-- 1 root root 4761 Oct 5 16:54 /etc/asound.state
Other things with amixer
You can use the command amixer
to change the volume as well.
100%
$ amixer sset Master 100% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
150%
$ amixer sset Master 150% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
NOTE: This method doesn't allow you to go higher than 100%, however.
mute
$ amixer sset Master muted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [off]
Front Right: Playback 65536 [100%] [off]
unmute
$ amixer sset Master unmuted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
|
show 3 more comments
From what I know you can use the softvol plugin for ALSA and set the max_dB
value. Something in direction of:
pcm.!default
type plug
slave.pcm "softvol"
pcm.softvol
type softvol
slave
pcm "hw:0,0"
# pcm "dmix" or this or the like.
control
name "PreAmp"
card 0
min_dB -5.0
max_dB 30.0 # 50.0 is max
resolution 16
Perhaps some hints here as well. Then reload alsa, play e.g. speaker-test -c2 -twav
to get it loaded and then adjust amp in alsamixer.
If one want to shut down PulseAudio, remember to deactivate autospawn
.
echo autospawn=no >> ~/.pulse/client.conf
or uncomment it in the global client.conf
(in /etc/pulse/
or the like). (Have also seen some replace daemon-binary
with /bin/true
.)
However using pactl etc. would perhaps be more preferable.
From commandline say:
pactl set-sink-volume 0 65536 # 100%
pactl set-sink-volume 0 98304 # 150%
pactl set-sink-volume 0 131072 # 200%
| |
| +----- Based on volume steps
+------- Sink number
To list and identify sinks say:
pactl list sinks
pacmd list-sinks # a bit more verbose, and list "volume steps"
As always man
and pacmd -h
, pactl -h
.
To set default volume to e.g. 150% edit ./pulse/default.pa
and add the line:
set-sink-volume 0 98304
|
+-- (Use full name if one e.g. have multiple USB-soundcards.)
For convenience add an alias or a short script to set this value when ever you want.
To restart PA say pulseaudio -k
, and pulseaudio --start
.
Another option would be to look into plugins e.g. LADSPA and shw in ALSA or PulseAudio.
EDIT:
OK. Came to think about it. This might be suitable. (Don't know how it escaped me first time around.)
- In
default.pa
add a Pulse Audio module from Device Drivers. - Restart Pulse Audio.
- Open Sound settings and set volume for original sink to e.g. 150%. (Or do this by commandline or pre-set it in
default.pa
as described above.) - Select the new module/sink as device for sound output.
This will give you 150% as 100% when using the normal volume meter.
Example – using module-remap-sink
:
Do not uncomment as the doc say.
In default.pa
:
.ifexists module-remap-sink.so
# Using remap-sink as dummy, not doing any re-mapping.
load-module module-remap-sink sink_name=VolDummy master=0 sink_properties=device.description=CrankThaVolume
.fail
.endif
# Set it as default:
set-default-sink VolDummy
Then restart Pulse Audio to get the new module registered.
Issuing:
$ pactl list modules # Should show "Usage counter: 1" for the module in question.
$ pactl list sinks
should show a new sink. You can still crank the volume for master by using command-line and/or adding lines to default.pa
.
Yeah, it looks like theset-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.
– mattdm
Oct 8 '13 at 23:03
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
add a comment |
When running alsamixer from the command line, be sure to run with the --view all
switch to ensure you're looking at all available mixer controls.
alsamixer -V all
Also, press F6 in alsamixer and check the settings for each device listed.
add a comment |
I had a similar problem one time in Fedora 18. Turned out Google's "pepperbox" API for Flash had some serious issues with sound, and I solved it by going into /home//.config/google-chrome and killing PepperFlash, then reinstalling flash plugins from Adobe.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f42561%2flow-sound-volume-on-lenovo-laptop-under-fedora%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've done this in the past and have had pretty good success with boosting the volume up. The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%.
However with the steps below should remain "sticky" from reboot to reboot.
Turning up the volume
If you right click on the speaker applet and select sound preferences you'll bring up this dialog.
confirming and saving changes
Turn the volume all the way up to 150%. Once it's been turned up you can close this dialog. If you go to a shell and type the command amixer
you can confirm this:
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 98304 [150%] [on]
Front Right: Playback 98304 [150%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [off]
Front Right: Capture 65536 [100%] [off]
If you then run this command you can save this state out so that the next time you restart your system, it will be the default.
# saves settings
$ sudo alsactl store
# confirm file's created
$ ls -l /etc/asound.state
-rw-r--r-- 1 root root 4761 Oct 5 16:54 /etc/asound.state
Other things with amixer
You can use the command amixer
to change the volume as well.
100%
$ amixer sset Master 100% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
150%
$ amixer sset Master 150% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
NOTE: This method doesn't allow you to go higher than 100%, however.
mute
$ amixer sset Master muted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [off]
Front Right: Playback 65536 [100%] [off]
unmute
$ amixer sset Master unmuted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
|
show 3 more comments
I've done this in the past and have had pretty good success with boosting the volume up. The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%.
However with the steps below should remain "sticky" from reboot to reboot.
Turning up the volume
If you right click on the speaker applet and select sound preferences you'll bring up this dialog.
confirming and saving changes
Turn the volume all the way up to 150%. Once it's been turned up you can close this dialog. If you go to a shell and type the command amixer
you can confirm this:
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 98304 [150%] [on]
Front Right: Playback 98304 [150%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [off]
Front Right: Capture 65536 [100%] [off]
If you then run this command you can save this state out so that the next time you restart your system, it will be the default.
# saves settings
$ sudo alsactl store
# confirm file's created
$ ls -l /etc/asound.state
-rw-r--r-- 1 root root 4761 Oct 5 16:54 /etc/asound.state
Other things with amixer
You can use the command amixer
to change the volume as well.
100%
$ amixer sset Master 100% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
150%
$ amixer sset Master 150% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
NOTE: This method doesn't allow you to go higher than 100%, however.
mute
$ amixer sset Master muted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [off]
Front Right: Playback 65536 [100%] [off]
unmute
$ amixer sset Master unmuted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
|
show 3 more comments
I've done this in the past and have had pretty good success with boosting the volume up. The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%.
However with the steps below should remain "sticky" from reboot to reboot.
Turning up the volume
If you right click on the speaker applet and select sound preferences you'll bring up this dialog.
confirming and saving changes
Turn the volume all the way up to 150%. Once it's been turned up you can close this dialog. If you go to a shell and type the command amixer
you can confirm this:
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 98304 [150%] [on]
Front Right: Playback 98304 [150%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [off]
Front Right: Capture 65536 [100%] [off]
If you then run this command you can save this state out so that the next time you restart your system, it will be the default.
# saves settings
$ sudo alsactl store
# confirm file's created
$ ls -l /etc/asound.state
-rw-r--r-- 1 root root 4761 Oct 5 16:54 /etc/asound.state
Other things with amixer
You can use the command amixer
to change the volume as well.
100%
$ amixer sset Master 100% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
150%
$ amixer sset Master 150% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
NOTE: This method doesn't allow you to go higher than 100%, however.
mute
$ amixer sset Master muted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [off]
Front Right: Playback 65536 [100%] [off]
unmute
$ amixer sset Master unmuted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
I've done this in the past and have had pretty good success with boosting the volume up. The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%.
However with the steps below should remain "sticky" from reboot to reboot.
Turning up the volume
If you right click on the speaker applet and select sound preferences you'll bring up this dialog.
confirming and saving changes
Turn the volume all the way up to 150%. Once it's been turned up you can close this dialog. If you go to a shell and type the command amixer
you can confirm this:
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 98304 [150%] [on]
Front Right: Playback 98304 [150%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [off]
Front Right: Capture 65536 [100%] [off]
If you then run this command you can save this state out so that the next time you restart your system, it will be the default.
# saves settings
$ sudo alsactl store
# confirm file's created
$ ls -l /etc/asound.state
-rw-r--r-- 1 root root 4761 Oct 5 16:54 /etc/asound.state
Other things with amixer
You can use the command amixer
to change the volume as well.
100%
$ amixer sset Master 100% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
150%
$ amixer sset Master 150% | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
NOTE: This method doesn't allow you to go higher than 100%, however.
mute
$ amixer sset Master muted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [off]
Front Right: Playback 65536 [100%] [off]
unmute
$ amixer sset Master unmuted | grep Front
Playback channels: Front Left - Front Right
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
edited Oct 5 '13 at 21:30
answered Oct 5 '13 at 20:58
slm♦slm
256k71544690
256k71544690
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
|
show 3 more comments
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
"The only problem with it is if you turn it down, then you'll have to come back into the system preferences under the speaker icon to turn it back up to 150%." This is what I'd really like to avoid. What I want is for the speaker icon volume slider to be changed, either to have a higher maximum or to be permanently boosted.
– mattdm
Oct 5 '13 at 21:24
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - I kind of figured that's what you were after but I figured I take a shot and provide this method that I've used. I'll keep digging, see if I can turn something else up.
– slm♦
Oct 5 '13 at 21:27
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
@mattdm - this has frustrated me at times too. Seems like there should be something better, if you find anything out, even with the plugins route, please share back here. I'd be curious to know it too!
– slm♦
Oct 10 '13 at 0:59
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
Did someone explain why it happens in the first place and why we can't just fix the issue instead of working around it?
– Pavel Šimerda
Jan 19 '15 at 16:55
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
@PavelŠimerda - you can see what was discussed about this through out this Q/A. No one ever mentions it and I've continued to use this workaround on Fedora 19 on the same hardware. I should mention that I've used this workaround maybe 2+ times since moving to F19 Dec/2014 so it's not like it's killing me. Just my $0.02.
– slm♦
Jan 19 '15 at 17:40
|
show 3 more comments
From what I know you can use the softvol plugin for ALSA and set the max_dB
value. Something in direction of:
pcm.!default
type plug
slave.pcm "softvol"
pcm.softvol
type softvol
slave
pcm "hw:0,0"
# pcm "dmix" or this or the like.
control
name "PreAmp"
card 0
min_dB -5.0
max_dB 30.0 # 50.0 is max
resolution 16
Perhaps some hints here as well. Then reload alsa, play e.g. speaker-test -c2 -twav
to get it loaded and then adjust amp in alsamixer.
If one want to shut down PulseAudio, remember to deactivate autospawn
.
echo autospawn=no >> ~/.pulse/client.conf
or uncomment it in the global client.conf
(in /etc/pulse/
or the like). (Have also seen some replace daemon-binary
with /bin/true
.)
However using pactl etc. would perhaps be more preferable.
From commandline say:
pactl set-sink-volume 0 65536 # 100%
pactl set-sink-volume 0 98304 # 150%
pactl set-sink-volume 0 131072 # 200%
| |
| +----- Based on volume steps
+------- Sink number
To list and identify sinks say:
pactl list sinks
pacmd list-sinks # a bit more verbose, and list "volume steps"
As always man
and pacmd -h
, pactl -h
.
To set default volume to e.g. 150% edit ./pulse/default.pa
and add the line:
set-sink-volume 0 98304
|
+-- (Use full name if one e.g. have multiple USB-soundcards.)
For convenience add an alias or a short script to set this value when ever you want.
To restart PA say pulseaudio -k
, and pulseaudio --start
.
Another option would be to look into plugins e.g. LADSPA and shw in ALSA or PulseAudio.
EDIT:
OK. Came to think about it. This might be suitable. (Don't know how it escaped me first time around.)
- In
default.pa
add a Pulse Audio module from Device Drivers. - Restart Pulse Audio.
- Open Sound settings and set volume for original sink to e.g. 150%. (Or do this by commandline or pre-set it in
default.pa
as described above.) - Select the new module/sink as device for sound output.
This will give you 150% as 100% when using the normal volume meter.
Example – using module-remap-sink
:
Do not uncomment as the doc say.
In default.pa
:
.ifexists module-remap-sink.so
# Using remap-sink as dummy, not doing any re-mapping.
load-module module-remap-sink sink_name=VolDummy master=0 sink_properties=device.description=CrankThaVolume
.fail
.endif
# Set it as default:
set-default-sink VolDummy
Then restart Pulse Audio to get the new module registered.
Issuing:
$ pactl list modules # Should show "Usage counter: 1" for the module in question.
$ pactl list sinks
should show a new sink. You can still crank the volume for master by using command-line and/or adding lines to default.pa
.
Yeah, it looks like theset-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.
– mattdm
Oct 8 '13 at 23:03
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
add a comment |
From what I know you can use the softvol plugin for ALSA and set the max_dB
value. Something in direction of:
pcm.!default
type plug
slave.pcm "softvol"
pcm.softvol
type softvol
slave
pcm "hw:0,0"
# pcm "dmix" or this or the like.
control
name "PreAmp"
card 0
min_dB -5.0
max_dB 30.0 # 50.0 is max
resolution 16
Perhaps some hints here as well. Then reload alsa, play e.g. speaker-test -c2 -twav
to get it loaded and then adjust amp in alsamixer.
If one want to shut down PulseAudio, remember to deactivate autospawn
.
echo autospawn=no >> ~/.pulse/client.conf
or uncomment it in the global client.conf
(in /etc/pulse/
or the like). (Have also seen some replace daemon-binary
with /bin/true
.)
However using pactl etc. would perhaps be more preferable.
From commandline say:
pactl set-sink-volume 0 65536 # 100%
pactl set-sink-volume 0 98304 # 150%
pactl set-sink-volume 0 131072 # 200%
| |
| +----- Based on volume steps
+------- Sink number
To list and identify sinks say:
pactl list sinks
pacmd list-sinks # a bit more verbose, and list "volume steps"
As always man
and pacmd -h
, pactl -h
.
To set default volume to e.g. 150% edit ./pulse/default.pa
and add the line:
set-sink-volume 0 98304
|
+-- (Use full name if one e.g. have multiple USB-soundcards.)
For convenience add an alias or a short script to set this value when ever you want.
To restart PA say pulseaudio -k
, and pulseaudio --start
.
Another option would be to look into plugins e.g. LADSPA and shw in ALSA or PulseAudio.
EDIT:
OK. Came to think about it. This might be suitable. (Don't know how it escaped me first time around.)
- In
default.pa
add a Pulse Audio module from Device Drivers. - Restart Pulse Audio.
- Open Sound settings and set volume for original sink to e.g. 150%. (Or do this by commandline or pre-set it in
default.pa
as described above.) - Select the new module/sink as device for sound output.
This will give you 150% as 100% when using the normal volume meter.
Example – using module-remap-sink
:
Do not uncomment as the doc say.
In default.pa
:
.ifexists module-remap-sink.so
# Using remap-sink as dummy, not doing any re-mapping.
load-module module-remap-sink sink_name=VolDummy master=0 sink_properties=device.description=CrankThaVolume
.fail
.endif
# Set it as default:
set-default-sink VolDummy
Then restart Pulse Audio to get the new module registered.
Issuing:
$ pactl list modules # Should show "Usage counter: 1" for the module in question.
$ pactl list sinks
should show a new sink. You can still crank the volume for master by using command-line and/or adding lines to default.pa
.
Yeah, it looks like theset-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.
– mattdm
Oct 8 '13 at 23:03
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
add a comment |
From what I know you can use the softvol plugin for ALSA and set the max_dB
value. Something in direction of:
pcm.!default
type plug
slave.pcm "softvol"
pcm.softvol
type softvol
slave
pcm "hw:0,0"
# pcm "dmix" or this or the like.
control
name "PreAmp"
card 0
min_dB -5.0
max_dB 30.0 # 50.0 is max
resolution 16
Perhaps some hints here as well. Then reload alsa, play e.g. speaker-test -c2 -twav
to get it loaded and then adjust amp in alsamixer.
If one want to shut down PulseAudio, remember to deactivate autospawn
.
echo autospawn=no >> ~/.pulse/client.conf
or uncomment it in the global client.conf
(in /etc/pulse/
or the like). (Have also seen some replace daemon-binary
with /bin/true
.)
However using pactl etc. would perhaps be more preferable.
From commandline say:
pactl set-sink-volume 0 65536 # 100%
pactl set-sink-volume 0 98304 # 150%
pactl set-sink-volume 0 131072 # 200%
| |
| +----- Based on volume steps
+------- Sink number
To list and identify sinks say:
pactl list sinks
pacmd list-sinks # a bit more verbose, and list "volume steps"
As always man
and pacmd -h
, pactl -h
.
To set default volume to e.g. 150% edit ./pulse/default.pa
and add the line:
set-sink-volume 0 98304
|
+-- (Use full name if one e.g. have multiple USB-soundcards.)
For convenience add an alias or a short script to set this value when ever you want.
To restart PA say pulseaudio -k
, and pulseaudio --start
.
Another option would be to look into plugins e.g. LADSPA and shw in ALSA or PulseAudio.
EDIT:
OK. Came to think about it. This might be suitable. (Don't know how it escaped me first time around.)
- In
default.pa
add a Pulse Audio module from Device Drivers. - Restart Pulse Audio.
- Open Sound settings and set volume for original sink to e.g. 150%. (Or do this by commandline or pre-set it in
default.pa
as described above.) - Select the new module/sink as device for sound output.
This will give you 150% as 100% when using the normal volume meter.
Example – using module-remap-sink
:
Do not uncomment as the doc say.
In default.pa
:
.ifexists module-remap-sink.so
# Using remap-sink as dummy, not doing any re-mapping.
load-module module-remap-sink sink_name=VolDummy master=0 sink_properties=device.description=CrankThaVolume
.fail
.endif
# Set it as default:
set-default-sink VolDummy
Then restart Pulse Audio to get the new module registered.
Issuing:
$ pactl list modules # Should show "Usage counter: 1" for the module in question.
$ pactl list sinks
should show a new sink. You can still crank the volume for master by using command-line and/or adding lines to default.pa
.
From what I know you can use the softvol plugin for ALSA and set the max_dB
value. Something in direction of:
pcm.!default
type plug
slave.pcm "softvol"
pcm.softvol
type softvol
slave
pcm "hw:0,0"
# pcm "dmix" or this or the like.
control
name "PreAmp"
card 0
min_dB -5.0
max_dB 30.0 # 50.0 is max
resolution 16
Perhaps some hints here as well. Then reload alsa, play e.g. speaker-test -c2 -twav
to get it loaded and then adjust amp in alsamixer.
If one want to shut down PulseAudio, remember to deactivate autospawn
.
echo autospawn=no >> ~/.pulse/client.conf
or uncomment it in the global client.conf
(in /etc/pulse/
or the like). (Have also seen some replace daemon-binary
with /bin/true
.)
However using pactl etc. would perhaps be more preferable.
From commandline say:
pactl set-sink-volume 0 65536 # 100%
pactl set-sink-volume 0 98304 # 150%
pactl set-sink-volume 0 131072 # 200%
| |
| +----- Based on volume steps
+------- Sink number
To list and identify sinks say:
pactl list sinks
pacmd list-sinks # a bit more verbose, and list "volume steps"
As always man
and pacmd -h
, pactl -h
.
To set default volume to e.g. 150% edit ./pulse/default.pa
and add the line:
set-sink-volume 0 98304
|
+-- (Use full name if one e.g. have multiple USB-soundcards.)
For convenience add an alias or a short script to set this value when ever you want.
To restart PA say pulseaudio -k
, and pulseaudio --start
.
Another option would be to look into plugins e.g. LADSPA and shw in ALSA or PulseAudio.
EDIT:
OK. Came to think about it. This might be suitable. (Don't know how it escaped me first time around.)
- In
default.pa
add a Pulse Audio module from Device Drivers. - Restart Pulse Audio.
- Open Sound settings and set volume for original sink to e.g. 150%. (Or do this by commandline or pre-set it in
default.pa
as described above.) - Select the new module/sink as device for sound output.
This will give you 150% as 100% when using the normal volume meter.
Example – using module-remap-sink
:
Do not uncomment as the doc say.
In default.pa
:
.ifexists module-remap-sink.so
# Using remap-sink as dummy, not doing any re-mapping.
load-module module-remap-sink sink_name=VolDummy master=0 sink_properties=device.description=CrankThaVolume
.fail
.endif
# Set it as default:
set-default-sink VolDummy
Then restart Pulse Audio to get the new module registered.
Issuing:
$ pactl list modules # Should show "Usage counter: 1" for the module in question.
$ pactl list sinks
should show a new sink. You can still crank the volume for master by using command-line and/or adding lines to default.pa
.
edited Apr 13 '17 at 12:22
Community♦
1
1
answered Oct 8 '13 at 10:28
RuniumRunium
19k43060
19k43060
Yeah, it looks like theset-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.
– mattdm
Oct 8 '13 at 23:03
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
add a comment |
Yeah, it looks like theset-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.
– mattdm
Oct 8 '13 at 23:03
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
Yeah, it looks like the
set-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.– mattdm
Oct 8 '13 at 23:03
Yeah, it looks like the
set-sink-volume
approach is the best that can reasonably be done, and it doesn't address the real want. Oh well. I'll look into plugins and see what they might be able to do for me.– mattdm
Oct 8 '13 at 23:03
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
@mattdm: Yes. Added a new solution that might fit your needs better.
– Runium
Oct 9 '13 at 3:55
add a comment |
When running alsamixer from the command line, be sure to run with the --view all
switch to ensure you're looking at all available mixer controls.
alsamixer -V all
Also, press F6 in alsamixer and check the settings for each device listed.
add a comment |
When running alsamixer from the command line, be sure to run with the --view all
switch to ensure you're looking at all available mixer controls.
alsamixer -V all
Also, press F6 in alsamixer and check the settings for each device listed.
add a comment |
When running alsamixer from the command line, be sure to run with the --view all
switch to ensure you're looking at all available mixer controls.
alsamixer -V all
Also, press F6 in alsamixer and check the settings for each device listed.
When running alsamixer from the command line, be sure to run with the --view all
switch to ensure you're looking at all available mixer controls.
alsamixer -V all
Also, press F6 in alsamixer and check the settings for each device listed.
edited Apr 23 '13 at 3:47
answered Mar 23 '13 at 1:46
drsdrs
3,33862961
3,33862961
add a comment |
add a comment |
I had a similar problem one time in Fedora 18. Turned out Google's "pepperbox" API for Flash had some serious issues with sound, and I solved it by going into /home//.config/google-chrome and killing PepperFlash, then reinstalling flash plugins from Adobe.
add a comment |
I had a similar problem one time in Fedora 18. Turned out Google's "pepperbox" API for Flash had some serious issues with sound, and I solved it by going into /home//.config/google-chrome and killing PepperFlash, then reinstalling flash plugins from Adobe.
add a comment |
I had a similar problem one time in Fedora 18. Turned out Google's "pepperbox" API for Flash had some serious issues with sound, and I solved it by going into /home//.config/google-chrome and killing PepperFlash, then reinstalling flash plugins from Adobe.
I had a similar problem one time in Fedora 18. Turned out Google's "pepperbox" API for Flash had some serious issues with sound, and I solved it by going into /home//.config/google-chrome and killing PepperFlash, then reinstalling flash plugins from Adobe.
edited 10 hours ago
Rui F Ribeiro
42.1k1484142
42.1k1484142
answered Feb 18 '13 at 15:59
Peace BlasterPeace Blaster
1881417
1881417
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f42561%2flow-sound-volume-on-lenovo-laptop-under-fedora%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
-alsa, fedora, pulseaudio
Or try a different kernel version? -- bugzilla.altlinux.org/show_bug.cgi?id=23705
– imz -- Ivan Zakharyaschev
Dec 14 '12 at 8:59
Did you ever tried alsamixer through command line? some time GUIs doesn't work properly! I had same problem on my dell laptop which solved by justify PCM column to 100%.
– hassan_noori
Jan 5 '13 at 9:01
Perhaps volume turned down with some physical wheel thingy? Happened to me once...
– vonbrand
Feb 4 '13 at 18:48
Do you use fedora 16 default (gnome)? Did you try
gnome-control-center sound
and maxing out the volume-bar at the bottom?– xx4h
Feb 12 '13 at 19:54
funny, i have an identical setup (520/F16) with no sound issues
– amphibient
Mar 23 '13 at 2:34