1 |
> > > > > System.map not found - unable to check symbols. |
2 |
> > > > > which doesn't seem to cause problems during/after booting (??). |
3 |
> > > > > |
4 |
> > > > > I did a manual kernel compilation |
5 |
> > > > |
6 |
> > > > To do this, I always do: |
7 |
> > > > |
8 |
> > > > make all modules_install install |
9 |
> > > > |
10 |
> > > > This will do all the necessary steps. |
11 |
> > > |
12 |
> > > I tried the make all option and it added a /boot -> . |
13 |
> > > Inside /boot. Also, a menu.lst file was created inside /boot/grub |
14 |
> > > that points to grub.conf. Other than that there no changes/additions |
15 |
> > > we made. |
16 |
> > |
17 |
> > 'make all' is supposed to compile the kernel, 'make modules_install' |
18 |
> > will compile the kernel modules, 'make install' will install the kernel |
19 |
> > and 'make all modules_install install' will do all three of those things. |
20 |
> |
21 |
> I tried multiple times, different ways installing the kernel (vanilla |
22 |
> sources) and reinstalling grub. Still the same message of "System.map |
23 |
> not found" during booting. |
24 |
> |
25 |
> > > I rebooted and had the same problem occurring: |
26 |
> > > |
27 |
> > > System.map not found -- unable to check symbols |
28 |
> > |
29 |
> > Could you provide the output of: |
30 |
> > |
31 |
> > # df -h | grep boot |
32 |
> > # ls -l /boot |
33 |
> |
34 |
> Nothing from the previous commands since /boot is not mounted (it is no |
35 |
> in fstab as suggested by the install handbook) |
36 |
> |
37 |
> > # uname -r |
38 |
> |
39 |
> 2.6.15.1 |
40 |
|
41 |
|
42 |
Where is the message comming from? do you get it during kernel load or once |
43 |
the initscripts with the green stars beside them start doing their thing? I'm |
44 |
guessing from the OP that you have x86 hardware? |
45 |
|
46 |
1) If its the kernel load (easier to check) I suggest the following. As root |
47 |
user... |
48 |
- make sure the boot partition is mounted run 'mount /boot' |
49 |
- make sure the /usr/src/linux link is pointing to the kernel you want to boot |
50 |
from |
51 |
- cd /usr/src/linux |
52 |
- run 'make clean' (this will essentially deletes all the compiled stuff |
53 |
except for your config file, in other words cleans up the tree :) |
54 |
- run 'make all modules_install install' |
55 |
- have a look in /boot to make sure the installer created the appropriate |
56 |
link 'System.map' to the version it just installed. use 'ls -l' to see this |
57 |
- now try a reboot making sure you use >> the same kernel you just built << |
58 |
do you still get the message? If so you may need to alter the kernel config |
59 |
and see if that makes any difference, or you might like to try a different |
60 |
kernel version. |
61 |
|
62 |
2) If its happening while the initscripts load, or at some other time after |
63 |
kernel boot, then its a gentoo specific issue and you need to work through |
64 |
those scripts somehow to isolate the cause. |
65 |
|
66 |
-- |
67 |
Thus spake the master programmer: |
68 |
"After three days without programming, life becomes meaningless." |
69 |
-- Geoffrey James, "The Tao of Programming" |