Hi bodhi, I saved envs. It's been running few days and it's stable. Thanks again for all your help. codierby codier - Debian
Hi bodhi, Got it. Since there is an issue to boot into stock so I will not saveenv to save it permanently for now. I tried to power off and start it by follow your instruction and it still didn't work I tested without setting any new envs so I run bootcmd instead of bootcmd_stock since they are the same. We test it before and it was able to boot into stock. __ __by codier - Debian
Hi bodhi, It didn't work. Just want to clearify something first. From your post "And then you should boot back to serial console, save the stock bootcmd" do you mean? setenv bootcmd_stock 'ide reset; ide read 0x40000 0x800 0x1800; ide read 0x900000 0x2000 0x1800; setenv bootargs $(console) $(bootargs_root) $(bootargs_mtd) $(bootargs_end); bootm 0x40000 0x900000;by codier - Debian
Hi bodhi, Ah.. nvm. I think it's because I formatted both hard drives in OMV. Since stock U-boot was saved from the hard disk so it won't boot from stock anymore. Do you have any idea that if I can use the 1MB flash as the stock u-boot? Thanks codierby codier - Debian
Hi bodhi, I tried the new envs and it worked great for USB debian but didn't work for stock. Marvell>> setenv bootcmd_stock 'ide reset; ide read 0x40000 0x800 0x1800; ide read 0x900000 0x2000 0x1800; setenv bootargs $(console) $(bootargs_root) $(bootargs_mtd) $(bootargs_end); bootm 0x40000 0x900000;run bootcmd2' Marvell>> setenv bootargs_mtd_debian 'mtdparby codier - Debian
Hi bodhi, Great. Thanks for all your help. by the way, could you show me how to backup mtds? And should I saveenv before or after the backup? codierby codier - Debian
Hi bodhi, I've changed it but I don't know if this is what supposed to see but it seems different than what we modified on console end. root@omv:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0 0x1000 0x1000 /dev/mtd2 0x0 0x1000 0x1000 root@omv:~# fw_printenv baudrate=115200 loads_echoby codier - Debian
Hi bodhi, fw_env.config doesn't show mtd1 nor mtd2 only mtd0. root@omv:~# cat /proc/mtd dev: size erasesize name mtd0: 0007e000 00001000 "u-boot" mtd1: 00001000 00001000 "env" mtd2: 00001000 00001000 "env2" root@omv:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /deby codier - Debian
Hi bodhi, It's still the same. Marvell>> setenv bootargs_mtd 'mtdparts=spi0.0:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2)' Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $(bootargs_mtd) earlyprintk=serial init=/bin/systemd' Marvell>> setenv load_uimage 'ext2load usb 0:by codier - Debian
Hi bodhi, I was thinking it might be the typo. haha I've updated the kernel but unfortunately problem still exist. Please see the boot log. 3 MTD partitions seems good now but I still have bad CRC warning when access fw_printenv. Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $(bootargs_mtd) earlyprintk=serial iniby codier - Debian
Hi bodhi, Can mvebu and kirkwood kernel interchangable? I am currently using kirkwood 5.2.9. Thanks Codierby codier - Debian
Hi bodhi, Thanks for the information. I have no knowledge for UART booting so I think I will just stick with the current env. I will wait for your next kernel, finalize the env and then save it after then. Codierby codier - Debian
I just read all threads. So we stopped because we can not stop the booting process?by codier - Off-Topic
Thanks Bodhi, everything is working great. Just want to confirm if I saved those envs as long as I serial cable connection then I could rescue it anytime if those envs messed up. Codierby codier - Debian
Hi Bodhi, Got ya. I found an problem in my ix2-ng as there is always an extra USB device being detected. I have no clue what is this extra USB device. When I insert the Uboot USB there shows totally 2 USB devices. This way works for booting up the USB uboot. Below is the success boot log Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootby codier - Debian
Strange. I use the same USB drive but with different set of variables. Maybe it's the coincidence. I changed to a new USB and confirmed the new envs are working. Should I regenerate the uInitrd boot file everytime if I see the following message? update-initramfs: Generating /boot/initrd.img-5.2.9-kirkwood-tld-1 Thanks Codierby codier - Debian
Hi Bodhi, The new set of envs didn't work. Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $(bootargs_mtd) earlyprintk=serial init=/bin/systemd' Marvell>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' Marvell>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrdby codier - Debian
Hi Bodhi, The systemd was working on my system so I think the guide is still valid. It stopped working after I installed OMV5 (Since your debian version is Buster now and only OMV5 can be installed). My USB is newly built so there is nothing. basically I will start from beginning and I will redo the steps to see if there is anything wrong. Just want to know if I am safe to saveenv for tby codier - Debian
Hi Bodhi, According to my situation root@debian:/media/omv5# fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/bin/systemd' Warning: Bad CRC, using default environment Can I set it via serial by using following? then just boot it to test? setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts inby codier - Debian
Hi Bodhi, Is there another way to set boot with systemd before your patch? Thanks Codierby codier - Debian
Sounds good. Thanks Bodhi. This is a nice lesson and I have learned alot.by codier - Debian
It does. root@ix2:/# cat /etc/fw_env.config /dev/mtd1 0x0 0x1000 0x1000 /dev/mtd2 0x0 0x1000 0x1000 root@ix2:/# fw_printenv baudrate=115200 loads_echo=0 rootpath=/srv/ubuntu netmask=255.255.255.0 run_diag=yes MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(iby codier - Debian
Hi Bodhi, 64k not working. root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0x7f000 0x1000 0x10000 root@debian:~# fw_printenv Environment does not start on (erase) block boundary Yes. I can boot into stock. Below is the dmesg Linux version 2.6.31.8 (soho@bsoho080.iomegacorp.com) (gcby codier - Debian
Hi Bodhi, Still the same. Marvell>> printenv baudrate=115200 loads_echo=0 rootpath=/srv/ubuntu netmask=255.255.255.0 run_diag=yes MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000by codier - Debian
Hi Bodhi, It's still the same. env baudrate=115200 loads_echo=0 rootpath=/srv/ubuntu netmask=255.255.255.0 run_diag=yes MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; lcd0_by codier - Debian
Hi Bodhi, I have no clue how to redefine the mtdparts and fw_env.config with my poor linux knowledge >_<. Codierby codier - Debian
Hi bodhi, Is it because the flash is too small? my ix2-ng has only 1MB flash versus ix2-dl has 1GB. ix2-dl has already been digged into it. At least I saw few posts regarding to this model. Codierby codier - Debian
Hi Bodhi, Please see the boot log. Marvell>> printenv baudrate=115200 loads_echo=0 rootpath=/srv/ubuntu netmask=255.255.255.0 run_diag=yes MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); booby codier - Debian
Hi Bodhi, Still no luck. None of them works. Marvell>> printenv baudrate=115200 loads_echo=0 rootpath=/srv/ubuntu netmask=255.255.255.0 run_diag=yes MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneCoby codier - Debian
Hi jdwl101, Thanks for your hints. It gave me something new now. root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x20000 0x20000 /dev/mtd2 0x0000 0x20000 0x20000 root@debian:~# fw_printenv Read error on /dev/mtd1: Success By the way, I remember I saw your post before and I thinby codier - Debian