lkml.org 
[lkml]   [2004]   [Dec]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
On a new installation Debian sarge, I had this as my working
bootloader stanza:

title Debian sarge 2.6.8-1-386
root (hd2,0)
kernel /vmlinuz ro root=/dev/sdc1 apm=off
initrd /initrd.img

(pointing to symlink initrd.img@ -> /boot/initrd.img-2.6.8-1-386)

This worked fine until I did an automatic upgrade of all my installed
packages, which seems to have included an upgrade of initrd.img. This
upgrade of packages came with an alert that my bootloader requires
that I add initrd=/initrd.img to the images=/vmlinuz stanza.

I found that the upgrade replaced my
"/boot/initrd.img-2.6.8-1-386" file with a file named
"/boot/initrd.img-2.6.8-1-386.new". Is this a
legitimate name?

More importantly, this new file has zero-length and so naturally
results in a kernel panic:

Cannot open root device 'sdc1' or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

Does it look like the new initrd.img package for 2.6.8 is broken or
simply a flawed installation? Should initrd.img-1-386 file not have
ended with ".new"? What should I do to correct this situation?

Haines Brown

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:08    [W:0.023 / U:0.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site