I managed to get a running 4.2 kernel. This time I went back to a kernel way before 3.16 (2.6.x) and avoided a bunch of uas errors that i noticed today while looking through /var/log/messages. It might be that while the filesystem has been fixed yesterday the files were still corrupted unnoticeable to fsck. Perhaps they got corrupted while being written during a uas error. I'm not sure. Thby h1ro - Debian
The mkimage command you posted above is exactly the one I used yesterday to generate the uImage. Also I have linux on my laptop and fsck is the first thing I tried from there when nothing else seemed to work ;)by h1ro - Debian
hey, thanks for your quick answers and super long persistence on this project. i have labeled it as rootfs. the strange thing is that the same kind of lighting sequence happens even in the working scenario. for this i just have to replace uImage and initrd and disable that dtb_file variable. to clarify: in both cases i see green blinking, then for 4 seconds orange solid, then green solid and hdby h1ro - Debian
Hey after a long time my dockstar rebooted and I realized that I must have left the kernel in limbo :) to fix everything I reverted to some backup and then from there installed the latest u-boot. in netconsole i can boot the old kernel (3.16) when I run setenv dtb_file. can't get any new stuff to work though. U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21 -0800) Seagate FreeAgent Dockby h1ro - Debian
bodhi Wrote: > I've only briefly looked at the Sata-only booting. > To me it's good for recovery purpose, not much > else. Booting with a modern u-boot in NAND is much > more flexible. But your u-boot in NAND can also boot kernel and rootfs from SATA, right?by h1ro - Debian
oh, then that's just some quirk on my old debian squeeze i guess. I ran update-initramfs -c -k 3.16.0-kirkwood-tld-3 manually to create it.by h1ro - Debian
Yes, in the last 3 kirkwood releases it's not included, see here: for x in 1 2 3; do echo `md5sum linux-3.16.0-kirkwood-tld-$x-bodhi/linux-image-*deb` `dpkg-deb -c linux-3.16.0-kirkwood-tld-$x-bodhi/linux-image-*deb|grep initrd` ; done e1d7c0ae5c68ca7f8440d7100f58f707 linux-3.16.0-kirkwood-tld-1-bodhi/linux-image-3.16.0-kirkwood-tld-1_1_armel.deb 696f86d265848ffby h1ro - Debian
your instructions include running this: mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.16.0-kirkwood-tld-2 -d /boot/initrd.img-3.16.0-kirkwood-tld-2 /boot/uInitrd I think you should add some documentation, because /boot/initrd.img-3.16.0-kirkwood-tld-2 doesn't exist even after installing the .deb. Same thing with the oxnas instructions, but thereby h1ro - Debian
Here's my config I used with 3.16.3 and the diff from bodhi's version. I have a NON-PCI version, so I disabled PCI in here. --Nixos *fixedby h1ro - Debian