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
denexo Wrote: ------------------------------------------------------- > @bodhi, > > if it is not a trouble for you, could you please > make a testing 3.17 kernel with the above > mentioned uvcvideo patches? I could try its > working status ;) Sure, I will when I have time to do it!by bodhi - Debian
@Robert, Activate netconsole fw_setenv preboot 'run preboot_nc' Set bootargs fw_setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params'by bodhi - Debian
bobafetthotmail, Yes, with the new pre-release u-boot. It is quite stable now, no long experimental. And with kernel 3.16 tdl-3 only.by bodhi - Debian
Thanks shv, it will come in handy someday!by bodhi - uBoot
@WarheadsSE, Thanks for confirming. Not a watchcat, but this watchdog has nine lives :)by bodhi - Debian
@Robert, Step 4 in the installation: Quote 4. Create uImage and uInitrd and setup for booting. I'm using the GoFlex Net booting with USB drive as an example here. Please replace its name (kirkwood-goflexnet.dtb) with the box you are installing on (for example, kirkwood-pogo_e02.dtb). Look inside /boot/dts/ for the correct DTB file name for your box. ………… 4a. Boot witby bodhi - Debian
@robert, Please refrain from changing the subject of this thread. It's a kernel release thread. The reason your SATA boot failed was because you have not adapted the DTB booting syntax (the instruction is for USB) in to your SATA boot commands. I will respond in detail in your new thread when I have time to post again (if you have not solved it by then).by bodhi - Debian
@bobafetthotmail, > In case you were wondering, I nuked "softdog" > process you pointed out above for addy75. > Blacklisted its kernel module and disabled the > daemon from its config (see here > https://tools.bitfolk.com/wiki/Softdog ). > > No difference. Reboot at around 30-35 sec from > start. Thanks for the info. Good to know this for a fact!by bodhi - Debian
@bobafetthotmail, > I have a nsa325v2 with stock U-boot and set it up > with the 3.16 debian rootfs with the watchdog > fixed. Make sure you run 3.16.0-kirkwood-tld-2 with stock U-Boot. The fix in 3.16.0-kirkwood-tld-3 works with new U-Boot. > > Installed OMV + some plugins that have nothing to > do with watchdogs. > > Now the dumb watchdog kicks in at aroby bodhi - Debian
Update your wget package. http://permalink.gmane.org/gmane.linux.debian.user.security.announce/3224by bodhi - Debian
Rootfs Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 was uploaded. Please see 1st post for download link.by bodhi - Debian
@highsinberg, Do what Almaz has suggested: recreate your rootfs, and reinstall packages. After you've rebuilt your package database like I posted above, all the inconsistency about dpkg/apt database should have been fixed. If the problem comes back like you've experienced above, it indicates that your rootfs is no good. Don't fight it :) you're going to waste your time agaiby bodhi - Debian