At Fri, 13 Feb 2009 14:22:00 -0500, Tim Barnette wrote: > > ..And it worked! I now have sound! Can you tell me what I actually did here? The problem was that your BIOS didn't set the correct default pin configuration. The driver doesn't know which pin should be used for the speaker output, as a consequence, it's set as INPUT. Now you set it OUTPUT manually by hda-verb, and (fortunately) the route to that pin was alive even though it wasn't declared, you get the speaker output now. The next step is to implement a proper pin-config to override by the driver. This won't be much work, but hey, wait for a while. (Or, did Herton already work on that?) thanks, Takashi > > On Fri, Feb 13, 2009 at 2:16 PM, Tim Barnette <tim.barnette@xxxxxxxxx> wrote: > > Takashi, I was able to build hda-verb and when I executed the command > below, it responded with: > nid=0xd, verb=0x707, param=0x40 > value=0x0 > > On Mon, Feb 2, 2009 at 10:25 AM, Takashi Iwai <tiwai@xxxxxxx> wrote: > > At Mon, 2 Feb 2009 10:17:03 -0500, > Tim Barnette wrote: > > > > Thanks, Takashi. I made this change and rebooted. > > > > I noticed right away the mute light is no longer on... but still no > sound > > through speakers, only headphones.. > > > > /sys/module/snd_hda_intel/parameters/model > > contains > > hp-dv5,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL> > > > > attached is the alsa-info.txt you requested.. > > Did you try the latest alsa-driver snapshot? > > If it still doesn't work, I guess this is a BIOS problem. > The other HP dv laptops show the widget 0x0d as the speaker while > yours is unused. > > Try to run: > hda-verb /dev/snd/hwC0D0 0x0d SET_PIN_WID 0x40 > > Takashi > > _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
