RE: [gentoo-user] System.map not found - unable to check symbols

> -----Original Message-----
> From: Glenn Enright [mailto:elinar@×××××××.nz]
> Sent: Tuesday, May 09, 2006 7:58 PM
> To: gentoo-user@l.g.o
> Subject: Re: [gentoo-user] System.map not found - unable to check
symbols
>
> > > > > > System.map not found - unable to check symbols.
> > > > > > which doesn't seem to cause problems during/after booting
(??).
> > > > > >
> > > > > > I did a manual kernel compilation
> > > > >
> > > > > To do this, I always do:
> > > > >
> > > > > 	make all modules_install install
> > > > >
> > > > > This will do all the necessary steps.
> > > >
> > > > I tried the make all option and it added a /boot -> .
> > > > Inside /boot. Also, a menu.lst file was created inside
/boot/grub
> > > > that points to grub.conf. Other than that there no
changes/additions
> > > > we made.
> > >
> > > 'make all' is supposed to compile the kernel, 'make
modules_install'
> > > will compile the kernel modules, 'make install' will install the
> kernel
> > > and 'make all modules_install install' will do all three of those
> things.
> >
> > I tried multiple times, different ways installing the kernel
(vanilla
> > sources) and reinstalling grub. Still the same message of
"System.map
> > not found" during booting.
> >
> > > > I rebooted and had the same problem occurring:
> > > >
> > > > System.map not found -- unable to check symbols
> > >
> > > Could you provide the output of:
> > >
> > > # df -h | grep boot
> > > # ls -l /boot
> >
> > Nothing from the previous commands since /boot is not mounted (it is
no
> > in fstab as suggested by the install handbook)
> >
> > > # uname -r
> >
> > 2.6.15.1
>
>
> Where is the message comming from? do you get it during kernel load or
> once
> the initscripts with the green stars beside them start doing their
thing?

Yes after the green starts. The actual message scrolls up tagged with a
yellow asterisk 

> I'm
> guessing from the OP that you have x86 hardware?

Yes I have x86

>
> 1) If its the kernel load (easier to check) I suggest the following.
As
> root
> user...
> - make sure the boot partition is mounted run 'mount /boot'
> - make sure the /usr/src/linux link is pointing to the kernel you want
to
> boot
> from
> - cd /usr/src/linux
> - run 'make clean' (this will essentially deletes all the compiled
stuff
> except for your config file, in other words cleans up the tree :)
> - run 'make all modules_install install'
> - have a look in /boot to make sure the installer created the
appropriate
> link 'System.map' to the version it just installed. use 'ls -l' to see
> this
> - now try a reboot making sure you use >> the same kernel you just
built
> <<
> do you still get the message? If so you may need to alter the kernel
> config
> and see if that makes any difference, or you might like to try a
different
> kernel version.
>
> 2) If its happening while the initscripts load, or at some other time
> after
> kernel boot, then its a gentoo specific issue and you need to work
through
> those scripts somehow to isolate the cause.
>
> --
> Thus spake the master programmer:
> 	"After three days without programming, life becomes
meaningless."
> 		-- Geoffrey James, "The Tao of Programming"


Thanks,

--
Valmor

-- 
gentoo-user@g.o mailing list