Kernel Bug Tracker – Bug 42720
Subwoofer in ASUS G73 does not work
Last modified: 2012-08-30 14:26:56 UTC
As per the bug report here:
and the bug report here:
the latest vanilla torvalds kernel 3.3-rc2 does not enable the subwoofer in the ASUS laptops. Apparently, the work done by ALSA developers has not been upstreamed for some reason. I am referring specifically to this code:
Of course this code no longer works with kernel 3.2 onwards. Thus, me filing this bug -- I can't use David's workaround anymore.
OK, upon further inspection, David's workaround has been partially upstreamed. The Bass Speaker has a separate volume control now. That causes an obvious problem -- changing the Master volume control does not affect at all the volume of the Bass Speaker.
I have upstreamed this bug to the ALSA bug tracker, where I'm sure it will die a slow death. :-D
Could you give alsa-info.sh output (run with --no-upload option) to this bugzilla?
I don't know which tree you are referring to as "upstream". Could you be specific?
Hey Takashi, sure!
Created attachment 72253 [details]
ALSA info for this machine
Upstream refers to the alsa project itself, as I understand the kernel periodically merges their work into the mainline.
Thanks, I fixed it in the upstream sound git tree.
Found in commit b544d1e0e233f83a2e6d20ee96b54ea272d5d5ba,
ALSA: hda/realtek - Add missing Bass and CLFE as vmaster slaves
It's slipped from today's pull request to Linus, but I'm going to send a request in the next week for 3.3-rc3.
Created attachment 72254 [details]
Takashi, your patch works fine, but there is another problem. Only the LEFT channel of the stereo signal drives the subwoofer -- the right channel does not.
Is this fixable? I'll do anything to fix that. I'll even boot windows and see if it works in there. GASP :-)
Sorry. The patch does not work as I previously stated. The Bass Speaker slider does not move when I move the Master, nor when I govern the volume of the device using pavucontrol.
I will try -rc3 today, hopefully I will report back today if your patch works
ok. This bug is fixed in RC3.