The address is one that shouldn't exist in the virtual memory map (so hopefully shouldn't interfere or clash with any other symbols in the file). Why does my System.map file not contain a 'Version_XXXXX' line?Įdit: I added a 'dummy' version line to the start of my System.map file: 0FFFFFFFFFFFFFFF d Version_265223 How big a problem is 'Cannot find map file.' boot message? Įdit: I have created these follow-on questions: Obviously, this leads to further questions, though. So, because it can't find this version line, klogd is rejecting the map file. However, this version line is not present in any of the map files that have been generated during my kernel build (nor in the map files that are supplied with my pre-packaged Trisquel installation). Where 'XXXXX' is the kernel version, encoded in base 256. line is because it is looking for a line in the map file of the form: _Version_XXXXX
However, the reason it is printing the Cannot find map file. line does indeed mean that klogd has found the map file in that location and has successfully opened it.
#OPEN MAP FILE CODE#
So, I've been digging through the source code for klogd, and I think I know what the answer is:įirstly, the Inspecting. This is why I suspect that klogd is finding the map file, but doesn't seem to be accepting it for some reason. It was only after I fixed /etc/fstab that that line started to appear in the log, and with the correct path to the map file. However, I initially had forgotten to add a line in /etc/fstab for the /boot partition (in which case, it obviously wouldn't be able to find the file) and that 'Inspecting. ' line might not literally mean that klogd is accessing the file, but might just mean that it has started looking for it. (That link contains some more background to the problem and things that have been suggested before).Įdit - to answer a suggestion that was made in the comments: The second line down there seems to indicate that it has found the /boot/System.map file however, the following line suggests that the file is being rejected (which I suspect may be at least partly responsible for the failure of the kernel to fully boot up).ĭoes anyone have any idea of what might be causing this? I asked this question before on the Linux Questions site ( link here) however, no-one there was able to figure it out. Oct 9 17:24:17 kernel: random: get_random_bytes called from start_kernel+0x30/0x3bc with crng_init=0 Oct 9 17:24:17 kernel: Loaded 100800 symbols from 32 modules. Oct 9 17:24:17 kernel: Cannot find map file.
Oct 9 17:24:17 kernel: Inspecting /boot/System.map In particular, I am puzzled by the following message at the start of the log file: Oct 9 17:24:17 kernel: klogd 1.5.1, log source = /proc/kmsg started. When I try to boot it from the GRUB command prompt, the screen goes black and no output shows however, it does write to the /var/log/kern.log file. The kernel version is 4.13.1 (linux-libre) and it is the first time I've tried to compile my own kernel. I have Trisquel GNU/Linux (version 7) installed on another partition on the machine, which works fine, so I know it is possible to boot up GNU/Linux on this hardware/firmware configuration. I am trying to use this custom kernel to boot up a Linux From Scratch installation that I have built.
#OPEN MAP FILE FREE#
The machine is an Apple Macbook (Intel Core 2 Duo, 64-bit) that has the free Libreboot firmware installed, with GRUB2 as a payload. I've been trying to get a Linux kernel to run that I've configured and compiled myself, but so far without success.
0 kommentar(er)
