@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
balou1974 Wrote: ------------------------------------------------------- > I think you mean the lockup problems starting with > 3.17.x and not solved since today (3.18.x). Well > 3.16.1 is quite okay for a while ;) Yes, indeed that is the big bug. Last I've learned, it's close to be resolved.by bodhi - uBoot
Buttzy10169 Wrote: ------------------------------------------------------- > bodhi, > > Took the plunge and flashed the new uboot and the > second sata seems to be working now. > > Im using the uboot you pointed to 2013.10 version > and kernel 3.18.1. Awesome! Thanks for confirming. Regarding UART, you could try to switch the usb serial module to another Linuxby bodhi - Debian
@Tomas, Cool! Let us know your reslult.by bodhi - uBoot
Cr2013, Not at all! Glad you found a good solution. As a NAS, Pogo v4 is good enough. Especially in a Gbit network.by bodhi - Debian
Cool:) Btw, I am waiting for an important 3.18 bug to resolve before releasing kernel 3.18.x.by bodhi - uBoot
@Buttzy & Eddie, davidedg has confirmed: with the new kernel 3.17 and new u-boot, both HDDs work. So the DTS is good. Make sure you see this in dmesg: [ 1.327311] USB Power: 5000 mV [ 1.330613] SATA1 Power: 5000 mVby bodhi - Debian
bastel Wrote: ------------------------------------------------------- > - External power did work, it also powers the fan > (basically something is very wrong with the fan > control, it's like they add voltages from X and > usb together, i.e. the fan will run without the > NSA320 connected to the power supply if I connect > the externally powered hdd) > 1) skippeby bodhi - Debian
balou1974 Wrote: ------------------------------------------------------- > Still a few problems, I tried to setup u-boot > enviroment like before but I found out a few > commands changed (bootm). > I got uImage and uintrd loaded but when I start > the kernel with 'bootm start $(loadaddr) > 0x1100000' 'bootm go' it will > show 'Starting kernelby bodhi - uBoot
balou1974, The Arch patch should contain the nsa-325_setup.c file. In that you can find the mtd parts definition, and the mtd0 writeable flag was masked. Remove the mask and it will be writeable. Pls post it here if you're not sure. I don't have the Qnap TS-219 P so don't know off-hand if its u-boot can be built. If you'd like, remind me in about 3 weeks when I get backby bodhi - uBoot
balou1974 Wrote: ------------------------------------------------------- > Well I tried it. Does not let me write ... > > root@debian:~/u-boot-utils# ./flash_erase > /dev/mtd0 0 4 > File open error Your mtd0 is probably protected by the kernel. Which kernel are you running?by bodhi - uBoot
balou1974, Your bad blocks are way out, not in first 1M. You can upgrade u-boot.by bodhi - uBoot
bastel Wrote: ------------------------------------------------------- > No, but I had one connected, that's why u-boot > finds 2 storage devices, while linux finds > neither. > I will try (later today) to supply external power > to the hdd and see if it boots then (depends if > the 5v power both usb and hdd or just hdd). Maybe > a powered hub in between will workby bodhi - Debian
bastel, I see you're booting with USB connect HDD. Have you tried with a USB thumb drive?by bodhi - Debian
@Tomas, > I will try it then. Is there a list of features > your kernel patch includes fo NSA325 devices? > Not specific, they are common for all Kirkwood devices. > [ 4.891585] Bad eraseblock 100 at > 0x000000c80000 > [ 4.901493] Bad eraseblock 200 at > 0x000001900000 These bad blocks are way out, not in first 1M, so it is safe to flash u-boot.by bodhi - uBoot
@Tomas, Very perceptive! you are right in a way. Since mainline kernel support Kirwood FDT, you can basically install it and use the appropriate DTS to boot the kernel. However, the NSA325 DTS is not in the mainine yet, so you need to use the NSA325 DTS I've included in the patch in the kernel thread and boot with it. This will give you a basic NSA325 supports. But in the Kirkwood patch sby bodhi - uBoot
@enki, Yes, I'll add more details when I can.by bodhi - uBoot