[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



----- Original Message -----
From: Jerome Acks Jr <jracksjr@bellatlantic.net>
To: <debian-user@lists.debian.org>
Sent: Friday, August 16, 2002 6:24 AM
Subject: Re: Warning: System.map-2.2.19 is not parseable as system.ap

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.

--
Jerome

______End of Qouted text____---

Hello Jerome,

sorry for being so late; I was caught in something else.

Here is the /etc/lilo.conf file, can u psot whats wrong ?

Sachin
( pls cc me the reply, I am not able to follow list. )

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda3

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
#
install=/boot/boot.b

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

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=40

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask,
<mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# Boot up Linux by default.
#
default=windows

image=/vmlinuz
 label=Linux
 read-only
# restricted
 alias=1

image=/bzImage4ess-modsetver
 label=Linuxnew
 read-only
 optional
# restricted
 alias=2

# If you have another OS on this machine to boot, you can uncomment
the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
 other=/dev/hda1
 label=windows
# restricted
 alias=3

image=/vmlinuz-2.2.12-20
 label=Linux2212
 read-only
 optional
# restricted
 alias=4







Reply to: