linux-mips
[Top] [All Lists]

Re: HAL2 driver 0.2

To: Matthias Kleinschmidt <mkleinschmidt@gmx.de>
Subject: Re: HAL2 driver 0.2
From: Ulf Carlsson <ulfc@bun.falkenberg.se>
Date: Wed, 7 Apr 1999 20:27:31 +0200
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>
In-reply-to: <19990407134133.A925@fmc-container.mach.uni-karlsruhe.de>; from Matthias Kleinschmidt on Wed, Apr 07, 1999 at 01:41:33PM -0400
Mail-followup-to: Matthias Kleinschmidt <mkleinschmidt@gmx.de>, Linux SGI <linux@cthulhu.engr.sgi.com>
References: <19990406221641.A6206@bun.falkenberg.se> <19990407015956.A2584@fmc-container.mach.uni-karlsruhe.de> <19990407122257.D19733@bun.falkenberg.se> <19990407134133.A925@fmc-container.mach.uni-karlsruhe.de>
Sender: owner-linux@cthulhu.engr.sgi.com
> 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

<Prev in Thread] Current Thread [Next in Thread>