/var/log/messages has this to say at the very beginning:
Jul 15 16:20:42 maryland init: Switching to runlevel: 6
Jul 15 16:29:13 maryland syslogd 1.3-3: restart.
Jul 15 16:29:13 maryland kernel: klogd 1.3-3, log source = /proc/kmsg started.
Jul 15 16:29:14 maryland kernel: Error in symbol table input.
Jul 15 16:29:14 maryland kernel: Cannot find map file.
Jul 15 16:29:14 maryland kernel: Error seeking in /dev/kmem
Jul 15 16:29:14 maryland kernel: Error adding kernel module table entry.
Jul 15 16:29:14 maryland kernel: Console: 16 point font, 400 scans
Jul 15 16:29:14 maryland kernel: Console: colour VGA+ 80x25, 1 virtual console (max 63)
...[normal startup stuff]
as compared to (for earlier kernels)
Jul 15 12:51:13 maryland init: Switching to runlevel: 6
Jul 15 12:52:54 maryland syslogd 1.3-3: restart.
Jul 15 12:52:54 maryland kernel: klogd 1.3-3, log source = /proc/kmsg started.
Jul 15 12:52:55 maryland kernel: Loaded 2912 symbols from /boot/System.map.
Jul 15 12:52:55 maryland kernel: Symbols match kernel version 2.0.30.
Jul 15 12:52:55 maryland kernel: Loaded 45 symbols from 5 modules.
Jul 15 12:52:55 maryland kernel: Console: 16 point font, 400 scans
...[etc]
I guess this means that /boot/System.map is not being read, but I can't see why. Also, it goes on to load all the modules, etc, and they seem to work just fine... (I have a lot of modules, even stuff like FAT fs and isofs and floppy driver) So I suppose the kernel symbols later somehow become "accessible"
What am I doing wrong? And how can I find out exactly what's happening here? I'd be grateful for any help/suggestions/pointers...
Thanks in advance,
-Vijay