On Wed, 26 Sep 2012, Lionel Gamay wrote: > It is quite weird to get this error on two different machines using > different architectures and even while trying two different kernels on > these two machines. Then four different configurations lead to this > message. BTW, you are right: it is "array..." and not "Array..." in > the error message. Another bad manual retyping.
Ok. And yet, I can't reproduce it here with the stock Wheezy stuff, So it depends on the other stuff that is getting installed to your initramfs. > I send you a copy of the initramfs generated on the i386 netbook > running the 3.5-trunk kernel from experimental. Looking at it, at least I can tell it is not broken in an obvious way... Please try this: 0. create a backup of the good initramfs images 1. install the new iucode-tool 2. install the new intel-microcode * at this point your initramfs is likely bad 3. edit /usr/share/initramfs-tools/scripts/init-premount/intel-microcode change the PREREQ="udev" at the top of the script to PREREQ="" 4. run "update-initramfs -u" * at this point, your initramfs is either bad, or fixed 5. make sure the initramfs images for the backup kernel is good, maybe using the backup you made on step 0 above. Reboot and test the new initramfs. If it is broken, use the backup kernel to boot, and purge intel-microcode to fix the initramfs. So, does the PREREQ change fix the issue you had? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
