Perhaps you have a problem with the way you built your kernel. I've had
a similar problem if I did something that changed things in between
doing a make vmlinux without doing a make clean first. Translation:
do a make clean before a make vmlinux and see if the resulting system
map doesn't work be
Thanks. I removed system.map.2.2.22 from / and see if /boot contains the
same file as my build and it looks correct (i have system.map.2.2.22 in
my /boot). uname -a reports: Linux buttercup 2.2.22 #1 Tue May 27
13:09:38 PHT 2003 sparc unknown
however, none of this worked :( if I may add, my previou
Thanks. I removed system.map.2.2.22 from / and see if /boot contains the
same file as my build and it looks correct (i have system.map.2.2.22 in
my /boot). uname -a reports: Linux buttercup 2.2.22 #1 Tue May 27
13:09:38 PHT 2003 sparc unknown
however, none of this worked :( if I may add, my previou
> I copied System.map-2.2.22 to / as per advised from the web, but doesnt
> work. What do you think is the problem here. Is this a serious error?
> Hope you could help me here.
Delete it from / and make sure the one in /boot matches your kernel
build.
--
Debian - http://www.debian.org/
Linux
Hi All,
after upgrading from kernel-2.2.20 to 2.2.22, using make-kpkg I got the
following error while doing ps:
{iommu_get_scsi_one_gflush} {___f_mmu_get_scsi_one}
Warning: /boot/System.map-2.2.22 does not match kernel data.
I copied System.map-2.2.22 to / as per advised from the web, but
Yoohoo All
I just upgraded my 2.4.18 Kernel to 2.4.20 on a sparc10 with make oldconfig.
After compiling and installing vmlinux and System.map under /boot like it
always worked before I get:
{iommu_unlockarea} {___f_mmu_unlockarea}
Warning: /boot/System.map does not match kernel data.
sparc10
6 matches
Mail list logo