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 better.
a On Fri, May 30, 2003 at 10:42:02AM +0800, Lito A. Lampitoc wrote: > 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 previous kernel is > 2.2.20-su4cdm and just to make it work I did the ff. before running silo > > ln -s . /boot/etc > ln -s . /boot/boot > mv /etc/silo.conf /boot > ln -s /boot/silo.conf /etc/silo.conf > > (your idea) > > do i have to repeat the same process again? > yes, I updated my silo.conf to reflect the new kernel. > > thanx. > > > > > On Thu, 2003-05-29 at 19:14, Ben Collins wrote: > > > 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. > -- > Lito A. Lampitoc :http://www.codewan.com.ph > Systems & Network Administrator :Countrywide Devt. Wide Area Network > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
