🚀 go-pugleaf

Paul Becker wrote:
>
> I have just installed Slackware 4.0 from CD, which worked fine. I
> recompiled the kernel for my setup, which also worked fine. However, the
> command depmod -a (executes at boot up) returns unresolved symbol for
> all my modules in /lib/modules/2.2.6.
>
> At first I noticed that all of the modules that were located there were
> there prior to my recompile. As I had excluded a lot of them entirely I
> realized that they were not removed when I did 'make modules_install'.
> Looking in the Makefile I see that it will create the /lib/modules
> directory. So, I axed the directory (rm -rf /lib/modules/2.2.6) and
> tried 'make modules' and 'make modules_install' again.  It made the
> directory and only placed the modules that I actually wanted in there
> however, it still gave me the same errors, just a shorter list thats
> all.
>
> Man depmod makes one mention of unresolved symbols (Option -e output the
> list of unresolved symbol for  each module) but makes no mention of it
> beyond this.  I can't find any mention of this problem or even a hint as
> to what is in any documentation. I haven't got a clue why it is doing
> this or what the implications are. I just want the messages gone.
>
> Please help.
>
> Paul Becker

Did you copy System.map to the sme place you put the new kernel ?
--

Bob Martin

Thank you! That worked. Just to clarify the order of operations when
compiling a kernel, which is not how it is stated in the HOWTO's.

make mrproper
make menuconfig (or config of choice)
make dep
make zImage
make modules
make modules_install
make zlilo

The HOWTO's say to make zImage, make zlilo and then make modules and make
modules_install. The System.map is being copied at the make zlilo stage,
which, as it turns out, was being run prematurely.

Bob Martin wrote:

Did you copy System.map to the sme place you put the new kernel ?
--

Bob Martin

> Paul Becker wrote:
> >
> > I have just installed Slackware 4.0 from CD, which worked fine. I
> > recompiled the kernel for my setup, which also worked fine. However, the
> > command depmod -a (executes at boot up) returns unresolved symbol for
> > all my modules in /lib/modules/2.2.6.
> >
> > At first I noticed that all of the modules that were located there were
> > there prior to my recompile. As I had excluded a lot of them entirely I
> > realized that they were not removed when I did 'make modules_install'.
> > Looking in the Makefile I see that it will create the /lib/modules
> > directory. So, I axed the directory (rm -rf /lib/modules/2.2.6) and
> > tried 'make modules' and 'make modules_install' again.  It made the
> > directory and only placed the modules that I actually wanted in there
> > however, it still gave me the same errors, just a shorter list thats
> > all.
> >
> > Man depmod makes one mention of unresolved symbols (Option -e output the
> > list of unresolved symbol for  each module) but makes no mention of it
> > beyond this.  I can't find any mention of this problem or even a hint as
> > to what is in any documentation. I haven't got a clue why it is doing
> > this or what the implications are. I just want the messages gone.
> >
> > Please help.
> >
> > Paul Becker
>
>

Not sure if this matters but I have NEVER used all these makes to do a
kernel.I simply do the config, image, modules and mod_install. Never had
a problem. What is the advantage of the others?

-Al

Paul Becker <pbe...@sympatico.ca> writes:

> Thank you! That worked. Just to clarify the order of operations when
> compiling a kernel, which is not how it is stated in the HOWTO's.
>
> make mrproper
> make menuconfig (or config of choice)
> make dep
> make zImage
> make modules
> make modules_install
> make zlilo
>
> The HOWTO's say to make zImage, make zlilo and then make modules and make
> modules_install. The System.map is being copied at the make zlilo stage,
> which, as it turns out, was being run prematurely.
>
> Bob Martin wrote:
>
> Did you copy System.map to the sme place you put the new kernel ?
> --
>
> Bob Martin
>
> > Paul Becker wrote:
> > >
> > > I have just installed Slackware 4.0 from CD, which worked fine. I
> > > recompiled the kernel for my setup, which also worked fine. However, the
> > > command depmod -a (executes at boot up) returns unresolved symbol for
> > > all my modules in /lib/modules/2.2.6.
> > >
> > > At first I noticed that all of the modules that were located there were
> > > there prior to my recompile. As I had excluded a lot of them entirely I
> > > realized that they were not removed when I did 'make modules_install'.
> > > Looking in the Makefile I see that it will create the /lib/modules
> > > directory. So, I axed the directory (rm -rf /lib/modules/2.2.6) and
> > > tried 'make modules' and 'make modules_install' again.  It made the
> > > directory and only placed the modules that I actually wanted in there
> > > however, it still gave me the same errors, just a shorter list thats
> > > all.
> > >
> > > Man depmod makes one mention of unresolved symbols (Option -e output the
> > > list of unresolved symbol for  each module) but makes no mention of it
> > > beyond this.  I can't find any mention of this problem or even a hint as
> > > to what is in any documentation. I haven't got a clue why it is doing
> > > this or what the implications are. I just want the messages gone.
> > >
> > > Please help.
> > >
> > > Paul Becker
> >
> >
>

--
Al Arduengo      ex...@austin.rr.com        http://home.austin.rr.com/exal
----
"Sometimes a cigar is just a cigar."      -- Sigmund Freud