my linux is dead after install kernel 2.6.11.11 , can't boot up.

[roadorange]

During the boot up process, it has this error:
RAMDISK: COmpressed image found at block 0
red hat nash version 3.5.13 starting
Loading ext3.ko module
insmod: QM_Modules

Error:/sbin/insmod exited abnormally
mount /proc/filesystem
creating block devices
creating root devices
creating root filesystem
mount: error 19 mounting ext3

Pivot root: pivot_root(/sysroot,/sysroot/initrd)failed: 2
umount /initrd/proc failed:2
free unused kernel memory: 240k freed
kernel panic- not syncing: no init found. Try passing init=option to kernel

i am using Red Hat Enterprise Linux3

here how i compile and install kernel

make gconfig 'config and save, i acutally didn't really config it. lol
make dep
make clean
make bzImage
make modules
make module_install
make install

these above processes are all good

#pwd
/usr/src/linux-2.6.11.11
mv arch/i386/boot/bzImage /boot/bzImage-2.6.11.11
cd /boot
rm System.map
ln -s System.map-2.6.11.11 System.map

then i read the book , it ask to configure my /etc/grub.conf
i use vi command and check . opos. it's already configure by itself. weirddddddddddddddddddd
here's the grub.conf file:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,5)
# kernel /vmlinuz-version ro root=/dev/hda7
# initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=10
splashimage=(hd0,5)/grub/splash.xpm.gz
title Red Hat Enterprise Linux AS (2.6.11.11)
root (hd0,5)
kernel /vmlinuz-2.6.11.11 ro root=LABEL=/
initrd /initrd-2.6.11.11.img
title Red Hat Enterprise Linux AS (2.4.21-4.EL)
root (hd0,5)
kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/
initrd /initrd-2.4.21-4.EL.img
title Windows Family
rootnoverify (hd0,0)
chainloader +1

i didn't edit or touch this file, the following configuration are automatically added by itself:
title Red Hat Enterprise Linux AS (2.6.11.11)
root (hd0,5)
kernel /vmlinuz-2.6.11.11 ro root=LABEL=/
initrd /initrd-2.6.11.11.img

i saw looks good, then i reboot and linux dies.

what should i do?
the last page of the book discuss moduel RAM disk. i skip it @_@""
i wasn't quiet understand
the book example is :
#mkinitrd /boot/initrd-2.4.22-1.img 2.4.22-1

do i need to type the following?
#mkinitrd /boot/initrd-2.6.11.11.img

how do i reboot into my linux and modify it?
b4 i upgrade kernel, i save boot image using:
mkbootdisk --iso --device myimage.iso 2.4.22-1
i save myimage.iso in my window hard drive.

[je_fro]

you need to make that initrd...

Do you have
/boot/initrd-2.6.11.11.img
?

[mrBen]

Also, what were you upgrading from? If it was a 2.4 kernel, then did you install the new modutils? If not, then this is probably why insmod exited 'abnormally' at the top of your output....

[roadorange]

Originally posted by mrBen
Also, what were you upgrading from? If it was a 2.4 kernel, then did you install the new modutils? If not, then this is probably why insmod exited 'abnormally' at the top of your output....

ya. the RHEL3 kernel is 2.4

i did this command after the first failed of booting 2.6.11.11
#mkinitrd /boot/initrd-2.6.11.11.img 2.6.11.11

then it said initrd-2.6.11.11.img is already exist

i didn't install modutils. i go find it and install it.

[mrBen]

Originally posted by roadorange
i didn't install modutils. i go find it and install it.

Ah - that could well be your problem - without the new modutils the kernel will not be able to load any modules. Which is a problem ;)

[bwkaz]

Any error from insmod that mentions QM_MODULES is an ENORMOUS red flag that says "this person needs to install the new modutils!" ;)

It's not called modutils anymore, though. It's now called module-init-tools. Grab the latest stable version from here:

http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/

(Looks like the latest stable is either 3.0 or 3.1.)

