Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I run Ubuntu 10.10 on my Intel DG965RY. My front audio ports don't work in Ubuntu, the rear one does. I never got it working earlier when I had Ubuntu 10.04 but this time I am going to try it again.

My codec is SigmaTel STAC9227

My ALSA information is here.

Handy details:

!!ALSA Version
Driver version:     1.0.23
Library version:    1.0.23
Utilities version:  1.0.23

!!Loaded ALSA modules

I know something that I will have to change the model of my module to make the front audio jack works but I couldn't find a model related line in my ALSA configuration file - /etc/modprobe.d/alsa-base.conf (I was able to get to that point in Ubuntu 10.04, may be something has changed).

How can I proceed from here?

Edit: Module details:

Module snd-hda-intel

    Module for Intel HD Audio (ICH6, ICH6M, ESB2, ICH7, ICH8, ICH9, ICH10,
            PCH, SCH),
        ATI SB450, SB600, R600, RS600, RS690, RS780, RV610, RV620,
            RV630, RV635, RV670, RV770,
        VIA VT8251/VT8237A,
        SIS966, ULI M5461

    [Multiple options for each card instance]
    model    - force the model name
    position_fix - Fix DMA pointer (0 = auto, 1 = use LPIB, 2 = POSBUF)
    probe_mask  - Bitmask to probe codecs (default = -1, meaning all slots)
              When the bit 8 (0x100) is set, the lower 8 bits are used
          as the "fixed" codec slots; i.e. the driver probes the
          slots regardless what hardware reports back
    probe_only    - Only probing and no codec initialization (default=off);
          Useful to check the initial codec status for debugging
    bdl_pos_adj    - Specifies the DMA IRQ timing delay in samples.
        Passing -1 will make the driver to choose the appropriate
        value based on the controller chip.
    patch    - Specifies the early "patch" files to modify the HD-audio
            setup before initializing the codecs.  This option is
        available only when CONFIG_SND_HDA_PATCH_LOADER=y is set.
        See HD-Audio.txt for details.
    beep_mode    - Selects the beep registration mode (0=off, 1=on, 2=
        dynamic registration via mute switch on/off); the default
        value is set via CONFIG_SND_HDA_INPUT_BEEP_MODE kconfig.

    [Single (global) options]
    single_cmd  - Use single immediate commands to communicate with
        codecs (for debugging only)
    enable_msi    - Enable Message Signaled Interrupt (MSI) (default = off)
    power_save    - Automatic power-saving timeout (in second, 0 =
    power_save_controller - Reset HD-audio controller in power-saving mode
        (default = on)

    This module supports multiple cards and autoprobe.

    See Documentation/sound/alsa/HD-Audio.txt for more details about
    HD-audio driver.

    Each codec may have a model table for different configurations.
    If your machine isn't listed there, the default (usually minimal)
    configuration is set up.  You can pass "model=<name>" option to
    specify a certain model in such a case.  There are different
    models depending on the codec chip.  The list of available models
    is found in HD-Audio-Models.txt

    The model name "genric" is treated as a special case.  When this
    model is given, the driver uses the generic codec parser without
    "codec-patch".  It's sometimes good for testing and debugging.

    If the default configuration doesn't work and one of the above
    matches with your device, report it together with
    output (with --no-upload option) to kernel bugzilla or alsa-devel
    ML (see the section "Links and Addresses").

    power_save and power_save_controller options are for power-saving
    mode.  See powersave.txt for details.

    Note 2: If you get click noises on output, try the module option
        position_fix=1 or 2.  position_fix=1 will use the SD_LPIB
        register value without FIFO size correction as the current
        DMA pointer.  position_fix=2 will make the driver to use
        the position buffer instead of reading SD_LPIB register.
        (Usually SD_LPIB register is more accurate than the
        position buffer.)

    NB: If you get many "azx_get_response timeout" messages at
    loading, it's likely a problem of interrupts (e.g. ACPI irq
    routing).  Try to boot with options like "pci=noacpi".  Also, you
    can try "single_cmd=1" module option.  This will switch the
    communication method between HDA controller and codecs to the
    single immediate commands instead of CORB/RIRB.  Basically, the
    single command mode is provided only for BIOS, and you won't get
    unsolicited events, too.  But, at least, this works independently
    from the irq.  Remember this is a last resort, and should be
    avoided as much as possible...

    MORE NOTES ON "azx_get_response timeout" PROBLEMS:
    On some hardwares, you may need to add a proper probe_mask option
    to avoid the "azx_get_response timeout" problem above, instead.
    This occurs when the access to non-existing or non-working codec slot
    (likely a modem one) causes a stall of the communication via HD-audio
    bus.  You can see which codec slots are probed by enabling
    CONFIG_SND_DEBUG_VERBOSE, or simply from the file name of the codec
    proc files.  Then limit the slots to probe by probe_mask option.
    For example, probe_mask=1 means to probe only the first slot, and
    probe_mask=4 means only the third slot.

    The power-management is supported.

Possible models for my codec:

  ref        Reference board
  ref-no-jd    Reference board without HP/Mic jack detection
  3stack    D965 3stack
  5stack    D965 5stack + SPDIF
  5stack-no-fp    D965 5stack without front panel
  dell-3stack    Dell Dimension E520
  dell-bios    Fixes with Dell BIOS setup
  volknob    Fixes with volume-knob widget 0x24
  auto        BIOS setup (default)

Unfortunately, I don't have much idea of putting them to use.


I tried every model listed for my codec but still couldn't get it to work.

options snd-hda-intel model=ref
options snd-hda-intel model=ref-no-jd
options snd-hda-intel model=3stack
options snd-hda-intel model=5stack
options snd-hda-intel model=5stack-no-fp
options snd-hda-intel model=dell-3stack
options snd-hda-intel model=dell-bios
options snd-hda-intel model=volknob
options snd-hda-intel model=auto

I tried them one by one by putting it at the end of config file

sudo gedit /etc/modprobe.d/alsa-base.conf

After every change I force-reload alsa

sudo alsa force-reload
share|improve this question

closed as too localized by bodhi.zazen, Marco Ceppi Feb 27 '12 at 16:22

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Does that confirm it as a bug? – Ashfame Jan 4 '11 at 20:42
I have the same problem with the SigmaTel STAC9274D (my motherboard is an Intel DX38BT), until now I failed to find the source of the problem. The funny thing is that the fron jacks are working fine on Ubuntu 8.10. – user10763 Feb 13 '11 at 17:27
This question seems abandoned, there is not further information or activity added to it for several months. I am flagging this to be closed by a moderator. If you think this issue is still affecting you you can flag a moderator to re-open it. – Bruno Pereira Feb 6 '12 at 16:38
Here is a similar question, which was opened because this one was closed -… – Mirzhan Irkegulov Feb 26 '12 at 5:54

1 Answer 1

I have exactly the same problem with exactly the same SigmaTel STAC9227 (though my motherboard is DQ965GF). I managed to get one of the front audio ports to work - the microphone. It started working after I applied '3stack' option. But you need to change the settings in your 'sound preferences' > 'input' > 'connector' should be set to 'microphone 2'. But I haven't been able to make the front audio output to work with any of the options as you stated. We'll have to dig deeper for the solution I guess :(

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.