monkmandolins, I don't use VAMP so can't give you specific advice. Perhaps some VAMP-specific forums would have this info.by bodhi - uBoot
balbes150, Thanks! Looks like I've missed this during the patch creation (it was created after the dtbs were compiled). One more line should be added: arch/arm/boot/dts/Makefile + kirkwood-nsa320.dtb \ + kirkwood-nsa325.dtb \by bodhi - Debian
Gareth, Yes. I should have said "Debian kernel" :) Arch is smaller with no initrd. That's made some difference in how soon the watchdog can be killed. And it is done during kernel init.by bodhi - uBoot
Gareth, Whatever works for you is good! The reason I'd suggested USB because if you can't boot 3.16-tld-2 on HDD then chance is that you will still have the same problem no matter which kernel you can try. The Arch patch is basically the same as my patch. In fact, that's where my NSA325 section of the patch came from (WarheadsSE is the developer for all things non-FDT NSA325)by bodhi - uBoot
Actually, I would like Gareth to try 3.16-tld-2 or earlier if booting stock u-boot, and 3.17-tld-1 if booting new u-boot. It would help others to know what to do when they have watchdog problem. It's great that 3.18 works, however it will benefit only a few :)by bodhi - uBoot
JohnW, Again, I did not need to do anything extra. System time just works out of the box. I am not sure why it was necessary for you to remove ntpdate, either. Anybody else has similar experience with the latest rootfs? if so, please post your observation.. If your ntpd is not running, start it, and it wiil be automatically run during reboot.by bodhi - Debian
JohnW Wrote: ------------------------------------------------------- > Just a note... The ntp-daemon doesn't autostart > with Debian on the 3.16 and 3.17 rootfs. > > You can start in manually. Tried some stuff > recommended by others on different forums to make > it work but didn't succeed. > > I have had to reinstall it to make it work with > &quoby bodhi - Debian
Arch Linux ARM: http://archlinuxarm.org/platforms/armv7/amlogic/odroid-c1by bodhi - Debian
@monkmandolins, usb_load_uimage=ext2load usb 0x800000 /uImage usb_load_uinitrd=ext2load usb 0x1100000 /uInitrd should be usb_load_uimage=ext2load usb $device 0x800000 /uImage usb_load_uinitrd=ext2load usb $device 0x1100000 /uInitrd If the above ddid not work, then make sure your rootfs (where /uImage and /uInitrd are) resides on partition 1. See this post for explanation about bootby bodhi - uBoot
Gareth, - Try booting kernel 3.16 with USB thumb drive only. - UART booting the NSA325 is quirky. You need to press power button, wait for it to turn off, then on again, and then execute kwboot within 1 second. All else fails, you can post the entire serial console log here.by bodhi - uBoot
megov, > #console=ttyS0,115200n8 earlyprintk root=/dev/ram0 > panic=3 :::DB88FXX81:eth0:none mtdparts=*here is a > long string* > > As I saw in documentation, "earlyprintk" may be > extended with mode detailed uart specifications. > I've tried both short and long form of it. Also I > change number of ttyS* in "console" and uart* in >by bodhi - uBoot
@Gareth, If you are running with stock u-boot then use Kernel 3.16.0-kirkwood-tld-2 (Updated 02 Sept 2014) in my kernel thread. Newer kernel in the thread will need newer u-boot.by bodhi - uBoot
@Don, I'll take a look at this in about a couple of weeks when I get home.by bodhi - Debian
@ shivahoj, If you could, downgrade to Kernel 3.16.0-kirkwood-tld-3 or earlier and let me know if everything is OK with it.by bodhi - Debian
:)) cool HW hack with the clothes pin.by bodhi - Debian
Don, > #grep -i f2fs /boot/config-3.17.*-tld-1 > CONFIG_F2FS_FS=y > CONFIG_F2FS_STAT_FS=y > CONFIG_F2FS_FS_XATTR=y > CONFIG_F2FS_FS_POSIX_ACL=y > CONFIG_F2FS_FS_SECURITY=y > CONFIG_F2FS_CHECK_FS=y > > Does that mean that f2fs is already in the kernel, > and no further action necessary to support it (ie > no need to rebuild uInitrd) ? Yes, it meby bodhi - Debian
@Don, grep -i f2fs /boot/config-3.17.*-tld-1 And btw, you could take out the rootfstype from bootargs. Make it a little easier to switch back to Ext3.by bodhi - Debian
megov, > 1. As for the boorargs, I'm sure that cmdline, > passing to kernel, contains the right > console specs. Because, when I replace /uImage > file on the usb stick > with image, extracted from stock mtd3 flash block > (the old stock 2.6.31 kernel), > the kernel output is fine and I can see the same > exact bootargs passed into the > kernel output.by bodhi - uBoot
@megov, I don't think ix2-dl is supported in my patched kernel 3.16 or 3.17. You might need to find a similar box that has either DTS or non-FDT patch. Your bootargs looks fine. It is just that the kernel image is not the right one.by bodhi - uBoot
megov Wrote: ------------------------------------------------------- > Hi! > > I've stuck in a strange problem while trying to > install Debian on my > Iomega/LenovoEMC ix2-dl device, so I decided to > ask community for help. > The situation for now is: > - have a working serial connection > - usb flash with 2 partitions (ext2 + ext3), > uImage+uIby bodhi - uBoot
balou1974, > By-the-way, kernel 3.18.2 was released yesterday - > many things have been fixed as it looks like the > big lockup, too I did not see the bug fix was included in 3.18.2. > Problems are magically gone! I am running 4 kirkwood devices using linux kernel 3.18.2 now but only Dns320 with dt-blob and kernel. The rest is still with mach-kernel Ts-219, 2x > Nsa325 aby bodhi - uBoot
Thanks joerg_999!by bodhi - uBoot
balou1974 Wrote: ------------------------------------------------------- > Thanks again! You are right! > > I simply cloned everything (u-boot, u-boot-env, > and the debian system and simply changed ethaddr) > ... You can't clone the bad blocks, though. Bad blocks could show up in the same region, but probably at different locations. You could compare dmesg output beby bodhi - uBoot
I concur with Gravelrash. All my USB boot drives (8 boxes) are up over 3 year long. All are Sandisk brand, formatted as Ext3. And I don't think typical USB flash drives have the type of provisioning that Don is thinking about. Except one: Sandisk Extreme USB 3.0 that actually has SSD controler kind of FW in it. IMO, if you take precaution like I mentioned before in one of the posts, thenby bodhi - Debian
balou1974, mtdblock5 is where your bad blocks were dectected in the first NSA325v2: [ 22.187173] Bad eraseblock 100 at 0x000000c80000 [ 22.197458] Bad eraseblock 200 at 0x000001900000 Are you sure this was 2nd unit? if it was, then where are the bad blocks in dmesg from that 2nd unit? dmesg | grep -i bad You could fix these (possible), but if you're not going to use stock FWby bodhi - uBoot
@rat, As a reminder when flashing u-boot, Dockstar does not have UART booting, so recovery is JTAG only.by bodhi - Debian
Eddie, Plug in both HDDs, boot with UART, interrupt u-boot at count down, ide resetby bodhi - Debian
Peacemaker, > If you "hacked" into your device you can just > backup the nand with dd, if not you can do this > from debian or from just ask me for my nand backup > :-) Shouldn't backup NAND with dd, always use nanddump (safer).by bodhi - Debian
@Tomas, Also does anyone know if the U-boot version can boot from linux raid device? No, U-Boot will not. If you want to use RAID, then the boot device should be USB, and then use RAID on SATA. > Also I am not sure it this still benlongs to this > thread. Please redirect me in such case. Please post this topic on the kernel thread: http://forum.doozan.com/read.php?2,12096 Aby bodhi - uBoot
rat, You are a seasoned embedded Linux users, I've learned a few things from you way back, you have no need for tutorial :) 1. Update your rootfs using kernel 3.16 or 3.17 wheezy. Either update kernel and change apt sources to wheezy, or start with fresh USB rootfs. http://forum.doozan.com/read.php?2,12096 2. Update u-boot: http://forum.doozan.com/read.php?3,12381by bodhi - Debian