At Wed, 18 Feb 2009 07:33:42 +0100,I wrote:> > At Tue, 17 Feb 2009 21:43:16 +0100,> Bartłomiej Holdenmayer wrote:> > > > Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:> > > At Fri, 13 Feb 2009 22:48:26 +0100,> > > Bartłomiej Holdenmayer wrote:> > > > > > > > Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:> > > > > At Fri, 13 Feb 2009 07:58:44 +0100,> > > > > I wrote:> > > > > > > > > > > > At Fri, 13 Feb 2009 04:37:54 +0100,> > > > > > Bartłomiej Holdenmayer wrote:> > > > > > > > > > > > > > Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:> > > > > > > > At Wed, 11 Feb 2009 03:20:44 +0100,> > > > > > > > Bartłomiej Holdenmayer wrote:> > > > > > > > > > > > > > > > > > Welcome,> > > > > > > > > I have no sound through HDMI.> > > > > > > > > I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And> > > > > > > > > newest bios F13A. > > > > > > > > > > > > > > > > > > I was googling for a week and only solution i found was to upgrade Alsa> > > > > > > > > and Nvidia to the newest version. I did, but i still do not have sound> > > > > > > > > over HDMI. In Win$ it is working ok.> > > > > > > > > > > > > > > > > > http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863> > > > > > > > > > > > > > > > Try the very latest alsa-driver snapshot below:> > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz> > > > > > > > > > > > > > > > > > > > > > > > Takashi> > > > > > > > > > > > > > I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot.> > > > > > > Still sound does not work over hdmi.> > > > > > > > > > > > Well, then the last suspect is BIOS.> > > > > > > > > > BTW, the very latest alsa-driver snapshot includes a new feature to> > > > > force the codec probing. Grab the latest one and try probe_mask=0x1ff> > > > > option. You'll have to see some new messages> > > > > hda_intel: codec_mask forced to 0xff> > > > > > > > > > Takashi> > > > > _______________________________________________> > > > > Alsa-devel mailing list> > > > > Alsa-devel@xxxxxxxxxxxxxxxx> > > > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel> > > > > > > > Can You please tell me what exactly should I do?> > > > > > Well, just like what I wrote in the above: grab the latest alsa-driver> > > snapshot tarball, build it, install it, and add probe_mask=0x1ff> > > module option to snd-hda-intel, then load it. If you've done it> > > properly, you see the message like above. And let's see whether the> > > driver can detect more codecs.> > > > > > > > > Takashi> > > _______________________________________________> > > Alsa-devel mailing list> > > Alsa-devel@xxxxxxxxxxxxxxxx> > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel> > > > I did ehat You wrote. Here is my dmesg:> > [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low)> > -> IRQ 2> > 2> > [ 14.729028] hda_intel: codec_mask forced to 0xff> > [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64> > [ 15.776021]> > ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k> > ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout,> > switching to> > polling mode: last cmd=0x100f0000> > [ 16.780019]> > ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k> > ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error;> > disabling it...> > [ 17.816508]> > ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k> > ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error;> > disabling it...> > [ 17.921600] input: HDA Digital PCBeep> > as /devices/pci0000:00/0000:00:1b.0/inp> > ut/input11> > [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front> > Jack as /d> > evices/pci0000:00/0000:00:1b.0/input/input12> > [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN> > Jack as > > /devices/pci0000:00/0000:00:1b.0/input/input13> > [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front> > Jack as> > /devices/pci0000:00/0000:00:1b.0/input/input14> > > > What next should I do?> > > > I have basic questions:> > Alsa to work good with my HDMI sound have to know what hardware is> > onboard and what it can do- features (f.ex.HDMI). What is responsible> > for recognition of hardware? Is that alsa-driver package? How can I> > force good recognition?> > > > aplay -l list devices it can use. Now for me it is:> > artek@hplaptop:~$ aplay -l> > **** Lista PLAYBACK urządzeń ****> > karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx> > Analog]> > Urządzenia podrzędne: 1/1> > Urządzenie podrzędne #0: subdevice #0> > karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx> > Digital]> > Urządzenia podrzędne: 1/1> > Urządzenie podrzędne #0: subdevice #0> > > > Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get> > 3rd device with aplay -l. Am I right about it?> > It's true for dedicated HDMI codec chip. But, right now it's mixed> for the HDMI routing from the analog codec chip. This should be fixed> in future.> > > What is that device: STAC92xx Digital?> > It's either an SPDIF or an HDMI output.> > Turn on "IEC958 Playback Switch", and just try to play something from> the default device. ... and post the alsa-info output, too. Takashi_______________________________________________Alsa-devel mailing listAlsa-devel@xxxxxxxxxxxxxxxxxxxx://mailman.alsa-project.org/mailman/listinfo/alsa-devel
