I just upgraded from the 2.4.18bf2.4 kernel, now LinuxOLD on my LILO
menu, to the 2.6.8 .... 686 kernel available from sarge. Unfortunately
the 2.6 kernel gives me the following panic:
VFS: Cannot open root device 2141 or unknown-block(33,65)
Please append a correct "root=" boot option
Kernelpanic: VFS: Unable to mount root fs on unknown-block(33,65)
The computer is a Gateway 500 with a Pentium III at 500 MHZ. I
looked through the man pages for lilo.conf, syslog, and a few others. I
also looked at the source, somewhat briefly, of course, for any special
options for 2.6 kernels that I needed to put into the lilo.conf file.
(I've also downloaded the source code for the 2.6.8 kernel.) The bf2.4
kernel works fine. However, both the 2.4.16-686 and the 2.6.8-2-686
kernels will panic. I'm only concerned about booting and using the 2.6
kernel, of course.
I am subscribed to the list, but CC's are fine.
What options or docs did I miss? Hopefully, it's just a change to
my lilo.conf file? Although my boot drive is /dev/hde, my root for
Linux is on /dev/hdf1 as you can see from the lilo.conf file. This
Gateway 500 also has Window 98SE on it. I added a second hard drive and
decided to put Debian GNU/Linux 3.0 (woody) on it.
Thank you for any help giving or pointing me to the correct information!
This is my /boot directory:
[EMAIL PROTECTED]:~/docs$ cat bootdir.txt
total 12620
drwxr-xr-x 2 root 4096 Jun 23 10:03 .
drwxr-xr-x 24 root 4096 Jun 23 10:00 ..
-rw-r--r-- 1 root 398501 Nov 27 2001 System.map-2.4.16-686
-rw-r--r-- 1 root 559088 May 14 2004 System.map-2.4.18-bf2.4
-rw-r--r-- 1 root 843026 May 19 04:27 System.map-2.6.8-2-686
-rw-r--r-- 1 root 512 May 14 2004 boot.2100
-rw-r--r-- 1 root 512 Jun 19 15:39 boot.2140
lrwxrwxrwx 1 root 11 May 14 2004 boot.b -> boot-menu.b
-rw-r--r-- 1 root 308326 Jun 19 15:13 coffee.bmp
-rw-r--r-- 1 root 34159 Nov 27 2001 config-2.4.16-686
-rw-r--r-- 1 root 16984 May 14 2004 config-2.4.18-bf2.4
-rw-r--r-- 1 root 55399 May 19 03:51 config-2.6.8-2-686
lrwxrwxrwx 1 root 15 Jun 19 15:13 debian.bmp -> /boot/sarge.bmp
-rw-r--r-- 1 root 153720 Jun 19 15:13 debianlilo.bmp
-rw-r--r-- 1 root 2682880 Apr 20 00:46 initrd.img-2.4.16-686
-rw-r--r-- 1 root 4636672 Jun 23 10:00 initrd.img-2.6.8-2-686
-rw------- 1 root 42496 Jun 23 10:03 map
-rw-r--r-- 1 root 23662 Jun 19 15:13 sarge.bmp
-rw-r--r-- 1 root 24116 Jun 19 15:13 sid.bmp
-rw-r--r-- 1 root 611285 Nov 27 2001 vmlinuz-2.4.16-686
-rw-r--r-- 1 root 1263339 May 14 2004 vmlinuz-2.4.18-bf2.4
-rw-r--r-- 1 root 1170965 May 19 04:27 vmlinuz-2.6.8-2-686
[EMAIL PROTECTED]:~/docs$
[EMAIL PROTECTED]:~/drivers$ cat lilo.conf
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
disk=/dev/hde
bios=0x80
disk=/dev/hdf
bios=0x81
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hde
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hdf1
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
#default=Linux
# Make menu 'wife-proof'
default=Windows(hde1)
image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hde1
label="Windows(hde1)"
#other=/dev/hdf5
# label="Linux(hdf5)"
#other=/dev/hdf6
# label="Other(hdf6)"
#other=/dev/hdf7
# label="Windows(hdf7)"
#other=/dev/hdf8
# label="Linux(hdf8)"
#other=/dev/hdf9
# label="Windows(hdf9)"
[EMAIL PROTECTED]:~/drivers$
I also have the source code for 2.6.8-2-686.
[EMAIL PROTECTED]:/lib/modules/2.6.8-2-686$ ll
total 832
drwxr-xr-x 5 root 4096 Jun 23 10:00 .
drwxr-xr-x 6 root 4096 Jun 23 09:59 ..
drwxr-xr-x 2 root 4096 Jun 23 09:59 boot
lrwxrwxrwx 1 root 35 Jun 20 07:40 build ->
/usr/src/kernel-headers-2.6.8-2-686
drwxr-xr-x 2 root 4096 Jun 23 09:59 initrd
drwxr-xr-x 10 root 4096 Jun 23 09:59 kernel
-rw-r--r-- 1 root 138720 Jun 23 10:00 modules.alias
-rw-r--r-- 1 root 69 Jun 23 10:00 modules.ccwmap
-rw-r--r-- 1 root 233307 Jun 23 10:00 modules.dep
-rw-r--r-- 1 root 517 Jun 23 10:00 modules.ieee1394map
-rw-r--r-- 1 root 1061 Jun 23 10:00 modules.inputmap
-rw-r--r-- 1 root 16427 Jun 23 10:00 modules.isapnpmap
-rw-r--r-- 1 root 131958 Jun 23 10:00 modules.pcimap
-rw-r--r-- 1 root 104901 Jun 23 10:00 modules.symbols
-rw-r--r-- 1 root 157116 Jun 23 10:00 modules.usbmap
lrwxrwxrwx 1 root 100 Jun 23 09:59 source ->
/home/horms/tmp/debian-kernel-test/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386-2.6.8/install-686
[EMAIL PROTECTED]:/lib/modules/2.6.8-2-686$
--
(Mr.) Gayle Lee Fairless, http://counter.li.org/
Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
