On Fri, Apr 16, 2004 at 10:13:08AM -0700, Matthew Richardson wrote:
> Hello,
>
> I installed with a minimal iso (woody_xfs_netinst.iso) from
> http://www.physik.tu-cottbus.de/~george/debian-xfs/. I then tried to isntall the
> 2.4.21-2 kernel image from the same site. The install went fine, but w
Matthew Richardson wrote:
> I installed with a minimal iso (woody_xfs_netinst.iso) from
> http://www.physik.tu-cottbus.de/~george/debian-xfs/. I then tried to
> isntall the 2.4.21-2 kernel image from the same site. The install went
> fine, but when trying to install the new kernel image I received
On Thu, Jun 05, 2003 at 04:59:04PM +0200, Sven Luther wrote:
> On Thu, Jun 05, 2003 at 10:43:22AM -0300, Theo Cabrerizo Diem wrote:
>
> > I'm using unstable (gcc 3.3) and won't build. I've installed gcc-3.2
> > package, changed HOSTCC and CC variables in kernel Makefile to
> > gcc-3.2 and worked f
On Thu, Jun 05, 2003 at 10:43:22AM -0300, Theo Cabrerizo Diem wrote:
> Hi,
>
> I'm using unstable (gcc 3.3) and won't build. I've installed gcc-3.2
> package, changed HOSTCC and CC variables in kernel Makefile to gcc-3.2
> and worked fine !...
>
> Maybe this isn't the best solution available, but
On Thu, 13 Mar 2003, Egor Tur wrote:
> Hi folk.
> I compile alsa module and try install it.
> When I do
> dpkg -i alsa-modules-2.4.20_0.9.0rc7-2_i386.deb
> I have:
> Configuration file for ALSA 0.9 exists.
> Attempting to start.
>
> depmod: *** Unresolved symbols in /lib/modules/2.4.20/alsa/snd-e
. What happens
when you are trying to insmod some module which is not loaded?
BTW: What are the EDA tools?
> - Original Message -
> From: "Shaul Karl" <[EMAIL PROTECTED]>
> To: "Jim Sytniak" <[EMAIL PROTECTED]>
> Cc:
> Sent: Thursday, May 30
to do that?
Thanks.
Jim
- Original Message -
From: "Shaul Karl" <[EMAIL PROTECTED]>
To: "Jim Sytniak" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, May 30, 2002 5:10 AM
Subject: Re: Unresolved symbols in binfmt_aout.o
> As a last resort you migh
As a last resort you might compile it in (as opposed to being a module).
--- Begin Message ---
I just loaded the minimal debian image for the
second time and continue to see the error...
depmod: ** Unresolved symbols in
/lib/modules/2.2.19/fs/binfmt_aout.o
if I add -e to depmod it tells me
On Tue, May 28, 2002 at 11:11:46PM -0500, [EMAIL PROTECTED] wrote:
> Quoting Colin Watson <[EMAIL PROTECTED]>:
> > You're going to have to contact the supplier for a module built against
> > a more recent kernel then ... CONFIG_MODVERSIONS can paper over some
> > problems, but not all of them.
>
>
Quoting Colin Watson <[EMAIL PROTECTED]>:
> On Tue, May 28, 2002 at 03:29:02PM -0500, [EMAIL PROTECTED] wrote:
> > I am running Woody with my own 2.4.18 kernel based on the 2.4.18-5 deb
> > package. I have a supplier that has delivered a kernel module for a
> special
> > software modem that was
On Tue, May 28, 2002 at 03:29:02PM -0500, [EMAIL PROTECTED] wrote:
> I am running Woody with my own 2.4.18 kernel based on the 2.4.18-5 deb
> package. I have a supplier that has delivered a kernel module for a special
> software modem that was developed using RH 7.2 with the default 2.4.7 kernel
On Tue, Mar 19, 2002 at 05:17:43PM -0500, Michael Marziani wrote:
> Brand new 2.2r5 install. I get this error several times on bootup, and
> if I do a depmod -e, I get:
>
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/fs/binfmt_aout.o
> depmod: do_truncate
Ignore it. I doubt you
> I know this may be a stupid question, but I'm trying
> to install a netgear ma401 802.11b card on my laptop.
> But after following the install it says that the
> drivers have unresolved symbols. What are unresolved
> symbols?
>
> lab
>
Not sure what the unresolved symbols are. However if you
On Sun, May 20, 2001 at 12:43:29AM -0300, Marcelo Chiapparini wrote:
>
> I had a problem like this some days ago whith 2.2.19. In your example the
> pci2220i.o is a module. It depends on other modules which either have been
> compiled into directly into the kernel or they were not included (dire
On Sat, May 19, 2001 at 10:43:48PM -0400, Michael P. Soulier wrote:
> So I installed the kernel image package for 2.4.4 686, and now when depmod
> -a runs, I get this:
>
> tigger:/etc# depmod -a
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.4-686/kernel/drivers/scsi/pci2220i.o
>
>
On Fri, 06 Apr 2001, William Staniewicz wrote:
> localhostnl:/home/wstan# lsmod
> Module Size Used by
> bsd_comp3672 0 (autoclean)
> lockd 41720 0 (autoclean) (unused)
> sunrpc 55452 0 (autoclean) [lockd]
> serial
localhostnl:/home/wstan# lsmod
Module Size Used by
bsd_comp3672 0 (autoclean)
lockd 41720 0 (autoclean) (unused)
sunrpc 55452 0 (autoclean) [lockd]
serial 19640 1 (autoclean)
opl3 10972
on Thu, Apr 05, 2001 at 11:48:12PM +, William Staniewicz ([EMAIL
PROTECTED]) wrote:
> Here is what I get when I do:
>
> localhostnl:/home/wstan# insmod opl3sa2
> Using /lib/modules/2.2.18pre21/misc/opl3sa2.o
> /lib/modules/2.2.18pre21/misc/opl3sa2.o: unresolved symbol
> unload_mpu401_R5febf2
Go where your modules are (you will see where they are from your error
messages) and remove them from there
You have probably compilled another kernel before and they are left there
Ross
> Hi,
>
> I am trying to install the tulip.o modules for my network cards. If I try
> depmod -a now I get a error which returns Unresolved symbols
> /lib/modules/2.2.18pre21/net/tulip.o
> Any ideas as to what I screwed up now? I just installed debian this week.
>
That might be a dumb questio
Johnny Blade wrote:
>
> I've been attempting to prepare my machine to play
> some quake, but I can't get the 3dfx.o module to work.
> I downloaded the device3dfx source using apt-get, ran
> the buildpkg script, and then installed the .deb
> created. As the deb is trying to update-modules, I
> se
Hi all,
It turns out I just needed to sleep and reboot the machine with new kernel.
All went well. Overly paranoid.
/Duncan
On Sun, Feb 11, 2001 at 06:02:25PM -0500, Duncan Watson wrote:
> Hi all,
>
> I am a newcomer to debian, but I am already a big fan. Apt-get is great
> and this list is a
I had the same problem. It was solved by updating modutils from testing.
-Original Message-
From: Daniel Marquez-Klaka [mailto:[EMAIL PROTECTED]
Sent: Monday, January 29, 2001 2:46 PM
To: debian-users Mail-List
Subject: unresolved symbols
Hello list,
i have running stabel. I installed k
To quote "Hall Stevenson" <[EMAIL PROTECTED]>,
# Do a "mv /lib/modules/2.2.17 /lib/modules/2.2.17-backup" and then
re-run
# "make modules_install".
Another option is to edit the kernel toplevel Makefile. It's probably
/usr/src/linux/Makefile .
Four lines down, there an EXTRAVERSION variable that
Thanks, that solved the problem.
Daniel
On Mon, 29 Jan 2001, Hall Stevenson wrote:
>> i have running stabel. I installed kernel-headers-2.2.17,
>> kernel-source-2.2.17 and kernel-package. Then i
>
>(Off-topic -- kernel-package isn't needed since you're compiling kernels
>the "old" way or the
> i have running stabel. I installed kernel-headers-2.2.17,
> kernel-source-2.2.17 and kernel-package. Then i
(Off-topic -- kernel-package isn't needed since you're compiling kernels
the "old" way or the "non-debian" way)
> made my own kernel ( make dep clean bzImage;
> make modules; make modules
Philipp Lehman <[EMAIL PROTECTED]> writes:
> I just upgraded a machine from unstable potato to stable potato
> and among other things, I recompiled the PCMCIA modules provided
> by pcmcia-source.
>
> Now I get unresolved symbols in epic_cb.o when doing a 'depmod
> -a'. This is merely a cosmetic i
Philipp Lehman <[EMAIL PROTECTED]> wrote:
>On Thu, 19 Oct 2000, Pascal Hos <[EMAIL PROTECTED]> wrote:
>
>>On Fri, Oct 20, 2000 at 12:35:32AM +0200, Philipp Lehman wrote:
>>> Now I get unresolved symbols in epic_cb.o when doing a 'depmod
>>> -a'. This is merely a cosmetic issue since I don't use t
On Thu, 19 Oct 2000, Pascal Hos <[EMAIL PROTECTED]> wrote:
>On Fri, Oct 20, 2000 at 12:35:32AM +0200, Philipp Lehman wrote:
>> Now I get unresolved symbols in epic_cb.o when doing a 'depmod
>> -a'. This is merely a cosmetic issue since I don't use this
>> particular module, but I was wondering how
On Fri, Oct 20, 2000 at 12:35:32AM +0200, Philipp Lehman wrote:
> I just upgraded a machine from unstable potato to stable potato
> and among other things, I recompiled the PCMCIA modules provided
> by pcmcia-source.
>
> Now I get unresolved symbols in epic_cb.o when doing a 'depmod
> -a'. This is
Here are my dmesg and my unresolved symbols out put attached. Hope someone can
help.
Alexandre Pereira da Silva wrote:
> The easyest way is recompile it in 2.2.14 if you have the source code or ask
> to module writer to that work. From you the only thing to be done is to
> check if your kernel h
I answer this myself because I solved the problem. It looks like when I
did dselect with apt after installing the base system the pcmcia-package
was updated (this is annoying for pcmcia because this probably means
that this can happen again!) and these new modules did not work with my
old kernel. E
On Tue, Mar 21, 2000 at 12:34:53PM -0500, Jonathan Markevich wrote:
> > Not sure if you know this but you can't compile 2.0.x modules with
> > 2.2.x kernel. Just get the 2.2.x version of *everything* and you
> > should be right.
>
> It's more specifically gcc you need. I used gcc272 and all was
>
On Mon, Mar 20, 2000 at 04:29:21PM +, David Wright wrote:
Out of everyone that got and read my message, you're the *only* one that
took offense. Well, that responded anyways. It seems most realized what I
said was extreme frustration and not a personal attack. Please accept my
messages in t
On Mon, Mar 20, 2000 at 02:12:33PM +0100, Antonio Fiol Bonnín wrote:
> I don't know nearly anything about this, but... did you activate module
> support in your kernel? It sounds like there has to be such a silly little
> thing that breaks it all.
No kidding, that's what I'm hoping for. And yes,
On Sun, Mar 19, 2000 at 09:25:58AM -0500, Jonathan Markevich wrote:
> Well I have to use 2.0.36. 2.2 doesn't work for me, remember? And I use
> stock kernels because it avoids another level of confusion and
Huh? you should have no trouble with 2.2.
Not sure if you know this but you can't compil
> So I have tried to replace it... reinstalling, trying other kernel versions
> (including this new-fangled kernel 2.2.x thing which is apparently the
> greatest thing since sliced bread, but won't run on a computer with THREE
> SERIAL PORTS!!! Ever heard of a machine so unusual? I mean a shared
I don't know nearly anything about this, but... did you activate module
support in your kernel? It sounds like there has to be such a silly little
thing that breaks it all.
If you compile the kernel properly (at least it happened ok to me when I
had 2.0.36), i.e. (make dep; make clean; make zImage
> Don't upgrade unless you have to. I always have to remind myself of that
> - if my machine is working and I can do the tasks I need to do, even
> though there is a new fangled a super-cool version of my software, I don't
> have to install it. I still need to remind myself.
It's not just super-
Don't upgrade unless you have to. I always have to remind myself of that - if
my machine is working and I can do the tasks I need to do, even though there is
a new fangled a super-cool version of my software, I don't have to install it.
I still need to remind myself.
That said, I just instal
On Thu, 12 Nov 1998, Curt Daugaard wrote:
> I've seen posts to this list about this problem before, but I
> can't recall the solution. I'm trying to revive an ip
> masquerading setup I had in the past, but when I try to start it
> up a get a long list of unresolved symbols on the net modules.
> T
So I'll answer my own post:
Though all other modules worked, and I had only one version of
modules installed, somehow the ipmasq pieces were not recognized.
A reinstall of the kernel-image using the kernel-package utility
solved it.
On Thu, Nov 12, 1998 at 08:54:50PM -0600, Curt Daugaard wrote:
>
Hi Curt,
On Thu, Nov 12, 1998 at 08:54:50PM -0600, Curt Daugaard wrote:
> I've seen posts to this list about this problem before, but I
> can't recall the solution. I'm trying to revive an ip
> masquerading setup I had in the past, but when I try to start it
> up a get a long list of unresolved s
On Sat, Apr 25, 1998 at 12:01:42AM -0400, [EMAIL PROTECTED] wrote:
> I am attempting to install Debian 1.3 by CD-ROM using
> a Philips/LMS CM-206 CD-ROM drive. The drive is
> proprietary, thus requiring the use of the device
> driver disk. The following error message appears
> when attempting to
> Hello,
>
> I am attempting to install Debian 1.3 by CD-ROM using
> a Philips/LMS CM-206 CD-ROM drive. The drive is
> proprietary, thus requiring the use of the device
> driver disk. The following error message appears
> when attempting to load the appropriate module:
>
> /lib/modules/2.0.29/c
45 matches
Mail list logo
