Overview: Volume control keys can be seen to change only the Master volume in alsamixer. PCM is at 100 on reboot/switching the output from headphones to speakers. Actual Results: The volume control when using the the Fn + volume keys controls the Master volume in alsamixer, but sound from speakers is either 100% or muted. On headphone output the volume is controlled correctly. On linux-image-5.8.0-48-generic there was speaker sound for only a brief moment right after startup. After that all sound stopped working, even though the visual volume meter in the sound settings showed activity on playback. Upgraded the kernel to linux-image-unsigned-5.11.12-051112-generic on which the sound works seems to work otherwise consistently, except for the volume control, which doesn't work as detailed above. I have also tried a few different model options in /etc/modprobe.d/alsa-base.conf as e.g. "option snd-hda-intel model=asus-zenbook", but these have had no effect on this issue with the volume control. Checking hdajackretask under Realtek ALC295 sound card the pins and their assignments look correct (at least based on the naming). As a further detail (possibly relevant detail as discussed in some other issues linked below), this laptop model has four speakers (two facing up on both sides of the keyboard, two facing down on the bottom part of the chassis) for regular stereo playback. I guess the two facing down should be for "bass" types of sounds. Could be related to these issues: 1: https://bugzilla.kernel.org/show_bug.cgi?id=212547 2: https://bugzilla.kernel.org/show_bug.cgi?id=203909 3: https://bugzilla.kernel.org/show_bug.cgi?id=198495 4: https://bugzilla.kernel.org/show_bug.cgi?id=209053 Expected Results: The volume control keys (Fn + volume up/down) and thus master volume would affect all sound playback. Additional Information: alsa-info: http://alsa-project.org/db/?f=922c36344e9e9aba5f48e1f7a1b269333321e591
New alsa-info (upgraded to Ubuntu 21.04 since posting the previous comment): http://alsa-project.org/db/?f=ab74f390ebc73ee2355ab1a8ea3ac76ccd041a32 The kernel version referred in the info is built from mainline 5.11.12 with a patch applied from here: https://bugzilla.kernel.org/show_bug.cgi?id=212547 The patch didn't resolve the volume control issue on this hardware.
For other models, let's track in other bug entries. Let's close.
Sorry, a wrong entry. Your machine has a simply different PCI SSID, so the patch doesn't change anything. A test patch for UX550VE is below. Please give it a try.
Created attachment 299461 [details] Test fix patch
Wow, thank you so much for taking the time and coming around to this. Truly appreciated!:) I've just tested applying the patch to the (almost) latest stable mainline kernel (5.14.16; at the time of writing this, looks like there are new releases on kernel.org) and it works! I'm very, very happy! Thank you so much. I'll go ahead and mark this resolved now. :) When do you think it would be merged upstream? Asking to get an idea about when it's "safe" to upgrade without applying the patch again.
Good to hear. The fix was submitted to upstream and merged now. https://lore.kernel.org/r/20211107083339.18013-1-tiwai@suse.de
Great! Thanks again!:)
I am experiencing a similar issue on ASUS M16 GU603HE with the ALC285 (SSID 0x1043:0x16b2) and this fix works for me too. Should I open another issue or just submit the patch? (Just adding this line to patch_realtek.c solved it SND_PCI_QUIRK(0x1043, 0x16b2, "ASUS GU603HE", ALC289_FIXUP_ASUS_GA401), )