All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Steffen" <c-steffen@web.de>
To: alsa-devel@alsa-project.org
Subject: Re: Problems with newest alsa driver on 2.6.30 kernel -	unknown symbols
Date: Sun, 18 Oct 2009 17:47:23 +0200	[thread overview]
Message-ID: <000b01ca500a$48ff0cd0$dafd2670$@de> (raw)
In-Reply-To: <000601ca5001$8f554540$adffcfc0$@de>

Tried it with the older version 1.0.20, which still gives me one error:

[  190.555043] snd_hda_codec: Unknown symbol snd_hwdep_new

Is there anything to change in the kernel config or whatever?

-----Ursprüngliche Nachricht-----
Von: alsa-devel-bounces@alsa-project.org
[mailto:alsa-devel-bounces@alsa-project.org] Im Auftrag von Christian
Steffen
Gesendet: Sonntag, 18. Oktober 2009 16:45
An: alsa-devel@alsa-project.org
Betreff: [alsa-devel] Problems with newest alsa driver on 2.6.30 kernel -
unknown symbols

Hi there,

while an older version of alsa drivers is working fine with my kernel
2.6.30, the newly compiled modules can't be inserted properly.
I compiled snd-had-intel modules for my kernel 2.6.30 and tried to
insert/start them.

dmesg returns me:

[  106.209451] snd_hda_codec: Unknown symbol __snd_printk
[  106.210340] snd_hda_codec: Unknown symbol snd_hwdep_new
[  106.212211] snd_hda_codec: disagrees about version of symbol
snd_pcm_hw_constraint_step
[  106.212217] snd_hda_codec: Unknown symbol snd_pcm_hw_constraint_step


Any idea?

Thanks,
Christian




_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2009-10-18 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 14:44 Problems with newest alsa driver on 2.6.30 kernel - unknown symbols Christian Steffen
2009-10-18 15:41 ` Adolf Winterer
2009-10-18 15:47 ` Christian Steffen [this message]
2009-10-19  6:14   ` Clemens Ladisch

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='000b01ca500a$48ff0cd0$dafd2670$@de' \
    --to=c-steffen@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.