I am having a problem getting my newly compiled 2.6.* series kernels
to boot in slackware 9.1.
slack is working well with default kernel 2.4.20, so i know the filesystem, etc.
is fine, i can always select default (2.4.20) at lilo prompt and boot ok.
I have compiled 2.6.5 - several times, with same result. ( I thought it may be
something i left out, .. i no longer feel this way, otherwise i wouldn't be
posting
.
(I have sucessfully compiled quite a few kernels before, this is not first time)
I have compiled 2.4.* series kernel on slack.
but have not sucessfully compiled 2.6.* on slackware 9.1 yet.
general steps for review.
-----------------------------------------------
get source from kernel.org
wget kernel.org/pub/linux/kernel/v2.6/linux-2.6.5.tar.bz2
tar xjvf kernel-2.6.5.tar.bz2
ls -s linux-2.6.5 linux
cd linux
apply specific patches.
make mrproper
make clean
make menuconfig
make && make modules && make modules_install
cp arch/i386/boot/bzImage /boot/kernel-2.6.5
mv /boot/System.map /boot/System.map-old
cp System.map /boot/System.map
ln -s /boot/kernel-2.6.5 /Linux-2.6.5
ln -s /boot/System.map /System.map
vi /etc/lilo.conf - add new kernel
boot=/dev/hda
root=/dev/hda2
message=/boot/bootmess.txt
prompt
timeout=150
delay=10
map=/System.map
vga=771
default=Linux-2.4.20
image=/vmlinuz-2.4.20
label=Linux-2.4.20
read-only
image=/Linux-2.6.5
label=Linux-2.6.5
read-only
/sbin/lilo
added
Linux-2.4.20*
Linux-2.6.5
cat /etc/fstab
####
# I am including this so you know, but this is not in fstab,
# does not get mounted, I thought this was part of the problem,
# like if i add a new kernel, i'm putting in on '/boot' which is actually
# on dev/hda2 because the real '/boot' is not mounted, however
# the system seems to know where real boot is, if i do a make install
# with the kernel the image get's moved to /dev/hda1 '/boot' properly.
###/dev/hda1 /boot ext2 defaults 0 0
/dev/hda2 / reiserfs defaults 1 1
/dev/hda5 /usr reiserfs defaults 1 2
/dev/hda6 /var reiserfs defaults 1 2
/dev/hda7 /home reiserfs defaults 1 2
/dev/hda8 /tmp reiserfs defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,user,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
all standard.
yes, kernel compiled with ext2 ext3 reiserfs ide, support (not as modules) etc.
problem occurs with booting new kernel.
dies with INIT: kernel panic no init found (try passing init= to kernel)
(I have tried passing init=/sbin/init, init=/bin/bash, root=/dev/hda2,
( even, root=/dev/hda1, for 'kicks')
to no-avail, I think the real problem lies in the fact that the kernel
sees root as ext2,... why(?!)
a few lines before that the informative line is:
VFS: mounting root ( ext2 filesystem ) ro
this is wrong, root is a reiserfs filesystem '/boot' is ext2.
( the default kernel sees this correctly ( VFS: mounting root (resierfs filesystem) ro )
I have been to google and back, I suppose i am missing something but i can't
seem to figure out what.
slackware has no mkinitrd, to create a initrd.img,
I have made sure my core tools are up to date for 2.6.*, i believe
i got them all. gcc, make, binutils, etc.
gcc version 3.2.2
GNU Make 3.80
GNU ld version 2.13.90.0.18 20030121
etc,...
thank you for all you help.
also is there a decent slackware post group somewhere, i haven't
fond one.
-cmus
2.6.* kernel not booting slack VFS: and INIT: fails
