Ubuntu
alsa-driver package

Asus G75v internal Subwoofer not working; alsa not aware of it

Bug #1045981 reported by Andrew Wheelwright on 2012-09-04

This bug affects 9 people

Affects		Status	Importance	Assigned to	Milestone
	alsa-driver (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

The internal subwoofer on my Asus G75v laptop does not work in (k)ubuntu (e.g. no sound).

The audio setup (KMix>Settings>Audio Setup>Audio Hardware Setup) does not list a profile for 2.1 audio.

I see the following profiles in the drop-down list:
Analog Stereo Duplex
Analog Stereo Output
Digital Stereo (IEC953) Output + Analog Stereo Input
Digital Stereo (IEC958) Output
Analog Stereo Input
Off

I've searched for a solution to this and have not found anything that works. Any help would be appreciated.

System Info:
Description: Ubuntu 12.04.1 LTS
Release: 12.04
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu1
  Candidate: 1.0.25+dfsg-0ubuntu1
  Version table:
*** 1.0.25+dfsg-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.25+dfsg-0ubuntu1~precise1 0
        500 http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu/ precise/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: sleepy 28658 F.... pulseaudio
/dev/snd/controlC0: sleepy 28658 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7310000 irq 48'
   Mixer name : 'VIA VT1802'
   Components : 'HDA:11068446,10431487,00100000'
   Controls : 32
   Simple ctrls : 19
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xf7080000 irq 17'
   Mixer name : 'Nvidia GPU 16 HDMI/DP'
   Components : 'HDA:10de0016,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
Date: Tue Sep 4 11:47:16 2012
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Tags:

Revision history for this message

Andrew Wheelwright (wheelwright-tech) wrote on 2012-09-04:

AlsaDevices.txt Edit (980 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (793 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (62.6 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (11.7 KiB, text/plain; charset="utf-8")
Card1.Amixer.values.txt Edit (499 bytes, text/plain; charset="utf-8")
Card1.Codecs.codec.0.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.1.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.2.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.3.txt Edit (1.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (128.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.4 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (20.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-09-26:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status:	New → Confirmed

Revision history for this message

Roberto Leinardi (leinardi) wrote on 2012-10-04:

The same thing happens here on Ubuntu 12.10 beta 2

Revision history for this message

Roberto Leinardi (leinardi) wrote on 2012-10-07:

I tried with "options snd-hda-intel model=auto" in /etc/modprobe.d/alsa-base.conf and "default-sample-channels = 6" in /etc/pulse/daemon.conf but nothing has changed.

Alsamixer can only see two channels.

Revision history for this message

Raymond (superquad-vortex2) wrote on 2012-11-01:

http://mailman.alsa-project.org/pipermail/alsa-devel/2012-October/056624.html

Revision history for this message

Raymond (superquad-vortex2) wrote on 2012-11-02: Re: [alsa-devel] Fix for Asus G75 notebook subwoofer

Download full text (4.1 KiB)

>
>>
>> can you post the output of alsa-info.sh ?
>
>
> Where can I find the script ? I've not it on my machine
>

http://git.alsa-project.org/?p=alsa-driver.git;a=history;hb=refs/heads/build;f=alsa/utils/alsa-info.sh

>>
>> 9.337454] ALSA hda_codec.c:4877 autoconfig: line_outs=1
>> (0x24/0x0/0x0/0x0/0x0) type:speaker
>> [ 9.337458] ALSA hda_codec.c:4881 speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
>> [ 9.337460] ALSA hda_codec.c:4885 hp_outs=1 (0x25/0x0/0x0/0x0/0x0)
>> [ 9.337462] ALSA hda_codec.c:4886 mono: mono_out=0x0
>> [ 9.337464] ALSA hda_codec.c:4889 dig-out=0x2d/0x0
>> [ 9.337465] ALSA hda_codec.c:4890 inputs:
>> [ 9.337467] ALSA hda_codec.c:4894 Internal Mic=0x29
>> [ 9.337469] ALSA hda_codec.c:4894 Mic=0x2b
>>
>> it is the auto parser put the speaker to autocfg->lineout

http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=90da78bf6aaabd4d31c6663b7c1d1b9c5a8c023f

mono pin complex are usually [Fixed] Speaker instead of [Jack] Line Out

>
>
> Yep, if you look at above, this one was exactly the output before my 2
patches; the only difference
> was line 24, marked as type=SPEAKER; no trace of mono pin 0x33.
> I guess the 0x33 is skipped because the parser don't find a path from it,
as it have a connection to
> widget 0x3e with is out of range (widgets are reported to be from 0x08 to
0x0c).

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1045981

Node 0x33 [Pin Complex] wcaps 0x40050c: Mono Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00]
  Pincap 0x00000010: OUT
  Pin Default 0x501701f0: [N/A] Speaker at Int N/A
    Conn = Analog, Color = Unknown
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x00:
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x3e

it is ignored by the auto parser because [N/A] instead of [Fixed]

> We could also patch the returned widget number to be 2 widgets more, even
id 0x3d is NOT there.
>
> The 0x3e is a stereo to mono mixer, connecting to 0x1c.
> As above, VT1802p reports to have widgets up to 0x3c.
>

do widge 0x3e has amp-out for subwoofer volume control ?

>>
>> should the auto parser put it into autocfg->mono_out?
>>
>
> maybe.... I didn't try that one.
> With both patches the stuffs appears like a 4 channel one; the correct
would be 2+1, but
> I didn't manage to get it right.

Node 0x2b [Pin Complex] wcaps 0x400481: Stereo
  Control: name="Mic Boost Volume", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name="Mic Jack", index=0, device=0
  Pincap 0x00002324: IN Detect
    Vref caps: HIZ 50 100
  Pin Default 0x01a1903e: [Jack] Mic at Ext Rear
    Conn = 1/8, Color = Pink
    DefAssociation = 0x3, Sequence = 0xe

as the mic jack cannot be retasked as output , No need to put hp in lineout

>
>>
>> can you post the output of alsa-info.sh ?
>
>
> Where can I find the script ? I've not it on my machine
>

http://git.alsa-project.org/?p=alsa-driver.git;a=history;hb=refs/heads/build;f=alsa/utils/alsa-info.sh

>>
>>     9.337454] ALSA hda_codec.c:4877 autoconfig: line_outs=1
>> (0x24/0x0/0x0/0x0/0x0) type:speaker
>> [    9.337458] ALSA hda_codec.c:4881    speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
>> [    9.337460] ALSA hda_codec.c:4885    hp_outs=1 (0x25/0x0/0x0/0x0/0x0)
>> [    9.337462] ALSA hda_codec.c:4886    mono: mono_out=0x0
>> [    9.337464] ALSA hda_codec.c:4889    dig-out=0x2d/0x0
>> [    9.337465] ALSA hda_codec.c:4890    inputs:
>> [    9.337467] ALSA hda_codec.c:4894  Internal Mic=0x29
>> [    9.337469] ALSA hda_codec.c:4894  Mic=0x2b
>>
>> it is the auto parser put the speaker to autocfg->lineout

http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=90da78bf6aaabd4d31c6663b7c1d1b9c5a8c023f

mono pin complex are usually [Fixed] Speaker instead of [Jack] Line Out

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1045981

Node 0x33 [Pin Complex] wcaps 0x40050c: Mono Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00]
  Pincap 0x00000010: OUT
  Pin Default 0x501701f0: [N/A] Speaker at Int N/A
    Conn = Analog, Color = Unknown
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x00:
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x3e

it is ignored by the auto parser because [N/A] instead of [Fixed]

do widge 0x3e has amp-out for subwoofer volume control ?

as the mic jack cannot be retasked as output , No need to put hp in lineout

>
> Resuming, without patches, the auto_parser report for asus :
>
> 0x24 Line out, type speaker
> 0x25 Hp out
> 0x33 is missing
>
> Forcing the connection from 0x33 to 0x1c (skipping so 0x3e) the pin 0x33
don't appear
> because bios marks it at none-connection.
> Forcing the connection to JACK, it puts as a mono speaker, so no sound
from it either.
> Forcing to be a line out, sound only from it because then 0x24 takes the
speaker place (marked as speaker in bios).
> Forcing both 0x24 and 0x33 to be line out gives 4 channel sound (with 2
rear channels output to 0x33 mono).
>
> No idea on how to get the 2+1 behaviour, but at least now it sounds.

multiout.extra_out seem support multi stereo streams in
snd_hda_multi_out_analog_prepare()

for (i = 0; i < ARRAY_SIZE(mout->extra_out_nid); i++)
                 if (!mout->no_share_stream && mout->extra_out_nid[i])
                         snd_hda_codec_setup_stream(codec,
                                                    mout->extra_out_nid[i],
                                                    stream_tag, 0, format);

how to put those internal speakers into multiout->extra_out in
via_auto_create_speaker_ctls() when the auto parser put the speaker into
autocfg->lineout ?

only two volume controls at 0x08 and 0x09,
there are three pin complexes 0x24, 0x25 and 0x33

Revision history for this message

Massimo (maxx5) wrote on 2012-11-02:

alsa_info output Edit (47.7 KiB, text/plain)

He, here the alsa-info output.

From what you can see, the codec reports controls up to 0x3c; there's almost another control at 0x3e which I dumped :

[ 467.214734] Widget #3e -- ANALOG MONO AUDIO MIXER
[ 467.214735] Input from widgets : 0x1c
[ 467.214738] Does NOT support unsolicited response
[ 467.214739] Out amp NOT present
[ 467.214741] In amp NOT present

The extra widget 3e is a stereo-to-mono mixer, input from mixer 1c and output on 0x33.

Widget 0x33 is NOT detected by alsa code because it's marked as no-connection output and because it takes its input from out of range widget 0x3e.
With the 2 patches dropped in alsa-devel, the output paths become following :

[ 1378.923620] ALSA patch_via.c:1861 output-path: depth=4, 08/34/14/24/00
[ 1378.923625] ALSA patch_via.c:1861 output-path: depth=4, 08/21/14/24/00
[ 1378.923820] ALSA patch_via.c:1861 output-path: depth=4, 09/3c/1c/33/00
[ 1378.924287] ALSA patch_via.c:1861 output-path: depth=4, 08/35/15/25/00
[ 1378.924291] ALSA patch_via.c:1861 output-path: depth=4, 08/21/15/25/00

So, the 0x8 DAC is shared between HP and front output, and DAC 0x09 is used for surround.
It works, even it shows as 4 channel audio instead 2+1 one... I don't know if it's possible to make it
showing as 2+1.

Besides the bugfix patch (the first one posted in alsa-devel) the patch are :

skip 0x3e control connecting 0x33 directly to 0x1c
force 0x33 to line output
force 0x24 to line output, otherwise auto_parser take it as a speaker and discards it

Ciao

Max

Revision history for this message

Raymond (superquad-vortex2) wrote on 2012-11-03:

http://voices.canonical.com/david.henningsson/2011/11/29/turn-your-mic-jack-into-a-headphone-jack/

can the hda-jack-retask be used to channge the pin default of 0x33 ?

you can not retask the mic as headphone since mic jack does not support output

Revision history for this message

Raymond (superquad-vortex2) wrote on 2012-11-05:

> So, the 0x8 DAC is shared between HP and front output, and DAC 0x09 is used for surround.

can you post the alsa-info.sh of the patched driver ?

do you have problem similar to

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/978880

Revision history for this message

Massimo (maxx5) wrote on 2012-11-06:

#10

alsa-info output for patched driver Edit (240.7 KiB, text/plain)

Hi, as from mailing list request, I'll add here the alsa-info output for patched driver.

Ciao

Max

Revision history for this message

Raymond (superquad-vortex2) wrote on 2012-11-07:

#11

if you look carefully, you should notice that 0x26 is not any detectable pin complex in vt1802

Node 0x26 [Vendor Defined Widget] wcaps 0xf00000: Mono

/* Mono Out */present = snd_hda_jack_detect(codec, 0x26);

parm = present ? AC_PWRST_D3 : AC_PWRST_D0; if (spec->codec_type == VT1802) { /* PW15 (33h), MW8(1ch), MUX8(3ch) */update_power_state(codec, 0x33, parm); update_power_state(codec, 0x1c, parm); update_power_state(codec, 0x3c, parm);

http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commitdiff;h=11890956e948e6ed1b3e4acc11b6879db6ace01b;hp=bc92df7fe55e49c616a003b0b77e7badf2736429

I don't understand how this patch can fix the problem since mic jack is not retaskable and all pin complexes are hardcoded in set widget power state

http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commitdiff;h=94c142a160d63edac0e1fca7848960dcf75dd2a9;hp=012e7eb1e501d0120e0383b81477f63091f5e365

Revision history for this message

Marcus Tomlinson (marcustomlinson) wrote on 2020-03-05:

#12

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-05-05:

#13

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]

Changed in alsa-driver (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntualsa-driver package

Asus G75v internal Subwoofer not working; alsa not aware of it

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
alsa-driver package