Results 1 to 2 of 2
I get the following warnings on boot: Inspecting /boot/System.map-188.8.131.52 Inspecting /usr/src/linux/System.map Cannot find map file The file in /boot is an exact copy of the one in my kernel build ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-08-2011 #1
[solved] Kernel can't find system map
Cannot find map file
The file in /boot is an exact copy of the one in my kernel build directory and /usr/src/linux is a link to that directory. So either of those files should be a valid map file. What is going wrong here?
Last edited by hazel; 10-08-2011 at 04:47 PM. Reason: Solved
- 10-08-2011 #2
Well, I found the answer. Should have googled it before putting up this post. Mea culpa! Apparently klogd identifies a map file by looking for a Version symbol. But kernels later than 2.6.27 don't define this symbol if KALLSYMS=y, because in that case, the kernel includes its own symbol table and doesn't need a map file.
The problem is that the kernel hackers and the people responsible for sysklogd can't agree on whose fault this is and which program should be changed, so it just doesn't get fixed.