关于lilo,这次真的没办法了！！！

4979458

slack 10.1
kernel 2.4.29 ----> 2.6.11
升完后一切都ok，用了许久都没问题。（也许有问题，偶没看出来 :rolleyes: ）

昨晚装了个fcitx输入法，装了个firefox，按论坛精华贴汉化了下系统，其他也没做什么，更没去动内核文件。

今天早上要进2.6.11时出现如下提示：

Loading Linux-2.6.11 EBDA is big; kernel setup stack overlaps Lilo second stage.

停在这里没法进入系统，Ctrl+Alt+Del没法重启。。。

另：2.4.29内核可以进入。

谁能解释下上面这段话的意思？现在该怎么办？

windrose

lilo.conf, please

4979458

my lilo.conf  thx windrose

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 600
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/hda1
  label = Windows
  table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins

image = /boot/vmlinuz-ide-2.4.29//这部分是我也自己改的，对应着旧内核
  root = /dev/hda9
  label = Linux-2.4.29
  read-only

image = /boot/vmlinuz-2.6.11//这一部分是添加的，用了好长一段时间，都可以正确引导
  root = /dev/hda9
  label = Linux-2.6.11
  read-only
# Linux bootable partition config ends

windrose

用 edba too big 作为关键词google一下，试试这个：
http://lists.debian.org/debian-boot/2001/09/msg00045.html

minus273

不象是这个问题

lang2

觉得像 initrd 没有装。testing/packages/linux-2.6.10/ 有一个 README.initrd
贴在下面了。

Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
Sun Oct 31 18:50:27 PST 2004

This document describes how to create and install an initrd, which may be
required to use the 2.6 kernel.  Also see "man mkinitrd".

1.  What is an initrd?
2.  Why to I need an initrd?
3.  How do I build the initrd?
4.  Now that I've built an initrd, how do I use it?


1.  What is an initrd?

Initrd stands for "initial ramdisk".  An initial ramdisk is a very small
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
and before the main root filesystem is mounted.

2.  Why do I need an initrd?

The usual reason to use an initrd is because you need to load kernel
modules before mounting the root partition.  Usually these modules are
required to support the filesystem used by the root partition (ext3,
reiserfs, xfs), or perhaps the controller that the hard drive is attached
to (SCSI, RAID, etc).  Essentially, there are so many different options
available in modern Linux kernels that it isn't practical to try to ship
many different kernels to try to cover everyone's needs.  It's a lot more
flexible to ship a generic kernel and a set of kernel modules for it.  The
generic 2.6 kernel in Slackware supports the ext2 filesystem (which is
used by the initrd), and also supports most IDE controllers (much like the
old bare.i kernel).  So, if you have an IDE based system that uses the
ext2 filesystem, then you will not need to use an initrd to boot.  
Otherwise, read on.

3.  How do I build the initrd?

The easiest way to make the initrd is to use the mkinitrd script included
in Slackware's mkinitrd package.  We'll walk through the process of
upgrading to the 2.6.10 Linux kernel using the packages found in
Slackware's testing/packages/linux-2.6.10/ directory.

First, make sure the kernel, kernel modules, and mkinitrd package are
installed (the current version numbers might be a little different, so
this is just an example):

  installpkg kernel-generic-2.6.10-i486-1.tgz
  installpkg kernel-modules-2.6.10-i486-1.tgz
  installpkg mkinitrd-1.0.1-i486-1.tgz

Change into the /boot directory:

  cd /boot

Now you'll want to run "mkinitrd".  I'm using reiserfs for my root
filesystem, and since it's an IDE system the reiserfs module will be
the only one I need to load:

  mkinitrd -c -k 2.6.10 -m reiserfs

This should do two things.  First, it will create a directory
/boot/initrd-tree containing the initrd's filesystem.  Then it will
create an initrd (/boot/initrd.gz) from this tree.  If you wanted to,
you could make some additional changes in /boot/initrd-tree/ and
then run mkinitrd again without options to rebuild the image.  That's
optional, though, and only advanced users will need to think about that.

Here's another example:  Build an initrd image using Linux 2.6.10 kernel
modules for a system with an ext3 root partition on /dev/hdb3.  Note
that you need both the jbd and ext3 modules to use ext3:

  mkinitrd -c -k 2.6.10 -m jbd:ext3 -f ext3 -r /dev/hdb3


4.  Now that I've built an initrd, how do I use it?

Now that you've got an initrd (/boot/initrd.gz), you'll want to load
it along with the kernel at boot time.  If you use LILO for your boot
loader you'll need to edit /etc/lilo.conf and add a line to load the
initrd.  Here's an example section of lilo.conf showing how this is
done:

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.10
  initrd = /boot/initrd.gz
  root = /dev/hda6
  label = Linux2610
  read-only
# Linux bootable partition config ends

The initrd is loaded by the "initrd = /boot/initrd.gz" line.
Just add the line right below the line for the kernel image you use.
Save the file, and then run LILO again ('lilo' at the command line).
You'll need to run lilo every time you edit lilo.conf or rebuild the
initrd.

Other bootloaders such as syslinux also support the use of an initrd.
See the documentation for those programs for details on using an
initrd with them.


---------

Have fun!

troll

关键在于人家用了很久，是突然出现这个问题的。