Problem with kernel update - solved
Hi again, thanks to the help of Jonathan Shipley I could solve the problem! It seems that it had not anything to do with the old version of the initrd-tools I used. The problem came from the file '/etc/mkinitrd/modules' which was completely empty in my case (except of some comment lines). Here is the solution from Jonathan: If you have an ext3 filesystem then you may need to create a new initrd.img with some additional drivers. You will then be able to mount the root filesystem and proceed as usual. I have these 3 lines in /etc/mkinitrd/modules jbd ext3 ext2 You should also have a line (amongst others) in /etc/mkinitrd/mkinitrd.conf # What modules to install. MODULES=dep This means that when you (this is the bit coming up...) try and make the initrd.img it will try and work out what modules to install in the img file. You can change this if needed, but it works for me. See mkinitrd.conf's man page. Now, to create a new initrd.img file you can do something like this: mkinitrd -o /boot/initrd.img-2.4.20-586tsc-test /lib/modules/2.4.20-586tsc/ You should now see perhaps a slightly larger file than before, because of the new modules included in the image. You should update your symlink /initrd.img to point to this file and not the default. I also have a initrd.img.old for the backup kernel, in case this one does not work. If you want to see if that they are really there, then: cramfsck -v -x /tmp/foo /boot/initrd.img-2.4.20-586tsc-test will uncompress the img file to /tmp/foo. You can now re-run lilo and give the new kernel a shot. Thanks alot for the help!! Now my kernel boots up nicely! Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with kernel update
Hi there again, --On Wednesday, February 26, 2003 07:44:48 PM +1100 Herbert Xu <[EMAIL PROTECTED]> wrote: On Wed, Feb 26, 2003 at 09:27:17AM +0100, Harry Brueckner wrote: My initrd-tools are version 0.1.37 which seems to be the most current version. Any other ideas? If you go to packages.debian.org/initrd-tools you'll find that the latest version is 0.1.38. Hmmm, seems like my mirror was a little old. I upgraded to 0.1.38 and now it does not loop but doesn't find any module either and stops with a kernel panic when it tries to kill init. :-/ I guess I have to compile my own kernel since the distributed package seems unusable somehow. :-/ Thanks for your help anyway! :-) Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with kernel update
On Wed, Feb 26, 2003 at 09:27:17AM +0100, Harry Brueckner wrote:
>
> My initrd-tools are version 0.1.37 which seems to be the most current
> version.
>
> Any other ideas?
If you go to packages.debian.org/initrd-tools you'll find that the
latest version is 0.1.38.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with kernel update
Hi there, --On Wednesday, February 26, 2003 07:46:33 AM +1100 Herbert Xu <[EMAIL PROTECTED]> wrote: Any idea what could be wrong? I found several postings about this problem but not a single useful reply to them. :-/ Upgrade your initrd-tools package and reinstall kernel-image. I removed the package, checked the version of my initrd package and installed the kernel again. The result is the very same - it hangs in an endless loop where it tries to load some modules. :-( My initrd-tools are version 0.1.37 which seems to be the most current version. Any other ideas? Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with kernel update
Harry Brueckner , Harry Brueckner <[EMAIL PROTECTED]> wrote:
>
> Any idea what could be wrong? I found several postings about this problem
> but not a single useful reply to them. :-/
Upgrade your initrd-tools package and reinstall kernel-image.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem with kernel update
Hello, I am fairly new to Debian (not to Linux though) and run into a problem with the kernel update. I installed the system from a woody CD-ROM and then upgraded the system to the current 'unstable' release. So far everything went just fine. Then I wanted to upgrade the kernel from 2.2.20 to the current 2.4.20 version where I wanted to use the 2.4.20-586tsc version. I installed the package using 'apt-get install kernel-image-2.4.20-586tsc' which also produced no error or any other problem. I modified /etc/lilo.conf and added the required initrd=... line. I also run 'lilo' a couple of times to check if anything goes wrong there but it works fine too. After rebooting the machine it runs into an endless loop, complaining that it is unable to insmod some modules. The output looks like this: [...] VFS: Mounted root (cramfs filesystem). Freeing unused kernel memory: 88k freed warning: can't open /etc/mtab: No such file or directory insmod: /lib/modules/2.4.20-586tsc/kernel/drivers/ide/ide-mod.o: No such file or directory insmod: insmod ide-probe-mod failed insmod: /lib/modules/2.4.20-586tsc/kernel/drivers/ide/ide-mod.o: No such file or directory insmod: insmod ide-disk failed kmod: runaway modprobe loop assumed and stopped insmod: insmod: /lib/modules/2.4.20-586tsc/kernel/net/unix/unix.o: No such file or directory kmod: runaway modprobe loop assumed and stopped insmod: insmod: insmod net-pf-1 failed insmod: insmod: /lib/modules/2.4.20-586tsc/kernel/net/unix/unix.o: No such file or directory kmod: runaway modprobe loop assumed and stopped [the insmod messages repeat endlessly] Any idea what could be wrong? I found several postings about this problem but not a single useful reply to them. :-/ Thanks for your help in advance. Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
