improper /boot/System.map when installing new kernel
doug reeder
I'm trying to compile and install 2.2.16 on a machine which is
currently running 2.2.17-14 (because the tape driver patches are only
for 2.2.16). It's an HP Visualize (essentially identical to an HP Kayak).
I have executed the following steps:
cd /usr/src/linux
make xconfig
make dep
make clean
make bzdisk
cp arch/i386/boot/bzImage /boot/vmlinuz-2.2.16-tape
make modules
make modules_install
depmod -a 2.2.16
mkinitrd /boot/initrd-2.2.16-tape.img 2.2.16-tape
emacs /etc/lilo.conf
lilo
depmod -a 2.2.16 gives the following errors, which are for modules
I can do without, for now:
/lib/modules/2.2.16/fs/vfat.o: unresolved symbol(s)
/lib/modules/2.2.16/fs/msdos.o: unresolved symbol(s)
/lib/modules/2.2.16/fs/fat.o: unresolved symbol(s)
/lib/modules/2.2.16/misc/lp.o: unresolved symbol(s)
When I try to boot using the new kernel, the system complains that
System.map has the wrong version number, which makes sense because
there is no version of System.map for 2.2.16, and System.map is a
symlink to 2.2.17-14:
/boot/System.map@ /boot/System.map-2.2.12-20smp
/boot/System.map-2.2.12-20 /boot/System.map-2.2.17-14
What do I need to run to fix System.map ?
--
P. Douglas Reeder Lecturer, Dept. Computer/Info. Science, Ohio State Univ.
ree...@cis.ohio-state.edu http://www.cis.ohio-state.edu/~reeder/reeder.html
GE/S d+ s+:- a C+@$ UH+ P+ L E W++ N+ o? K? w !O M+ V PS+() PE Y+ PGP- t 5+ !X
R>+ tv+ b+++>$ DI+ D- G e+++ h r+>+++ y+>++
Jason Lott
System.map should appear in the source tree as "/usr/src/linux/System.map" for
example.
>
>/boot/System.map@ /boot/System.map-2.2.12-20smp
>/boot/System.map-2.2.12-20 /boot/System.map-2.2.17-14
>
>
>
>What do I need to run to fix System.map ?
Try make bzImage instead of make bzdisk... I've never used make bzdisk before,
so I can't say for sure that it doesn't generate a System.map file.
Ted Pavlic
> I have executed the following steps:
> cd /usr/src/linux
> make xconfig
> make dep
> make clean
> make bzdisk
> cp arch/i386/boot/bzImage /boot/vmlinuz-2.2.16-tape
Have you considering doing a "make install" instead of this copy? System.map
is generated after kernel compilation. It should autmoatically dump the
kernel in /boot and run lilo (you may need to modify lilo manually as the
kernel name may not be the same in /boot as it is in /etc/lilo.conf). It
will also generate and copy the System.map into /boot (along with any other
needed /boot files).
> make modules
> make modules_install
"make install" is much like "make modules_install", but it's for the kernel
and not for modules, obviuosly. :)
> depmod -a 2.2.16
> mkinitrd /boot/initrd-2.2.16-tape.img 2.2.16-tape
> emacs /etc/lilo.conf
> lilo
I hope that helps out. My kernel compilations usually go something like
this:
cd /usr/src/linux
# I'm just not an X person :)
make menuconfig
# I like to chain these together because I like walking away
# and lettings things run
make dep &&
make clean &&
make bzImage &&
make install &&
make modules &&
make modules_install
# I'm just not an emacs person :)
vi /etc/lilo.conf
lilo
All the best --
Ted
Kwan Lowe
> depmod -a 2.2.16 gives the following errors, which are for modules
> I can do without, for now:
> /lib/modules/2.2.16/fs/vfat.o: unresolved symbol(s)
> /lib/modules/2.2.16/fs/msdos.o: unresolved symbol(s)
> /lib/modules/2.2.16/fs/fat.o: unresolved symbol(s)
> /lib/modules/2.2.16/misc/lp.o: unresolved symbol(s)
These occur because the modules exist from a previous kernel build, but are not
currently enabled in the active kernel. The easiest way to fix this is to rename
the lib/modules/2.2.16 directory then rerun 'make modules_install'. Doing so
will recreate the 2.2.16 directory with only the active modules.
> When I try to boot using the new kernel, the system complains that
> System.map has the wrong version number, which makes sense because
> there is no version of System.map for 2.2.16, and System.map is a
> symlink to 2.2.17-14:
> /boot/System.map@ /boot/System.map-2.2.12-20smp
> /boot/System.map-2.2.12-20 /boot/System.map-2.2.17-14
Make sure you copy the System.map from your kernel sources to /boot. Then,
delete the symlink to the old version.
from:
http://www.digitalhermit.com/linux/kernel.html