maximilian attems schrieb: > is it reproducible? Yes. I updated a bunch of packages, making the slug unbootable. Then I flashed the backup. After a normal boot, I installed initramfs-tools 0.91e, flashed again, which made it boot OK. Then I updated only initrd-tools to 0.92, making it unbootable again.
So generating a broken initrd seems to be well reproducible. I presume that the bad initrd always fails to boot and the good one always boots OK, which was confirmed at least a few times. > if yes please put somewhere the good and the bad initramfs for review. http://www.kevin-price.de/478236/ The one without .bak is the current working one. The .bak one is the last one before that, which must be the broken one. If you have any doubts, I will need do re-flash the .bak one to see if it is really the broken one, tonight. I can see that the broken one is bigger. Might there be a capacity issue in my flash ROM? Here's my /proc/mtd: (good working state) dev: size erasesize name mtd0: 00040000 00020000 "RedBoot" mtd1: 00020000 00020000 "SysConf" mtd2: 00020000 00020000 "Loader" mtd3: 00160000 00020000 "Kernel" mtd4: 00600000 00020000 "Ramdisk" mtd5: 00020000 00020000 "FIS directory" "cat /dev/mtdblock*" produces 8388608 bytes of output. > ok cool so it will be debuggable Yes. Is there a clean way to activate debugging messages in the initrd? So long Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
