* Re: [Alsa-user] em28xx_alsa: disagrees about version of symbol xxx after upgrading CentOS 5.2 ALSA .14 for ALSA .17
[not found] ` <48E524B8.80002@messagenetsystems.com>
@ 2008-10-03 14:08 ` Robert Vincent Krakora
0 siblings, 0 replies; only message in thread
From: Robert Vincent Krakora @ 2008-10-03 14:08 UTC (permalink / raw)
To: alsa-devel; +Cc: geisj
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-10-03 14:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <48E3DE07.4000707@messagenetsystems.com>
[not found] ` <48E4D486.9080801@googlemail.com>
[not found] ` <48E524B8.80002@messagenetsystems.com>
2008-10-03 14:08 ` [Alsa-user] em28xx_alsa: disagrees about version of symbol xxx after upgrading CentOS 5.2 ALSA .14 for ALSA .17 Robert Vincent Krakora
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox