Summary: | [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound from Subwoofer in 2.1 mode | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | jason.braddock.69 |
Component: | alsa | Assignee: | pulseaudio-bugs |
Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | gnome, lennart |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | asus alc663 with sonic master subwoofer detectable jack using pin sense of node 0x1e |
Description
jason.braddock.69
2015-08-05 20:05:14 UTC
pulseaudio 6.0 is not enough as you need those lfe filter patches you should find the following message in your pukseaudio log pa_log_debug(" lfe filter activated (LR4 type), the crossover_freq = %uHz", crossover_freq); http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=c36e191ce5d38173424c3db9ba06638fd6b8408e can your sonic master subwoofer be detected by hdajacksensetest ? since pincap of node 0x1e does not support DETECT sudo hda-jack-sense-test -a : *** Without subwoofer: Pin 0x1e (Black SPDIF Out): present = No *** With subwoofer: Pin 0x1e (Black SPDIF Out): present = Yes (In reply to Raymond from comment #1) > > pulseaudio 6.0 is not enough as you need those lfe filter patches > > you should find the following message in your pukseaudio log > > pa_log_debug(" lfe filter activated (LR4 type), the crossover_freq = %uHz", > crossover_freq); > > http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/ > ?id=c36e191ce5d38173424c3db9ba06638fd6b8408e OK, I guess I should update to git version of pulse. Is there a guide for recompiling Pulse? Or maybe a ppa with daily builds for ubuntu? http://colin.guthr.ie/2010/09/compiling-and-running-pulseaudio-from-git/ you need to ask David whether he has ppa for pulseaudio with lfe filter AFAIK, Ubuntu 15.10 alpha pulseaudio has LFE filter BUT it is quite unstable and not suitable for any production computer (numerous bug cannot unlock screen saver ) Created attachment 117571 [details] [review] asus alc663 with sonic master subwoofer detectable jack using pin sense of node 0x1e using modified int __snd_hda_jack_add_kctl() to create "Ext Subwoofer Jack" kctl which use pin sense of 0x1e (In reply to Raymond from comment #2) > can your sonic master subwoofer be detected by hdajacksensetest ? > > since pincap of node 0x1e does not support DETECT > > > > sudo hda-jack-sense-test -a : > *** Without subwoofer: > Pin 0x1e (Black SPDIF Out): present = No > *** With subwoofer: > Pin 0x1e (Black SPDIF Out): present = Yes Hi, how can I install hda-jack-sense-test? I tried sudo add-apt-repository ppa:diwic/misc but the repository doesn't work anymore... Or maybe I did something wrong... http://git.alsa-project.org/?p=alsa-tools.git;a=tree you need hdajacksensetest which use parser code in hdajackretask you can also use hda-verb when subwoofer is plugged and unplugged hda-verb /dev/snd/hwC0D0 0x1e GET_PIN_SENSE 0 when user select 2.1 profile or other surround profile pulseaudio change to stereo when the headphone is plugged but remain at stereo after headphone is unplugged (In reply to Raymond from comment #8) > you can also use hda-verb when subwoofer is plugged and unplugged > > hda-verb /dev/snd/hwC0D0 0x1e GET_PIN_SENSE 0 WITHOUT subwoofer: sudo ./hda-verb /dev/snd/hwC0D0 0x1e GET_PIN_SENSE 0 nid = 0x1e, verb = 0xf09, param = 0x0 value = 0x0 WITH subwoofer: sudo ./hda-verb /dev/snd/hwC0D0 0x1e GET_PIN_SENSE 0 nid = 0x1e, verb = 0xf09, param = 0x0 value = 0x80000000 (In reply to Raymond from comment #7) > http://git.alsa-project.org/?p=alsa-tools.git;a=tree > > > you need hdajacksensetest which use parser code in hdajackretask WITHOUT subwoofer: sudo ./hdajacksensetest -a Pin 0x11 (Not connected): present = No Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker, ATAPI): present = No Pin 0x15 (Not connected): present = No Pin 0x16 (Internal Speaker, ATAPI): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Pink Mic, Rear side): present = No Pin 0x19 (Internal Mic, ATAPI): present = No Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Black SPDIF Out, Right side): present = No Pin 0x21 (Green Headphone, Rear side): present = No WITH subwoofer: sudo ./hdajacksensetest -a Pin 0x11 (Not connected): present = No Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker, ATAPI): present = No Pin 0x15 (Not connected): present = No Pin 0x16 (Internal Speaker, ATAPI): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Pink Mic, Rear side): present = No Pin 0x19 (Internal Mic, ATAPI): present = No Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Black SPDIF Out, Right side): present = Yes Pin 0x21 (Green Headphone, Rear side): present = No (In reply to jason.braddock.69 from comment #11) > (In reply to Raymond from comment #7) > > http://git.alsa-project.org/?p=alsa-tools.git;a=tree > > > > > > you need hdajacksensetest which use parser code in hdajackretask > > WITHOUT subwoofer: > sudo ./hdajacksensetest -a > Pin 0x11 (Not connected): present = No > Pin 0x12 (Not connected): present = No > Pin 0x13 (Not connected): present = No > Pin 0x14 (Internal Speaker, ATAPI): present = No > Pin 0x15 (Not connected): present = No > Pin 0x16 (Internal Speaker, ATAPI): present = No > Pin 0x17 (Not connected): present = No > Pin 0x18 (Pink Mic, Rear side): present = No > Pin 0x19 (Internal Mic, ATAPI): present = No > Pin 0x1a (Not connected): present = No > Pin 0x1b (Not connected): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Black SPDIF Out, Right side): present = No > Pin 0x21 (Green Headphone, Rear side): present = No > > > > WITH subwoofer: > sudo ./hdajacksensetest -a > Pin 0x11 (Not connected): present = No > Pin 0x12 (Not connected): present = No > Pin 0x13 (Not connected): present = No > Pin 0x14 (Internal Speaker, ATAPI): present = No > Pin 0x15 (Not connected): present = No > Pin 0x16 (Internal Speaker, ATAPI): present = No > Pin 0x17 (Not connected): present = No > Pin 0x18 (Pink Mic, Rear side): present = No > Pin 0x19 (Internal Mic, ATAPI): present = No > Pin 0x1a (Not connected): present = No > Pin 0x1b (Not connected): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Black SPDIF Out, Right side): present = Yes > Pin 0x21 (Green Headphone, Rear side): present = No Just to give more precision (not sure if it helps): - There is an SPDIF output on the right side of the board. It is combined with the standard analogic stereo 3.5jack (same physical port). I have no SPDIF capable hardware to test the output. - The subwoofer physical port is located on left side of the board and is a smaller jack (probably a 2.5 jack), with 4 connectors on it... this number is quite weird so maybe the sobwoofer does itself the mix+lowpass? I'll try to open it and see. In the end, the pin list is messing with SPDIF output and subwoofer while those two outputs are physically distinct... Hi ppl, well i'm here to post experiences with this, first i have an asus N46VB with the same audio system, i used this comp with ubuntu debian and now gentoo, i remember fight a lot with all this systems to this works because there are a lot of cases: Using the Stereo profile - some times the external subwoofer works and others not. if i use a 2.1 profile like in the ubuntu guides some times works, others basically i don't get any sound like this case, or i can't select the profile, bacause don't is available. well there is the fight to this works, acutally works on gentoo but with some version changes stop working... anyway is a mess with this xD i realize the tests posted here and i get the same results, including the same pin... i know in ubuntu you can use the subwoofer but you need start testing profiles and a trick is change the asus-mode in the modules's options, but it don't remove this bug bacause the problem exist anyway, i can confirm this type of issues in my system. Distr: Gentoo 64 PulseAudio: 7.1 Kernel: 4.1.7 (hardened) Desktop: Gnome 3.16 respect the patch in the attachments i can't test it here is the log of the patch: Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sound/pci/hda/hda_generic.c b/sound/pci/hda/hda_generic.c |index b077bb6..af206a2 100644 |--- a/sound/pci/hda/hda_generic.c |+++ b/sound/pci/hda/hda_generic.c -------------------------- File sound/pci/hda/hda_generic.c is read-only; trying to patch anyway checking file sound/pci/hda/hda_generic.c Using Plan A... Hunk #1 succeeded at 1163 (offset -3 lines). Hunk #2 succeeded at 2100 (offset -3 lines). Hunk #3 succeeded at 4444 (offset -3 lines). Hunk #4 succeeded at 4726 (offset -3 lines). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sound/pci/hda/hda_generic.h b/sound/pci/hda/hda_generic.h |index 56e4139..0803afa 100644 |--- a/sound/pci/hda/hda_generic.h |+++ b/sound/pci/hda/hda_generic.h -------------------------- File sound/pci/hda/hda_generic.h is read-only; trying to patch anyway checking file sound/pci/hda/hda_generic.h Using Plan A... Hunk #1 succeeded at 160. Hunk #2 succeeded at 238. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sound/pci/hda/hda_jack.c b/sound/pci/hda/hda_jack.c |index 366efbf..f9b61b6 100644 |--- a/sound/pci/hda/hda_jack.c |+++ b/sound/pci/hda/hda_jack.c -------------------------- File sound/pci/hda/hda_jack.c is read-only; trying to patch anyway checking file sound/pci/hda/hda_jack.c Using Plan A... Hunk #1 succeeded at 19. Hunk #2 succeeded at 158. Hunk #3 succeeded at 218. Hunk #4 FAILED at 395. Hunk #5 FAILED at 416. Hunk #6 FAILED at 433. Hunk #7 FAILED at 462. Hunk #8 succeeded at 511 (offset 40 lines). Hunk #9 succeeded at 528 (offset 40 lines). Hunk #10 succeeded at 544 (offset 40 lines). Hunk #11 succeeded at 559 (offset 40 lines). Hunk #12 succeeded at 580 (offset 40 lines). 4 out of 12 hunks FAILED Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sound/pci/hda/hda_jack.h b/sound/pci/hda/hda_jack.h |index 387d309..ef3d162 100644 |--- a/sound/pci/hda/hda_jack.h |+++ b/sound/pci/hda/hda_jack.h -------------------------- File sound/pci/hda/hda_jack.h is read-only; trying to patch anyway checking file sound/pci/hda/hda_jack.h Using Plan A... Hunk #1 FAILED at 41. 1 out of 1 hunk FAILED Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c |index c456c04..3df56c8 100644 |--- a/sound/pci/hda/patch_realtek.c |+++ b/sound/pci/hda/patch_realtek.c -------------------------- File sound/pci/hda/patch_realtek.c is read-only; trying to patch anyway checking file sound/pci/hda/patch_realtek.c Using Plan A... Hunk #1 succeeded at 3598 (offset 5 lines). Hunk #2 succeeded at 3687 (offset 4 lines). Hunk #3 succeeded at 3755 (offset 3 lines). Hunk #4 succeeded at 3823. Hunk #5 succeeded at 3891 (offset -3 lines). Hunk #6 succeeded at 3964 (offset -6 lines). Hunk #7 succeeded at 3980 (offset -6 lines). Hunk #8 succeeded at 4027 (offset -6 lines). Hunk #9 succeeded at 6118 (offset -122 lines). Hunk #10 succeeded at 6289 (offset -122 lines). Hunk #11 succeeded at 6509 (offset -122 lines). Hunk #12 succeeded at 6549 (offset -122 lines). Hunk #13 succeeded at 6574 (offset -122 lines). Hunk #14 succeeded at 6658 (offset -122 lines). done well that is, anything ask. Thy all note, jason.braddock in pulseaudio 7.1 the 2.1 profile exist be default, so you don't need create it anymore, try upgrade to aproaching to that version and may can works the subwoofer, i suppose in my system the issue will be detect the subwoofer when is connected. the patch is only useful when pulseaudio can switch automatically from stereo to 2.1 when exterenal subwoofer is plugged. you can still test pulseaudio 7.1 by maunally change the profile without the above patch Note: searching in the web i found a little thing, the alc663 driver is a 5.1 not 2.1, this probably can be extended to the profiles of pulseaudio. Source: http://www.realtek.com/products/productsView.aspx?Langid=1&PFid=37&Level=5&Conn=4&ProdID=165 In the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=70821 Thx for the note raymond. As you can see in the las message, i check the profiles available in the default.conf and exist a 5.1 profile, ¿why i can't select it? https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=8e38395360844806041ea69ab9690f5f174bc40c static const struct snd_pcm_chmap_elem asus_pcm_2_1_chmaps[] = { + { .channels = 2, + .map = { SNDRV_CHMAP_FL, SNDRV_CHMAP_FR } }, + { .channels = 4, + .map = { SNDRV_CHMAP_FL, SNDRV_CHMAP_FR, + SNDRV_CHMAP_NA, SNDRV_CHMAP_LFE } }, /* LFE only on right */ + { } since the subwoofer node 0x16 does not provide jack detect signal, the driver just create surround speaker phantom jack for those asus n751jm with alc668 , the subwoofer node 0x1a support jack detect, so it is possible to create "external subwoofer" jack for the detection of sonic master subwoofer on alc663 node 0x1e seem can report the status of the subwoofer but pincap does not expose this capability and lack of unsolicited event only 4 channels is supported since one DAC is used by the headphone, you need to use 2.1 profile post the pulseaudio verbose log if it still not working -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/299. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.