Hi Bodhi! QuoteI would suggest runing Debian permanently on USB rootfs or SATA rootfs. Use this box to learn Linux. Yes, this is my decision. I cannot use the standard OS (support ended) I will try to configure samba Thank you very much for your advices!by Oleg - Debian
Hit any key to stop autoboot: 0 Marvell>> setenv bootcmd_stock 'nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000' Marvell>> setenv bootcmd_usb 'echo Booting Debian ...; usb start; run usb_bootcmd; usb stop' Marvell>> setenv bootcmd 'run bootcmd_usb; run bootcmd_stock; reset' Marvell>> bby Oleg - Debian
Quotebodhi setenv bootcmd_stock 'echo Booting Stock ...; nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000" ** Too many args (max. 16) ** if I do so setenv bootcmd_stock 'echo Booting Stock ...; nand read.e 0x800000 0x100000 0x300000 setenv bootargs $(console) $(bootargs_root); bootm 0x800000" Bad Magic Number in aby Oleg - Debian
Hi Bodhi! Quote Do you have serial console on this 2nd box? If you do then it boot up with serial console, interrupt u-boot at count down, and get the envs listing: printenv Yes of course https://forum.doozan.com/read.php?2,112609,113099#msg-113099 log printenv original firmware ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Oct 12 2009 - 13:41:53) Marvell version: 3.4.16by Oleg - Debian
Hi Bodhi! report Quotebodhi I meant log in to stock OS root@192.168.10.250's password: -bash-3.2# blparam -bash: blparam: command not found -bash-3.2# find /usr -name '*blparam*' -bash-3.2# -bash-3.2# find -name '*blparam*' -bash-3.2# Quote Did you install Debian on the 2nd box, too? the original firmware remains in the attachment the contents of the /by Oleg - Debian
Hi Bodhi! I completed the task what is the next step? Quotebodhi Log into the 2nd Verbatim box, and run blparam root@debian:~# blparam -bash: blparam: command not found root@debian:~# find /usr -name '*blparam*' root@debian:~# log printenv original firmware ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Oct 12 2009 - 13:41:53) Marvell version: 3.4.16 U-Boot codeby Oleg - Debian
bodhi Wrote: ------------------------------------------------------- ... > The 1st envs listing should be the original stock > definition. I didn't do it ((( but QuoteI have two Verbatim MediaShare 1TB (47490) № 1 works on original firmware Will the envs listing in this box work? > > And the current fw_env.config in the rootfs cannot > be used. So I will nby Oleg - Debian
Bodhi, Did I do the right thing? Quotebodhi There is one more thing to do: set up the /etc/fw_env.config file so that you can read/write u-boot envs while in Debian. root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 Before loading ** MARVELL BOARD: DB-88F6281A-by Oleg - Debian
Thanks for the help! What else do I need to do? Your opinion P.S. how to return to boot from NAND?by Oleg - Debian
bodhi Wrote: ------------------------------------------------------- > Oleg, > > > U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:38:05 > > -0700) > > Netgear Stora MS2110 > > > > SoC: Kirkwood 88F6281_A1 > > DRAM: > > Yes, RAM is the first thing to hang u-boot when > the memory size is incorrect. > > But the good news is UARTby Oleg - Debian
How after setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd' setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000' setenv usb_by Oleg - Debian
daviddyer Wrote: ------------------------------------------------------- > Try kwboot with your mtd0 image. > > ./kwboot -t -B 115200 /dev/ttyUSB0 -b > verbatim_mtd0.img -p > > If it can work, at least we can confirm we have an > easy way to recover the box if we accidentally do > something wrong. Everything is fine! root@xubuntu-System-Product-Name:by Oleg - Debian
Yes of course I'll try daviddyer wrote pogo e02 has no sata, I guess stora's dtb should be better. is it not important to uвoot ? I wrote above I have two Verbatim MediaShare 1TB (47490) № 1 works on stock firmware it can be accessed via SSH can an file "verbatim_mtd0.img" help? bodhi what do you think? I speak clearly? Google translator (by Oleg - Debian
Something went wrong... root@xubuntu-System-Product-Name:/home/xubuntu/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 1 % [..............................................................by Oleg - Debian
Topic title scares me :) Bricked NSA320S during 2017.07 flash https://forum.doozan.com/read.php?3,51739,51919#msg-51919 But I'll tryby Oleg - Debian
Thank you bodhi! think my NAND is 256MB but this is not enough... Quotedaviddyer Maybe you can try to kwboot with stora's uboot. Bodhi's modern uboot is much better than stock one. https://forum.doozan.com/read.php?3,12381 is not mine Verbatim MediaShare which one to use? log printenv: ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (Oct 12 2009 - 13:41:53) Marvby Oleg - Debian
Do I need to transfer the download to NAND?by Oleg - Debian
daviddyer Wrote: ------------------------------------------------------- > Looks great. > > Maybe you can try to kwboot with stora's uboot. > Bodhi's modern uboot is much better than stock > one. Thank you I am satisfied dts kirkwood-pogo_e02.dtb need to try?by Oleg - Debian
bodhi Wrote: ------------------------------------------------------- > Oleg, > Those envs settings were not very good. > This is a better example I wrote (I forgot to add > to the Wiki, will do so): > Boot > Kirkwood rootfs with stock u-boot I used dts kirkwood-netgear_stora_ms2000.dtb This is victory? dts kirkwood-pogo_e02.dtb need to try? __ __by Oleg - Debian
At this step "It turned out to run Debian Wheezy for Netgear Stora according to this article https://github.com/kirov/stora-debian-install/blob/master/README.md" I gave commands setenv mainlineLinux yes setenv arcNumber 2743 setenv bootcmd_usb 'usb reset; ext2load usb 0 0x200000 /boot/uImage; ext2load usb 0 0x800000 /boot/uInitrd' setenv bootcmd 'setenv bootargby Oleg - Debian
bodhi Wrote: ------------------------------------------------------- ... > Generate the uImage with DTB embedded inside: > cd /media/sdb1/boot > cp -a zImage-5.2.9-kirkwood-tld-1 zImage.fdt > cat dts/kirkwood-netgear_stora_ms2000.dtb >> > zImage.fdt > mv uImage uImage.orig > mkimage -A arm -O linux -T kernel -C none -a > 0x00008000 -e 0x00008000 -n >by Oleg - Debian
bodhi Wrote: ------------------------------------------------------- > Oleg, > > This is a Kirkwood box. So it is easy to run > Debian on it. If you like to do that (instead of > restoring stock OS), then do the steps below. > > ===== > > 1. Create a new Debian rootfs on USB: > > Using > Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > frby Oleg - Debian
Thanks for the quick response! I read this forum and tried instruction https://forum.doozan.com/read.php?2,12096 this step is not mine Verbatim MediaShare QuotePlease replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name). which DTB to use? P.S. It turned out to run Debian Wheezby Oleg - Debian
I welcome everyone! Trying to revive Verbatim MediaShare 1TB (47490) Info I have two Verbatim MediaShare 1TB (47490) № 1 works on stock firmware it can be accessed via SSH (user_hipserv2_verbatim_VBMR-HRCW-XXXX-XXXX@192.168.XXX.XXX № 2 blocked (no access to myverbatim.com) there is a serial cable I will be glad to receive your instructions step by step P.S. I don't know Liby Oleg - Debian