bodhi, by extracting the file linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2 it does only contain the items below root@image-pc:/media/sdb1# ls config-4.14.1-kirkwood-tld-1 linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2 linux-4.14.1-kirkwood-tld-1.patch linux-dtb-4.14.1-kirkwood-tld-1.tar linux-headers-4.14.1-kirkwood-tld-1_1.0_armel.deb linux-image-4.14.1-kirkwood-tld-1_1.0_armel.deb lost+by lille - Debian
thank you. the rootfs is on the second primary partition root@xyz:/mnt/rootfsnsa# ls -lart insgesamt 96 drwx------ 2 root root 16384 Mai 15 2017 lost+found drwxr-xr-x 5 root root 4096 Mai 19 2017 dev drwxr-xr-x 2 root root 4096 Mai 19 2017 home drwxr-xr-x 2 root root 4096 Mai 19 2017 proc drwxr-xr-x 2 root root 4096 Mai 19 2017 opt drwxr-xr-x 2 root root 4096 Mai 1by lille - uBoot
I have lost my serial connection just before 8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8). the U-Boot was flashed successfully to NSA325> version U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28by lille - uBoot
a simple wget http://projects.doozan.com/uboot/valid-uboot.md5 helped me out LOL lille Wrote: ------------------------------------------------------- > installation of Uboot doesn't work here > > U-Boot 2011.12 (Feb 20 2012 - 21:21:59) > Pogoplug E02 > > SoC: Kirkwood 88F6281_A0 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 1by lille - Debian
installation of Uboot doesn't work here U-Boot 2011.12 (Feb 20 2012 - 21:21:59) Pogoplug E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB If you agree, type 'ok' and press ENTER to continue: ok # checking for /usr/sbin/nandwrite... # checking for /usr/sbin/nanddump... # checking for /usr/sbin/flash_erase... # checking for /by lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > Get a listing of envs in serial console > > > printenv > > > And post the output here, in code tags (it will ge > t truncated if you dont use code tags). bodhi, you´ll find 2 text files attached to this post. one is called booting (with this environment variables itby lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > Has this box booted stock OS successfully right be > fore you've started to set envs to boot both Debia > n and stock? If true, do you have the serial boot > log for stock? > > If not, was this bad block shown since begining or > only recently? > > > Bad blocby lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > Try the revised envs: > > > setenv bootcmd_stock 'setenv mainlineLinux no; set > env bootargs $(bootargs_stock); nand read.e $(load > addr) $(kernel_addr) 0xA00000; bootm $(loadadr)' > setenv bootcmd 'run bootcmd_linux; run bootcmd_sto > ck; reset' >by lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > Sorry that was a typo! > > > setenv bootcmd 'run bootcmd_linux; run bootcmd_sto > ck; reset' > boot > thanks, I´m too stupid to see this immediately ;) now it tries to boot the kernel, but it stops, no ramfs is loaded afterwards Marvell>> setenv bootcmby lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > Interrupt serial console and > > > setenv bootcmd 'bootcmd_linux; bootcmd_stock; rese > t' > boot > does also nothing Hit any key to stop autoboot: 0 Marvell>> setenv bootcmd 'bootcmd_linux; bootcmd_stock; reset' Marvell>> boot Unknownby lille - Debian
bodhi Wrote: ------------------------------------------------------- > There was a typo and I've corrected it above. Thank you for your tremendous support! First of all I had to set the environment variable 'enaMonExt' to 'yes' because if, then & else could not be interpreted Marvell>> setenv bootcmd 'if run bootcmd_linux; then; else bootcmd_sby lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > > > > BTW, I am not willing to install your U-boot, be > ca > > use I want to boot to stock rootfs and your U-bo > ot > > version doesn't allow this until today afaik. > > That's OK. No need to install new u-boot if you st > ill want to boot stock.by lille - Debian
bodhi Wrote: ------------------------------------------------------- > The envs got cut off on the right side. Please rep > ost. It is in my post above, it is only visible by scrolling horizontally within the frame. For a better reading, and not to prolong this thread with never-ending logs, I have copied it for you here: serial console log have a look at the raw paste data aby lille - Debian
▒ __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| **by lille - Debian
bodhi Wrote: ------------------------------------------------------- > Quote1. If you have serial console, > > > > Marvell>> boot > > > And seeing this entore serial boot log I will be a > ble to see if you failed or succcessful booting to > stock OS. thank you for your support! here we go: U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell verby lille - Debian
bodhi Wrote: ------------------------------------------------------- > lille, > > > how can I reset the U-boot env to default state? > > Of course you can. But I need to know what you hav > e on this box. > > 1. If you have serial console, > > - Post the entire serial boot log > - Log into stock OS or Debian and get the output o > f >by lille - Debian
how can I reset the U-boot env to default state?by lille - Debian