. 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
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 that
"do_truncate" is the offending party.
I've searched the achive and have found that oth
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
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
I have no idea what this error means, or what it will end up affecting.
The only additional module
6 matches
Mail list logo
