Here's the output of dpkg-reconfigure $ sudo dpkg-reconfigure linux-image-2.6.14-2-k7 Password: Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.14-5 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.14-5 was configured last, according to dpkg) I'm afraid it's not useful at all. But I attach the init shellscript and the initrd tree structure. cu, Thanks for your dedication, Pau A Saturday 17 December 2005 20:53, Sven Luther va escriure: > On Sat, Dec 17, 2005 at 08:25:21PM +0100, Jonas Smedegaard wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Sat, 17 Dec 2005 19:48:49 +0100 > > > > Sven Luther <sven.luther@wanadoo.fr> wrote: > > > > Please tell me how to obtain the installation log you mentioned > > > > earlier. > > > > > > not sure, Jonas will probably give you the exact command to test > > > this, but you could do : > > > > > > dpkg-reconfigure linux-image-2.6.14-2-<your_flavour> > > > > Sounds right. > > > > > and paste the whole output to this bug report. Also, if you could put > > > your /boot/initrd.img-2.6.14-2-<your_flavour> online somewhere that > > > would be helpfull, or list its content, not sure how exactly, but it > > > involves gzip and cpio. > > > > Well, I use mc: > > > > 1) Place the marker on top of your initrd below /boot > > > > 2) ALT+o to get same dir in opposite pane > > > > 3) CTRL+x s to create symlink of the initrd file: > > > > a) Edit symlink name: TAB, END, add ".cpio", ENTER > > > > 4) Move to the cpio-named symlink and press ENTER to browse in it... > > Yeah, but i think a command which can have the output redirected to a file > he can post to the bug report would be more helpfull here: > > Friendly, > > Sven Luther
Attachment:
init.gz
Description: GNU Zip compressed data
Attachment:
tree.out.gz
Description: GNU Zip compressed data