lille, As always, the best way for me to see any problem is the serial console log. Please reboot, log into Debian and execute. ifconfig -a ethtool eth0 And post the entire serial console log up until this point here (the entire serial console log would start at the u-boot banner).by bodhi - Debian
dippes, Boot with the rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 on USB. And post the entire serial console log here (from u-boot banner until it stucks or reset). I'd like to see what happens after this line [ 0.281228] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driverby bodhi - Debian
LWL, > I'm hoping that I > haven't somehow fried the UART on the pogo, but > that would be strange if that was the case with > both of them. It is likey to be working fine since you can see the outputs. Since we cannot see the envs, there is no way to confirm this speculation: it is possible that the stdin env was not set to serial, but the stdout was. > Aby bodhi - uBoot
debi Wrote: ------------------------------------------------------- > Hi bodhi, > > Yes, that did the trick. I've tested it a few > times before saving the modified envs. Until now I > haven't noticed any issues. Many thanks once > again! Maybe your instructions can be added to the > Wiki if someone needs to keep stock OS > functionalities and thereforeby bodhi - Debian
What type of USB drive are you using? USB 2.0, 3.0, model, brand ... lsusb -vvv You could try to recreate the rootfs using a different USB stick. Prefereably USB 2.0, Sandisk brand.by bodhi - Debian
lille, Many lines were jumbled on the right side. Not sure of you have weird characters actually embedded in the envs. For example, Quote> bootcmd_exec=run load_uimage; if run load_initrd; > then if run load_dtb; then boo > > >by bodhi - Debian
lille Wrote: ------------------------------------------------------- > thanks mate. > > here we go again, below info listed from debian > > root@xyz:~# cat /proc/mtd > dev: size erasesize name > mtd0: 00100000 00020000 "uboot" > mtd1: 00080000 00020000 "uboot_env" > mtd2: 00080000 00020000 "key_store" > mtd3: 000800by bodhi - Debian
LWL, > So I thought I would try to interrupt u-boot at > the "Hit any key to stop autoboot:" line but I > can't seem to interrupt the boot no matter what > key I press. I never get the u-boot prompt so I > can't print out the environment variables. > > I have attached a serial connection (soldered to > board) and am using a PL2303HX TTL to USby bodhi - uBoot
Ben, > As long as u-boot can start, I can set the NAS in > rescue mode (pressing a button at boot time) and > acces u-boot with a netconsole. So I could try to > update the parameter. Then you shoud enter this env in netconsole. That way it is only temporary for this boot. After you reset or recycle power, the new value will be gone, and it will be back to the way it was. Youby bodhi - Debian
dippes, This is a strange problem. The behavior as though the DTB was corrupted. We could try to flash the latest u-boot for this box (uboot.2015.10-tld-2) in serial console to see if it helps. But even with new u-boot, it might not boot pass that point.by bodhi - Debian
dippes, Are you root at this point? /media/stick > tar xvjf Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 It you were root, then all the steps look good. If you were not, then redo the above step.by bodhi - Debian
lille, Plug in the USB rootfs, power up, interrupt serial console and do what you did, ie. loading src file to reset the envs, and then, setenv devices 'usb ide' setenv ethaddr 00:00:11:22:33:44 setenv dtb_file '/boot/dts/kirkwood-nsa325.dtb' setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000by bodhi - Debian
lille, QuoteU-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 WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 NSA325> usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Deviby bodhi - Debian
lille, > I have used an usb stick in the meantime > (nevertheless you could provide me with the > commands for SATA if you´ll find the time for > it). I´ve booted debian again. what´s next? Cool! If you can boot with USB rootfs, then it is easier, there is no need to try the SSD yet. Plug in the USB rootfs, power up, interrupt serial console and do what you did, ie.by bodhi - Debian
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