Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] latest update makes alsa screwy!

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Robin Cook <rcook AT wyrms.net>
  • To: Lyon Lemmens <redlemon AT knoware.nl>
  • Cc: eric AT sandall.us, sm-discuss AT lists.ibiblio.org, SourceMage Grimoire <sm-grimoire AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] latest update makes alsa screwy!
  • Date: Wed, 11 Sep 2002 07:39:25 -0500

The alsa-driver spell is missing the provides file that the alsa-driver-virmidi has and the rc3 also fails to build for me with a parse error.

The missing provide is what is causing the alsa-lib to dispel alsa-driver and try casting alsa-driver-virmidi.

Lyon Lemmens wrote:
On Monday 09 September 2002 06:43, Eric Sandall wrote:

Jeremy Kolb said:

ok, just sorcery updated and now when i cast alsa-driver i get a whole
bunch of undefined symbols in my
/lib/modules/2.4.19-preempt-3/kernel/sound/*.o files. then i go to cast
alsa-lib and it decides to uninstall alsa-driver and install
alsa-driver-virmidi instead (which is at rc2 where as the rest of the
alsa spells are rc3). then it finally gets to compiling alsa-lib and
then dies because halfway through the /usr/src/alsa-lib-0.9-rc3
(something like that) directory mysteriously disappears. just posted to
bugzilla bug 919.

Jeremy

P.S. and what is the difference between alsa-driver and
alsa-driver-virmidi? that should be clearly defined in the DETAILS
section, but i see no difference between the two. is this "better" then
the plane old alsa-driver?

Are your linux modules installed into /lib/modules/2.4.19-preempt-3/, or
does the alsa-driver spell create that? If so, then I believe the
problem is that the alsa-driver spell is misreading the kernel version of
where to put it (it's set to go to /lib/modules/`installed_version
linux-new`/).

And I have no idea what the difference is, though I've been asked a few
times already. :)

-One of Four
a.k.a. sandalle


I have got the same problem with the plain-vanilla linux kernel. After alsa updated I get the undefined symbols.

The problem, IMHO, is that alsa keeps pace with the kernel releases. So eg. after 2.4.19-rc3, you also get a alsa-rc3.

Now, we don't do kernel rc's (I hope), so we probably shold hold off on alsa updates until the next kernel release. I would suggest you revert to the previous alsa version.






Archive powered by MHonArc 2.6.24.

Top of Page