From: Robert Vincent Krakora <rob.krakora@messagenetsystems.com>
To: alsa-devel@alsa-project.org
Cc: geisj@messagenetsystems.com
Subject: Re: [Alsa-user] em28xx_alsa: disagrees about version of symbol xxx after upgrading CentOS 5.2 ALSA .14 for ALSA .17
Date: Fri, 03 Oct 2008 10:08:59 -0400 [thread overview]
Message-ID: <48E6277B.5050307@messagenetsystems.com> (raw)
In-Reply-To: <48E524B8.80002@messagenetsystems.com>
All:
I have searched on the web and it seems that at least one person has
overcome the problem I am having by rebuilding soundcore.ko (See here:
http://redmonk.com/sogrady/2008/04/29/sog-1-busted-sound-0-getting-audio-working-on-the-x300-under-ubuntu/).
There is a sound_core.c in the ALSA tar ball. Why doesn't ALSA rebuild
the soundcore.ko module? The functions that em28xx_alsa is complaining
about reside in soundcore.ko according to my research. Basically, I
downloaded .18rc3 driver, lib and util and configured, built and
installed. I rebooted and em28xx_alsa complained that symbols that
resided down in soundcore.ko did not jive with the versions of the same
symbols for which it was trying to resolve linkages. I rebuilt the
video4linux code, reinstalled and rebooted and the problem was still
present. It looks as though one should be able to build an new
soundcore.ko with a ALSA package but there are no instructions on how to
do so. Please help!!!
Best Regards,
--
Rob Krakora
Software Engineer
MessageNet Systems
101 East Carmel Dr. Suite 105
Carmel, IN 46032
(317)566-1677 Ext. 206
(317)663-0808 Fax
prev parent reply other threads:[~2008-10-03 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48E3DE07.4000707@messagenetsystems.com>
[not found] ` <mj5dr5-abk.ln1@CPE-124-182-251-164.sa.bigpond.net.au>
2008-10-02 12:44 ` [Alsa-user] em28xx_alsa: disagrees about version of symbol xxx after upgrading CentOS 5.2 ALSA .14 for ALSA .17 Robert Vincent Krakora
[not found] ` <48E4D486.9080801@googlemail.com>
[not found] ` <48E524B8.80002@messagenetsystems.com>
2008-10-03 14:08 ` Robert Vincent Krakora [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=48E6277B.5050307@messagenetsystems.com \
--to=rob.krakora@messagenetsystems.com \
--cc=alsa-devel@alsa-project.org \
--cc=geisj@messagenetsystems.com \
/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.