@nibre, Your bootargs looks OK, and other u-boot envs are OK, too. So now it points to your rootfs and the uImage. - Did you recreate the uImage file with embedded DTB? if you did, then restore the orginal uImage from the basic rootfs (it needs to be one without embedded DTB). - If the above was already checked out, then it's better to recreate the basic rootfs from scratch using an Eby bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > ? No takers ? ok I am interested. But no time to collaborate :) please let us know your progress. Fyi, CloudEngines is selling the SafePlug (it's a TOR box) but afaict it's not that safe!by bodhi - Debian
nibre Wrote: ------------------------------------------------------- > For me cat /proc/mtd returns > mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" > mtd1: 00e00000 00020000 "boot" > mtd2: 07200000 00020000 "rootfs" > > So should I change mtd0 in the commands to mtd1? No need to, but if you are running new u-boot then yes. Change it soby bodhi - uBoot
Addy, Oops, typos in the if statements :) But you get the idea? hdd1 and hdd2 were the old settings. Corrected commands should be: Quoteif [ -d /sys/class/leds/nsa325:green:sata1 ]; then echo ide-disk1 > /sys/class/leds/nsa325:green:sata1/trigger fi if [ -d /sys/class/leds/nsa325:green:sata2 ]; then echo ide-disk2 > /sys/class/leds/nsa325:green:sata2/trigger fiby bodhi - Debian
@Peter, Look in your log file var/log/message to see if dhcp re-attempt to connect? if you log to ram then use logread.by bodhi - Debian
@addy, Try execute it at command line: echo default-on > /sys/class/leds/nsa325:green:sata2/trigger echo none > /sys/class/leds/nsa325:green:sata2/trigger Do you see the SATA2 LED light turned on/off with these 2 commands?by bodhi - Debian
@nibre, Usually you will see the message: Quote## Flattened Device Tree blob at 62c00000 Booting using the fdt blob at 0x62c00000 Starting kernel ... This behavior points to your u-boot envs problem, most likely bootargs. Please interrupt netconsole during the count down and get the listing of the envs and post here. > printenvby bodhi - Debian
@nibre, Yes. stock u-boot does not boot USB drive. You'll need to either install new u-boot, or boot with tftp. - For new u-boot see: http://forum.doozan.com/read.php?3,16017 - For tftp booting , see section Updated 29 Oct 2014, kernel installation section B in the first post.by bodhi - Debian
addy75, There was an extra space in the these 2 commands I posted before! (I've modified the post). pls try again: if [ -d /sys/class/leds/nsa325:green:sys ]; then echo default-on > /sys/class/leds/nsa325:green:sys/trigger echo none > /sys/class/leds/nsa325:orange:sys/trigger fi if [ -d /sys/class/leds/nsa325:green:sata1 ]; then echo ide-disk1 >by bodhi - Debian
Hi addy75, > I'm working with kernel 3.17.0-kirkwood-tld-1 and > uboot uboot.2013.10-tld-1. > The system (rootfs) is installed an an ssd, my > data-disk is an 4TB WD Red. > System works goods (little problems with the > mysql-server for owncloud but i will fixit ;-) ) Thanks! these information are very helpful. > I adjusted the settings in rc.local. Yesby bodhi - Debian
@addy75, Are you running the new u-boot, or stock? sounds like you overcame the watchdog while using OMV. It would be helpful to other users if you could briefly describe which u-boot image you are using, which kernel version, and what storage devices you are using (USB, HDD, ...) and where is the rootfs resides (USB or HDD).by bodhi - Debian
addy75, Check your /sys/class/leds, and your settings of the LEDS. Some of the LED names were changed in 3.17 in DTS. # ls /sys/class/leds/ -1 . .. nsa325:green:copy nsa325:green:sata1 nsa325:green:sata2 nsa325:green:sys nsa325:green:usb nsa325:orange:sys nsa325:red:copy nsa325:red:sata1 nsa325:red:sata2 In 3.16 they were set like this: if [ -d /sys/class/leds/nsa325:green:by bodhi - Debian
denexo, Not exactly! loading the kernel uImage/uInitrd and mounting rootfs are 2 different phases in booting. Just so happen that the rootfs is on an Ext4 partition (therefore uImage and uInitrd are on /boot of that partition). 1. uImage and uInitrd loading: instead of ex2tload, use ext4load, see if it behaves differently: ext4load usb 0:1 /boot/uImage ext4load usb 0:1 /boot/uInitrdby bodhi - uBoot
@denexo, > Is it possible to be able to load > Jeff''s rescue system at NAND when no other rootfs > is found? If it helps, i have kept a backup of fw > boot env config prior installing your U-BOOT. What > i mostly want to ask if setting the following boot > envs (as seen at Jeff's script): > > fw_setenv rescue_installed 1 > fw_setenv set_bootaby bodhi - uBoot
Wow! this is the big motha of the zyxel series ;-) dual-core Freescale! http://www.amazon.co.uk/Zyxel-NSA540-Power-Diskless-1-2GHZ/dp/B00O4FMSNOby bodhi - Off-Topic
@denexo, I've double checked the patch! the patch was applied correctly. So we're out of luck until someone else test this change and confirm one way or the other.by bodhi - Debian
@denexo, Let me create the delta patch and confirm that it was good. Among the 3 files in that patch, 2 already in my source tree, so I actualy patched only 1 file.by bodhi - Debian
May I suggest we move this to a new thread, specific about performance? @Shv, please start the new thread with your numbers. I think you had the most info so it would be helpful.by bodhi - Debian
Katsumoto, I don't think u-boot support booting with iScsi. But you can boot the kernel with tftp, providing you can run tftp server on the iscsi NAS. Or boot with nfs if you can run nfs server on that NAS. And I should also add that, if you can set up tftp on the iscsi NAS to boot uImage and uInitrd, then it's possible that the rootfs can be on the iscsi drive. So the end resultby bodhi - uBoot
I think we are talking apple and orange here :)) I am sure Shv meant the local HDD speed: QuoteIf you look at my comparision of device performance at http://pogoplug.cwsurf.de/forum/viewtopic.php?f=4&t=13#p75 you will see that you don't reach the highest possible speed with your Pogoplug E02. Moreover you can see that the Goflex Net device can read data from harddrive with 100MB/s froby bodhi - Debian
shv, > What throughput can be reached > with the Debian Kernel on the Zyxel NSA325v2? > Could it be improved if the same or similar > optimizations are used for the Debian kernel? I'm not sure what optimization done were done on Arch and FreeNAS. Do you have some benchmarks that indicate there are differences in performance between Debian & Arch?by bodhi - Debian
denexo & others, Here is the kernel 3.17.0-oxnas-tld-2, which incorporated the uvc_video patch. Download at dropbox: linux-3.17.0-oxnas-tld-2.bodhi.tar.bz2 md5: eb088226f869206ebad88036018d89cc Please test and let me know.by bodhi - Debian
robert, > I did follow! :) > All them, sequentially! (It was not clear for me) > > Step 3, has sense, (i mean to me) because this > new kernel is ftd. > It is true. Since you installed u-boot first, I can see why you thought it was necessary to do this first :) in any case, the u-boot envs in the kernel thread are the ones to use.by bodhi - Debian
Eike Wrote: ------------------------------------------------------- > Hi bodhi, > > i really don't wanna mess this thread up, but > before flashing to NAND i wanna ensure, that the > following two bad blocks are harmless. Can you > confirm? You never did :) questions and answers are great (as long as not troubleshooting). > root@debian:/# dmesg | grep -iby bodhi - uBoot
bobafetthotmail, > @bodhi: Tried uart booting, but the darn thing > keeps erroring at 94-97% saying "protocol error". > It takes a bit of skill and timing because the box > powers up for a couple seconds, and can begin uart > boot, but then reboots. So I need to time the key > presses to start sending after this "two-second > boot then reboot" momby bodhi - Debian
@robert, Yes. Do this to get back to a default set of ens as described in the u-boot thread: B. Flashing default u-boot envs image And then immediately (without reboot), follow the instruction in the kernel thread (Updated 26 Oct 2014) to setup FDT kernel booting envs: 4a. Boot with DTB file (standard way to boot FDT kernel). Recommended. And you did the wrong thing: you did notby bodhi - Debian
I see what you meant. I think it is a good approach. So to recap: Quote - when booting we disable it - before starting the kernel (bootm xxxx) we re-enable it according to the following env: watchdog_enable = 0 disabled watchdog_enable = 1 enabled I can add this env to u-boot and make it available only to NSA325.by bodhi - Debian
@Peter, It's best to trouble shoot this with netconsole or serial console. However, if you post the log of what you did, usually we can spot a wrong setting some where. Both green and red LED is orange LED. It means that u-boot did not find one of the 3 kernel files that it tried to load (depending how you set the envs). In this case, probaly the envs were not set properly. So check yby bodhi - Debian
@robert, Your u-boot envs seem to be messed up! I can't see where this dt_usb_bootcmd env came from. Are your current u-boot envs different from the listing above? Be careful changing them, you could get locked out netconsole too if the related envs are not set correctly. You could either try to fix it, or switch to USB booting and then fix it in Debian. mkimage is available in the rooby bodhi - Debian
@WarheadsSE, > This might even be best to leave > as the enable/disable via a well documented > environment(!!) command to use with run That's a great idea while u-boot is running! But the problem is once u-boot hand it off to the kernel (starting uImage) we can't run it anymore.by bodhi - Debian