[alsa-devel] No sound for HP Pavilion DV4z
tiwai at suse.de
Mon Feb 9 18:24:57 CET 2009
At Mon, 9 Feb 2009 17:18:59 +0000 (UTC),
aeleneski at comcast.net wrote:
> Thanks for your time and all these suggestions. Still no luck though.
> Seems like you might not be able to have two files ending in alsa-base in
> the /etc/modprobe.d/ folder. That was the reason for the orange speaker
> indicator. I had
> alsa-base and backup-alsa-base, for some reason it was grabbing the settings
> from the backup.
Ah, yes, module-init-tools doesn't check every backup file suffix.
Better to remove completely old files.
> Anyway, with probe only, orange sound indicator, when doing aplay -l I get
> **** List of PLAYBACK Hardware Devices ****
> card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
With probe_only option, it doesn't make sense to run aplay. This
option basically means "probe codecs but don't set up for use yet".
This is useful to check the raw setup by BIOS before overriding or
modifying by the driver.
One thing we can try is to add the pin config dynamically then
reconfigure. For example, load the driver with probe_only=1, then
do the following as root:
echo 0x0d 0x71c 0x10 > /sys/class/sound/hwC0D0/init_verbs
echo 0x0d 0x71d 0x11 > /sys/class/sound/hwC0D0/init_verbs
echo 0x0d 0x71e 0x17 > /sys/class/sound/hwC0D0/init_verbs
echo 0x0d 0x71f 0x90 > /sys/class/sound/hwC0D0/init_verbs
echo 1 > /sys/class/sound/hwC0D0/reconfig
Then the driver will (re-)configure the PCM and mixers.
> Attached are the requested logs.
> I tried using the hda-verb command you supplied, the only difference is
> that upon restarting after setting the command, I noticed the speakers crack,
> but still no sound.
> Not really sure what I should be looking for here.
> ----- Original Message -----
> From: "Takashi Iwai" <tiwai at suse.de>
> To: aeleneski at comcast.net
> Cc: alsa-devel at alsa-project.org
> Sent: Friday, February 6, 2009 3:11:01 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [alsa-devel] No sound for HP Pavilion DV4z
> At Thu, 5 Feb 2009 23:45:25 +0000 (UTC),
> aeleneski at comcast.net wrote:
> > Ok, seems like I have no luck. Here were some general tests that I did and
> > dmesg results:
> > alias snd-card-0 snd-hda-intel
> > alias sound-slot-0 snd-hda-intel
> > options snd-hda-intel model=hp-dv5
> > [ 94.194443] hda-intel: Invalid position buffer, using LPIB read method
> > [ 265.860938] HDA Intel 0000:01:05.1: PCI INT B disabled
> > [ 265.968343] HDA Intel 0000:00:14.2: PCI INT A disabled
> > [ 266.908393] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) ->
> > 16
> > [ 266.944615] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2
> > input/input14
> > [ 267.037347] input: HDA ATI SB at 0xd2500000 irq 16 Mic at Ext Front Jack
> > /devices/pci0000:00/0000:00:14.2/input/input15
> > [ 267.064233] input: HDA ATI SB at 0xd2500000 irq 16 HP Out at Ext Front
> > as /devices/pci0000:00/0000:00:14.2/input/input16
> > [ 267.080415] HDA Intel 0000:01:05.1: PCI INT B -> GSI 19 (level, low) ->
> > 19
> > [ 267.080445] HDA Intel 0000:01:05.1: setting latency timer to 64
> > [ 315.093428] hda-intel: Invalid position buffer, using LPIB read method
> > instead.
> This isn't too bad, but...
> > options snd-hda-intel model=hp-dv5 enable_msi=1
> > [ 514.468839] APIC error on CPU1: 00(08)
> > [ 514.468851] APIC error on CPU0: 00(08)
> > [ 515.472557] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/
> > hda_intel.c:621: hda_intel: No response from codec, disabling MSI: last cmd=
> > 0x000f0000
> > [ 516.476554] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/
> > hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling
> > mode: last cmd=0x000f0000
> This seems more serious.
> > options snd-hda-intel model=hp-dv5 probe_mask=1
> > [ 512.740875] HDA Intel 0000:01:05.1: PCI INT B disabled
> > [ 512.853833] HDA Intel 0000:00:14.2: PCI INT A disabled
> > [ 514.077692] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) ->
> > 16
> > [ 514.150312] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2
> > input/input17
> > [ 514.412696] input: HDA ATI SB at 0xd2500000 irq 16 Mic at Ext Front Jack
> > /devices/pci0000:00/0000:00:14.2/input/input18
> > [ 514.433025] input: HDA ATI SB at 0xd2500000 irq 16 HP Out at Ext Front
> > as /devices/pci0000:00/0000:00:14.2/input/input19
> > [ 514.454995] HDA Intel 0000:01:05.1: PCI INT B -> GSI 19 (level, low) ->
> > 19
> > [ 514.455153] HDA Intel 0000:01:05.1: setting latency timer to 64
> And this is better.
> So, obviously the problem looks like the communication with the
> secondary codec.
> > Now something weird is that when I initially changed to just model=hp-dv5,
> > mute light on my laptop
> > went from orange to white. But no sound played. Then after the above tests
> > failed, I started to try different models again (such as auto, laptop) and
> > now that light is orange. So I changed back to just model=hp-dv5, and the
> > light is still orange.
> > Any other suggestions?
> OK, first try to load the module with probe_only=1 option.
> Reboot once after setting this model to restore the original BIOS
> setup. Then run alsa-info.sh --no-upload, and attach the generated
> file. If you get errors, try to get /proc/asound/card0/codec#* files,
> at least.
> Then set model=hp-dv5, reboot and get alsa-info output, too.
> Also, make sure to use the very latest alsa-driver snapshot,
> Check the changelogs in alsa-driver*/HEAD and alsa-driver*/alsa-kernel/HEAD
> The problem could be the invalid BIOS pin setup.
> In that case, you can try to change the pin control manually via
> hda-verb program, such as,
> hda-verb /dev/snd/hwC0D0 0x0d SET_PIN_WID 0x40
> See Documentation/sound/alsa/HD-Audio.txt in the recent kernel
> (found in alsa-driver snapshot, too).
More information about the Alsa-devel