From alsa-user-owner@alsa.jcu.cz  Sun Nov 22 16:24:44 1998
Received: from nurock.kek.jp (root@nurock.kek.jp [130.87.218.140])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id QAA30929
	for <alsa-user@jcu.cz>; Sun, 22 Nov 1998 16:23:13 +0100
Received: from nurock.kek.jp (really [127.0.0.1]) by nurock.kek.jp
	via in.smtpd with esmtp (ident sharkey using rfc1413)
	id <m0zhbGI-000TJYC@nurock.kek.jp> (Debian Smail3.2.0.101)
	for <alsa-user@jcu.cz>; Mon, 23 Nov 1998 00:17:18 +0900 (JST) 
Message-Id: <m0zhbGI-000TJYC@nurock.kek.jp>
To: alsa-user@jcu.cz
cc: rsankara@sparc2000.utsi.edu, ahermans@vf.telia.no
From: sharkey@ale.physics.sunysb.edu
Subject: Re: Audio PCI 1371.. installation help needed 
In-reply-to: Your message of "Sun, 22 Nov 1998 15:38:35 +0100."
             <Pine.LNX.4.00.9811221536490.16747-100000@pluto.andeby> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 23 Nov 1998 00:17:17 +0900
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

> An other thing that could be happening is that the sources in
> /usr/src/linux is wrong. When you compile ALSA you'll have to have the
> source of the kernel you are running in /usr/src/linux. If it's a
> different you can get these unresolved symbols stuff..

In general that's true, but I don't think that's the case this time.  If there
was a kernel mismatch, the symbols which weren't resolved should be kernel
symbols, AFAIK.

I had this problem a while back.  (See the alsa-user list around the end of
May, 1998)  The errors I was getting were:

/lib/modules/2.0.33/misc/snd.o: unresolved symbol mem_map_R48cdefaf
/lib/modules/2.0.33/misc/snd.o: unresolved symbol iput_R52d90afb
/lib/modules/2.0.33/misc/snd.o: unresolved symbol proc_unregister_R3fbb95d5
/lib/modules/2.0.33/misc/snd.o: unresolved symbol proc_root_R6ec32c17
/lib/modules/2.0.33/misc/snd.o: unresolved symbol register_chrdev_R5ed8cb3a
/lib/modules/2.0.33/misc/snd.o: unresolved symbol __iget_R3fdb7b83
/lib/modules/2.0.33/misc/snd.o: unresolved symbol proc_register_dynamic_Rcc643d

and stuff like that.

But in this case, the symbols which aren't being resolved (such as
snd_rawmidi_register, etc.) are all internal to ALSA, so it's not likely to be
a kernel problem.

Eric


