I'm back to where I was yesterday. I'm able to bootsd from the card image you sent to me. As before with the fs.img from the update.1.8.zip, the first boot has a lot more error messages that look like:
end_request: I/O error, dev mmcblk0, sector 2765263
I wasn't able to reproduce the behavior where the device boots to one of the configurations screens. Each time today, the device stops on the startup screen with 7 squares.
I tried to manually execute the insmod command that was failing:
Code:
# insmod /lib/modules/module.ko pre_format=0
Checking parameters:
Start_block 1318 Length 6874
pMTD_CommonChip=0xc3ea10b4
&pMTD_CommonChip->controller=0xc3ea112c
&pMTD_CommonChip->controller->lock=0xc3ed1ca0
&pMTD_CommonChip->controller->active=0xc3ed1ca0
&pMTD_CommonChip->controller->wq=0xc3ed1ca4
&pMTD_CommonChip->state=0xc3ea1124
Startblock or length must be 8's multiply. Execute auto modify
Startblock 1320 length 6872
flash disk firmware version debug?73 Aug 20 2009
start_block=1320 length=6872 pre_format=0
Init Flash Error !!!
fd_init Done !!!
insmod: can't insert '/lib/modules/module.ko': Operation not permitted
# /bin/mount -t vfat -o iocharset=utf8 /dev/mtdblock6 /mnt/onboard
mount: mounting /dev/mtdblock6 on /mnt/onboard failed: No such device or address
I've attached the output from the 1st and 2nd bootsd attempts after restoring the kernel image.
Do you have any suggestions for flashing fs.img to mtdblock4? The mm technique took 15 hours with my setup. fs.img would take 24 days at that rate.