alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Valerio Tesei <valerio.tesei@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig
Date: Thu, 07 Apr 2011 21:44:40 +0200	[thread overview]
Message-ID: <4D9E1428.1080702@gmail.com> (raw)
In-Reply-To: <BANLkTikorXUoaGiJ94i_syzfN-0Oy98tzw@mail.gmail.com>

I checkout the takashi kernel tree, selected hda-intel and alsa as
module and reboot.

After probe i get these debug http://pastebin.com/7hGVe4U3 with (i
think) useful informations about,

Looking for the ioremap that Raymond ask about i found :

[ 1048.230360] nvidia: module license 'NVIDIA' taints kernel.
[ 1048.230363] Disabling lock debugging due to kernel taint
[ 1048.664298] nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 1048.664304] nvidia 0000:01:00.0: setting latency timer to 64
[ 1048.664308] vgaarb: device changed decodes:
PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 1048.664529] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  270.18 
Tue Jan 18 21:46:26 PST 2011
[ 1048.866318] ioremap error for 0xdde70000-0xdde71000, requested 0x10,
got 0x0

So i could say that ioremap is about nvidia, do you?

This is my latest alsa-info
http://www.alsa-project.org/db/?f=184ce71bf28e38656c1a31a607f9c38c396808a3

Dont care about "failed to load firmware bla bla bla" i found wrong
google informations about it :)

Hope to be helpful,

V.

Il 07/04/2011 15:13, Raymond Yau ha scritto:
> 2011/4/7 Valerio tesei <valerio.tesei@gmail.com>
>
>> This evening i will check out the Takashi sound-2.6 git kernel tree and
>> update it every day to give feedback on problems with this card on my
>> motherboard.
>>
>> If i could help in any other way (debug, dmesg or others) let me know :)
>>
>> why alsaconf does not find my card? what i'm wrong?
>>
>> anyway, thanks for all this work.
>>
>>
> You have to find out from system log which hardware cannot ioremap
>
> [ 250.950937] ioremap error for 0xdde70000-0xdde71000, requested 0x10, got
> 0x0
>
> Is it normal to have so many hda_codec_cleanup_stream  ?
>
> [ 369.824424] hda_codec_cleanup_stream: NID=0x9
> [ 369.824857] hda_codec_cleanup_stream: NID=0x9
> [ 369.825335] hda_codec_cleanup_stream: NID=0x9
> [ 369.825764] hda_codec_cleanup_stream: NID=0x9
> [ 369.826232] hda_codec_cleanup_stream: NID=0x9
> [ 369.826634] hda_codec_cleanup_stream: NID=0x9
> [ 369.827095] hda_codec_cleanup_stream: NID=0x9
>
>
> The HDA controller seem support multi stream capture
>
> [ 6.748965] hda-intel: chipset global capabilities = 0x4401
>
> Two stereo ADCs support 16/20/24-bit PCM format, multiple stereo recording
>
> but the driver only create 1 capture stream.but two capture volume/switches
> and input sources
>
> ARECORD
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
>
> Simple mixer control 'Input Source',0
>  Capabilities: cenum
>  Items: 'Rear Mic' 'Front Mic' 'Line'
>  Item0: 'Rear Mic'
> Simple mixer control 'Input Source',1
>  Capabilities: cenum
>  Items: 'Rear Mic' 'Front Mic' 'Line'
>  Item0: 'Rear Mic'
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel


-- 
*Email:* valerio.tesei@gmail.com
*Cellulare:* +39.3394768306
*Gtalk:* valerio.tesei@gmail.com
*LinkedIn:* http://www.linkedin.com/pub/valerio-tesei/22/a87/577

  parent reply	other threads:[~2011-04-07 19:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 14:59 [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig Raymond Yau
2011-04-06  6:19 ` Takashi Iwai
2011-04-06  7:35   ` Raymond Yau
2011-04-06  7:41     ` Takashi Iwai
2011-04-06  8:29       ` Raymond Yau
2011-04-06  9:29         ` Takashi Iwai
2011-04-06 10:49           ` Valerio tesei
2011-04-07  1:53             ` Raymond Yau
2011-04-07 12:59               ` Valerio tesei
2011-04-07 13:13                 ` Raymond Yau
2011-04-07 13:55                   ` Valerio tesei
2011-04-07 19:44                   ` Valerio Tesei [this message]
2011-04-08  0:48                     ` Raymond Yau
2011-04-06 12:59           ` Raymond Yau
2011-04-06 13:07             ` Takashi Iwai
2011-04-06 13:19               ` Takashi Iwai
2011-04-08  2:06           ` Raymond Yau
2011-04-08  8:38             ` Valerio tesei
2011-04-08  9:28               ` OT: applying patches (was: [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig) Paul Menzel
2011-04-08  9:47                 ` Valerio tesei
2011-04-08 10:27                   ` snd-hda-intel and parameter `patch` (was: OT: applying patches) Paul Menzel
2011-04-08 14:44                     ` snd-hda-intel and parameter `patch` David Henningsson
2011-04-10  1:21               ` [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig Raymond Yau
2011-04-11  8:21                 ` Valerio tesei
2011-04-11 19:28                   ` Valerio Tesei
2011-04-13  8:52                     ` Raymond Yau
2011-04-13 11:08                       ` Valerio tesei
2011-04-13 19:12                         ` Valerio Tesei
2011-04-14 11:11                         ` Raymond Yau
2011-04-18 19:53                           ` Valerio Tesei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D9E1428.1080702@gmail.com \
    --to=valerio.tesei@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).