Originally posted by roadorange
make gconfig 'config and save, i acutally didn't really config it. lol
make dep
make clean
make bzImage
make modules
make module_install
make install You don't need to do most of those anymore. All you need to do is:

make gconfig
make
make modules_install
cp arch/i386/boot/bzImage /boot/whatever-you-want-to-call-it

Or, replace the last two with "make install".

You have to be root for the last one or two (make install or make modules_install, plus everything after that), but not for the others. (Unless you extracted the kernel sources to somewhere that only root has write permission... in which case you may want to rethink how you do kernel compiles. ;))

[je_fro]

chown -R je_fro:users /usr/src/linux

[roadorange]

Originally posted by bwkaz
Any error from insmod that mentions QM_MODULES is an ENORMOUS red flag that says "this person needs to install the new modutils!" ;)

It's not called modutils anymore, though. It's now called module-init-tools. Grab the latest stable version from here:

http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/

(Looks like the latest stable is either 3.0 or 3.1.)

You don't need to do most of those anymore. All you need to do is:

make gconfig
make
make modules_install
cp arch/i386/boot/bzImage /boot/whatever-you-want-to-call-it

Or, replace the last two with "make install".

You have to be root for the last one or two (make install or make modules_install, plus everything after that), but not for the others. (Unless you extracted the kernel sources to somewhere that only root has write permission... in which case you may want to rethink how you do kernel compiles. ;))

nice link. i downloaded the patch-modutils something. it's not the file i need.
the link u gave me is probably what i need. i am still fixing it.
so now, all i need to do is install the thing, then i will reboot it.

thanks

[roadorange]

Originally posted by je_fro
you need to make that initrd...

Do you have
/boot/initrd-2.6.11.11.img
?
ya. the file is already exist by itself there.

[bwkaz]

Originally posted by je_fro
chown -R je_fro:users /usr/src/linux (I just do the compilation in my home directory. It's not like that breaks anything. ;))

[roadorange]

hi. my linux kernel doesn't fix.
i download moudle-init-tool source
then i install it using :
configure
make
make install
(then i think: i better read instruction b4 doing anything, i open readme file and read)

haha. i start over and i do:
configure
make links ( or link)
make
make install
depmod 2.6.11.11

and reboot the kernel 2.6.11.11 and failed
am i doing right from above command?

do i need to recompile and reinstall the kernel after installing the module-init-tool??? because it takes 4 hours to install new kernel, that's why i want to ask before i recompile them again, it takes long time.

since i did those above commands, i doubt if i can boot my 2.4 kernel.
LOL>.............................................
LOL>

[bwkaz]

Originally posted by roadorange
and reboot the kernel 2.6.11.11 and failed With the same error?

[roadorange]

Originally posted by bwkaz
With the same error?
same error .yes
i just doube whether i install module-init-tool correctly.
i am also not sure if i need to recompile and reinstall the kernel after i installed module-init-tool.

i get same error after i stalled module-init-tool.
1). do i really need to recompile and reinstall kernel 2.6.11.11?
2). do i install module-init-tool correctly???

[bwkaz]

Originally posted by roadorange
same error .yes
i just doube whether i install module-init-tool correctly.
i am also not sure if i need to recompile and reinstall the kernel after i installed module-init-tool.

i get same error after i stalled module-init-tool.
1). do i really need to recompile and reinstall kernel 2.6.11.11?
2). do i install module-init-tool correctly??? 1) I don't think that's necessary, no.

2) I don't think so, but I'm not sure how to undo what you've already done.

First, you need to add --prefix=/ to your ./configure line. This will make it put insmod into /sbin instead of /usr/local/sbin (the default). Actually, this is probably the entire reason it's not working, right here -- the shell finds insmod in /bin or /sbin first, and doesn't get to search /usr/local/sbin. But the version in /bin or /sbin is still the modutils version.

Try this to be sure:

insmod --version
/sbin/insmod --version
/bin/insmod --version
/usr/local/sbin/insmod --version

