From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: kreuzritter2000@gmx.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Major Bug in Alsa 0.9 for over 1 year
Date: Sat, 30 Nov 2002 14:36:36 +1100 [thread overview]
Message-ID: <3DE83244.7080907@superbug.demon.co.uk> (raw)
In-Reply-To: <22050.1035518578@www52.gmx.net>
kreuzritter2000@gmx.de wrote:
>Hello,
>
>I allways have the same bug when trying to modprobe the cs4232 or cs4236
>sounddriver for my Terratec EWS654XL soundcard.
>
>The bug is called unresolved symbol, this bug exists in ALSA 0.9 since the
>existing of ALSA 0.9.
>
>I tried nearly every ALSA 0.9x version.
>
>
>
This "bug" is mostly causes by in-correct install of alsa.
In order to install alsa, you must first compile and install your own
kernel.
Once the kernel is installed and running, you can then compile and
install alsa-driver.
Once you have alsa-driver installed, with all the modules, you can then
compile and install alsa-lib.
Also, the kernel must be compiled with the same compiler as the
alsa-driver modules. E.g. You cannot have compiled the kernel with gcc
2.95 and compile alsa-driver with gcc 3.2. Using different compilers
causes all sorts of strange un-predictable problems. I took a few days
once tried to track down a kernel oops, only to find that simply
compiling both kernel and kernel-module with the same compiler fixed the
issue.
That should solve all "unresolved symbols".
Cheers
James
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
prev parent reply other threads:[~2002-11-30 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 4:02 Major Bug in Alsa 0.9 for over 1 year kreuzritter2000
2002-10-25 7:10 ` Jaroslav Kysela
2002-10-25 12:02 ` AW: " Karsten Wiese
2002-10-25 12:58 ` Clemens Ladisch
2002-10-26 10:37 ` karsten wiese
2002-11-30 3:36 ` James Courtier-Dutton [this message]
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=3DE83244.7080907@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=kreuzritter2000@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 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.