From: Ulf Carlsson <ulfc@bun.falkenberg.se>
To: Matthias Kleinschmidt <mkleinschmidt@gmx.de>
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>
Subject: Re: HAL2 driver 0.2
Date: Wed, 7 Apr 1999 20:27:31 +0200 [thread overview]
Message-ID: <19990407202731.A1042@bun.falkenberg.se> (raw)
In-Reply-To: <19990407134133.A925@fmc-container.mach.uni-karlsruhe.de>; from Matthias Kleinschmidt on Wed, Apr 07, 1999 at 01:41:33PM -0400
> I had version information activated in the first place. Now I compiled the
> kernel without it and installed alsa...-pre5-2... but I still have unresolved
> modules.
>
> insmod snd.o now gives me
>
> snd.o: unresolved symbol register_sound_dsp_Rb255d4ae snd.o: unresolved symbol
> register_sound_special_Rdf061e7e
This is a bit strange. I don't have those symbols either. I have the normal
register_sound_dsp and register_sound_special symbols. I'm looking at this
problem and how I'll solve it completely. It's a bit tricky to build modules
which are compatible.
It looks like the rest of the symbols in the kernel are resolved. Maybe you
forgot to rebuild the modules or to install them when you built them?
Anyhow, in the meanwhile you may build your own driver package. There shouldn't
be any problem if you have a kernel installed in /usr/src/linux, just get the
source package of the drivers instead an execute:
rpm --rebuild alsa-driver-0.3.0-pre5-2.src.rpm
(Please have a bit patiance, you're the first tester)
- Ulf
next prev parent reply other threads:[~1999-04-07 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-07 2:16 HAL2 driver 0.2 Ulf Carlsson
1999-04-07 1:52 ` Matthias Kleinschmidt
1999-04-07 2:15 ` Ariel Faigon
1999-04-07 2:15 ` Ariel Faigon
1999-04-07 5:59 ` Matthias Kleinschmidt
1999-04-07 16:22 ` Ulf Carlsson
1999-04-07 17:41 ` Matthias Kleinschmidt
1999-04-07 18:27 ` Ulf Carlsson [this message]
1999-04-07 21:15 ` Matthias Kleinschmidt
1999-04-08 4:14 ` Ulf Carlsson
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=19990407202731.A1042@bun.falkenberg.se \
--to=ulfc@bun.falkenberg.se \
--cc=linux@cthulhu.engr.sgi.com \
--cc=mkleinschmidt@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.