On Mon, 28 May 2007, Emanuele Rocca wrote: > Hi, > there seems to be something wrong with recent changes to hook-functions. > > With initramfs-tools 0.88: > > [EMAIL PROTECTED]:~# LANG=C dpkg-reconfigure linux-image-2.6.22-rc3 > Running depmod. > Finding valid ramdisk creators. > Using mkinitramfs-kpkg to build the ramdisk. > Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird > mkdir: cannot create directory `/tmp/mkinitramfs_FD9659/lib/udev/': File > exists urgs thats due udev hook not using mkdir -p, so that should be harmless. > cp: `/lib/firmware/ql2100_fw.bin' and > `/tmp/mkinitramfs_FD9659/lib/firmware/ql2100_fw.bin' are the same file > cp: `/lib/firmware/ql2200_fw.bin' and > `/tmp/mkinitramfs_FD9659/lib/firmware/ql2200_fw.bin' are the same file > cp: `/lib/firmware/ql2300_fw.bin' and > `/tmp/mkinitramfs_FD9659/lib/firmware/ql2300_fw.bin' are the same file > cp: `/lib/firmware/ql2322_fw.bin' and > `/tmp/mkinitramfs_FD9659/lib/firmware/ql2322_fw.bin' are the same file > cp: `/lib/firmware/ql2400_fw.bin' and > `/tmp/mkinitramfs_FD9659/lib/firmware/ql2400_fw.bin' are the same file
should be harmless too. > > Trying to boot with this initrd the kernel is not able to find the > firmware for my qla2xxx, although a diff -Nur between the contents of > the following two images yields to nothing: could you post the diff? > [EMAIL PROTECTED]:~# ls -l /boot/initrd.img-2.6.22* > -rw-r--r-- 1 root root 5268495 2007-05-28 12:33 /boot/initrd.img-2.6.22-rc3 > -rw-r--r-- 1 root root 5269374 2007-05-27 22:30 > /boot/initrd.img-2.6.22-rc3.bak > > The one suffixed with '.bak' is a working initrd built with 0.87b. > > Albeit it's not the source of this problem, notice the creation of the > local variable "man_x" and the usage of "mam_x" in the script: thanks fixed in git repo. hmm i need more info on that one as i don't have the hardware to reproduce. could you try to run the initramfs without firmware-qlogic installed, does it than boot? -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
