← Back to team overview

desktop-packages team mailing list archive

[Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound


patch file is a plain text file which looks like below:
[codec] 0x12345678 0xabcd1234 2 [model] auto [pincfg] 0x12 0x411111f0
[verb] 0x20 0x500 0x03 0x20 0x400 0xff [hint] jack_detect = no
The file needs to have a line `[codec]`. The next line should contain
three numbers indicating the codec vendor-id (0x12345678 in the
example), the codec subsystem-id (0xabcd1234) and the address (2) of the
codec. The rest patch entries are applied to this specified codec until
another codec entry is given. Passing 0 or a negative number to the
first or the second value will make the check of the corresponding field
be skipped. It'll be useful for really broken devices that don't
initialize SSID properly. The `[model]` line allows to change the model
name of the each codec. In the example above, it will be changed to
model=auto. Note that this overrides the module option. After the
`[pincfg]` line, the contents are parsed as the initial default pin-
configurations just like `user_pin_configs` sysfs above. The values can
be shown in user_pin_configs sysfs file, too. Similarly, the lines after
`[verb]` are parsed as `init_verbs` sysfs entries, and the lines after
`[hint]` are parsed as `hints` sysfs entries, respectively. Another
example to override the codec vendor id from 0x12345678 to 0xdeadbeef is
like below:
[codec] 0x12345678 0xabcd1234 2 [vendor_id] 0xdeadbeef
In the similar way, you can override the codec subsystem_id via
`[subsystem_id]`, the revision id via `[revision_id]` line. Also, the
codec chip name can be rewritten via `[chip_name]` line.
[codec] 0x12345678 0xabcd1234 2 [subsystem_id] 0xffff1111 [revision_id]
0x10 [chip_name] My-own NEWS-0002
The hd-audio driver reads the file via request_firmware(). Thus, a patch
file has to be located on the appropriate firmware path, typically,
/lib/firmware. For example, when you pass the option `patch=hda-
init.fw`, the file /lib/firmware/hda-init.fw must be present. The patch
module option is specific to each card instance, and you need to give
one file name for each instance, separated by commas. For example, if
you have two cards, one for an on-board analog and one for an HDMI video
board, you may pass patch option like below:
options snd-hda-intel patch=on-board-patch,hdmi-patch

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.

  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
  **** List of PLAYBACK Hardware Devices ****
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
   /dev/snd/controlC0:  tuned      1851 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

To manage notifications about this bug go to: