At Tue, 13 Feb 2007 10:44:27 +0900 (JST), Shingo HORISAWA wrote: > > Hi, Takashi. > > > Hm, but if built properly with --with-debug=detect > > option, the driver > > must tells you a model name when you pass model=XXX > > option. Make sure > > that the model option is really passed. You can see > > the actual value > > in /sysfs/modules/snd_hda_intel/parameters/model > > file. > > Sorry, I could find such descriptions on /var/log/messages > > when ALSA was restarted. > > When I didn't specify model, it says: > > kernel: PCI: Enabling device 0000:00:14.2 (0000 -> 0002) > kernel: ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 > (level, low) -> IRQ 201 > kernel: ALSA > /usr/local/src/alsa/alsa-driver-hg20070210/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:696: > codec_mask = 0x1 > kernel: hda_codec: Unknown model for ALC262, trying > auto-probe from BIOS... The question is whether this message _always_ appears regardless what model option you give. If yes, the module parameter isn't passed correctly, i.e. something wrong with your system. > kernel: ALSA > /usr/local/src/alsa/alsa-driver-hg20070210/pci/hda/hda_codec.c:2171: > autoconfig: line_outs=0 (0x0/0x0/0x0/0x0/0x0) > kernel: ALSA > /usr/local/src/alsa/alsa-driver-hg20070210/pci/hda/hda_codec.c:2175: > speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) > kernel: ALSA > /usr/local/src/alsa/alsa-driver-hg20070210/pci/hda/hda_codec.c:2179: > hp_outs=1 (0x15/0x0/0x0/0x0/0x0) > kernel: ALSA > /usr/local/src/alsa/alsa-driver-hg20070210/pci/hda/hda_codec.c:2187: > inputs: mic=0x0, fmic=0x18, line=0x0, fline=0x0, > cd=0x0, aux=0x0 So, you have only "Front Mic" as the capture source. Is your mixer setting correct? Attach the generated file via "alsactl -f somefile store" together with /proc/asound/card0/codec#0 content. > And I could find the following messages > when model is except "hp-bpc" and "hippo" on console. > > /usr/sbin/alsactl: set_control:970: failed to obtain > info for control #3 (No such file or directory) It's harmless as long as you call alsactl with -F option. Otherwise, it's a bug of init or udev script that calls alsactl. Takashi ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel