[Pkg-alsa-devel] Bug#289870: marked as done (alsa-source: Unresolved symbols in snd.o)
Debian Bug Tracking System
owner@bugs.debian.org
Wed, 19 Jan 2005 06:18:25 -0800
Your message dated Wed, 19 Jan 2005 15:11:48 +0100
with message-id <1106143909.31227.14.camel@thanatos>
and subject line Bug#289870: unresolved symbols
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Jan 2005 14:02:36 +0000
>From miller@yoyo.org Tue Jan 11 06:02:36 2005
Return-path: <miller@yoyo.org>
Received: from outmx023.isp.belgacom.be [195.238.2.204]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CoMbU-0003w3-00; Tue, 11 Jan 2005 06:02:36 -0800
Received: from outmx023.isp.belgacom.be (localhost [127.0.0.1])
by outmx023.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with ESMTP id j0BE2Ud1018158
for <submit@bugs.debian.org>; Tue, 11 Jan 2005 15:02:30 +0100
(envelope-from <miller@yoyo.ORG>)
Received: from wolverine.wsl.COM (178-26.240.81.adsl.skynet.be [81.240.26.178])
by outmx023.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with ESMTP id j0BE2NMR018076;
Tue, 11 Jan 2005 15:02:23 +0100
(envelope-from <miller@yoyo.ORG>)
Received: from root by wolverine.wsl.COM with local (Exim 4.34)
id 1CoMbJ-0003Kv-KO; Tue, 11 Jan 2005 15:02:25 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: J G Miller <miller@yoyo.ORG>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: alsa-source: Unresolved symbols in snd.o
Reply-To: J G Miller <miller@yoyo.ORG>
X-Mailer: reportbug 3.5
Date: Tue, 11 Jan 2005 15:02:25 +0100
Message-Id: <E1CoMbJ-0003Kv-KO@wolverine.wsl.COM>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: alsa-source
Version: 1.0.7-2
Severity: normal
The ALSA driver modules for 1.0.7-2 build satisfactorily with kernel
source kernel-source-2.4.27 2.4.27-7 using
/usr/bin/gcc -> gcc-3.3
but there are unregistered sysmbols in the snd.o file.
depmod: *** Unresolved symbols in /lib/modules/2.4.27/updates/alsa/snd.o
depmod: register_sound_special_Rsmp_4827febd
depmod: unregister_sound_special_Rsmp_99c95fa5
I also have the same problem with the em8300 module from the
em8300-source 0.14.0-2 package.
depmod: *** Unresolved symbols in /lib/modules/2.4.27/kernel/drivers/video/em8300.o
depmod: register_sound_dsp_Rsmp_385b825d
depmod: unregister_sound_dsp_Rsmp_cd083b10
Any assistance in resolving this problem would be greatly appreciated.
Greg Miller
PS In the /usr/share/doc/alsa-source/README.Debian file, I would
suggest that the necessary instruction to enable CONFIG_SOUND as a
module in the kernel configuration should be added.
-- System Information:
Debian Release: sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages alsa-source depends on:
ii bzip2 1.0.2-3 high-quality block-sorting file co
ii debconf 1.4.41 Debian configuration management sy
ii debconf-utils 1.4.41 debconf utilities
ii debhelper 4.2.30 helper programs for debian/rules
ii dpkg-dev 1.10.25 Package building tools for Debian
ii gcc [c-compiler] 4:3.3.5-1 The GNU C compiler
ii gcc-3.3 [c-compiler] 1:3.3.5-6 The GNU C compiler
ii gcc-3.4 [c-compiler] 3.4.3-7 The GNU C compiler
ii make 3.80-9 The GNU version of the "make" util
-- debconf information:
alsa-common/card-list:
* alsa-source/cards_to_be_built: emu10k1 (PCI: EMU10K1 (SB Live! or E-mu APS))
* alsa-source/debug: false
alsa-source/cards:
* alsa-source/has_pnp: false
---------------------------------------
Received: (at 289870-done) by bugs.debian.org; 19 Jan 2005 14:13:57 +0000
>From jdthood@aglu.demon.nl Wed Jan 19 06:13:57 2005
Return-path: <jdthood@aglu.demon.nl>
Received: from mailservice.tudelft.nl [130.161.131.5]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrGar-0005oy-00; Wed, 19 Jan 2005 06:13:57 -0800
Received: from localhost (localhost [127.0.0.1])
by rav.antivirus (Postfix) with ESMTP id 89FFA223123;
Wed, 19 Jan 2005 15:13:25 +0100 (CET)
Received: from localhost (x117.decis.nl [130.161.177.117])
by mx0.tudelft.nl (Postfix) with ESMTP id B5C5C222F86;
Wed, 19 Jan 2005 15:13:23 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
by localhost (Postfix) with ESMTP id DF6B210D5EA;
Wed, 19 Jan 2005 15:11:49 +0100 (CET)
Subject: Re: Bug#289870: unresolved symbols
From: Thomas Hood <jdthood@aglu.demon.nl>
To: 289870-done@bugs.debian.org
Cc: i2c@packages.debian.org
In-Reply-To: <26969.1106142550@jem.yoyo.org>
References: <26969.1106142550@jem.yoyo.org>
Content-Type: text/plain
Date: Wed, 19 Jan 2005 15:11:48 +0100
Message-Id: <1106143909.31227.14.camel@thanatos>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at tudelft.nl
Delivered-To: 289870-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Wed, 2005-01-19 at 14:49 +0100, J G Miller wrote:
> Having done a uname -a above and seeing the date January 4th 2005,
> which compares with a much later date on the .config file for the
> kernel, it is evident that the running kernel is not the latest
> compiled kernel.
As I suspected. ;)
> On doing some more tests, I have discovered that the newly built
> kernel package does not install if
>
> /lib/modules/<kernel_version>/...i2c-core.o
>
> does not exist
Weird!
> , and that if it does exist from a previously installed
> i2c package, then the newly built kernel again does not install unless
> the -force--overwrite option is added to the dpkg command to overwrite
> this file which is in the i2c package.
Looking at i2c's BTS summary page, I see that there have been some grave
bugs in i2c packages' handling of diversions, resulting in file
conflicts. My guess is that this is the reason you are having problems.
I suggest you upgrade to the latest 2.4.27 kernel and latest i2c
package.
I think that i2c's maintainer should reconsider using the diversion
system in order to substitute i2c's modules for kernel-image's; the
diversion system is notoriously easy to mess up. I think that
the /lib/modules/*/kernel/ subdirectory should be reserved for the
kernel-image package. Instead i2c* should put its modules
in /lib/modules/*/updates/i2c/; then the module loader will give them
priority over like-named modules under other subdirectories
of /lib/modules/*/. This is what we did in order to allow people to
install alsa-modules packages on systems with kernel-image-2.6*.
(cc:ing to the maintainer of i2c)
--
Thomas Hood <jdthood@aglu.demon.nl>