Post what all of those say. One should say "no such file or directory". I am guessing that two will say something about modutils, and only the last one will say something about module-init-tools. If so, then that's definitely the problem.

But second, you need to change the way you build module-init-tools, too. It should go like this:

./configure --prefix=/
make moveold # ONLY RUN THIS ONCE EVER!!!!
make
make install
./generate-modprobe.conf /etc/modprobe.conf You need to make moveold to rename your current modutils binaries to modprobe.old, insmod.old, depmod.old, etc. The module-init-tools version will test the current kernel, and if it's before 2.5.whatever, it'll run modprobe.old, insmod.old, etc. Otherwise, it'll continue.

The reason you have to only run "make moveold" once is that the first time you run it, it'll be moving modutils binaries. The second time you run it, it'll overwrite the modutils version with the module-init-tools version that you'll be installing in a minute. That will prevent you from booting any 2.4 kernels at all.

Then, you do the standard make, make install.

Then, you make a modprobe.conf file based on your current modutils configuration. The config file has changed, so the module-init-tools package comes with a utility to generate the new syntax file. You should only run this once too.

From the README, it looks like "make links" is only used if you install it into /usr/local -- but if you do that, then your system bootscripts won't be able to use it unless they specifically go looking for it. That's what's causing your problems now, I think.

[roadorange]

i followed these commands:
./configure --prefix=/
make moveold # ONLY RUN THIS ONCE EVER!!!!
make
make install
./generate-modprobe.conf /etc/modprobe.conf


but lastly:

[root@localhost module-init-tools-3.1]# ./generate-modprobe.conf /etc/modprobe.conf
Warning: not translating path[updates]=/lib/modules/updates
Warning: not translating path[unsupported]=/lib/modules/unsupported
[root@localhost module-init-tools-3.1]#

i reboot 2.6.11.11 linux and fail.

[roadorange]

oh. my linux kernel is fixed. thanks for the help
i recreate initrd-2.6.11.11.img file. o^-^o
it works now.
thanks for the help. bwkaz

bwakaz, you are expert. ^^

when linux kernel 2.6.11.11 is botting, the USB is failed to boot and ithe kernel doesn't bring up my NIC too. ALthought i didn't configure much the kernel before i install it, i thought the default setting of configuation will choose the basic stuff for me. I only change the processsor to PIII. the rest i leave them by default.

when the kernel boots, it pop up a mssege box to ask me : keep configuration, remove configuration, and Do nothing.

I choose "do nothing" because if i choose remove existing driver, it might also affect the configuration in 2.4 = ="

[bwkaz]

Originally posted by roadorange
when linux kernel 2.6.11.11 is botting, the USB is failed to boot and ithe kernel doesn't bring up my NIC too. ALthought i didn't configure much the kernel before i install it, i thought the default setting of configuation will choose the basic stuff for me. Well, no, the defaults aren't autodetected from your system. The defaults are the same for everybody. You probably should have a couple terminals running, one inside "make menuconfig" on 2.6, and one with a text editor on the 2.4 .config file. Look up the 2.4 kernel's settings for just the stuff you don't know about (but leave ACPI / APIC / UP-APIC / IO-APIC all turned on).

But if you have a .config file from kernel 2.4, it may not work to use it either -- early 2.6 kernels broke when you tried to use .config files from 2.4 on them. (They'd compile just fine, but when you booted them you'd just get a black screen.) I don't know if this is fixed now or not.

What you should probably do is build everything as a module (as much as possible, anyway). This way, the drivers you need are only a modprobe away once you get a shell going. You may have to figure out what to modprobe, but at least it'll be possible.

when the kernel boots, it pop up a mssege box to ask me : keep configuration, remove configuration, and Do nothing. Well, I think that's actually Red Hat's configuration program. You're probably right in saying "do nothing", but I don't know that for sure (don't use Red Hat).

[silverdrgn]

http://www.justlinux.com/forum/showthread.php?p=817684#post817684



please help!!! having major issues with new kernel install.