[olug] Can't boot to 2.6 Kernel

Brandon Lederer brandon at tolkien-movies.com
Sat Mar 6 22:28:34 UTC 2004


Unless you KNOW you need initrd, dont use it.  Copy the system.map file out of 
the /usr/src/linux.  You need the system.map file and thats probably what its 
complaining about.  make sure u dont overwrite the original system.map thats 
there.  usually it has a version associated with it.

On Saturday 06 March 2004 04:19 pm, CM Miller wrote:
> --- Daniel Linder <dan at linder.org> wrote:
> > Can you double check by doing the following and
> > e-mailing us the output?
> > 1: "ls -al /usr/src | grep linux.2.6.3"
>
> root at xanadu:/usr/src# ls -al | grep linux.2.6.3
> drwxrwxr-x   19 1046     1046         4096 Mar  6
> 09:44 linux-2.6.3
> -rwx------    1 root     knoppix  192737280 Feb 21
> 20:03 linux-2.6.3.tar
>
> > 2: "ls -al /usr/src/linux.2.6.3#"
>
> total 11540
> drwxrwxr-x   19 1046     1046         4096 Mar  6
> 16:26 .
> drwxrwsr-x    5 1000     knoppix      4096 Feb 21
> 20:18 ..
> -rw-r--r--    1 root     root          457 Feb 21
> 20:58 ..tmp_kallsyms1.o.cmd
> -rw-r--r--    1 root     root          457 Feb 21
> 20:58 ..tmp_kallsyms2.o.cmd
> -rw-r--r--    1 root     root          579 Feb 21
> 20:58 ..tmp_vmlinux1.cmd
> -rw-r--r--    1 root     root          595 Feb 21
> 20:58 ..tmp_vmlinux2.cmd
> -rw-r--r--    1 root     root        37330 Feb 21
> 20:27 .config
> -rw-r--r--    1 root     root         4527 Feb 21
> 20:27 .config.cmd
> -rw-r--r--    1 root     root        37330 Feb 21
> 20:27 .config.old
> -rw-r--r--    1 root     root       414969 Feb 21
> 20:58 .tmp_kallsyms1.S
> -rw-r--r--    1 root     root       144440 Feb 21
> 20:58 .tmp_kallsyms1.o
> -rw-r--r--    1 root     root       414969 Feb 21
> 20:58 .tmp_kallsyms2.S
> -rw-r--r--    1 root     root       144440 Feb 21
> 20:58 .tmp_kallsyms2.o
> drwxr-xr-x    2 root     root         4096 Feb 21
> 20:28 .tmp_versions
> -rwxr-xr-x    1 root     root      3095432 Feb 21
> 20:58 .tmp_vmlinux1
> -rwxr-xr-x    1 root     root      3238925 Feb 21
> 20:58 .tmp_vmlinux2
> -rw-r--r--    1 root     root            2 Feb 21
> 20:58 .version
> -rw-r--r--    1 root     root          583 Feb 21
> 20:58 .vmlinux.cmd
> -rw-r--r--    1 1046     1046        18691 Feb 18
> 04:58 COPYING
> -rw-r--r--    1 1046     1046        85286 Feb 18
> 04:58 CREDITS
> drwxrwxr-x   42 1046     1046         4096 Feb 18
> 04:59 Documentation
> -rw-r--r--    1 1046     1046        51469 Feb 18
> 04:58 MAINTAINERS
> -rw-r--r--    1 1046     1046        32443 Feb 18
> 04:58 Makefile
> -rw-r--r--    1 1046     1046        14489 Feb 18
> 04:59 README
> -rw-r--r--    1 1046     1046         2815 Feb 18
> 04:58 REPORTING-BUGS
> -rw-r--r--    1 root     root       662190 Feb 21
> 20:58 System.map
> drwxrwxr-x   22 1046     1046         4096 Feb 18
> 04:57 arch
> drwxrwxr-x    2 1046     1046         4096 Feb 21
> 20:41 crypto
> drwxrwxr-x   43 1046     1046         4096 Feb 21
> 20:51 drivers
> drwxrwxr-x   52 1046     1046         4096 Feb 21
> 20:40 fs
> drwxrwxr-x   34 1046     1046         4096 Feb 21
> 20:28 include
> drwxrwxr-x    2 1046     1046         4096 Feb 21
> 20:58 init
> drwxrwxr-x    2 1046     1046         4096 Feb 21
> 20:40 ipc
> drwxrwxr-x    3 1046     1046         4096 Feb 21
> 20:33 kernel
> drwxrwxr-x    4 1046     1046         4096 Feb 21
> 20:58 lib
> drwxrwxr-x    2 1046     1046         4096 Feb 21
> 20:35 mm
> drwxrwxr-x   32 1046     1046         4096 Feb 21
> 20:57 net
> -rw-r--r--    1 root     root            0 Mar  6
> 16:26 output
> drwxrwxr-x    6 1046     1046         4096 Feb 21
> 20:28 scripts
> drwxrwxr-x    3 1046     1046         4096 Feb 21
> 20:41 security
> drwxrwxr-x   15 1046     1046         4096 Feb 21
> 20:51 sound
> drwxrwxr-x    2 1046     1046         4096 Feb 21
> 20:28 usr
> -rwxr-xr-x    1 root     root      3238925 Feb 21
> 20:58 vmlinux
>
> > > So I will be able to reboot and choose the kernel
> >
> > of
> >
> > > my choice (2.4 or 2.6) even though I get an error
> > > message each time I re-run ./sbin/lilo?
> >
> > I don't have a system with LILO anymore -- went the
> > way of the Grub... :)
> >
> > When you run /sbin/lilo, and it has no errors, I
> > think it just spits back
> > the label of each kernel it found in the config
> > file.  If you run
> > "/sbin/lilo -v -t", what output does it spit back?
>
> root at xanadu:/sbin# ./lilo -v -t
> LILO version 22.5.8 (test mode), Copyright (C)
> 1992-1998 Werner Almesberger
> Development beyond version 21 Copyright (C) 1999-2003
> John Coffman
> Released 10-Oct-2003, and compiled at 15:58:18 on Oct
> 11 2003
> Compiled for Debian GNU/Linux.
>
> Reading boot sector from /dev/hda
> Using MENU secondary loader
> Calling map_insert_data
>
> Boot image: /boot/vmlinuz-2.4.22-xfs
> Mapping RAM disk /boot/initrd.gz
> Added Linux *
>
> Boot image: /boot/vmlinuz-2.6.3
> Mapping RAM disk /boot/initrd.2.6.3.gz
> Fatal: Empty map section
>
>
>
> =====
> * * * * * * * * * * * * * * * *
> GAIM ID:  cmmiller1973
> * * * * * * * * * * * * * * * *
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug


More information about the OLUG mailing list