Re: Warning: System.map-2.2.19 is not parseable as system.ap

["Dr. Sachin Kale" <sauravsk@agd2.dot.net.in>]

----- Original Message -----
From: Vineet Kumar <debian-user@virtual.doorstop.net>
To: <debian-user@lists.debian.org>
Cc: Dr. Sachin Kale <sauravsk@agd2.dot.net.in>
Sent: Saturday, August 24, 2002 5:10 AM
Subject: Re: Warning: System.map-2.2.19 is not parseable as system.ap

* Dr. Sachin Kale (sauravsk@agd2.dot.net.in) [020823 09:16]:
> * Jerome Acks Jr:
> > On Thu, Aug 15, 2002 at 07:19:41AM +0530, Dr. Sachin Kale wrote:
> > > Hello,
> > > I had a small doubt -
> > > what  do you do with the systemmap that is formed in a directery
> > after
> > > new kernel compilation ? I copied the same to /boot & edited the
> > > corresponding line in lilo.conf. Now I get more than a page of
> > > unresolved symbols whether I boot with original kernel or newly
> > > compiled kernel.
> > > What am I doing wrong ?
> >
> > Hi Sachin,
> >
> > If you used make-kpkg to compile and build a deb for the kernel
and
> > dpkp to install the kernel, System.map-xxx automatically get
installed
> > in /boot.
> >
> > I have on line in lilo.conf that reads "map=/boot/map", no direct
> > reference to System.map-xxx, and every works fine. Please post
your
> > lilo.conf to the list so we can see what it look like.

Lilo's map file is completely different from the kernel's System.map
file.

> # Specifies the location of the map file
> #
> map=/boot/System.map4ess-modsetver

________Qoute______

This setting probably hosed your System.map .  You'll need to re-copy
it
from your kernel build directory into /boot.  Also, change that line
back to map=/boot/map and re-run lilo.

_______End qoute_______

I tried that but, still no use. I think System.map file is corrupt, &
even on copying the new one from the /usr/src its giving lots of
unresolved symbols  error.

I think I should get familiar with kernel-package & do it debian way.
( If there is no other way. )
Sachin