> Would be nice, even if I some how stopped working > on this nas. So - here is OX820_boot.zip attached. It has SPL file and u-boot. Just use DD to put the SPL file on your disk. Then put u-boot in first partition and /boot folder. Name it as u-boot.img. B.T.W I just tested this 2013.10 SPL + U-boot. Both SATA ports and both USB ports find device as expected.by tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > Argrr! I got a different kernel panic now. I guess > it's time to dig into the OpenWrt patch. How about root device with that kernel? RW or RO?by tilator - Debian
I suppose the problem might be this: OX820 processor can only boot from sata if there are some special bytes in start of the disk. The bytes are set using this script: perl <<EOF | dd of="$disk" bs=512 print "\x00" x 0x1a4; print "\x00\x5f\x01\x00"; print "\x00\xdf\x00\x00"; print "\x00\x80\x00\x00"; printby tilator - Debian
bodhi Wrote: ------------------------------------------------------- > I'm at 2015.10 for u-boot: > http://forum.doozan.com/read.php?3,16017 > > But I don't think u-boot is related at all to your > problem with RO rootfs. Most likely the rootfs fs > was set to RO due to the kernel booting problem. I agree. This has to be kernel problem. I have just been tryiby tilator - Debian
> In any case, I've just got passed this > kernel panic and getting back to a good baseline. I still wonder what to do. I did already try to make partition table and everything twice. I even changed from GPT to MSDOS. Nothing changed. And - it always boots with an older kernel. It's only this newer kernel having "readonly root" problem. There is u-boot 2014.10by tilator - Debian
> It does not look like they have 4.4 yet. Currently > they are at 4.0. > > https://dev.openwrt.org/browser/trunk/target/linux > /oxnas?rev=45711&order=name How about this: https://dev.openwrt.org/browser/trunk/target/linux/oxnasby tilator - Debian
> > Was it a cold boot, or was it a reboot? If a > > reboot, was stock kernel running before it? > > > I think I can see that this actually was not > successful. Did it just hang here? Actually you are right. After cold boot it simply freezes here: [ 3.581611] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities [ 3.607293]by tilator - Debian
Second boot just hang up. Only difference is, first boot has booting with original kernel before this. Second has booting with 4.4.0 kernel (with hang and panic) before it.by tilator - Debian
Here is same kernel as above after power boot. As you can see, the RTC is not up now (1.047884s). Of cource booting hang up again with readonly root: ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-4.4.0 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3787808 Bytes = 3.6 MiB Load Address: 60008000 Entry Point: 60008000 Verifyby tilator - Debian
So, here you have kernel boot log: ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-4.4.0 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3787808 Bytes = 3.6 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 61000000 Booting using the fdt blob at 0x61000000 Loaby tilator - Debian
> Which RTC does the Akitio uses? I forgot all about > this subject! It has Dallas ds1307. There is some "bitbangind" serial driver in front of it. > It would be helpful to post the > serial console log of what you meant (if you need > help troubleshooting it). I would like to have help here. Akitio original kernel must do some kind of reset to the serial conby tilator - uBoot
> Please post serial console log (and printenv > output in serial console). > > BTW, did you build kernel 4.4 using my patch? I'm > having a kernel panic running it pretty early and > trying to troubleshoot. I think it's a bad > build/patch so I am reviewing my new patch. I'll get log ASAP. The device is now busy with hard drive check. I got the keby tilator - Debian
It is possible to have both SATA up with 2013.10 stage1 and u-boot. At least this works with Akitio mycloud mini having OX820 and two sata connections too. Do you need the files? My problem is the serial driver needed for rtc. There is still some strange reset problem. Rtc works with first boot, but not any more with second (or other) boot time.by tilator - uBoot
I try to use kernel 4.4 with Akitio Mycloud mini and stage1 loader from u-boot version 2013.10 capable to load u-boot and kernel from sata using sata as root device too. This does not work. It always mounts root readonly and naturally falls in kernel panic while accessing virtual memory. Is there some trick to make it mount rw? I have used GPT and MSDOS partition tables with the same resultby tilator - Debian
There has been some poweroff trouble quite some time. At least my device (Akitio Mycloud mini) has had this issue with even patch made by Daniel Golle in kernel version 3.18. So, I suppose this is kernel trouble more than one of Debian.by tilator - Debian
> Can you describe the rtc problem you have? does > the DC01 have RTC? > > The Pogo V3 (so are many other plugs such as > Dockstar, GoFlex Net) can not be powered down > completely. After you shutdown, note that Ethernet > LED is still flashing, and if you have a USB hub, > it still draws power. DC01 has Dallas ds1307 rtc. Trouble is, if the device is not powby tilator - Debian
Hi, I had some free time and took my Silverstone DC01 (an OX820 device too) and compiled 4.1.6 kernel for it. And - once again run in trouble with rtc because this kernel does not power off this device properly. I suppose the processor needs some spesific bits to be set to make it power off. Does anyone know how this is done? -- tilatorby tilator - Debian
Peacemaker Wrote: ------------------------------------------------------- > I just patched 3.18.0 Kernel OpenWRT kernel seems to have lots of generic patches. Maybe there is something necessary.by tilator - Debian
Sounds nice. I have not had enough time yet to try this with my Akitio Mycloud Mini and Silverstone DC01 devices. Maybe some day at christmas. BTW, did you use directly OpenWRT kernel or just patch original with the few patches?by tilator - Debian
By the way - what's this: https://dev.openwrt.org.cn/browser/openwrttrunk/trunk/target/linux/oxnas/files/drivers/ataby tilator - Debian
WarheadsSE Wrote: ------------------------------------------------------- > > #define > SATA_REG_BASE OXNAS_HW_PA_TO_VA(0x05900000) > #define > SATA_PHY_BASE OXNAS_HW_PA_TO_VA(0x04900000) > #define SATA_PHY_BASE_PA 0x44900000 > #define SATA_REG_BASE_PA 0x45900000 > #define SATA0_REGS_BASE (SATA_REG_BASE + > 0x00000) > #define SATA1_Rby tilator - Debian
> You could try to boot with this attached dtb. I > think it should work with the Pogo V3 Classic, > even booting the full Pogo Pro kernel, since it > does not have pci controller in it. Thanks again. I'll try it today. BTW: is there a simple typo in the instructions at the line beginning dpkg -i and ending .bz2by tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > Try this kernel I've just uploaded: > http://forum.doozan.com/read.php?2,16044 > > The /proc/device-tree does polulate correctly. Thanks, I'll try it. It seems to me like the whole trouble comes from the device tree. I suppose SATA_OXNAS_MAX_PORTS = 1 setting in kernel sata_oxnas.c file is hby tilator - uBoot
> Let us know your progress. Since you wanted to know: Kernel 3.13.5 registers second SCSI host. Something is still wrong since both are at same address. **************************************************************************** # ls -la /sys/class/scsi_host/ total 0 drwxr-xr-x 2 root root 0 1970-01-01 02:00 . drwxr-xr-x 26 root root 0 1970-01-01 02:00 .. lrwxrwxrwx 1 rooby tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > tilator, > > I'm not quite sure I understand your quesiton! Did > you compile the kernel, but not sure how to > generate the dtb file? Or are you looking for a > kernel package and dtb file so you can use? The trouble is I can compile kernel with different options and boot with it, but /proc/dby tilator - uBoot
I got source from Shuttle for KD20. Kernel version is here the same old one (2.6.31.14) but if someone is interested, I can share it. At least SATA drivers seem a little different than those for Silverstone/Akitio.by tilator - uBoot
> Let us know your progress. There is not much to tell, but let's put it here. I have been trying to compile DTS/DTB file using u-boot source. I suppose all needed settings are there. The Pogoplug V3 DTS file might be done with u-boot settings CONFIG_SYS_IDE_MAXDEVICE=1 and CONFIG_SYS_IDE_MAXBUS=1. Result is of cource one SATA node. It works for Pogoplug but not some other ox820by tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > tilator, > > Look for the SATA driver in kernel drivers/ata. If > number of ports is defined/hardcoded, it should be > in there. Yes, I did that before. There is hard coded setting "SATA_OXNAS_MAX_PORTS = 1". I did try to set value 2 and ended up with booting errors. I have to try thisby tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > OK. So you're not running the version out of > kref's source tree, you have patched it. U-boot is kref's version _but_ settings for CONFIG_SYS_IDE_MAXDEVICE and CONFIG_SYS_IDE_MAXBUS are changed from 1 to 2. Everything else is exactly as they are in kref's source. > I can only suggest thatby tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > tilator, > > > I already found out myself that uboot had only one > SATAdevise set on and it needed to be changed > > > I'm afraid you're confusing me :) the U-Boot > 2013.10 that you've installed recognized both > SATAs as you showed above. U-boot 2013.10 recognizesby tilator - uBoot