benoqkuke, This address needs to be adjusted to boot the 4.14.1 Debian rootfs ramdisk_addr=0x01000000 Most likely, the ramdisk address should be: 0x02100000 Since you are booting with stock u-boot, and don't have serial console, it is dangerous to modify u-boot envs. A wrong setting could make your box semi-bricked until you connect serial console and recover. I cannot guarby bodhi - Debian
feas Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > Ivan > > > > > It is possible that USB drive is not > > sufficiently > > > effective to store the rootfs? > > > > No. That's not the problem. > > > > > > Have yby bodhi - Debian
Ivan > It is possible that USB drive is not sufficiently > effective to store the rootfs? No. That's not the problem. Have you tried: apt-get clean dpkg --clear-avail rm /var/lib/apt/lists/* --force dpkg --configure -aby bodhi - Debian
lille , I'll rewrite it for SATA.by bodhi - Debian
lille Wrote: ------------------------------------------------------- > Thank you so much. I did so many mistakes but they > help me in understanding the U-boot process > better. > > Apologies for asking so many dumb questions. Maybe > I should read more about this embedded linux > booting evironment variables and the memory > technology behind it (mtd) just befoby bodhi - Debian
Here is how to set the default envs in serial console: https://forum.doozan.com/read.php?3,38889,40034#msg-40034 The default envs for uboot.2016.05-tld-1 and uboot.2017.07-tld-1 are very similar. So you can restore the default envs to uboot.2016.05-tld-1 defaults first to allow booting into Debian again, Once you got back to that state, we can see how the default envs image for uboot.201by bodhi - Debian
dippes, Please post the entire log of the terminal session when you create the rootfs usingDebian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2. I think there is something went wrong when you did that. Just copy and paste the terminal log of how you create the partition, and format with ext3, and untar the rootfs tarball. Perhaps I will be able to spot something that was incorrect.by bodhi - Debian
lille, Note that I said QuoteYou can set the bootargs env to boot with systemd perrmanently, It is best to do this in netconsole/serial console. But you did: Quote> fw_setenv set_bootargs 'setenv bootargs > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 $mtdparts init=/bin/systemd' In order to start using fw_setenv, the mtd definition and the /etc/fw_envby bodhi - Debian
lille Wrote: ------------------------------------------------------- > now u-boot doesn't boot into linux anymore. after > powering the nsa325, it got stuck with a u-boot > prompt only > > > U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 > -0700) > ZyXEL NSA325 2-Bay Power Media Server > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB > WARNINGby bodhi - Debian
You can set the bootargs env to boot with systemd perrmanently, It is best to do this in netconsole/serial console.by bodhi - Debian
lille Wrote: ------------------------------------------------------- > 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-dtbby bodhi - Debian
Ben, There is not enough info for me to tell the reason. 1. You are running with stock u-boot? what are the u-boot envs? If you have serial console, then power up and interrupt serial console, and list the envs, and let it boot all the way into Debian. printenv and then boot 2. Which DTB file are you using to boot with? ---- If you have serial console then please post the enby bodhi - Debian
dippes, 1. Use another USB thumb drive and create a new rootfs using Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2. QuoteUpdated 02 Aug 2017: Rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 was uploaded. Basic Debian stretch Oxnas rootfs for Popo Pro/Classic V3 plug: - tarball size: 180M - install size: 477M - Installed packages: nano, avahi, ntp, busybox-syslogd (logby bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,47309,47309#msg-47309by bodhi - Debian
robert1968@gmail.com Wrote: ------------------------------------------------------- > Dear Bodhi, > > Thanks for help when I was in trouble... > > As of now, GoFlex Net is working fine and Im happy > with it. > > > Espressobin in some thread and you also found > promising this board. > > But I m curious what is your opininion now? > &by bodhi - Off-Topic
lille, 2 problems. 1. That's a wrong organization for 2-parttion rootfs. These files must be under /boot of the 1st partition: -rwxr-xr-x 1 root root 3154832 Mai 19 2017 zImage-4.4.0-kirkwood-tld-1 -rw------- 1 root root 3154832 Mai 19 2017 vmlinuz-4.4.0-kirkwood-tld-1 -rw-r--r-- 1 root root 7179935 Mai 19 2017 uInitrd -rw-r--r-- 1 root root 3154896 Mai 19 2017 uImage.orby bodhi - uBoot
dippes, Let's take out the mtdparts. setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr' setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm' bootby bodhi - Debian
Your env settings were messed up, so it does not boot with the basic rootfs 3.17, which has the original uImage in /boot (and the DTB in /boot/dts). Power up, interrupt serial console and setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=41000000.nand:14m(boot),-(data) earlyprintk=serial' setenv dt_bootm 'bootm $uimage_by bodhi - Debian
lille, Your rootfs on SSD is not good. So, to see why and fix the problem, mount it on another Linux box. And assuming it is mounted at /media/sdb1 cd /media/sdb1 ls -lart cd /media/sdb1/boot ls -lart And please post the output here.by bodhi - uBoot
robert1968@gmail.com Wrote: > So I changed to an "original chines" power supply. > It is 5A written on it. probably can provide 1-2 > A. :) That's even better.by bodhi - Off-Topic
Last post moved here: https://forum.doozan.com/read.php?3,47169,47169#msg-47169by bodhi - uBoot
An important reminder: this MVEBU series is affected by the Spectre bug. So be careful until I can release new kernel: https://forum.doozan.com/read.php?2,18483,47114#msg-47114by bodhi - Debian
> Perhaps speculation wasn't even a glint in arms > eye back then ;) Right :)by bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > From all the information I've been reading it > appears that what is being called Meltdown only > affects Intel and a few as yet rare ARM 64 chips. > The Spectre issue is more widespread but shouldn't > affect any of the ARM5 chips, so Kirkwood won't be > affected. > > Raby bodhi - Debian
> The whole thing is > very poor quality. I think they re-used > code/designs from other products and shipped it as > soon as it worked stable enough to not annoy > customers too much. Zyxel, Seagate, Cloudengine FW are also of poor quality. But WD FW is probably the worst.by bodhi - Off-Topic
habibie Wrote: ------------------------------------------------------- > If you wanna save $$$, a > $10 > Pogoplug Pro may not be a bad choice at all. No, only 128MB RAM.by bodhi - Off-Topic
dippes Wrote: ------------------------------------------------------- > I have tried other Stick but it boots up to this > point and then it breaks up. See the attachment > below. > > > \0x08\0x08\0x08 7 \0x08\0x08\0x08 6 > \0x08\0x08\0x08 5 \0x08\0x08\0x08 4 > \0x08\0x08\0x08 3 \0x08\0x08\0x08 2 > \0x08\0x08\0x08 1 \0x08\0x08\0x08 0 > (Re)start USB...by bodhi - Debian
Robert, NSA325 (2 SATA 512MB RAM). This box price had recently been reduced to under 100 USD. NSA310S (1 SATA 256MB RAM). Not bad if NSA325 is too expensive. But a little slower than the NSA325. Dreamplug (1 eSATA 512MB RAM). Least expensive, but not sure if you can get it in EU.by bodhi - Off-Topic
hmartin Wrote: ------------------------------------------------------- > It has just been revealed that there are numerous, > serious vulnerabilities and a backdoor present in > the stock firmware from Western Digital: > http://gulftech.org/advisories/WDMyCloud%20Multiple%20Vulnerabilities/125 > > These vulnerabilities affect all WD MyCloud > products running the Wesby bodhi - Debian
dippes Wrote: ------------------------------------------------------- > Sorry it was my failure > > > dippest-VirtualBox rootfs # ls -l > insgesamt 84884 > drwxr-xr-x 2 root root 4096 Nov 1 2014 > bin > drwxr-xr-x 3 root root 4096 Nov 1 2014 > boot > -rwxrwx--- 1 root vboxsf 86736625 Jan 3 19:00 > Debian-3.17.0-oxnas-tld-1-rootfs-by bodhi - Debian