From: WILMES Andreas <administrator@webspace.ms>
To: Daniel Herrmann <daniel.herrmann1@gmx.de>
Cc: Alsa-devel@alsa-project.org
Subject: Re: [Alsa-user] Problems with Soundblaster X-Fi
Date: Mon, 15 Jun 2009 11:16:52 +0200 [thread overview]
Message-ID: <4A361184.4080909@webspace.ms> (raw)
In-Reply-To: <4A36112E.3080901@gmx.de>
Daniel Herrmann wrote:
> WILMES Andreas schrieb:
>> Daniel Herrmann wrote:
>>> WILMES Andreas schrieb:
>>>> Daniel Herrmann wrote:
>>>>
>>>>> Hey all,
>>>>>
>>>>> i tried out the new devel-snapshot including alsa-support for my
>>>>> Soundblaster x-Fi card.
>>>>>
>>>>> Installed it via ./configure; make; make install and rebooted.
>>>>>
>>>>> The driver didnt load at all.
>>>>>
>>>>> Trying to load the driver manually brings up the following message:
>>>>>
>>>>>
>>>>>> modprobe snd-ctxfi
>>>>>>
>>>>> FATAL: Error inserting snd_ctxfi
>>>>> (/lib/modules/2.6.28-11-generic/kernel/sound/pci/ctxfi/snd-ctxfi.ko):
>>>>> Unknown symbol in module, or unknown parameter
>>>>>
>>>>>
>>>>>> dmesg shows the following:
>>>>>>
>>>>> [ 2146.563073] snd_ctxfi: disagrees about version of symbol
>>>>> snd_ctl_add
>>>>> [ 2146.563081] snd_ctxfi: Unknown symbol snd_ctl_add
>>>>> [ 2146.563291] snd_ctxfi: disagrees about version of symbol
>>>>> snd_pcm_new
>>>>> [ 2146.563295] snd_ctxfi: Unknown symbol snd_pcm_new
>>>>> [ 2146.563482] snd_ctxfi: disagrees about version of symbol
>>>>> snd_card_register
>>>>>
>>>>> [...] and so on, about 60 lines
>>>>>
>>>>> [ 3198.031060] snd_ctxfi: disagrees about version of symbol
>>>>> snd_pcm_period_elapsed
>>>>> [ 3198.031063] snd_ctxfi: Unknown symbol snd_pcm_period_elapsed
>>>>>
>>>>>
>>>>>> lspci | grep -i audio
>>>>>>
>>>>> 00:0a.0 Multimedia audio controller: Creative Labs SB X-Fi
>>>>>
>>>>> Currently using Ubuntu 9.04 Jaunty with the current
>>>>> 2.6.28-11-generic kernel
>>>>>
>>>>> Maybe anyone has an idea, why i cant install the driver?
>>>>> It worked for me before, but unfortunatly i had to reinstall
>>>>> ubuntu after getting a weird dependeny problem in apt.
>>>>> Not shure why it doesn't do so now...
>>>>>
>>>>> Thanks in advance for your help and thanks for the great work you do!
>>>>>
>>>>>
>>>> I had the same error. Then I rebooted and the error disappeared.
>>>> Hope that will help.
>>>>
>>> Hm, i rebooted more than once - same error.
>>>
>>> Daniel
>>>
>> I deleted /usr/include/asm and I symlinked it to
>> /usr/src/linux-headers-2.6.28-11/include/asm-generic and I did a
>> recompile. After rebooting then the error disappeared.
>>
> HM... You deleted it and made a symlink from it? How does this work?
> How can i link something deleted?!
>
> Can't follow you ;)
Oh I'm Sorry.
/usr/include/asm was a static folder containing a lot of files before. I
linked /usr/src/linux-headers-2.6.28-11/include/asm-generic to
/usr/include/asm then.
next prev parent reply other threads:[~2009-06-15 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A35683E.70900@gmx.de>
[not found] ` <4A3575BE.7090206@webspace.ms>
[not found] ` <4A360322.7060703@gmx.de>
2009-06-15 9:08 ` [Alsa-user] Problems with Soundblaster X-Fi WILMES Andreas
[not found] ` <4A36112E.3080901@gmx.de>
2009-06-15 9:16 ` WILMES Andreas [this message]
2009-06-15 9:45 WILMES Andreas
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=4A361184.4080909@webspace.ms \
--to=administrator@webspace.ms \
--cc=Alsa-devel@alsa-project.org \
--cc=daniel.herrmann1@gmx.de \
/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