[SOLVED] Kernel compile 2.6.10 and Debian

[KarrottoP]

I am using Debian (unstable) and I am trying to get Kernel 2.6.10 (from apt-get source) up and running. After I got everything configured and compiled I did a mkinitrd and then edited lilo.conf to call initrd=/boot/initrd-2.6.10.img in the /vmlinuz section. I then ran lilo. When I reboot I get a kernel panic - not syncing: VPS: unable to mount root fs on unknown block (3,1)

I have no idea what I need to do to get things working, I did not even mess with initrd in previous versions of the kernel I have been using.

Thanks in advance

Jason Self

[je_fro]

boot to your old kernel and make sure that you included filesystem support for whatever filesystem you're using.

[KarrottoP]

That was my first thought, but I knew I had support for ext2 and ext3 in the kernel, so after you suggested it I recompiled the kenrel, with every filesystem built in....It still doesn't work :(

[je_fro]

would you post your /etc/lilo.conf and your /etc/fstab here?

[bwkaz]

What about support for whatever IDE chipset your root partition's disk is on? That should be built-in too, I believe.

[Seven up]

and maybe this is what you meant by

but I knew I had support for ext2 and ext3 in the kernel, so after you suggested it I recompiled the kenrel, with every filesystem built in

But make sure you aren't using them as modules. I manage to forget that everytime. :)

[KarrottoP]

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/hda1 / ext2 errors=remount-ro 0 1
proc /proc proc defaults 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0

[KarrottoP]

# /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=0x81

#disk=/dev/sda
# bios=0x80

# 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/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1

# 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
# 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

image=/vmlinuz
label=Linux
read-only
initrd=/boot/initrd.img-2.6.10
# 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

[KarrottoP]

Thanks, and to answer Seven up, I did get them in the kernel (not as modules)

Thanks,
Jason

[Bryon Speede]

Did you compile in support for cramfs? Debian loads into a compressed ramdisk and then boots from there, so you must have cramfs enabled.

[KarrottoP]

I didn't have cramfs but I recompile the kernel again with it enabled (I also did another mkinitrd in /boot/) When I restarted I still go the same error...I did notice the last two lines before the error are finding cramfs at block 0 and then loads it with what appears to be success (it says done)

[bwkaz]

Originally posted by bwkaz
What about support for whatever IDE chipset your root partition's disk is on? That should be built-in too, I believe. Dunno if you missed this or not, but I still suspect that it's causing your problem... ;)

[Gertrude]

Just add to what bwkaz just said. Boot up a working kernel. Then run 'dmesg', and somewhere close to the beginning of that output you should see what chipset your IDE controller is. Make sure you compile support for into the kernel, and not as a module. By default I believe the Debian2.6 kernels have them all as modules.

You can also try to disable anything in Advanced Partition Support under the file systems section in the kernel.

[je_fro]

Is it trying to mount hdd2 here? Are you sure you ran lilo?

VPS: unable to mount root fs on unknown block (3,1)

[XiaoKJ]

did you compile it as a deb? if you did, why are you using /vmlinuz? isn't it in /boot/vmlinuz-2.6.10 or something?

if you compiled your own not as a deb, then did you even copy the bzImage over?

finally, did you make clean when you compiled again?

Sorry -- these are the newbie questions. but they are often forgotten

[KarrottoP]

Well, it works now. The chipset was with modules as Gertrude had said... I built them in and it worked. Thanks everyone for the help....The 2.6 kernel on debian is a bit of a new monster for me.

Unfortunately Cron is halting the system now, but I think I can figure this one out on my own.

Thanks again