Linux Documentation
 help / color / mirror / Atom feed
From: Rong Zhang <i@rong.moe>
To: Faaris Ansari <faaris.ansari@gmail.com>, tiwai@suse.de
Cc: adventureFAN@gmx.de, corbet@lwn.net, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
	perex@perex.cz,  rdunlap@infradead.org,
	skhan@linuxfoundation.org, tiwai@suse.com
Subject: Re: [PATCH 0/4] ALSA: usb-audio: Demote the severity of sticky GET_CUR
Date: Sun, 27 Sep 2026 02:25:22 +0800	[thread overview]
Message-ID: <98dc534b684e3301bf30c9d7a3e97196f7eff4d5.camel@rong.moe> (raw)
In-Reply-To: <191af638-f19f-423c-8306-d96ea2b3dcad@gmail.com>

Hi Faaris,

On Fri, 2026-09-25 at 19:33 +0100, Faaris Ansari wrote:
> Hi there,
> 
> I am continuing to have a bug across the latest 7.2 kernels, as well as 
> 6.18 and 6.12 LTS branches concerning hardware volume control on my 
> Audient EVO4, that I think is related to this issue - would appreciate 
> some guidance if not.
> 
> Specifically, when changing volume via the knob on the front of the 
> device, everything works perfectly, but when modifying volume through 
> pwvucontrol or wpctl the volume drastically lowers. As far as I can 
> understand, pipewire is resorting to a software mixer for the device for 
> some reason, whilst also actively modifying the hardware volume at the 
> same time - is this what should occur with "sticky mixers"?
> 
> prior to kernels 7.2 (tested 7.1.13) the volume control works perfectly 
> via wpctl.
> 
> I attempted to add a quirk flag to snd_usb_audio to work around the 
> issue without success:
> 
> ```
> 
> sudo modprobe snd_usb_audio quirk_flags=2708:0006:mixer_get_cur_broken
> 
> ```

Nah. This is not the proper way to specify module parameters. It silently
succeeds when the module is already loaded, without actually modifying
the parameter. It only works when the module has not been loaded.

It's more preferred to write the option to /etc/modprobe.d/, unload the
module, and probe the driver again. After that, check
/sys/module/snd_usb_audio/parameters/quirk_flags to see if it's applied.

Note that while you can modify the parameter through sysfs, I don't
recommend you to do so, as it can't handle line feed properly.

> 
> 
> I also tried applying these patches to add extra mixer controls to my 
> EVO4: https://lore.kernel.org/lkml/20260919151840.24371-1-arc@gmx.li/
> 
> This worked fine after I modified the UCM conf for the device to follow 
> the new (correct) naming scheme for the master volume, but the volume 
> problem was still occuring.
> 
> 
> is this problem I'm having related to these sticky mixers?
> 
> 
> I originally reported this to wireplumber thinking it was an issue 
> there, more information is provided at the link below:
> 
> https://gitlab.freedesktop.org/pipewire/wireplumber/-/work_items/1022
> 
> 
> As I've never reported anything upstream to the kernel before, I'd 
> appreciate extra guidance where necessary. Would love to get this solved 
> as its making all volume control on my system unusable, and the change 
> which has caused it has also been pushed to LTS kernels, 
> 

No, v7.2 is a *stable* version instead of an *LTS* version.

> leaving me with 
> no working kernel besides reverting to the now EOL 7.1 series.

Please test v7.3-rc.

Thanks,
Rong

> 
> 
> Faaris

  reply	other threads:[~2026-09-26 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 18:52 [PATCH 0/4] ALSA: usb-audio: Demote the severity of sticky GET_CUR Rong Zhang
2026-08-22 18:52 ` [PATCH 1/4] ALSA: doc: usb-audio: Add doc for QUIRK_FLAG_ALWAYS_SET_RATE Rong Zhang
2026-08-22 18:52 ` [PATCH 2/4] ALSA: usb-audio: Demote the severity of sticky GET_CUR Rong Zhang
2026-08-22 18:52 ` [PATCH 3/4] ALSA: usb-audio: Reverse MIXER_GET_CUR_BROKEN as MIXER_GET_CUR_OK Rong Zhang
2026-08-22 18:52 ` [PATCH 4/4] ALSA: usb-audio: Add quirk flags for Logitech PRO X Wireless Rong Zhang
2026-08-23  9:04 ` [PATCH 0/4] ALSA: usb-audio: Demote the severity of sticky GET_CUR Takashi Iwai
2026-09-25 18:33   ` Faaris Ansari
2026-09-26 18:25     ` Rong Zhang [this message]
2026-09-28 15:44     ` Takashi Iwai
2026-09-28 16:46       ` Faaris Ansari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=98dc534b684e3301bf30c9d7a3e97196f7eff4d5.camel@rong.moe \
    --to=i@rong.moe \
    --cc=adventureFAN@gmx.de \
    --cc=corbet@lwn.net \
    --cc=faaris.ansari@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox