At Wed, 27 Oct 2010 12:57:35 +0530,
Jaswinder Singh wrote:
quoted text
> 
> On Wed, Oct 27, 2010 at 11:18 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Wed, 27 Oct 2010 10:05:06 +0530,
> > Jaswinder Singh wrote:
> >>
> >
> > OK, and does it work with other kernel versions or other OS?
> >
> 
> Yes, I also tried with older kernel version but no success.
> 
> Only Linux OS is installed on this machine.
> 
> >>
> >> If more information is needed or need to run some tests, please let me know.
> >
> > Try probing as a module.  It makes easier to debug.
> 
> I loaded it as module with debugging :
> 
> $ lsmod
> Module                  Size  Used by
> snd_hda_codec_hdmi     23156  1
> snd_hda_intel          24921  0
> snd_hda_codec          83458  2 snd_hda_codec_hdmi,snd_hda_intel
> snd_hwdep               5916  1 snd_hda_codec
> 
> [    7.854510] IOAPIC[0]: Set routing entry (8-22 -> 0xa9 -> IRQ 22
> Mode:1 Active:1)
> [    7.854515] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
> low) -> IRQ 22
> [    7.854569] HDA Intel 0000:00:1b.0: irq 47 for MSI/MSI-X
> [    7.854589] HDA Intel 0000:00:1b.0: setting latency timer to 64
> [    7.854593] ALSA sound/pci/hda/hda_intel.c:2529: chipset global
> capabilities = 0x4401
> [    7.859681] ALSA sound/pci/hda/hda_intel.c:913: codec_mask = 0x0
> [    7.859687] ALSA sound/pci/hda/hda_intel.c:2624: no codecs found!

So, the hardware (BIOS) tells no codec is connected to this bus.

As a last resort, you can try to load with probe_mask=0x10f.  This
will probe the codec chips forcibly no matter whether it's present or
not.


Takashi
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/