Welcome! Log In Create A New Profile

Advanced

Debian on Synology RS816 (Armada 385)

Posted by zifxify 
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 05:13AM
@bodhi

I have installed Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2 to HDD but will stick with tftp for kernel / dtb files as its easier to swap them out if we are testing things.

Just as a reminder to boot linux-4.12.4-mvebu-tld-1 we need to use ds116.dtb and that only brings up one sata port, so I have upgraded to to linux-4.20.6-mvebu-tld-1 and then using your amarda-385-synology-816.dtb version 1 I get two sata ports which are the first two drives from the left facing the NAS. The second drive is seen as /dev/sda the first as /dev/sdb.

I have added build-essential and various other tools to the rootfs and plan to do all work directly on the NAS, I have added 2GB of swap to help in this regard.

Was thinking we should probably add version numbers to DTB's if we are going to have a few or one of us will loose track of which is which.

Tomorrow I will test with armada-385-synology-816.dtb version 2 and see which drive bays are bootable with that one.
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 05:28AM
Richard,

> upgraded to to linux-4.20.6-mvebu-tld-1 and then
> using your amarda-385-synology-816.dtb version 1 I
> get two sata ports which are the first two drives
> from the left facing the NAS. The second drive is
> seen as /dev/sda the first as /dev/sdb.
>

> I have added build-essential and various other
> tools to the rootfs and plan to do all work
> directly on the NAS, I have added 2GB of swap to
> help in this regard.
>

I too, think that will help greatly to do it natively on this box. With its horse power, you can build the kernel with my patch and config file quickly when you need to.


> Was thinking we should probably add version
> numbers to DTB's if we are going to have a few or
> one of us will loose track of which is which.
>

Good idea :)

One things that bothers me is why I could not find any trace of the RS 816-specific patch in the GPL kernel source code on Synology web site. Perhaps it is not up to date.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 01:35PM
@bohdi
>One things that bothers me is why I could not find any trace of the RS 816-specific patch in the GPL kernel >source code on Synology web site. Perhaps it is not up to date.

The RS816 was released August 2016, the RS815 was released April 2015 and used the same armada-38x with the only meaningful difference between the two models being a bump in speed from 1.33 Ghz to 1.8Ghz. All models previous to the RS815 used armada-37x. The latest Synology GPL is November 2017 whilst the first preceding version without armada-38x in it was December 2014.

Based on the above I think we should find what we need for the RS816 in the released GPL and perhaps the best way forward is hunting for changes between the two GPL dates. I will make a start doing this but Synology switched from a single download to split downloads which may hamper a simple diff between the two.
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 03:25PM
@bohdi

I have run armada-385-synology-rs816-v2.dtb (note the v2) which is the last version you provided with just pcie2 enabled expecting to see the drive the rootfs is reported on changed or even needing to move the HDD to drive 3 or 4 before its seen but basically nothing changed drive 1 is still seen as /dev/sdb and drive 2 as /dev/sda I'm starting to wonder if the DTB is having much impact on the drive initialization and its more in the kernel.

I have taken a quick look at the Dec 2014 GPL and was surprised that the Synology specific customization were limited to half a dozen kernel config options compared to the Nov 2017 which has dozens. I need to work through them but that is going to take time. I think Synology are just replacing source code by individual file, I'm sure they have patches but they are not sharing those so for each file we think may be important we need to take a diff against an original to see what they have changed.

Meanwhile partly to check my build environment is good but also out of unfounded optimism something might improve I am compiling Linux-5.1 with your patch applied and your config. I will report back when it is done.



Edited 1 time(s). Last edit at 05/07/2019 03:36PM by richjn.
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 10:42PM
Richard,

> I have run armada-385-synology-rs816-v2.dtb (note
> the v2) which is the last version you provided
> with just pcie2 enabled expecting to see the drive
> the rootfs is reported on changed or even needing
> to move the HDD to drive 3 or 4 before its seen
> but basically nothing changed drive 1 is still
> seen as /dev/sdb and drive 2 as /dev/sda I'm
> starting to wonder if the DTB is having much
> impact on the drive initialization and its more in
> the kernel.

In a modern kernel running with device tree, there should be nothing in the kernel code that needed to trigger the SATA activation. It's all in the DTB.

Stock kernel might be taking a lazy approach, when they just patch some code so they don't have to update the DTS.


>
> I have taken a quick look at the Dec 2014 GPL and
> was surprised that the Synology specific
> customization were limited to half a dozen kernel
> config options compared to the Nov 2017 which has
> dozens. I need to work through them but that is
> going to take time. I think Synology are just
> replacing source code by individual file, I'm sure
> they have patches but they are not sharing those
> so for each file we think may be important we need
> to take a diff against an original to see what
> they have changed.
>
> Meanwhile partly to check my build environment is
> good but also out of unfounded optimism something
> might improve I am compiling Linux-5.1 with your
> patch applied and your config. I will report back
> when it is done.


I'm building and testing kernel 5.1 for Kirkwood and MVEBU boxes right now. I should have it ready for release here soon.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 10:50PM
@bodhi

Understood on the DTB, guess we just need to find out what we are missing.

My build environment is all good

uname -a
Linux debian 5.1.0-tld-1 #1 SMP PREEMPT Tue May 7 12:34:41 PDT 2019 armv7l GNU/Linux

But no change in sata ports

lsblk
NAME      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda         8:0    1  1.8T  0 disk
sdb         8:16   1  1.8T  0 disk
|-sdb1      8:17   1  1.8T  0 part /
`-sdb2      8:18   1  1.3G  0 part [SWAP]
mtdblock0  31:0    0    4M  0 disk
mtdblock1  31:1    0    4M  0 disk

Anything you would like me to concentrate on if we're not hunting in kernel source for answers ?
Re: Debian on Synology RS816 (Armada 385)
May 07, 2019 11:09PM
Richard,


> My build environment is all good
>
> uname -a
> Linux debian 5.1.0-tld-1 #1 SMP PREEMPT Tue May 7
> 12:34:41 PDT 2019 armv7l GNU/Linux

Cool!

> Anything you would like me to concentrate on if
> we're not hunting in kernel source for answers ?

Since you can recompile the DTB at will now. I think you can try to activate the pcie3 and pcie4 to see if it will make any difference.

In our armada-385-synology-rs816-v2.dtb right now, only 1 pcie is enabled.

pcie {
                        
			status = "okay";

			pcie@2,0 {
				/* Port 1, Lane 0 */
				status = "okay";
			};

		};

You can try to modify the DTS and compile version 3

pcie {
                        
			status = "okay";

			pcie@2,0 {
				/* Port 1, Lane 0 */
				status = "okay";
			};
			pcie@3,0 {
				/* Port 2, Lane 0 */
				status = "okay";
			};

		};

And try then version 4, with pcie4 enabled.

If any of the 2 tweaks above brings up another SATA, then we know the PCIe ports are configured as X1 port.

See the comments about these PCIe ports in
arch/arm/boot/dts/armada-385.dtsi

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 08, 2019 01:21AM
@bodhi
Tried pcie 2 and 3 enabled then pcie 2, 3 and 4 enabled but still only 2 sata ports brought up on both trials with the rootfs displayed as /dev/sdb in drive 1 viewed from from front, left to right.
Re: Debian on Synology RS816 (Armada 385)
May 08, 2019 04:47AM
Richard,

> Tried pcie 2 and 3 enabled then pcie 2, 3 and 4
> enabled but still only 2 sata ports brought up on
> both trials with the rootfs displayed as /dev/sdb
> in drive 1 viewed from from front, left to right.

OK, so this behavior seems to indicate a need to turn on power for the other ports.

Let's look back in this thread to see what zifxify did with GPIO. I recall something about some GPIO that can be a trigger for the other HDD port.

I'll look at the DTS again to confirm.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 08, 2019 04:41PM
@bodhi
I've looked back at zifxify efforts with the gpio which seemed to be on the right track but no conclusive solution at the end of it. I have dumped debugfs for the gpio pins output below.

root@debian:~# cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-31, parent: platform/f1018100.gpio, f1018100.gpio:
 gpio-13  (ds116:orange:disk   ) out lo
 gpio-15  (pwr-sata0           ) out hi

gpiochip1: GPIOs 32-59, parent: platform/f1018140.gpio, f1018140.gpio:
 gpio-48  (soc:gpio-fan        ) out lo
 gpio-49  (soc:gpio-fan        ) out lo
 gpio-50  (soc:gpio-fan        ) out hi
 gpio-58  (usb3-vbus0          ) out hi
 gpio-59  (usb3-vbus1          ) out hi

One other thing I was wondering if we should strip the DTB down to the bare essentials in case the ds116 we are basing on actually reserved pins we need ?

EDIT
The above carried out with armada-385-synology-rs816-v4.dtb which I have attached.



Edited 1 time(s). Last edit at 05/08/2019 04:43PM by richjn.
Attachments:
open | download - armada-385-synology-rs816-v4.dts (6.6 KB)
Re: Debian on Synology RS816 (Armada 385)
May 08, 2019 11:55PM
Hi Richard,

Yes, good idea to see if we can remove GPIO definition to avoid conflict. Even though they (DS116 and RS816) are from the same manufacturer, GPIOs are reassigned as convenient for a specific box.

There are several GPIOs that are fixed location as the SoC needs them. But when you see LEDs or Fan GPIOs, you can do the test in Linux to see if they are the same and remove them if they are not.

For example,

gpio-leds {
			compatible = "gpio-leds";

			/* The green part is on gpio0.20 which is also used by
			 * sata0, and accesses to SATA disk 0 make it blink so it
			 * doesn't need to be declared here.
			 */
			orange {
				gpios = <&gpio0 13 GPIO_ACTIVE_HIGH>;
				label = "ds116:orange:disk";
				default-state = "off";

Here is the userspace GPIO control method. I have included this in the Wiki thread under

Quote

Sensors & Fan

OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package
OWFS & Motion Detection (external link)
How to control GPIO in Linux userspace for GPIO-enable fan

https://forum.doozan.com/read.php?2,12096,35663#msg-35663

So you would echo a 0 or 1 to clear or set GPIO 13 to see if Orange LED is off/on (if GPIO is ACTIVE_HIGH then 0 would clear it).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 09, 2019 01:40AM
@bodhi
I will get onto this Saturday, work is very inconsiderate of my time allocation sometimes :-)
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 03:35PM
@bodhi
I have removed the gpio-leds section altogether from the dts the listed pin 13 wasn't doing anything and besides for now I don't care about the leds.

I have also removed the gpio-fans section which I tested one pin entry at a time but in all cases the fans (there are 3 on the rs816) still appear to function normally.

This only leaves sata pin 15 and usb pins 58 & 59 active from a debugfs dump
root@debian:~# cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-31, parent: platform/f1018100.gpio, f1018100.gpio:
 gpio-15  (pwr-sata0           ) out hi

gpiochip1: GPIOs 32-59, parent: platform/f1018140.gpio, f1018140.gpio:
 gpio-58  (usb3-vbus0          ) out hi
 gpio-59  (usb3-vbus1          ) out hi

uart1 pin19 and usb pins 26, 27 are still defined in the dts but seemingly unused, I could try deleting those sections or alternatively the pin 58, 59 sections and see which if either are actually controlling the usb's ?

Also is it safe for me to cycle the remaining pins to "1" and see if any HDD's turn up or do I need to do more than this to test effectively ?
Attachments:
open | download - armada-385-synology-rs816-v5.dts (5.9 KB)
open | download - armada-385-synology-rs816-v5.dtb (17 KB)
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 05:36PM
@bodhi
I was conscious that I hadn't tried the synology-rs816-stock.dtb on linux-5.1 so gave it a try. On previous kernels this got as far as not finding the rootfs (no drives in /dev/) and dumping to an initramfs prompt.

A bit different on linux-5.1 with a very early kernel panic at
kernel BUG at drivers/irqchip/irq-armada-370-xp.c:658!
Not sure what to make of that ?

The complete log.
Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.1.0-tld-1 (root@debian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PREEMPT Tue May 7 12:34:41 PDT 2019
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Synology RS816
[    0.000000] printk: bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] random: get_random_bytes called from start_kernel+0x78/0x4e0 with crng_init=0
[    0.000000] percpu: Embedded 18 pages/cpu s41932 r8192 d23604 u73728
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 260608
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=20 mtdparts=spi0.0:4m(boot),-(spi-rootfs) earlyprintk=serial
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1017076K/1048576K available (9216K kernel code, 824K rwdata, 2376K rodata, 1024K init, 332K bss, 31500K reserved, 0K cma-reserved, 262144K highmem)
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: CPU: 0 PID: 0 at drivers/irqchip/irq-gic.c:1433 gic_of_init+0x50/0x3bc
[    0.000000] Modules linked in:
[    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.1.0-tld-1 #1
[    0.000000] Hardware name: Marvell Armada 380/385 (Device Tree)
[    0.000000] [<c0117494>] (unwind_backtrace) from [<c0111ebc>] (show_stack+0x10/0x14)
[    0.000000] [<c0111ebc>] (show_stack) from [<c098ac74>] (dump_stack+0x70/0x8c)
[    0.000000] [<c098ac74>] (dump_stack) from [<c0126c94>] (__warn+0xdc/0xfc)
[    0.000000] [<c0126c94>] (__warn) from [<c0126dc4>] (warn_slowpath_null+0x38/0x44)
[    0.000000] [<c0126dc4>] (warn_slowpath_null) from [<c0d31a9c>] (gic_of_init+0x50/0x3bc)
[    0.000000] [<c0d31a9c>] (gic_of_init) from [<c0d44a74>] (of_irq_init+0x1e8/0x308)
[    0.000000] [<c0d44a74>] (of_irq_init) from [<c0d09590>] (mvebu_init_irq+0x8/0x64)
[    0.000000] [<c0d09590>] (mvebu_init_irq) from [<c0d02dac>] (init_IRQ+0x78/0x88)
[    0.000000] [<c0d02dac>] (init_IRQ) from [<c0d00d3c>] (start_kernel+0x2f8/0x4e0)
[    0.000000] [<c0d00d3c>] (start_kernel) from [<00000000>] (  (null))
[    0.000000] ---[ end trace ad7ce707d3e43b4b ]---
[    0.000000] ------------[ cut here ]------------
[    0.000000] kernel BUG at drivers/irqchip/irq-armada-370-xp.c:658!
[    0.000000] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[    0.000000] Modules linked in:
[    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W         5.1.0-tld-1 #1
[    0.000000] Hardware name: Marvell Armada 380/385 (Device Tree)
[    0.000000] PC is at armada_370_xp_mpic_of_init+0x78/0x300
[    0.000000] LR is at _raw_write_unlock+0x20/0x4c
[    0.000000] pc : [<c0d31f34>]    lr : [<c09a67a4>]    psr: 600000d3
[    0.000000] sp : c0e01ed8  ip : f1020ccf  fp : c0ebf318
[    0.000000] r10: c0be9f18  r9 : c0ebf32a  r8 : c0e01f5c
[    0.000000] r7 : c0e08d48  r6 : 00000000  r5 : ef7f29f4  r4 : ef00cc40
[    0.000000] r3 : ef65e0a9  r2 : ef65e0a9  r1 : 00000002  r0 : 00000000
[    0.000000] Flags: nZCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment none
[    0.000000] Control: 10c5387d  Table: 0000404a  DAC: 00000051
[    0.000000] Process swapper/0 (pid: 0, stack limit = 0x(ptrval))
[    0.000000] Stack: (0xc0e01ed8 to 0xc0e02000)
[    0.000000] 1ec0:                                                       00000000 00000000
[    0.000000] 1ee0: 2ea51000 f1020a00 f1020ccf ef7f2a48 00000200 00000000 00000000 00000000
[    0.000000] 1f00: 00000000 f1021070 f10210c7 ef7f2a48 00000200 00000000 00000000 00000000
[    0.000000] 1f20: 00000000 ef65e0a9 ef00cc40 ef7f24b4 c0e01f5c c0e01f64 c0e01f5c c0ebf32a
[    0.000000] 1f40: c0be9f18 c0d44a74 00000000 00000000 0000003f c0e08d48 00000000 c0e01f5c
[    0.000000] 1f60: c0e01f5c ef00c280 ef00c280 ef65e0a9 ef01a700 c0d5da28 efffce00 ffffffff
[    0.000000] 1f80: c0ece400 c0e08d40 c0ece400 00000001 c0d5da38 c0d09590 c0d5da28 c0d02dac
[    0.000000] 1fa0: 00000000 c0d00d3c ffffffff ffffffff 00000000 c0d00744 00000000 c0e08d48
[    0.000000] 1fc0: 00000000 c0d5da38 ef60e1a9 00000000 00000000 c0d00330 00000051 10c0387d
[    0.000000] 1fe0: 00000210 00ff7000 414fc091 10c5387d 00000000 00000000 00000000 00000000
[    0.000000] [<c0d31f34>] (armada_370_xp_mpic_of_init) from [<c0d44a74>] (of_irq_init+0x1e8/0x308)
[    0.000000] [<c0d44a74>] (of_irq_init) from [<c0d09590>] (mvebu_init_irq+0x8/0x64)
[    0.000000] [<c0d09590>] (mvebu_init_irq) from [<c0d02dac>] (init_IRQ+0x78/0x88)
[    0.000000] [<c0d02dac>] (init_IRQ) from [<c0d00d3c>] (start_kernel+0x2f8/0x4e0)
[    0.000000] [<c0d00d3c>] (start_kernel) from [<00000000>] (  (null))
[    0.000000] Code: e59f0260 ebcfef72 e3500000 1a000001 (e7f001f2)
[    0.000000] ---[ end trace ad7ce707d3e43b4c ]---
[    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[    0.000000] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---


Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 05:50PM
@bodhi
Just ran again this time with the dtb pulled from flash and we revert to the same initramfs prompt as on previous kernels.

There is something happening that I just can't see / don't understand or maybe my synology-rs816-stock.dtb had not compiled correctly I will go back and check / rebuild it.

Edit
Tried to rebuild and get a host of warnings but no errors although the following reads more like an error than a warning to me.
Warning (pci_bridge): /soc/pcie-controller: node name is not "pci" or "pcie"
Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge'

The full message
root@debian:/usr/src/linux-5.1# make ARCH=arm synology-rs816-stock.dtb
  DTC     arch/arm/boot/dts/synology-rs816-stock.dtb
arch/arm/boot/dts/synology-rs816-stock.dts:614.19-687.5: Warning (pci_bridge): /soc/pcie-controller: node name is not "pci" or "pcie"
arch/arm/boot/dts/synology-rs816-stock.dtb: Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge'
arch/arm/boot/dts/synology-rs816-stock.dts:56.4-23: Warning (clocks_property): /soc/devbus-bootcs:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:66.4-23: Warning (clocks_property): /soc/devbus-cs0:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:76.4-23: Warning (clocks_property): /soc/devbus-cs1:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:86.4-23: Warning (clocks_property): /soc/devbus-cs2:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:96.4-23: Warning (clocks_property): /soc/devbus-cs3:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:489.5-24: Warning (clocks_property): /soc/internal-regs/timer@c600:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:248.5-24: Warning (clocks_property): /soc/internal-regs/i2c@11000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:260.5-24: Warning (clocks_property): /soc/internal-regs/i2c@11100:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:414.5-24: Warning (clocks_property): /soc/internal-regs/serial@12000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:424.5-24: Warning (clocks_property): /soc/internal-regs/serial@12100:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:213.5-24: Warning (clocks_property): /soc/internal-regs/clock-gating-control@18220:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:526.5-28: Warning (clocks_property): /soc/internal-regs/timer@20300:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:526.5-28: Warning (clocks_property): /soc/internal-regs/timer@20300:clocks: cell 2 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:533.5-28: Warning (clocks_property): /soc/internal-regs/watchdog@20300:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:533.5-28: Warning (clocks_property): /soc/internal-regs/watchdog@20300:clocks: cell 2 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:174.5-24: Warning (clocks_property): /soc/internal-regs/ethernet@70000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:188.5-24: Warning (clocks_property): /soc/internal-regs/ethernet@30000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:200.5-24: Warning (clocks_property): /soc/internal-regs/ethernet@34000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:496.5-25: Warning (clocks_property): /soc/internal-regs/usb@58000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:540.5-25: Warning (clocks_property): /soc/internal-regs/xor@60800:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:561.5-25: Warning (clocks_property): /soc/internal-regs/xor@60900:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:357.5-24: Warning (clocks_property): /soc/internal-regs/sata@a8000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:365.5-25: Warning (clocks_property): /soc/internal-regs/sata@e0000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:383.5-25: Warning (clocks_property): /soc/internal-regs/sdhci@d8000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:503.5-24: Warning (clocks_property): /soc/internal-regs/usb3@f0000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:512.5-24: Warning (clocks_property): /soc/internal-regs/usb3@f8000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:123.5-20: Warning (clocks_property): /soc/internal-regs/corediv-clock@e4250:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:147.5-24: Warning (clocks_property): /soc/internal-regs/mdio:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:165.5-33: Warning (clocks_property): /soc/internal-regs/bm_pnc@c0000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:165.5-33: Warning (clocks_property): /soc/internal-regs/bm_pnc@c0000:clocks: cell 2 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:286.5-24: Warning (clocks_property): /soc/internal-regs/clock-complex@18700:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:374.5-25: Warning (clocks_property): /soc/internal-regs/tdm@b0000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:396.5-24: Warning (clocks_property): /soc/internal-regs/audio-controller@e8000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:446.5-24: Warning (clocks_property): /soc/internal-regs/spi@10600:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:466.5-24: Warning (clocks_property): /soc/internal-regs/spi@10680:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:475.5-24: Warning (clocks_property): /soc/internal-regs/nand@d0000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:582.5-51: Warning (clocks_property): /soc/internal-regs/crypto@9D000:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:582.5-51: Warning (clocks_property): /soc/internal-regs/crypto@9D000:clocks: cell 2 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:582.5-51: Warning (clocks_property): /soc/internal-regs/crypto@9D000:clocks: cell 4 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:582.5-51: Warning (clocks_property): /soc/internal-regs/crypto@9D000:clocks: cell 6 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:636.5-24: Warning (clocks_property): /soc/pcie-controller/pcie@1,0:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:652.5-24: Warning (clocks_property): /soc/pcie-controller/pcie@2,0:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:668.5-24: Warning (clocks_property): /soc/pcie-controller/pcie@3,0:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:684.5-24: Warning (clocks_property): /soc/pcie-controller/pcie@4,0:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:754.4-23: Warning (clocks_property): /cpus/cpu@0:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:764.4-23: Warning (clocks_property): /cpus/cpu@1:clocks: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:525.5-109: Warning (interrupts_extended_property): /soc/internal-regs/timer@20300:interrupts-extended: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:525.5-109: Warning (interrupts_extended_property): /soc/internal-regs/timer@20300:interrupts-extended: cell 4 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:525.5-109: Warning (interrupts_extended_property): /soc/internal-regs/timer@20300:interrupts-extended: cell 8 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:525.5-109: Warning (interrupts_extended_property): /soc/internal-regs/timer@20300:interrupts-extended: cell 12 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:525.5-109: Warning (interrupts_extended_property): /soc/internal-regs/timer@20300:interrupts-extended: cell 16 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:525.5-109: Warning (interrupts_extended_property): /soc/internal-regs/timer@20300:interrupts-extended: cell 18 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:173.5-37: Warning (interrupts_extended_property): /soc/internal-regs/ethernet@70000:interrupts-extended: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:187.5-37: Warning (interrupts_extended_property): /soc/internal-regs/ethernet@30000:interrupts-extended: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:199.5-37: Warning (interrupts_extended_property): /soc/internal-regs/ethernet@34000:interrupts-extended: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:605.5-37: Warning (interrupts_extended_property): /soc/internal-regs/pmu:interrupts-extended: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:620.4-23: Warning (msi_parent_property): /soc/pcie-controller:msi-parent: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:753.4-23: Warning (resets_property): /cpus/cpu@0:resets: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:763.4-23: Warning (resets_property): /cpus/cpu@1:resets: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:504.5-24: Warning (gpios_property): /soc/internal-regs/usb3@f0000:vbus-gpio: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:504.5-24: Warning (gpios_property): /soc/internal-regs/usb3@f0000:vbus-gpio: Could not get phandle node for (cell 0)
arch/arm/boot/dts/synology-rs816-stock.dts:513.5-24: Warning (gpios_property): /soc/internal-regs/usb3@f8000:vbus-gpio: cell 0 is not a phandle reference
arch/arm/boot/dts/synology-rs816-stock.dts:513.5-24: Warning (gpios_property): /soc/internal-regs/usb3@f8000:vbus-gpio: Could not get phandle node for (cell 0)



Edited 1 time(s). Last edit at 05/10/2019 07:54PM by richjn.
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 08:40PM
richjn Wrote:
-------------------------------------------------------
> @bodhi
> I have removed the gpio-leds section altogether
> from the dts the listed pin 13 wasn't doing
> anything and besides for now I don't care about
> the leds.
>
> I have also removed the gpio-fans section which I
> tested one pin entry at a time but in all cases
> the fans (there are 3 on the rs816) still appear
> to function normally.
>
> This only leaves sata pin 15 and usb pins 58 & 59
> active from a debugfs dump
>
> root@debian:~# cat /sys/kernel/debug/gpio
> gpiochip0: GPIOs 0-31, parent:
> platform/f1018100.gpio, f1018100.gpio:
>  gpio-15  (pwr-sata0           ) out hi
> 
> gpiochip1: GPIOs 32-59, parent:
> platform/f1018140.gpio, f1018140.gpio:
>  gpio-58  (usb3-vbus0          ) out hi
>  gpio-59  (usb3-vbus1          ) out hi
>
>
> uart1 pin19 and usb pins 26, 27 are still defined
> in the dts but seemingly unused, I could try
> deleting those sections or alternatively the pin
> 58, 59 sections and see which if either are
> actually controlling the usb's ?
>
> Also is it safe for me to cycle the remaining pins
> to "1" and see if any HDD's turn up or do I need
> to do more than this to test effectively ?

Richard,

It is safe to cycle the pins on your test box . Make sure you dont have any thing important on the HDDs or USB that you cannot recreate.

Many pins are “fixed” the SoC, meaning they serve some purposes that nobody changes the definition. Usually the higher MPP pins are ones assigned to SATA, USB, LEDs

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 08:42PM
And I don’t think we can use stock DTB with new kernel so no need to try fixing it!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 10:51PM
@bodhi
All thought of fixing stock dtb discarded :-)

The pin we need is 37

root@debian:~# lsblk
NAME      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda         8:0    1  1.8T  0 disk 
sdb         8:16   1  1.8T  0 disk 
|-sdb1      8:17   1  1.8T  0 part /
`-sdb2      8:18   1  1.3G  0 part [SWAP]
sdc         8:32   1  1.8T  0 disk 
sdd         8:48   1  1.8T  0 disk 
mtdblock0  31:0    0    4M  0 disk 
mtdblock1  31:1    0    4M  0 disk 
root@debian:~#

