Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged

Bug #1302090 reported by Fabián Ezequiel Gallina
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
ALSA driver
Confirmed
Unknown
alsa-driver (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Here's the required release and package information:

    Description: Ubuntu Trusty Tahr (development branch)
    Release: 14.04

    Package: linux-image-extra-3.13.0-19-generic
    Version: 3.13.0-19.40

When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo.

I would love the sound output to be stereo by default and not be forced to plug anything to achieve that.

Attached is the alsa-info.sh output for my machine.

Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :
Revision history for this message
Raymond (superquad-vortex2) wrote :

Audio and Speakers
Internal High-Definition 5.1 Performance Audio with Dolby Home Theater v4 Software (Standard)
2.1 Speaker configuration with Subwoofer
Audio Powered by Klipsch®
7.1 Digital Audio out using HDMI out connection

(2x) Audio Out 1/8" Ports (One compatible with inline mic headset)
(1x) Line In Microphone 1/8" Port (retaskable for 5.1 analog audio output)

how many internal speakers ?

only stereo speakers at node 0x14

Node 0x14 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name="Speaker Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Speaker Phantom Jack", index=0, device=0
  Amp-In caps: N/A
  Amp-In vals: [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003c: IN OUT HP EAPD Detect
  EAPD 0x2: EAPD
  Pin Default 0x90170110: [Fixed] Speaker at Int N/A
    Conn = Analog, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 3
     0x0c 0x0d 0x0e*

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

Revision history for this message
Raymond (superquad-vortex2) wrote :

which node is the headset ?

try hda-jack-sense-test

as Mic Jack is designed for supporting 5.1 external speakers by retasking, two headphone jacks seem support surround 4.0

control.17 {
  iface CARD
  name 'Headphone Front Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.18 {
  iface CARD
  name 'Headphone Surround Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name="Headphone Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Front Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0x0001001c: OUT HP EAPD Detect
  EAPD 0x2: EAPD
  Pin Default 0x0321101f: [Jack] HP Out at Ext Left
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0xf
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=01, enabled=1
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 3
     0x0c* 0x0d 0x0e
Node 0x16 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name="Headphone Playback Switch", index=1, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Surround Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0x0000001c: OUT HP Detect
  Pin Default 0x03211020: [Jack] HP Out at Ext Left
    Conn = 1/8, Color = Black
    DefAssociation = 0x2, Sequence = 0x0
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=02, enabled=1
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 3
     0x0c 0x0d* 0x0e

Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :

The laptop has only one set of internal Left-Right speakers.

Here's the output for hda_jack_sense_test:

# First headphone jack plugged in (the one that sits closer to the front of the laptop).

Pin 0x15 (Black HP Out): present = Yes
Pin 0x16 (Black HP Out): present = No
Pin 0x19 (Black Mic): present = No

# Second headphone jack plugged in.

Pin 0x15 (Black HP Out): present = No
Pin 0x16 (Black HP Out): present = Yes
Pin 0x19 (Black Mic): present = No

# No headphones plugged.

Pin 0x15 (Black HP Out): present = No
Pin 0x16 (Black HP Out): present = No
Pin 0x19 (Black Mic): present = No

Revision history for this message
Raymond (superquad-vortex2) wrote :

do you mean that it has no internal subwoofer ?

which headphone jack support headset ?

(2x) Audio Out 1/8" Ports (One compatible with inline mic headset)
(1x) Line In Microphone 1/8" Port (retaskable for 5.1 analog audio output)

do it has a headset icon and a headphome icon near the jacks ?

do the headset mic work as expected ?

Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :

My bad, it does also have an internal subwoofer. Sorry.

The headset supporting jack is this one (it is marked with the icon you mention): Pin 0x15 (Black HP Out): present = Yes

Unfortunately I don't have a headset with inline mic available to test. FWIW the microphone jack does work as intended.

At last but not least, I checked the sources for which the driver got built, and yes, it seems I don't have those changes. I'll try to get them tested and see if the issue gets solved. Will keep you posted.

Revision history for this message
Raymond (superquad-vortex2) wrote :

autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
   speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
   hp_outs=2 (0x15/0x16/0x0/0x0/0x0)
   mono: mono_out=0x0
   inputs:
     Internal Mic=0x12
     Mic=0x19

you still need to find out the node for the headset mic and the subwoofer

the problem is only three volume controls but two headphones , speaker and subwoofer , (front, rear, center/lfe)

summary: - Speaker sound output is mono until a headphone jack is plugged
+ Dell Alienware 14, Speaker sound output is mono until a headphone jack
+ is plugged
Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :

Hello,

Could you provide some guidance so I could find out those nodes for you?

On a related note I haven't tried the latest drivers yet, but I will soon and post any relevant information here.

Revision history for this message
Raymond (superquad-vortex2) wrote :

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

try hdajackretask to change one of the remain unconnected pin complexes which pincap support out for the missing speaker using advanced override option

Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :

Thanks for the pointer,

The pin for the subwoofer is 0x1a. Attached is a screenshot with the seetings I used for the override.

With this the subwoofer works fine and the alsamixer control "Bass Speaker" allows toggling it. But I still need to plug the headset on the jack to get stereo.

I'll get myself a headset with inline mic to discover the last pin.

Revision history for this message
Raymond (superquad-vortex2) wrote :

do the subwoofer need both left and right channel ?

try hda-analyer to change the volume sliders of audio mixer which is connected to subwoofet (node 0x0d ?)

speaker-test -c2 -t wave -D hw:0,0

do it work with 2.1 mode ?

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1286021

Revision history for this message
Raymond (superquad-vortex2) wrote :

you have to post the output of alsa-info,sh and pactl list

before you plugged headphone (speaker not working) and after you plugged headphone (speaker working)

Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :

FWIW I'm not using pulseaudio, so no pactl here.

2.1 works fine since the discovery of the subwoofer pin.

Attached are the requested alsa-info.sh outputs.

Not sure about what you mean if the subwoofer needs both left and right channel:

If it's that if I could use the subwoofer alone without the speakers, that's doable, it's just a matter of muting "Speaker" and leave "Bass Speaker" on, and then I have output just from the subwoofer.

If it's that if I can control left and right channels for the subwoofer itself, I can, using the hda_analyzer at the node 0x1a, under the output amplifier group "Val[0]" seems to mute a half of the subwoofer and "Val[1]" mutes the other, seriously I don't know how that happens, I always assumed the subwoofer to be a single speaker, but there it is.

As an additional note, the subwoofer is tied up to the Audio Mixer at node 0x0e (Attached hda_analyzer screenshot as well for it), muting "Val[0]" mutes all left output (as in Speakers, Subwoofer) and "Val[1]" does the same but with the right channel.

Thanks again.

Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :
Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :
Revision history for this message
Fabián Ezequiel Gallina (fgallina) wrote :
Revision history for this message
Raymond (superquad-vortex2) wrote :

.092201] input: HDA Intel PCH Headphone Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input19
[152768.092392] input: HDA Intel PCH Headphone Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
[152768.092619] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
[152890.220402] hda-codec: reconfiguring
[152891.270534] hda-codec: out of range cmd 0:20:400:ffff7fff

seem you are using dynamic reconfiguration instead of early patching

did you use "apply now" only instead of "install boot override" to create the firmware file to fix up the pin ?

speaker and subwoofer have their own volume controls and two headphone share the volume control

Revision history for this message
Raymond (superquad-vortex2) wrote :

Default Association and Sequence are used together by software to group Pin Complexes (and therefore jacks) together into functional blocks to support multichannel operation. Software may assume that all jacks with the same association number are intended to be grouped together, for instance to provide six channel analog output. The Default Association can also be used by software to prioritize resource allocation in constrained situations. Lower Default Association values would be higher in priority for resources such as processing nodes or Input and Output Converters.

Revision history for this message
Raymond (superquad-vortex2) wrote :

Sequence indicates the order of the jacks in the association group. The lowest numbered jack in the association group should be assigned the lowest numbered channels in the stream, etc. The numbers need not be sequential within the group, only the order matters. Sequence numbers within a set of Default Associations must be unique.

Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Raymond (superquad-vortex2) wrote :

http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-on-newer-laptops/

the most reliable source is to actually look at the small icon present next to the jack. Does it look like a headphone (without mic), headset (with mic) or a microphon

http://bazaar.launchpad.net/~unity-settings-daemon-team/unity-settings-daemon/trunk/view/head:/plugins/media-keys/what-did-you-plug-in/pa-backend.c

In PulseAudio ports will show up with the following names:
   Headphones - analog-output-headphones
   Headset mic - analog-input-microphone-headset
   Jack in mic-in mode - analog-input-microphone

   However, since regular mics also show up as analog-input-microphone,
   we need to check for certain controls on alsa mixer level too, to know
   if we deal with a separate mic jack, or a multi-function jack with a
   mic-in mode (also called "headphone mic").
   We check for the following names:

   Headphone Mic Jack - indicates headphone and mic-in mode share the same jack,
     i e, not two separate jacks. Hardware cannot distinguish between a
     headphone and a mic.
   Headset Mic Phantom Jack - indicates headset jack where hardware can not
     distinguish between headphones and headsets
   Headset Mic Jack - indicates headset jack where hardware can distinguish
     between headphones and headsets. There is no use popping up a dialog in
     this case, unless we already need to do this for the mic-in mode.
*/

you may need to file upstream bug report

since there should be either headset Mic Jack or headset Mic phantom Jack for you to use the headset mic

control.17 {
  iface CARD
  name 'Headphone Front Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.18 {
  iface CARD
  name 'Headphone Surround Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

Revision history for this message
Pietro (p-punk) wrote :

Hello i think i have the same issue since i have the same system Alienware 14 with ALC668 driver on Ubuntu Trusty Tahr 14.04

let you the alsa-info i hope it's enough information i have tried hdajackretask and it's a good tool but the problem remains

Thank you.

Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
Raymond (superquad-vortex2) wrote :

you have not set node 0x1a to speaker in /sys/class/sound/hwC1D0/user_pin_configs:

/sys/class/sound/hwC1D0/init_pin_configs:
0x12 0x99a30140
0x14 0x90170110
0x15 0x0321101f
0x16 0x03211020
0x18 0x40030008
0x19 0x03a11030
0x1a 0x411111f0
0x1b 0x411111f0
0x1d 0x41000001
0x1e 0x411111f0
0x1f 0x411111f0

/sys/class/sound/hwC1D0/driver_pin_configs:

/sys/class/sound/hwC1D0/user_pin_configs:
0x12 0x99a30140
0x14 0x90170110
0x15 0x0321101f
0x16 0x03211020
0x18 0x40030008
0x19 0x03a11030
0x1a 0x411111f0
0x1b 0x411111f0
0x1d 0x41000001
0x1e 0x411111f0
0x1f 0x411111f0

Revision history for this message
Raymond (superquad-vortex2) wrote :

do suvpbwoofer really work since both speaker and subwoofer connect to same audio output ?

to add volume controls to speaker and subwoofer ,

either use hda Jack retask to remove one headphone jack

or

modify driver to increase badness when there are two headphone Jacks and two speaker pins ,but only three audio output when cfg->line_out_type == auto_pin_hp_out since Def assoc of second headphone Jack is larger than that of subwoofer (lower priority to assign volume control/audio output )

this force driver to assign audio output/volume control to two speakers first

Revision history for this message
Cesar (cesarp) wrote :

Hi, I have the same laptop, operating system, and the same problem, too.

Please let me know how can I be of help.

Thanks.

Revision history for this message
Cesar (cesarp) wrote :

Now all of a sudden no sound from speakers, only from headphones...

Revision history for this message
Pietro (p-punk) wrote :

Hey Thank you so much to everybody, specially Raymond (superquad-vortex2) for pointing to node 0x1a, work like a charm installing hdajackretask, chosing Realtek ALC668, marking show unconnected pins and, find Pin ID 0x1a mark override, choose line out (center/LFE) and apply now and that's it enjoy the great sound of Alienware 14, i hope this work for others, sorry for my terrible english.

Revision history for this message
Cesar (cesarp) wrote :

Yes, it works!

Things look a little bit different in alsamixer, though. Now instead of 'Enabled' it displays 'Line Out' in the auto-mute feature, but the functionality remains intact. Also 'Speaker' is set to 0 and cannot be changed. I'm attaching a screenshot as reference.

I haven't seen any other unwanted effects from the override. I'm able to adjust the volume using the fn keys and from the sound settings, as always. Will report back if I find something else.

Thanks for your help guys.

Revision history for this message
Raymond (superquad-vortex2) wrote :

reatasking subwoofer as line out is a trick which force the driver share volume control with speaker

the drawback is missing volume control of the subwoofer but you have volume controls for your headset and headphone

Revision history for this message
Raymond (superquad-vortex2) wrote :

#define assoc_of_nid(c,p) get_defcfg_association(snd_hda_codec_get_pincfg(c,p))

     if ((cfg->speaker_outs == 2) && (cfg->hp_outs == 2))
          if (cfg->line_out_type == AUTO_PIN_HP_OUT)
              for(i=0; i<2; i++)
                   if (assoc_of_nid(codec,cfg->line_out_pins[i]) > assoc_of_nid(codec,cfg->speaker_pins[i]))
                            badness++;

add the above in fill_and_eval_dacs() in hda_generic.c after

  if ( spec->mixer_nid) {

  }

this increase badness of cfg->line_out_type == AUTO_PIN_HP_OUT by one when the second headphone have higher def association than subwoofer , driver create speaker and bass speaker volume controls and headphone volume control for headset and headphone

2 comments hidden view all 211 comments
Revision history for this message
Guy (guy-b) wrote :

Hi,

I did the instructions in #30 (Pietro) but I had to choose the option "install boot override" with "apply now" the device was allways occupied.
Anyway, now it showing the same in alsamixer as #31 (cesar) but to get the subwoofer working I have to plug the headphones into one of the two (headphone or headset) connectors. As soon as I remove them I loose the subwoofer !

What I'm doing wrong ?

I'm on Ubuntu server + xfce4 with his mixer (alsa) which shows also a setting switches > "speaker" that enable/disable de front speaker.

Thank you for any help.

Revision history for this message
Guy (guy-b) wrote :
Revision history for this message
Guy (guy-b) wrote :
Revision history for this message
Guy (guy-b) wrote :

Nobody to help ? Could someone confirme that you don't need to plug the headphones to get the subwoofer working ? Here is what I have in syslog concerning the hda-intel :

01-14 03:44 kernel: [ 5.318176] hda-intel 0000:00:03.0: Applying patch firmware 'hda-jack-retask.fw'
01-14 03:44 kernel: [ 5.318333] hda-intel 0000:00:1b.0: Applying patch firmware 'hda-jack-retask.fw'
01-14 03:44 kernel: [ 5.319998] HDA driver get symbol successfully from i915 module
01-14 03:44 kernel: [ 5.320025] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
01-14 03:44 kernel: [ 5.327609] snd_hda_intel 0000:00:03.0: irq 48 for MSI/MSI-X
01-14 03:44 kernel: [ 5.330441] SKU: Nid=0x1d sku_cfg=0x41000001
01-14 03:44 kernel: [ 5.330443] SKU: port_connectivity=0x1
01-14 03:44 kernel: [ 5.330444] SKU: enable_pcbeep=0x0
01-14 03:44 kernel: [ 5.330445] SKU: check_sum=0x00000000
01-14 03:44 kernel: [ 5.330445] SKU: customization=0x00000000
01-14 03:44 kernel: [ 5.330446] SKU: external_amp=0x0
01-14 03:44 kernel: [ 5.330447] SKU: platform_type=0x0
01-14 03:44 kernel: [ 5.330448] SKU: swap=0x0
01-14 03:44 kernel: [ 5.330448] SKU: override=0x1
01-14 03:44 kernel: [ 5.330717] autoconfig: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:line
01-14 03:44 kernel: [ 5.330718] speaker_outs=1 (0x14/0x0/0x0/0x0/0x0)
01-14 03:44 kernel: [ 5.330720] hp_outs=2 (0x15/0x16/0x0/0x0/0x0)
01-14 03:44 kernel: [ 5.330720] mono: mono_out=0x0
01-14 03:44 kernel: [ 5.330721] inputs:
01-14 03:44 kernel: [ 5.330723] Mic=0x19
01-14 03:44 kernel: [ 5.330724] Internal Mic=0x12
01-14 03:44 kernel: [ 5.330725] realtek: No valid SSID, checking pincfg 0x41000001 for NID 0x1d
01-14 03:44 kernel: [ 5.330726] realtek: Enabling init ASM_ID=0x0001 CODEC_ID=10ec0668
01-14 03:44 kernel: [ 5.336462] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input12
01-14 03:44 kernel: [ 5.336517] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input11
01-14 03:44 kernel: [ 5.336563] input: HDA Intel PCH Speaker as /devices/pci0000:00/0000:00:1b.0/sound/card1/input10
01-14 03:44 kernel: [ 5.336612] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9
01-14 03:44 kernel: [ 5.336661] init: failsafe main process (810) killed by TERM signal
01-14 03:44 kernel: [ 5.340994] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input15
01-14 03:44 kernel: [ 5.341064] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input14
01-14 03:44 kernel: [ 5.341113] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input13

Thank you.

Revision history for this message
Guy (guy-b) wrote :

Anybody out there ?

131 comments hidden view all 211 comments
Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

only need firmware for 0000:00:1b.0 (card 1) for the codec alc668

[ 13.653394] snd_hda_intel 0000:00:03.0: Applying patch firmware 'hda-jack-retask.fw'
[ 13.653506] snd_hda_intel 0000:00:1b.0: Applying patch firmware 'hda-jack-retask.fw'

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #93)
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/
> Documentation/sound/alsa/HD-Audio.txt
>
>
>
> Early Patching
> ~~~~~~~~~~~~~~
> When CONFIG_SND_HDA_PATCH_LOADER=y is set, you can pass a "patch" as a
> firmware file for modifying the HD-audio setup before initializing the
> codec. This can work basically like the reconfiguration via sysfs in
> the above, but it does it before the first codec configuration.
>
> A patch file is a plain text file which looks like below:
>
> ------------------------------------------------------------------------
> [codec]
> 0x12345678 0xabcd1234 2
>
> [model]
> auto
>
> [pincfg]
> 0x12 0x411111f0
>
> did you set the correct codec id and subsystem id and model
>
> since you need model dell-headset-multi to call the function
> alc_fixup_headset_mode_alc668 to init the headset
>
> and those pin fix to remove headphone mic by the original mic jack and
> subwoofer
> remove the headphone jack so that line out type =speaker for the 2.1 channel
> map

data from my hda-jack-restask.fw file

[codec]
0x10ec0668 0x102805a9 0

[pincfg]
0x12 0x99a30140
0x14 0x90170110
0x15 0x0321101f
0x16 0x411111f0
0x18 0x40030008
0x19 0x03a11030
0x1a 0x90100111
0x1b 0x411111f0
0x1d 0x41000001
0x1e 0x411111f0
0x1f 0x411111f0

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to mohammed imran from comment #97)
> (In reply to Raymond from comment #93)
> > https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/
> > Documentation/sound/alsa/HD-Audio.txt
> >
> >
> >
> > Early Patching
> > ~~~~~~~~~~~~~~
> > When CONFIG_SND_HDA_PATCH_LOADER=y is set, you can pass a "patch" as a
> > firmware file for modifying the HD-audio setup before initializing the
> > codec. This can work basically like the reconfiguration via sysfs in
> > the above, but it does it before the first codec configuration.
> >
> > A patch file is a plain text file which looks like below:
> >
> > ------------------------------------------------------------------------
> > [codec]
> > 0x12345678 0xabcd1234 2
> >
> > [model]
> > auto
> >
> > [pincfg]
> > 0x12 0x411111f0
> >
> > did you set the correct codec id and subsystem id and model
> >
> > since you need model dell-headset-multi to call the function
> > alc_fixup_headset_mode_alc668 to init the headset
> >
> > and those pin fix to remove headphone mic by the original mic jack and
> > subwoofer
> > remove the headphone jack so that line out type =speaker for the 2.1
> channel
> > map
>
> data from my hda-jack-restask.fw file
>
> [codec]
> 0x10ec0668 0x102805a9 0
>
> [pincfg]
> 0x12 0x99a30140
> 0x14 0x90170110
> 0x15 0x0321101f
> 0x16 0x411111f0
> 0x18 0x40030008
> 0x19 0x03a11030
> 0x1a 0x90100111
> 0x1b 0x411111f0
> 0x1d 0x41000001
> 0x1e 0x411111f0
> 0x1f 0x411111f0

Amended file in hda-jack-restask.fw
[codec]
0x10ec0668 0x102805a9 0

[pincfg]
0x12 0x99a30140
0x14 0x90170110
0x15 0x0321101f
0x16 0x411111f0
0x18 0x40030008
0x19 0x03a11030
0x1a 0x90100111
0x1b 0x03a1113c /* use as headset mic, without its own jack detect */
0x1d 0x41000001
0x1e 0x411111f0
0x1f 0x411111f0

&&&&&&&&&&&&&&&&&&&

data as per alsa-base.conf
#my entry

snd_hda_intel: model=,dell-headset-multi, patch=,/lib/firmware/hdajackretask.fw
snd_hda_intel: patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw

control.16 {
  iface CARD
  name 'Headset Mic Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

am i right? or wrong? file attached.

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #93)
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/
> Documentation/sound/alsa/HD-Audio.txt
>
>
>
> Early Patching
> ~~~~~~~~~~~~~~
> When CONFIG_SND_HDA_PATCH_LOADER=y is set, you can pass a "patch" as a
> firmware file for modifying the HD-audio setup before initializing the
> codec. This can work basically like the reconfiguration via sysfs in
> the above, but it does it before the first codec configuration.
>
> A patch file is a plain text file which looks like below:
>
> ------------------------------------------------------------------------
> [codec]
> 0x12345678 0xabcd1234 2
>
> [model]
> auto
>
> [pincfg]
> 0x12 0x411111f0
>

#my entry

options snd_hda_intel: patch=hda-jack-retask.fw

control.16 {
  iface CARD
  name 'Headset Mic Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
> did you set the correct codec id and subsystem id and model
>
> since you need model dell-headset-multi to call the function
> alc_fixup_headset_mode_alc668 to init the headset
>
> and those pin fix to remove headphone mic by the original mic jack and
> subwoofer
> remove the headphone jack so that line out type =speaker for the 2.1 channel
> map

data form

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

only need this line

options snd-hda-intel model=,dell-headset-multi patch=,hda-jack-retask.fw

and remove the line created by hda-jack-retask in alsa-base.conf

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #100)
> only need this line
>
> options snd-hda-intel model=,dell-headset-multi patch=,hda-jack-retask.fw
>
> and remove the line created by hda-jack-retask in alsa-base.conf

I don't any other line has being created by hda-jack-restask. i have made the necessary amendments.

it is possible for you to remote into my system and you can run the test's needed.

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

[codec]
0x10ec0668 0x102805a9 0

[model]
dell-headset-multi

[pincfg]

0x16 0x411111f0
0x19 0x03a11030
0x1a 0x90100111

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

Created attachment 218841
alsamixer

alsamixer state , have a look and tell.

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

You have to post output of alsa-info.sh

Check whether you have capture source which has three source

Internal Mic, headset Mic and Mic

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

http://bazaar.launchpad.net/~unity-settings-daemon-team/unity-settings-daemon/trunk/view/head:/plugins/media-keys/what-did-you-plug-in/pa-backend.c

The “what did you plug in”-dialog is a part of unity-settings-daemom,

this dialog is designed for those dell laptop with single combo jack and won't work on your dell alienware 14

as you cannot select your mic jack since the dialog is only looking of "Headphone mic jack"

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

(In reply to mohammed imran from comment #103)
> Created attachment 218841 [details]
> alsamixer
>
> alsamixer state , have a look and tell.

This look like you are using dell-headset-multi plus subwoofer fix up

If Headphone Mic cannot be fixed up to Mic jack by early patching , you need to modify patch_realtek.c to create dell-alienware model

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/sound/pci/hda/patch_realtek.c

 [ALC668_FIXUP_DELL_MIC_NO_PRESENCE] = {
  .type = HDA_FIXUP_PINS,
  .v.pins = (const struct hda_pintbl[]) {
   { 0x19, 0x03a1913d }, /* use as headphone mic, without its own jack detect */
   { 0x1b, 0x03a1113c }, /* use as headset mic, without its own jack detect */
   { }
  },
  .chained = true,
  .chain_id = ALC668_FIXUP_HEADSET_MODE
 },

the simplest way is

1) remove 'headphone mic" fixup from ALC668_FIXUP_DELL_MIC_NO_PRESENCE

2) remove node 0x16 "headphone'

3) add subwoofer pin

{ 0x16 , 0x411111f0 },

{ 0x1a , 0x90100111 },

recompile hda driver

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

enum {
 ALC662_FIXUP_ASPIRE,
 ALC662_FIXUP_LED_GPIO1,
 ALC662_FIXUP_IDEAPAD,
 ALC272_FIXUP_MARIO,
 ALC662_FIXUP_CZC_P10T,
 ALC662_FIXUP_SKU_IGNORE,
 ALC662_FIXUP_HP_RP5800,
 ALC662_FIXUP_ASUS_MODE1,
 ALC662_FIXUP_ASUS_MODE2,
 ALC662_FIXUP_ASUS_MODE3,
 ALC662_FIXUP_ASUS_MODE4,
 ALC662_FIXUP_ASUS_MODE5,
 ALC662_FIXUP_ASUS_MODE6,
 ALC662_FIXUP_ASUS_MODE7,
 ALC662_FIXUP_ASUS_MODE8,
 ALC662_FIXUP_NO_JACK_DETECT,
 ALC662_FIXUP_ZOTAC_Z68,
 ALC662_FIXUP_INV_DMIC,
 ALC662_FIXUP_DELL_MIC_NO_PRESENCE,
 ALC668_FIXUP_DELL_MIC_NO_PRESENCE,
 ALC662_FIXUP_HEADSET_MODE,
 ALC668_FIXUP_HEADSET_MODE,
 ALC662_FIXUP_BASS_MODE4_CHMAP,
 ALC662_FIXUP_BASS_16,
 ALC662_FIXUP_BASS_1A,
 ALC662_FIXUP_BASS_CHMAP,
 ALC668_FIXUP_AUTO_MUTE,
 ALC668_FIXUP_DELL_DISABLE_AAMIX,
 ALC668_FIXUP_DELL_XPS13,
 ALC662_FIXUP_ASUS_Nx50,
 ALC668_FIXUP_ASUS_Nx51,
        ALC668_FIXUP_DELL_ALIENWARE.
        A:C668_FIXUP_DELL_ALIENWARE_51,
};

 [ALC668_FIXUP_DELL_ALIENWARE] = {
  .type = HDA_FIXUP_PINS,
  .v.pins = (const struct hda_pintbl[]) {
                        { 0x16 , 0x411111f0 },
                        { 0x1a , 0x90100111 },
   { 0x1b, 0x03a1113c }, /* use as headset mic, without its own jack detect */
   { }
  },
  .chained = true,
  .chain_id = ALC668_FIXUP_HEADSET_MODE
 },

 [ALC668_FIXUP_DELL_ALIENWARE_51] = {
  .type = HDA_FIXUP_PINS,
  .v.pins = (const struct hda_pintbl[]) {
                   {0x15, 0x02014010},
                   {0x16, 0x02014011},
                   {0x19, 0x02014012},
   { }
  },

 },

static const struct hda_model_fixup alc662_fixup_models[] = {
 {.id = ALC272_FIXUP_MARIO, .name = "mario"},
 {.id = ALC662_FIXUP_ASUS_MODE1, .name = "asus-mode1"},
 {.id = ALC662_FIXUP_ASUS_MODE2, .name = "asus-mode2"},
 {.id = ALC662_FIXUP_ASUS_MODE3, .name = "asus-mode3"},
 {.id = ALC662_FIXUP_ASUS_MODE4, .name = "asus-mode4"},
 {.id = ALC662_FIXUP_ASUS_MODE5, .name = "asus-mode5"},
 {.id = ALC662_FIXUP_ASUS_MODE6, .name = "asus-mode6"},
 {.id = ALC662_FIXUP_ASUS_MODE7, .name = "asus-mode7"},
 {.id = ALC662_FIXUP_ASUS_MODE8, .name = "asus-mode8"},
        {.id = ALC668_FIXUP_DELL_MIC_NO_PRESENCE, .name = "dell-headset-multi"},
 {.id = ALC668_FIXUP_DELL_ALIENWARE, .name = "dell-alienware"},
 {.id = ALC668_FIXUP_DELL_ALIENWARE_51, .name = "dell-51"},
 {}
};

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

(In reply to mohammed imran from comment #103)
> Created attachment 218841 [details]
> alsamixer
>
> alsamixer state , have a look and tell.

do the headset mic work as expected or not ?

the early patching fix the pin before driver apply dell-headset-multi model pin fixup

so the mic jack cannot be fix up

you can use hint to disable loopback mixing if this is any noise simolar to xps 13 using ALC668_FIXUP_DELL_DISABLE_AAMIX

[hint]
mixer_nid=0

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #104)
> You have to post output of alsa-info.sh
>
> Check whether you have capture source which has three source
>
> Internal Mic, headset Mic and Mic

Your ALSA information is located at

http://www.alsa-project.org/db/?f=cc4c2d4193b7b9ba3ee9be368f1fecb023930b3d

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #106)
> (In reply to mohammed imran from comment #103)
> > Created attachment 218841 [details]
> > alsamixer
> >
> > alsamixer state , have a look and tell.
>
> This look like you are using dell-headset-multi plus subwoofer fix up
>
>
> If Headphone Mic cannot be fixed up to Mic jack by early patching , you
> need to modify patch_realtek.c to create dell-alienware model

Yup you are right, when plugging in my earphone (Apple iphones model) i get to see the unity dialog, asking me what i have inserted. Pic attached.

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

Created attachment 218901
dialog box unity

Yup you are right, when plugging in my earphone (Apple iphones model) i get to see the unity dialog, asking me what i have inserted. Pic attached.

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to mohammed imran from comment #112)
> Created attachment 218901 [details]
> dialog box unity
>
> Yup you are right, when plugging in my earphone (Apple iphones model) i get
> to see the unity dialog, asking me what i have inserted. Pic attached.

But the dialog only pops up when i plug it in my headphones with mic icon, the third plughole of the three O-O-O (Mic-HeadPhone-Headphone/w Mic).

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #102)
> [codec]
> 0x10ec0668 0x102805a9 0
>
> [model]
> dell-headset-multi
>
> [pincfg]
>
> 0x16 0x411111f0
> 0x19 0x03a11030
> 0x1a 0x90100111

[codec]
0x10ec0668 0x102805a9 0

[model]
dell-headset-multi

[pincfg]
0x12 0x99a30140
0x14 0x90170110
0x15 0x0321101f
0x16 0x411111f0
0x18 0x40030008
0x19 0x03a11030
0x1a 0x90100111
0x1b 0x03a1113c /* use as headset mic, without its own jack detect */
0x1d 0x41000001
0x1e 0x411111f0
0x1f 0x411111f0

ok, do i need to remove the extra pincfg?

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #107)
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/sound/pci/
> hda/patch_realtek.c
>
>
> [ALC668_FIXUP_DELL_MIC_NO_PRESENCE] = {
> .type = HDA_FIXUP_PINS,
> .v.pins = (const struct hda_pintbl[]) {
> { 0x19, 0x03a1913d }, /* use as headphone mic, without
> its own jack
> detect */
> { 0x1b, 0x03a1113c }, /* use as headset mic, without
> its own jack detect
> */
> { }
> },
> .chained = true,
> .chain_id = ALC668_FIXUP_HEADSET_MODE
> },
>
>
> the simplest way is
>
> 1) remove 'headphone mic" fixup from ALC668_FIXUP_DELL_MIC_NO_PRESENCE
>
> 2) remove node 0x16 "headphone'
>
> 3) add subwoofer pin
>
> { 0x16 , 0x411111f0 },
>
> { 0x1a , 0x90100111 },
>
>
> recompile hda driver

Umm, how to do this patching stuff and where to paste this code? Was your a suggestion or a test for me to perform?

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

(In reply to mohammed imran from comment #110)
> (In reply to Raymond from comment #104)
> > You have to post output of alsa-info.sh
> >
> > Check whether you have capture source which has three source
> >
> > Internal Mic, headset Mic and Mic
>
> Your ALSA information is located at
>
> http://www.alsa-project.org/db/?f=cc4c2d4193b7b9ba3ee9be368f1fecb023930b3d

snd_hda_intel: model=,dell-headset-multi patch=,hda-jack-retask.fw
snd_hda_intel: patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw

you still have two lines in alsa-base.conf

options snd-hda-intel model=,dell-headset-multi patch=,hda-jack-retask.fw
options snd-hda-intel patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw

you have to remove

options snd-hda-intel patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

Created attachment 219001
Comment 116

See only one line that you have asked should remain? i don't know where the extra one got inserted.

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #116)
> (In reply to mohammed imran from comment #110)
> > (In reply to Raymond from comment #104)
> > > You have to post output of alsa-info.sh
> > >
> > > Check whether you have capture source which has three source
> > >
> > > Internal Mic, headset Mic and Mic
> >
> > Your ALSA information is located at
> >
> > http://www.alsa-project.org/db/?f=cc4c2d4193b7b9ba3ee9be368f1fecb023930b3d
>
> snd_hda_intel: model=,dell-headset-multi patch=,hda-jack-retask.fw
> snd_hda_intel:
> patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-
> retask.fw
>
>
>
> you still have two lines in alsa-base.conf
>
> options snd-hda-intel model=,dell-headset-multi patch=,hda-jack-retask.fw
> options snd-hda-intel
> patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-
> retask.fw
>
> you have to remove
>
> options snd-hda-intel
> patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-
> retask.fw

See only one line that you have asked should remain? i don't know where the extra one got inserted.

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

(In reply to mohammed imran from comment #115)
> (In reply to Raymond from comment #107)
> >
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/sound/pci/
> > hda/patch_realtek.c
> >
> >
> > [ALC668_FIXUP_DELL_MIC_NO_PRESENCE] = {
> > .type = HDA_FIXUP_PINS,
> > .v.pins = (const struct hda_pintbl[]) {
> > { 0x19, 0x03a1913d }, /* use as headphone mic, without
> its own jack
> > detect */
> > { 0x1b, 0x03a1113c }, /* use as headset mic, without
> its own jack detect
> > */
> > { }
> > },
> > .chained = true,
> > .chain_id = ALC668_FIXUP_HEADSET_MODE
> > },
> >

> Umm, how to do this patching stuff and where to paste this code? Was your a
> suggestion or a test for me to perform?

just append at the end of alc662_fixup[] after [ALC668_FIXUP_ASUS_Nx51]

s

Revision history for this message
In , superquad.vortex2 (superquad.vortex2-linux-kernel-bugs) wrote :

to enable both headphone and headset, you need to test whether headset and headphone can share volume control by prefered_dacs, this force driver assigned DACs to speaker and bass speaker first

 static hda_nid_t preferred_pair[] = {
+ 0x14, 0x02,
+ 0x1a, 0x03,
+ 0x15, 0x04,
+ 0x16, 0x04,
+ 0
+ };

+ spec->gen.preferred_dacs = preferred_pair;

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #120)
> to enable both headphone and headset, you need to test whether headset and
> headphone can share volume control by prefered_dacs, this force driver
> assigned DACs to speaker and bass speaker first
>
>
> static hda_nid_t preferred_pair[] = {
> + 0x14, 0x02,
> + 0x1a, 0x03,
> + 0x15, 0x04,
> + 0x16, 0x04,
> + 0
> + };
>
> + spec->gen.preferred_dacs = preferred_pair;

So you want me to copy the code above, and edit the patch_realtek.c with the changes above and then recompile a new kernel? right

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

Hi,

Sorry was away on vacation.

Any update on the issue?

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

(In reply to Raymond from comment #120)
> to enable both headphone and headset, you need to test whether headset and
> headphone can share volume control by prefered_dacs, this force driver
> assigned DACs to speaker and bass speaker first
>
>
> static hda_nid_t preferred_pair[] = {
> + 0x14, 0x02,
> + 0x1a, 0x03,
> + 0x15, 0x04,
> + 0x16, 0x04,
> + 0
> + };
>
> + spec->gen.preferred_dacs = preferred_pair;

Hey Raymond, any updates yet? or progress? Please advise?

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

Hi, can anyone else up take this bug or issue up?

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

So you fix the sound:

1. Open a Terminal (Ctrl + Alt + T).

2. Write 'sudo su' to login as root.

3. Install via apt 'alsa-tools-gui'.

4. Logout via exit.

5. Write 'hdajackretask' and press enter.

6. Click on 'Intel Haswell HDMI' and select 'Realtek ALC3661'.

7. A lot of new entrys are visible. Select 'Show unconnected pins'.

8. Click on 'Overwrite' on Pin ID '0x1a'.

9. Click on the Context Menu and select 'Line out (Center/LFE)'.

10. Click on 'Apply now' and enter your user password.

11. Click on 'Install boot overwrite' to save the settings permanently.

12. Click on your Volume Icon on the top (Ubuntu Unity) and remove the marker 'mute'.

13. Reboot and your sound work perfect.

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Created attachment 255623
After reboot

Followed the Above on my Alienware 18 running Linux Mint 18.1

I did everything in the list above

apart from "Click on your Volume Icon on the top (Ubuntu Unity) and remove the marker 'mute'."

as It didn't show anything different in my Sound properties

The attachment shown is after a reboot

So its back to the drawing board for me
Cheers
Gaz

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

Mine is Alienware 14, and sound is fine now, a major improvement, but as you see the developer of person assisting me,has now disappeared.
I am on Ubuntu 16.10.

mail me on <email address hidden> or come to ubuntu IRC channel and we shall take it from their. see what can be done.

regards.

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Ok I did a full reinstall this arvo
First thing I did was the Fix above

But sadly it has had no effect
Back to the drawing board

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

I hope someone pics up our bug report.

Revision history for this message
In , imranmohd72 (imranmohd72-linux-kernel-bugs) wrote :

sudo] password for immu:
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3661 Analog [ALC3661 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Here are mine

gaz-alienware # arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3661 Analog [ALC3661 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Wow I wonder where HDMI has gone

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Created attachment 255685
Sound

Found them

gazalienware-Alienware-18 ~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3661 Analog [ALC3661 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

gaz-alienware # lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Created attachment 255687
Alsa

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Created attachment 255689
htmi

Revision history for this message
In , gaznims (gaznims-linux-kernel-bugs) wrote :

Created attachment 255691
more

Changed in alsa-driver:
status: Unknown → Confirmed
Displaying first 40 and last 40 comments. View all 211 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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