Multiple problems with alsamixer after opening up laptop (no problems in other OSs)
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
This randomly started happening today. Yesterday I opened up my laptop to clean it out. I also disconnected the CMOS battery cable by mistake.
When I open alsamixer
in a terminal, the following things happen when I try to control the channels:
Controlling the 'PCM' channel is the only way for me to change the volume.
Using the up/down arrow keys when selecting the master channel, it changes the numbers but doesn't actually change the volume. Even weirder: controlling the master volume mutes it instead. It also mutes the headphone channel, but not the speaker channel.
Unmuting the master channel by pressing 'M' doesn't bring the audio back. To do that, I have to press Fn+F1, which is bound to
pactl set-sink-mute 0 toggle
in sxhkdrc (using bspwm).Using Fn+F2/F3 (bound to
pactl set-sink-volume 0 -/+ 5%
) to decrease/increase changes the master channel but doesn't change the audio, but also doesn't mute it.(un)Muting the headphone channel doesn't do anything to the audio. Increasing/decreasing the headphone channel doesn't change the volume.
Muting the master channel also mutes the headphone channel, but unmuting the master channel doesn't unmute the headhpone channel.
I can't get the speakers to work at all.
When I lower the master channel using the function keys all the way to 0, the headphone channel goes down as well. When the headphone channel gets to 0, it mutes only the right channel (wtf?).
Everything works in Windows (I did have a problem with audio drivers in Windows but a reboot fixed it) and in Ubuntu 18.10 on a USB live stick. I'm on a laptop (Lenovo Legion Y520) running Arch Linux. According to alsamixer I'm using the HDA Intel PCH
soundcard and Realtek ALC233
chip.
More problems (I think related) after I cleaned my laptop:
xev and xbindkeys don't recognize Fn+F1 / Fn+F2 / Fn+F3 anymore. I can still use them for controlling the master channel but It doesn't give me any keycodes.
Here's where it gets weird: Holding down the Fn key, tapping the F2 key first and then quickly the F3 key gives me an XF86AudioRaiseVolume key event in both xev and in xbindkeys. The other way around (F3 first and then F2) prints an XF86AudioLowerVolume event.
keyboard pulseaudio alsa bios alsamixer
add a comment |Â
up vote
0
down vote
favorite
This randomly started happening today. Yesterday I opened up my laptop to clean it out. I also disconnected the CMOS battery cable by mistake.
When I open alsamixer
in a terminal, the following things happen when I try to control the channels:
Controlling the 'PCM' channel is the only way for me to change the volume.
Using the up/down arrow keys when selecting the master channel, it changes the numbers but doesn't actually change the volume. Even weirder: controlling the master volume mutes it instead. It also mutes the headphone channel, but not the speaker channel.
Unmuting the master channel by pressing 'M' doesn't bring the audio back. To do that, I have to press Fn+F1, which is bound to
pactl set-sink-mute 0 toggle
in sxhkdrc (using bspwm).Using Fn+F2/F3 (bound to
pactl set-sink-volume 0 -/+ 5%
) to decrease/increase changes the master channel but doesn't change the audio, but also doesn't mute it.(un)Muting the headphone channel doesn't do anything to the audio. Increasing/decreasing the headphone channel doesn't change the volume.
Muting the master channel also mutes the headphone channel, but unmuting the master channel doesn't unmute the headhpone channel.
I can't get the speakers to work at all.
When I lower the master channel using the function keys all the way to 0, the headphone channel goes down as well. When the headphone channel gets to 0, it mutes only the right channel (wtf?).
Everything works in Windows (I did have a problem with audio drivers in Windows but a reboot fixed it) and in Ubuntu 18.10 on a USB live stick. I'm on a laptop (Lenovo Legion Y520) running Arch Linux. According to alsamixer I'm using the HDA Intel PCH
soundcard and Realtek ALC233
chip.
More problems (I think related) after I cleaned my laptop:
xev and xbindkeys don't recognize Fn+F1 / Fn+F2 / Fn+F3 anymore. I can still use them for controlling the master channel but It doesn't give me any keycodes.
Here's where it gets weird: Holding down the Fn key, tapping the F2 key first and then quickly the F3 key gives me an XF86AudioRaiseVolume key event in both xev and in xbindkeys. The other way around (F3 first and then F2) prints an XF86AudioLowerVolume event.
keyboard pulseaudio alsa bios alsamixer
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This randomly started happening today. Yesterday I opened up my laptop to clean it out. I also disconnected the CMOS battery cable by mistake.
When I open alsamixer
in a terminal, the following things happen when I try to control the channels:
Controlling the 'PCM' channel is the only way for me to change the volume.
Using the up/down arrow keys when selecting the master channel, it changes the numbers but doesn't actually change the volume. Even weirder: controlling the master volume mutes it instead. It also mutes the headphone channel, but not the speaker channel.
Unmuting the master channel by pressing 'M' doesn't bring the audio back. To do that, I have to press Fn+F1, which is bound to
pactl set-sink-mute 0 toggle
in sxhkdrc (using bspwm).Using Fn+F2/F3 (bound to
pactl set-sink-volume 0 -/+ 5%
) to decrease/increase changes the master channel but doesn't change the audio, but also doesn't mute it.(un)Muting the headphone channel doesn't do anything to the audio. Increasing/decreasing the headphone channel doesn't change the volume.
Muting the master channel also mutes the headphone channel, but unmuting the master channel doesn't unmute the headhpone channel.
I can't get the speakers to work at all.
When I lower the master channel using the function keys all the way to 0, the headphone channel goes down as well. When the headphone channel gets to 0, it mutes only the right channel (wtf?).
Everything works in Windows (I did have a problem with audio drivers in Windows but a reboot fixed it) and in Ubuntu 18.10 on a USB live stick. I'm on a laptop (Lenovo Legion Y520) running Arch Linux. According to alsamixer I'm using the HDA Intel PCH
soundcard and Realtek ALC233
chip.
More problems (I think related) after I cleaned my laptop:
xev and xbindkeys don't recognize Fn+F1 / Fn+F2 / Fn+F3 anymore. I can still use them for controlling the master channel but It doesn't give me any keycodes.
Here's where it gets weird: Holding down the Fn key, tapping the F2 key first and then quickly the F3 key gives me an XF86AudioRaiseVolume key event in both xev and in xbindkeys. The other way around (F3 first and then F2) prints an XF86AudioLowerVolume event.
keyboard pulseaudio alsa bios alsamixer
This randomly started happening today. Yesterday I opened up my laptop to clean it out. I also disconnected the CMOS battery cable by mistake.
When I open alsamixer
in a terminal, the following things happen when I try to control the channels:
Controlling the 'PCM' channel is the only way for me to change the volume.
Using the up/down arrow keys when selecting the master channel, it changes the numbers but doesn't actually change the volume. Even weirder: controlling the master volume mutes it instead. It also mutes the headphone channel, but not the speaker channel.
Unmuting the master channel by pressing 'M' doesn't bring the audio back. To do that, I have to press Fn+F1, which is bound to
pactl set-sink-mute 0 toggle
in sxhkdrc (using bspwm).Using Fn+F2/F3 (bound to
pactl set-sink-volume 0 -/+ 5%
) to decrease/increase changes the master channel but doesn't change the audio, but also doesn't mute it.(un)Muting the headphone channel doesn't do anything to the audio. Increasing/decreasing the headphone channel doesn't change the volume.
Muting the master channel also mutes the headphone channel, but unmuting the master channel doesn't unmute the headhpone channel.
I can't get the speakers to work at all.
When I lower the master channel using the function keys all the way to 0, the headphone channel goes down as well. When the headphone channel gets to 0, it mutes only the right channel (wtf?).
Everything works in Windows (I did have a problem with audio drivers in Windows but a reboot fixed it) and in Ubuntu 18.10 on a USB live stick. I'm on a laptop (Lenovo Legion Y520) running Arch Linux. According to alsamixer I'm using the HDA Intel PCH
soundcard and Realtek ALC233
chip.
More problems (I think related) after I cleaned my laptop:
xev and xbindkeys don't recognize Fn+F1 / Fn+F2 / Fn+F3 anymore. I can still use them for controlling the master channel but It doesn't give me any keycodes.
Here's where it gets weird: Holding down the Fn key, tapping the F2 key first and then quickly the F3 key gives me an XF86AudioRaiseVolume key event in both xev and in xbindkeys. The other way around (F3 first and then F2) prints an XF86AudioLowerVolume event.
keyboard pulseaudio alsa bios alsamixer
keyboard pulseaudio alsa bios alsamixer
asked 38 mins ago
zjeffer
336
336
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f479662%2fmultiple-problems-with-alsamixer-after-opening-up-laptop-no-problems-in-other-o%23new-answer', 'question_page');
);
Post as a guest
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
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
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