root@debian:~# ls /dev/disk/by-path/
.                                   platform-f10a8000.sata-ata-1-part2
..                                  platform-soc:pcie-pci-0000:01:00.0-ata-2
platform-f10a8000.sata-ata-1        platform-soc:pcie-pci-0000:01:00.0-ata-3
platform-f10a8000.sata-ata-1-part1  platform-soc:pcie-pci-0000:01:00.0-ata-4


What do we do next ?



Edited 1 time(s). Last edit at 05/10/2019 11:11PM by richjn.
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 11:20PM
Richard,

> The pin we need is 37

Good works :)

So what did you see on these disks? can you mount them, and list the content?

sda         8:0    1  1.8T  0 disk 
sdb         8:16   1  1.8T  0 disk 
|-sdb1      8:17   1  1.8T  0 part /
`-sdb2      8:18   1  1.3G  0 part [SWAP]
sdc         8:32   1  1.8T  0 disk 
sdd         8:48   1  1.8T  0 disk

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 11:32PM
@bodhi
I zeroed the disks previous to trying this. I will setup some partitions now, mount, write data and report back here shortly.
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 11:33PM
And please post the entire dmesg log for this. I'd like to see the SATA ports activation by the kernel when you turn on the pins, and the command you used.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 11:48PM
@bodhi
Disks formating will take a couple of minutes.

Command used
echo 37 > /sys/class/gpio/export
echo "on" > /sys/class/gpio/gpio37/direction
echo 1 > /sys/class/gpio/gpio37/value
udevadm trigger

dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.1.0-tld-1 (root@debian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PREEMPT Tue May 7 12:34:41 PDT 2019
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Synology RS116
[    0.000000] printk: bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 262144
[    0.000000]   Normal zone: 1536 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 65536 pages, LIFO batch:15
[    0.000000] random: get_random_bytes called from start_kernel+0x78/0x4e0 with crng_init=0
[    0.000000] percpu: Embedded 18 pages/cpu s41932 r8192 d23604 u73728
[    0.000000] pcpu-alloc: s41932 r8192 d23604 u73728 alloc=18*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 260608
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=20 mtdparts=spi0.0:4m(boot),-(spi-rootfs) earlyprintk=serial
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1017088K/1048576K available (9216K kernel code, 824K rwdata, 2376K rodata, 1024K init, 332K bss, 31488K reserved, 0K cma-reserved, 262144K highmem)
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000006] sched_clock: 64 bits at 933MHz, resolution 1ns, wraps every 4398046511103ns
[    0.007975] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x1ae5b571769, max_idle_ns: 881590513431 ns
[    0.019059] Switching to timer-based delay loop, resolution 1ns
[    0.025111] Ignoring duplicate/late registration of read_current_timer delay
[    0.032128] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.043361] Console: colour dummy device 80x30
[    0.047800] Calibrating delay loop (skipped), value calculated using timer frequency.. 1866.00 BogoMIPS (lpj=9330000)
[    0.058363] pid_max: default: 32768 minimum: 301
[    0.063041] LSM: Security Framework initializing
[    0.067682] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.074265] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.081580] *** VALIDATE proc ***
[    0.084956] *** VALIDATE cgroup1 ***
[    0.088519] *** VALIDATE cgroup2 ***
[    0.092099] CPU: Testing write buffer coherency: ok
[    0.096963] CPU0: Spectre v2: using BPIALL workaround
[    0.102090] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.165012] Setting up static identity map for 0x100000 - 0x100060
[    0.171229] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.176435] mvebu-pmsu: Initializing Power Management Service Unit
[    0.194994] rcu: Hierarchical SRCU implementation.
[    0.234993] smp: Bringing up secondary CPUs ...
[    0.295050] Booting CPU 1
[    0.297792] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.297795] CPU1: Spectre v2: using BPIALL workaround
[    0.308513] smp: Brought up 1 node, 2 CPUs
[    0.312588] SMP: Total of 2 processors activated (3732.00 BogoMIPS).
[    0.318927] CPU: All CPU(s) started in SVC mode.
[    0.324012] devtmpfs: initialized
[    0.329042] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.336918] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.346714] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.352877] prandom: seed boundary self test passed
[    0.358866] prandom: 100 self tests passed
[    0.362941] pinctrl core: initialized pinctrl subsystem
[    0.368826] NET: Registered protocol family 16
[    0.373720] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.380901] audit: initializing netlink subsys (disabled)
[    0.386871] audit: type=2000 audit(0.360:1): state=initialized audit_enabled=0 res=1
[    0.394605] cpuidle: using governor ladder
[    0.398703] cpuidle: using governor menu
[    0.402738] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.410712] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.416625] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[    0.424678] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[    0.445483] vgaarb: loaded
[    0.448408] SCSI subsystem initialized
[    0.452328] libata version 3.00 loaded.
[    0.452594] usbcore: registered new interface driver usbfs
[    0.458122] usbcore: registered new interface driver hub
[    0.463461] usbcore: registered new device driver usb
[    0.468900] media: Linux media interface: v0.10
[    0.473450] videodev: Linux video capture interface: v2.00
[    0.479076] pps_core: LinuxPPS API ver. 1 registered
[    0.484015] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.493691] PTP clock support registered
[    0.498387] clocksource: Switched to clocksource arm_global_timer
[    0.838048] VFS: Disk quotas dquot_6.6.0
[    0.842011] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.855054] NET: Registered protocol family 2
[    0.859727] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.867356] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.874417] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.880884] TCP: Hash tables configured (established 8192 bind 8192)
[    0.887259] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.893173] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.899625] NET: Registered protocol family 1
[    0.904199] RPC: Registered named UNIX socket transport module.
[    0.910106] RPC: Registered udp transport module.
[    0.914786] RPC: Registered tcp transport module.
[    0.919472] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.925883] PCI: CLS 0 bytes, default 64
[    0.925976] Unpacking initramfs...
[    1.153592] Freeing initrd memory: 7784K
[    1.157601] NetWinder Floating Point Emulator V0.97 (double precision)
[    1.164342] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    1.173761] Initialise system trusted keyrings
[    1.178199] Key type blacklist registered
[    1.182274] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[    1.188753] zbud: loaded
[    1.191706] NFS: Registering the id_resolver key type
[    1.196739] Key type id_resolver registered
[    1.200922] Key type id_legacy registered
[    1.204916] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.211590] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.218014] jffs2: version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[    1.225316] orangefs_debugfs_init: called with debug mask: :none: :0:
[    1.231807] orangefs_init: module version upstream loaded
[    1.283225] Key type asymmetric registered
[    1.287303] Asymmetric key parser 'x509' registered
[    1.292270] bounce: pool size: 64 pages
[    1.296152] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    1.305009] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[    1.313763] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    1.319676] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.325135] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    1.331983] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.338219] pci_bus 0000:00: scanning bus
[    1.338301] pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400
[    1.338315] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.338516] pci 0000:00:03.0: [11ab:6820] type 01 class 0x060400
[    1.338529] pci 0000:00:03.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.338692] pci 0000:00:04.0: [11ab:6820] type 01 class 0x060400
[    1.338704] pci 0000:00:04.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.339416] pci_bus 0000:00: fixups for bus
[    1.339424] PCI: bus0: Fast back to back transfers disabled
[    1.344971] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[    1.344975] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.352957] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 0
[    1.352960] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.360939] pci 0000:00:04.0: scanning [bus 00-00] behind bridge, pass 0
[    1.360942] pci 0000:00:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.368915] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[    1.368992] pci_bus 0000:01: scanning bus
[    1.369013] pci 0000:01:00.0: [1b4b:9215] type 00 class 0x010601
[    1.369032] pci 0000:01:00.0: reg 0x10: [io  0xfffffff8-0xffffffff]
[    1.369040] pci 0000:01:00.0: reg 0x14: [io  0xfffffffc-0xffffffff]
[    1.369048] pci 0000:01:00.0: reg 0x18: [io  0xfffffff8-0xffffffff]
[    1.369055] pci 0000:01:00.0: reg 0x1c: [io  0xfffffffc-0xffffffff]
[    1.369063] pci 0000:01:00.0: reg 0x20: [io  0xffffffe0-0xffffffff]
[    1.369071] pci 0000:01:00.0: reg 0x24: [mem 0x42000000-0x420007ff]
[    1.369078] pci 0000:01:00.0: reg 0x30: [mem 0xd0000000-0xd000ffff pref]
[    1.369127] pci 0000:01:00.0: PME# supported from D3hot
[    1.369132] pci 0000:01:00.0: PME# disabled
[    1.369275] pci 0000:00:02.0: ASPM: current common clock configuration is broken, reconfiguring
[    1.399083] pci_bus 0000:01: fixups for bus
[    1.399090] PCI: bus1: Fast back to back transfers disabled
[    1.404635] pci_bus 0000:01: bus scan returning with max=01
[    1.404639] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.404646] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 1
[    1.404729] pci_bus 0000:02: scanning bus
[    1.405408] pci_bus 0000:02: fixups for bus
[    1.405411] PCI: bus2: Fast back to back transfers enabled
[    1.410879] pci_bus 0000:02: bus scan returning with max=02
[    1.410883] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    1.410890] pci 0000:00:04.0: scanning [bus 00-00] behind bridge, pass 1
[    1.410965] pci_bus 0000:03: scanning bus
[    1.411641] pci_bus 0000:03: fixups for bus
[    1.411644] PCI: bus3: Fast back to back transfers enabled
[    1.417102] pci_bus 0000:03: bus scan returning with max=03
[    1.417106] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
[    1.417111] pci_bus 0000:00: bus scan returning with max=03
[    1.417133] pci 0000:00:02.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    1.423984] pci 0000:00:02.0: BAR 13: assigned [io  0x10000-0x10fff]
[    1.430313] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[    1.437501] pci 0000:00:03.0: BAR 6: assigned [mem 0xe0200000-0xe02007ff pref]
[    1.444693] pci 0000:00:04.0: BAR 6: assigned [mem 0xe0300000-0xe03007ff pref]
[    1.451887] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[    1.459079] pci 0000:01:00.0: BAR 5: assigned [mem 0xe0010000-0xe00107ff]
[    1.465836] pci 0000:01:00.0: BAR 4: assigned [io  0x10000-0x1001f]
[    1.472078] pci 0000:01:00.0: BAR 0: assigned [io  0x10020-0x10027]
[    1.478315] pci 0000:01:00.0: BAR 2: assigned [io  0x10028-0x1002f]
[    1.484557] pci 0000:01:00.0: BAR 1: assigned [io  0x10030-0x10033]
[    1.490799] pci 0000:01:00.0: BAR 3: assigned [io  0x10034-0x10037]
[    1.497037] pci 0000:00:02.0: PCI bridge to [bus 01]
[    1.501982] pci 0000:00:02.0:   bridge window [io  0x10000-0x10fff]
[    1.508219] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    1.514979] pci 0000:00:03.0: PCI bridge to [bus 02]
[    1.519925] pci 0000:00:04.0: PCI bridge to [bus 03]
[    1.524900] pcieport 0000:00:02.0: assign IRQ: got 0
[    1.524908] pcieport 0000:00:02.0: enabling device (0140 -> 0143)
[    1.530988] pcieport 0000:00:02.0: enabling bus mastering
[    1.531021] pcieport 0000:00:03.0: assign IRQ: got 0
[    1.531028] pcieport 0000:00:03.0: enabling bus mastering
[    1.531052] pcieport 0000:00:04.0: assign IRQ: got 0
[    1.531058] pcieport 0000:00:04.0: enabling bus mastering
[    1.531455] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.588743] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    1.596294] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.658729] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    1.702375] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.709915] printk: console [ttyS0] disabled
[    1.734275] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 12500000) is a 16550A
[    1.743228] printk: console [ttyS0] enabled
[    1.751646] printk: bootconsole [earlycon0] disabled
[    1.782345] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 23, base_baud = 12500000) is a 16550A
[    1.792176] ahci 0000:01:00.0: assign IRQ: got 47
[    1.792186] ahci 0000:01:00.0: version 3.0
[    1.792195] pci 0000:00:02.0: enabling bus mastering
[    1.802375] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 4 ports 6 Gbps 0xf impl SATA mode
[    1.810517] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs 
[    1.819830] scsi host0: ahci
[    1.822999] scsi host1: ahci
[    1.826148] scsi host2: ahci
[    1.829313] scsi host3: ahci
[    1.832392] ata1: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010100 irq 48
[    1.839854] ata2: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010180 irq 48
[    1.847283] ata3: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010200 irq 48
[    1.854717] ata4: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010280 irq 48
[    1.863448] m25p80 spi0.0: found n25q064, expected mx25l6405d
[    1.869355] m25p80 spi0.0: n25q064 (8192 Kbytes)
[    1.873997] 2 cmdlinepart partitions found on MTD device spi0.0
[    1.879950] Creating 2 MTD partitions on "spi0.0":
[    1.884766] 0x000000000000-0x000000400000 : "boot"
[    1.890176] 0x000000400000-0x000000800000 : "spi-rootfs"
[    1.896552] libphy: Fixed MDIO Bus: probed
[    1.901065] libphy: orion_mdio_bus: probed
[    1.907462] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[    1.916065] mvneta f1070000.ethernet eth0: Using hardware mac address 00:50:43:1c:24:27
[    1.924317] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.930893] ehci-pci: EHCI PCI platform driver
[    1.935390] ehci-orion: EHCI orion driver
[    1.939866] usbcore: registered new interface driver usblp
[    1.945399] usbcore: registered new interface driver usb-storage
[    1.951613] mousedev: PS/2 mouse device common for all mice
[    1.957827] armada38x-rtc f10a3800.rtc: registered as rtc0
[    1.963511] i2c /dev entries driver
[    1.993494] orion_wdt: Initial timeout 171 sec
[    2.015042] marvell-cesa f1090000.crypto: CESA device successfully registered
[    2.022473] hidraw: raw HID events driver (C) Jiri Kosina
[    2.028151] usbcore: registered new interface driver usbhid
[    2.033764] usbhid: USB HID core driver
[    2.037884] drop_monitor: Initializing network drop monitor service
[    2.044509] NET: Registered protocol family 10
[    2.049464] Segment Routing with IPv6
[    2.053183] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.059882] NET: Registered protocol family 17
[    2.064420] 8021q: 802.1Q VLAN Support v1.8
[    2.068660] Key type dns_resolver registered
[    2.073050] ThumbEE CPU extension supported.
[    2.077341] Registering SWP/SWPB emulation handler
[    2.082565] registered taskstats version 1
[    2.086679] Loading compiled-in X.509 certificates
[    2.091566] zswap: loaded using pool lzo/zbud
[    2.104533] Key type big_key registered
[    2.112496] Key type encrypted registered
[    2.118237] v5.0-sata0: supplied by pwr_en_sata0
[    2.123013] ahci-mvebu f10a8000.sata: masking port_map 0x3 -> 0x1
[    2.129192] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x1 impl platform mode
[    2.138301] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs 
[    2.147725] scsi host4: ahci-mvebu
[    2.151473] scsi host5: ahci-mvebu
[    2.155097] ata5: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 41
[    2.163081] ata6: DUMMY
[    2.165781] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    2.171167] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 1
[    2.178797] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[    2.188095] xhci-hcd f10f0000.usb3: irq 42, io mem 0xf10f0000
[    2.193893] ata3: SATA link down (SStatus 0 SControl 300)
[    2.199345] ata1: SATA link down (SStatus 0 SControl 300)
[    2.199512] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    2.204805] ata4: SATA link down (SStatus 0 SControl 300)
[    2.213086] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.225770] usb usb1: Product: xHCI Host Controller
[    2.230686] usb usb1: Manufacturer: Linux 5.1.0-tld-1 xhci-hcd
[    2.236544] usb usb1: SerialNumber: f10f0000.usb3
[    2.241524] hub 1-0:1.0: USB hub found
[    2.245306] hub 1-0:1.0: 1 port detected
[    2.249409] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    2.254749] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
[    2.262285] xhci-hcd f10f0000.usb3: Host supports USB 3.0  SuperSpeed
[    2.268791] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.276974] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.01
[    2.285285] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.292546] usb usb2: Product: xHCI Host Controller
[    2.297445] usb usb2: Manufacturer: Linux 5.1.0-tld-1 xhci-hcd
[    2.303311] usb usb2: SerialNumber: f10f0000.usb3
[    2.308244] hub 2-0:1.0: USB hub found
[    2.312033] hub 2-0:1.0: 1 port detected
[    2.316282] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.321636] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[    2.329212] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[    2.338503] xhci-hcd f10f8000.usb3: irq 43, io mem 0xf10f8000
[    2.344426] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    2.352740] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.360002] usb usb3: Product: xHCI Host Controller
[    2.364901] usb usb3: Manufacturer: Linux 5.1.0-tld-1 xhci-hcd
[    2.370765] usb usb3: SerialNumber: f10f8000.usb3
[    2.375699] hub 3-0:1.0: USB hub found
[    2.379489] hub 3-0:1.0: 1 port detected
[    2.383570] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.388920] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
[    2.396444] xhci-hcd f10f8000.usb3: Host supports USB 3.0  SuperSpeed
[    2.398407] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.402949] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.410307] ata2.00: NCQ Send/Recv Log not supported
[    2.417309] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.01
[    2.422262] ata2.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[    2.430559] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.436772] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[    2.444019] usb usb4: Product: xHCI Host Controller
[    2.452343] ata2.00: NCQ Send/Recv Log not supported
[    2.455822] usb usb4: Manufacturer: Linux 5.1.0-tld-1 xhci-hcd
[    2.460825] ata2.00: configured for UDMA/133
[    2.466665] usb usb4: SerialNumber: f10f8000.usb3
[    2.466873] hub 4-0:1.0: USB hub found
[    2.479467] hub 4-0:1.0: 1 port detected
[    2.481294] scsi 1:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[    2.491949] armada38x-rtc f10a3800.rtc: setting system clock to 2019-05-11T03:14:05 UTC (1557544445)
[    2.501620] sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    2.508546] v12.0-sata0: supplied by pwr_en_sata0
[    2.509569] sd 1:0:0:0: [sda] 4096-byte physical blocks
[    2.514224] v12.0-sata0: disabling
[    2.519519] sd 1:0:0:0: [sda] Write Protect is off
[    2.527617] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.527660] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.559603] sd 1:0:0:0: [sda] Attached SCSI removable disk
[    2.678401] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.685349] ata5.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[    2.691568] ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32)
[    2.699108] ata5.00: configured for UDMA/133
[    2.703582] scsi 4:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[    2.712078] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    2.719997] sd 4:0:0:0: [sdb] 4096-byte physical blocks
[    2.725277] sd 4:0:0:0: [sdb] Write Protect is off
[    2.730102] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    2.730139] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.814610]  sdb: sdb1 sdb2
[    2.818037] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[    2.824666] Freeing unused kernel memory: 1024K
[    2.858691] Checked W+X mappings: passed, no W+X pages found
[    2.864376] Run /init as init process
[    2.904192] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[    2.907253] random: udevadm: uninitialized urandom read (16 bytes read)
[    2.912008] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[   23.444126] PM: Image not found (code -22)
[   24.002039] random: fast init done
[   27.718315] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[   27.807826] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[   30.806313] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   30.813619] sd 4:0:0:0: Attached scsi generic sg1 type 0
[   32.046345] Adding 1366012k swap on /dev/sdb2.  Priority:-2 extents:1 across:1366012k FS
[   32.187535] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[   32.629461] random: crng init done
[   32.632882] random: 7 urandom warning(s) missed due to ratelimiting
[   33.769732] mvneta f1070000.ethernet eth0: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510]
[   33.778618] mvneta f1070000.ethernet eth0: configuring for phy/sgmii link mode
[   38.988653] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   38.996532] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2007.275979] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2007.313234] ata4.00: NCQ Send/Recv Log not supported
[ 2007.318244] ata4.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[ 2007.324452] ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2007.331380] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2007.338884] ata4.00: NCQ Send/Recv Log not supported
[ 2007.343875] ata4.00: configured for UDMA/133
[ 2007.348425] scsi 3:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[ 2007.358301] sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 2007.366564] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[ 2007.372403] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 2007.374135] sd 3:0:0:0: [sdc] Write Protect is off
[ 2007.378674] ata3.00: NCQ Send/Recv Log not supported
[ 2007.385218] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 2007.387689] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2007.387789] ata3.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[ 2007.405050] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2007.413899] ata3.00: NCQ Send/Recv Log not supported
[ 2007.419081] ata3.00: configured for UDMA/133
[ 2007.425234] scsi 2:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[ 2007.426100] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[ 2007.433825] sd 2:0:0:0: Attached scsi generic sg3 type 0
[ 2007.446874] sd 2:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 2007.454687] sd 2:0:0:0: [sdd] 4096-byte physical blocks
[ 2007.460112] sd 2:0:0:0: [sdd] Write Protect is off
[ 2007.464929] sd 2:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 2007.464968] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2007.493381] sd 2:0:0:0: [sdd] Attached SCSI removable disk
[ 4789.024594]  sda: sda1
[ 4818.239928]  sdc: sdc1
[ 4845.263111]  sdd: sdd1
Re: Debian on Synology RS816 (Armada 385)
May 10, 2019 11:58PM
@bodhi

root@debian:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            497M     0  497M   0% /dev
tmpfs           101M  1.2M  100M   2% /run
/dev/sdb1       1.8T  2.6G  1.7T   1% /
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           468M     0  468M   0% /run/shm
tmpfs           501M     0  501M   0% /tmp
/dev/sda1       1.8T   69M  1.7T   1% /root/1
/dev/sdc1       1.8T   69M  1.7T   1% /root/2
/dev/sdd1       1.8T   69M  1.7T   1% /root/3

Transfer via scp
[richard@Linux linux]$ scp linux-5.1.tar.xz root@192.168.1.243:/root/1 
root@192.168.1.243's password: 
linux-5.1.tar.xz                                        100%  101MB  34.0MB/s   00:02    
[richard@Linux linux]$

ls -la /root/1
root@debian:~# ls -la /root/1
total 103888
drwxr-xr-x 3 root root      4096 May 10 21:55 .
drwx------ 8 root root      4096 May 10 21:51 ..
-rw-r--r-- 1 root root 106244476 May 10 21:55 linux-5.1.tar.xz
drwx------ 2 root root     16384 May 10 21:39 lost+found
root@debian:~# 
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 12:07AM
Richard,

Very good.

[ 2007.275979] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2007.313234] ata4.00: NCQ Send/Recv Log not supported
[ 2007.318244] ata4.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[ 2007.324452] ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2007.331380] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2007.338884] ata4.00: NCQ Send/Recv Log not supported
[ 2007.343875] ata4.00: configured for UDMA/133
[ 2007.348425] scsi 3:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[ 2007.358301] sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 2007.366564] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[ 2007.372403] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 2007.374135] sd 3:0:0:0: [sdc] Write Protect is off
[ 2007.378674] ata3.00: NCQ Send/Recv Log not supported
[ 2007.385218] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 2007.387689] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2007.387789] ata3.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[ 2007.405050] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2007.413899] ata3.00: NCQ Send/Recv Log not supported
[ 2007.419081] ata3.00: configured for UDMA/133
[ 2007.425234] scsi 2:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[ 2007.426100] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[ 2007.433825] sd 2:0:0:0: Attached scsi generic sg3 type 0
[ 2007.446874] sd 2:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 2007.454687] sd 2:0:0:0: [sdd] 4096-byte physical blocks
[ 2007.460112] sd 2:0:0:0: [sdd] Write Protect is off
[ 2007.464929] sd 2:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 2007.464968] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2007.493381] sd 2:0:0:0: [sdd] Attached SCSI removable disk
[ 4789.024594]  sda: sda1
[ 4818.239928]  sdc: sdc1
[ 4845.263111]  sdd: sdd1

Quote

Command used
echo 37 > /sys/class/gpio/export
echo "on" > /sys/class/gpio/gpio37/direction
echo 1 > /sys/class/gpio/gpio37/value
udevadm trigger


And the DTS is version 4?

armada-385-synology-rs816-v4.dts

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 12:13AM
@bodhi
v5 with the gpio led and fans removed. I posted it further up this page but re-attaching here.

Edit
Just noticed I had typo above, actual command was "out" not "on"



Edited 1 time(s). Last edit at 05/11/2019 12:28AM by richjn.
Attachments:
open | download - armada-385-synology-rs816-v5.dts (5.9 KB)
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 03:13AM
Richard,

> v5 with the gpio led and fans removed. I posted it
> further up this page but re-attaching here.
>
> Edit
> Just noticed I had typo above, actual command was
> "out" not "on"

OK. I'll modify v5 and see if we can have a real solution.

Or perhaps I can tell what I have in mind and you try it: In version 6 of the DTS, create a new sata1 regulator using the existing sata0 regulator as the example. And use GPIO 37 for this new regulator.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 05/11/2019 03:14AM by bodhi.
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 05:31AM
@bodhi
I did as you suggested but it didn't work, maybe I missed something.
I have attached armada-385-synology-rs816-v6.dts if you could check for me please.
Attachments:
open | download - armada-385-synology-rs816-v6.dts (6.2 KB)
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 05:34AM
@bodhi
Spotted it myself 37 is in gpio1.
Will try again now
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 06:01AM
@bodhi

Hmm still no go, my new sata regulator looks like this.
reg_sata1: pwr-sata1 {
		compatible = "regulator-fixed";
		regulator-name = "pwr_en_sata1";
		regulator-min-microvolt = <12000000>;
		regulator-max-microvolt = <12000000>;
		enable-active-high;
		regulator-boot-on;
		gpio = <&gpio1 37 GPIO_ACTIVE_HIGH>;
	};

And when that didn't work I remembered some gpio alias in the stock dts so added
aliases {
		gpio0 = "/soc/internal-regs/gpio@18100";
		gpio1 = "/soc/internal-regs/gpio@18140";
	};

But that didn't help either, can you spot anything ?
Re: Debian on Synology RS816 (Armada 385)
May 11, 2019 07:09AM
Have you tried the brute force approach?

Usually at this point I pull up “dmesg -w” in one window and then run a script that sequentially activates each unassigned gpio pin in another. I can usually find the sata pwr pins based on when the dmesg output shows the drive being recognized.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: