I did not see any kernel related problem.by bodhi - Debian
@zer0 & denexo, Here is kernel linux-3.16.0-oxnas-tld-3. Please test and let me know if it works for you! Dowload at Dropbox linux-3.16.0-oxnas-tld-3-bodhi.tar.bz2 md5: 0f3ca0717b2438676c7a7eec8f264963by bodhi - Debian
QuoteWarheadsSE > This only real difference I see is that you need > to have the port @ 0x45910000, and they appear to > have the same DMA/SGDMA/etc. Good hints! then cloning the second port from the first one is straight forward.by bodhi - Debian
h1ro, But it doesn't matter whether it was pre-made. root@HomeMBP:/boot# dpkg -i /localdisk/linux/linux-image-3.16.0-kirkwood-tld-3_3_armel.deb Selecting previously unselected package linux-image-3.16.0-kirkwood-tld-3. (Reading database ... 64462 files and directories currently installed.) Unpacking linux-image-3.16.0-kirkwood-tld-3 (from .../linux-image-3.16.0-kirkwood-tld-3_3_armby bodhi - Debian
Stay tuned, I've rebuilt and veriffied the modules, but has not got time to upload. Will do that tonight!by bodhi - Debian
h1ro, > 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 theby bodhi - Debian
@WarheadsSE, Attached here is the latest changes I've made to the nsa325 u-boot. This has the uEnv.txt loading capability implemented and scripted in the default envs. I hope this is all we need to go forward to the GitHub update?by bodhi - uBoot
Peacemaker, I think you could start with the DTS. You already made the change to 2 SATA ports in the driver. But the DTS needs another entry for the 2nd port. The things to look for is the settings in that entry. I don't know how hard it is to find it in the GPL for this box, but I assume it is possible. ./arch/arm/boot/dts/ox820.dtsi sata@45900000 { compatible = "plxtechby bodhi - Debian
@sunfire, Please try new kernel and let me know.by bodhi - uBoot
Kernel 3.16.0-kirkwood-tld-3 package was uploaded. The only update in this kernel is to incorporate the fix for NSA325 watchdog. Please see 1st post for download link. NOTE: for NSA325, don't install this kernel if you still have the stock u-boot. This kernel will not kill the watchdog by itself, it is assumed that the new u-boot was already installed and already turned off the watchdog dby bodhi - Debian
@Peacemaker, QuoteOverall I'm not quite happy with the patched Kernel 2.6: But Krefs Oxnas Kernel works well with the .dts from the openwrt-oxnas-projekt, but only with one sata port. So as I'd like to use both sata, and have not a clue how to activate the 2 ports ( just change the emmu form maxports form 1 to 2 dont work :-| ) or add the old sata driver to the 3.1X kernel. Theby bodhi - Debian
@Nixos, Thanks. BTW, you did not have to disable PCI. Using the Pogo Classic DTB would be enough to run the box correctly.by bodhi - Debian
As requested by a forum member, attached is the patch for kernel linux-oxnas-3.12.13-tld-5.by bodhi - Debian
Peacemaker, > The disk is not spinning up, but it is running > anywhy as I boot from the disk. Strange, meaning you have only one SATA disk plugged in and you can boot from that?by bodhi - Debian
@zer0 & denexo, I'll give it a shot! will rebuild it to see if it helps. @ nixOS, It would be helpful if you can post the diff between my .config and your final one. It'll be easier for others who are looking for the same thing, if it is incorporated to the released kernel.by bodhi - Debian
@WarheadsSE, It seems your suggestion is what has happened :) I rebuilt the kernel without the GPIO tripping code and then booted a few times without seeing the watchdog. The total boot time, with a USB 4TB HDD attached, varied from 32 to 41 seconds. I purposely caused unclean shutdowns to get fsck on rootfs to get it delay that much. But of course, only sunfire can verify this for sure!by bodhi - uBoot
@zer0 and others, Would be better if you recompile the whole kernel from scratch after make distclean This kernel config is no where near what we have in the kirkwood kernel. I've started with kref's config so it only contains a limited set of supported devices. It does need more work to add what we already have in that kirkwood config. I could try building the next versionby bodhi - Debian
@denexo, Did you try to compile the whole thing like they did? if you'd like, post the diff of your .config and my .config and I can try compiling it.by bodhi - Debian
@WarheadsSE, I'd assumed the GPIO was set, not toggling. But I'll try that.by bodhi - uBoot
@WarheadsSE, My conclusion is somehow something caused the watchdog to run again, even it was turned off in kernel nsa325_setup. Perhaps we need a module to wack it again?by bodhi - uBoot
All, On further thought, I think this is best to handle this in kernel initrd.by bodhi - uBoot
sunfire, QuoteI tested bootdelay 10 and 20, and only 20 works. It always reset after mount the partitions or init the network. After reset it show the normal u-boot banner: U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_?? DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err:by bodhi - uBoot
WarheadsSE Wrote: ------------------------------------------------------- > It's just as likely that you have only temporarily > disabled it with that mashing of the GPIO. So should we try smashing it again at the point where u-boot exit to buy some more time. Kludgy, but it might be necessary if we can't permanently disable it, can we? I recall you were thinking about doingby bodhi - uBoot
Peacemaker, > I tested a bit the old U-Boot: > I got it working booting stage1 + uboot dirct from > hdd, but the uboot don't init the hdd, to load > kernel & initrd from hdd. How about interrupting u-boot and look at the envs? it could be as simple as that.by bodhi - Debian
intrax, Among us, WarheadsSE is the expert for this SoC family. You could save sometime by starting with my Git or kref's Git. And port the settings from the stock 2.6.24.4. The advantage is the drivers for USB and SATA might be OK unchanged. IMO, the most important thing to look at porting is the DTS. Chance is that if you can create a DTS for OX810 then you've completed a big poby bodhi - Debian
@denexo, The patch is provided in the tarball. All you need to do is to download the 3.16 source from the kernel source tree, apply the patch and build. Or you could choose to clone kref's Git, and build. EDIT: corrected info.by bodhi - Debian
Darn :) Warhead, so is it possible that the watchdog was temporarily resurrected somehow when the kernel start booting? Our GPIO setting in u-boot was unset somehow?by bodhi - uBoot
Peacemaker Wrote: ------------------------------------------------------- > Bodhi, do you really think this will work? The > nas320 is a krikwood divice and not like the kd20 > a oxnas? > > I think I'll just use for the first time the > Vendor stage1+uboot. As the new U-Boot need's a > lot of changes as well (and I'm not realy good in > modifying kby bodhi - Debian
Peacemaker Wrote: ------------------------------------------------------- > Bodhi, do you really think this will work? The > nas320 is a krikwood divice and not like the kd20 > a oxnas? > > I think I'll just use for the first time the > Vendor stage1+uboot. As the new U-Boot need's a > lot of changes as well (and I'm not realy good in > modifying kby bodhi - Debian