FVDW-SL on a Seagate Personal Cloud - additional steps

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby fvdw » Thu Feb 07, 2019 5:39 pm

And the next kernel, added a macro to autoload the led driver
You do not have the required permissions to view the files attached to this post.
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby m1m1sm1t1c0 » Fri Feb 08, 2019 3:12 am

Kernel #8
Code: Select all
login as: root
root@192.168.221.6's password:
root@nas-mimismo:/ # ls -l /sys/devices/platform
total 0
drwxr-xr-x  3 root root    0 2018-01-01 12:00 alarmtimer
drwxr-xr-x  4 root root    0 1999-12-31 19:00 Fixed MDIO bus.0
drwxr-xr-x  4 root root    0 1999-12-31 19:00 gpio-keys
drwxr-xr-x  4 root root    0 1999-12-31 19:00 gpio-leds
drwxr-xr-x  3 root root    0 2018-01-01 12:00 gpio_poweroff
drwxr-xr-x  4 root root    0 1999-12-31 19:00 leds-ns2l
drwxr-xr-x  3 root root    0 2018-01-01 12:00 pmu
drwxr-xr-x  2 root root    0 2019-02-07 21:55 power
drwxr-xr-x  4 root root    0 1999-12-31 19:00 reg-dummy
drwxr-xr-x  5 root root    0 1999-12-31 19:00 regulators
drwxr-xr-x  3 root root    0 2018-01-01 12:00 regulatory.0
drwxr-xr-x  4 root root    0 1999-12-31 19:00 serial8250
drwxr-xr-x  7 root root    0 1999-12-31 19:00 soc
-rw-r--r--  1 root root 4096 2019-02-07 21:53 uevent
root@nas-mimismo:/ # ls -l /sys/devices/platform/leds-ns2l
total 0
lrwxrwxrwx  1 root root    0 2019-02-07 21:54 driver -> ../../../bus/platform/drivers/leds-ns2l
-rw-r--r--  1 root root 4096 2019-02-07 21:54 driver_override
drwxr-xr-x  3 root root    0 1999-12-31 19:00 leds
-r--r--r--  1 root root 4096 2019-02-07 21:54 modalias
lrwxrwxrwx  1 root root    0 2019-02-07 21:54 of_node -> ../../../firmware/devicetree/base/leds-ns2l
drwxr-xr-x  2 root root    0 2019-02-07 21:55 power
lrwxrwxrwx  1 root root    0 2019-02-07 21:54 subsystem -> ../../../bus/platform
-rw-r--r--  1 root root 4096 2018-01-01 12:00 uevent
Last edited by m1m1sm1t1c0 on Fri Feb 08, 2019 3:17 am, edited 1 time in total.
m1m1sm1t1c0
 
Posts: 42
Joined: Tue Jun 28, 2016 12:50 pm

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby m1m1sm1t1c0 » Fri Feb 08, 2019 3:14 am

Kernel #9
Code: Select all
login as: root
root@192.168.221.6's password:
root@nas-mimismo:/ # dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.6.6 (root@fvdwsl-5big2.local) (gcc version 4.9.3 (GCC) ) #9 Thu Feb 7 18:33:37 CET 2019
[    0.000000] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine model: Seagate Personal Cloud (Cumulus, SRN21C)
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c0881a8c, node_mem_map dfb7a000
[    0.000000]   Normal zone: 1152 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda7
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 510032K/524288K available (6123K kernel code, 291K rwdata, 2040K rodata, 228K init, 416K bss, 14256K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0800fe4   (8164 kB)
[    0.000000]       .init : 0xc0801000 - 0xc083a000   ( 228 kB)
[    0.000000]       .data : 0xc083a000 - 0xc0882fa0   ( 292 kB)
[    0.000000]        .bss : 0xc0882fa0 - 0xc08eb108   ( 417 kB)
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: DT/platform modifies aux control register: 0x12086302 -> 0x1a086302
[    0.000000] Aurora cache controller enabled, 4 ways, 256 kB
[    0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302
[    0.000000] Switching to timer-based delay loop, resolution 48ns
[    0.000007] sched_clock: 32 bits at 20MHz, resolution 48ns, wraps every 103356786663ns
[    0.000022] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 91987540234 ns
[    0.000295] Console: colour dummy device 80x30
[    0.000311] Calibrating delay loop (skipped), value calculated using timer frequency.. 41.55 BogoMIPS (lpj=207773)
[    0.000324] pid_max: default: 32768 minimum: 301
[    0.000453] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000462] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001053] CPU: Testing write buffer coherency: ok
[    0.001284] Setting up static identity map for 0x8200 - 0x8258
[    0.001587] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1
[    0.001719] mvebu-pmsu: Initializing Power Management Service Unit
[    0.005568] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    0.005800] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.005905] xor: measuring software checksum speed
[    0.100057]    arm4regs  :   919.600 MB/sec
[    0.200055]    8regs     :   772.400 MB/sec
[    0.300055]    32regs    :   880.400 MB/sec
[    0.300062] xor: using function: arm4regs (919.600 MB/sec)
[    0.300084] pinctrl core: initialized pinctrl subsystem
[    0.300792] NET: Registered protocol family 16
[    0.301259] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.301869] cpuidle: using governor ladder
[    0.305977] sram soc:sa-sram: found no memory resource
[    0.305999] sram: probe of soc:sa-sram failed with error -22
[    0.306626] No ATAGs?
[    0.306640] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.306764] mvebu-pmsu: CPU idle is currently broken: disabling
[    0.480345] raid6: int32x1  gen()   142 MB/s
[    0.650195] raid6: int32x1  xor()   136 MB/s
[    0.820116] raid6: int32x2  gen()   213 MB/s
[    0.990081] raid6: int32x2  xor()   155 MB/s
[    1.160084] raid6: int32x4  gen()   179 MB/s
[    1.330088] raid6: int32x4  xor()   140 MB/s
[    1.500281] raid6: int32x8  gen()   175 MB/s
[    1.670129] raid6: int32x8  xor()   116 MB/s
[    1.670135] raid6: using algorithm int32x2 gen() 213 MB/s
[    1.670141] raid6: .... xor() 155 MB/s, rmw enabled
[    1.670147] raid6: using intx1 recovery algorithm
[    1.670708] SCSI subsystem initialized
[    1.670879] libata version 3.00 loaded.
[    1.672424] clocksource: Switched to clocksource armada_370_xp_clocksource
[    1.672713] FS-Cache: Loaded
[    1.678499] NET: Registered protocol family 2
[    1.679000] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    1.679037] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    1.679073] TCP: Hash tables configured (established 4096 bind 4096)
[    1.679141] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    1.679155] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    1.679268] NET: Registered protocol family 1
[    1.679544] RPC: Registered named UNIX socket transport module.
[    1.679552] RPC: Registered udp transport module.
[    1.679557] RPC: Registered tcp transport module.
[    1.679563] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.679580] PCI: CLS 0 bytes, default 64
[    1.679828] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    1.680725] futex hash table entries: 256 (order: -1, 3072 bytes)
[    1.681314] workingset: timestamp_bits=13 max_order=17 bucket_order=4
[    1.681676] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.681932] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.682298] ntfs: driver 2.1.32 [Flags: R/W].
[    1.682332] fuse init (API version 7.24)
[    1.682606] JFS: nTxBlock = 3984, nTxLock = 31877
[    1.687933] async_tx: api initialized (async)
[    1.688029] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    1.688046] io scheduler noop registered
[    1.688060] io scheduler deadline registered
[    1.688088] io scheduler cfq registered (default)
[    1.688683] armada-370-pinctrl f1018000.pin-ctrl: registered pinctrl driver
[    1.689459] irq: Cannot allocate irq_descs @ IRQ39, assuming pre-allocated
[    1.689849] irq: Cannot allocate irq_descs @ IRQ71, assuming pre-allocated
[    1.690121] irq: Cannot allocate irq_descs @ IRQ103, assuming pre-allocated
[    1.690807] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[    1.690823] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    1.690834] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[    1.690845] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.690874] pci 0000:00:01.0: [11ab:6710] type 01 class 0x060400
[    1.691092] PCI: bus0: Fast back to back transfers disabled
[    1.691104] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.691253] pci 0000:01:00.0: [1b21:1142] type 00 class 0x0c0330
[    1.691286] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x40007fff 64bit]
[    1.691393] pci 0000:01:00.0: PME# supported from D3hot
[    1.691596] PCI: bus1: Fast back to back transfers disabled
[    1.691609] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.691676] pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
[    1.691691] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8007fff 64bit]
[    1.691708] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.691720] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80fffff]
[    1.691760] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    1.691960] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.733181] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.734203] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.773154] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.774325] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.775546] console [ttyS0] disabled
[    1.795674] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 20, base_baud = 12500000) is a 16550A
[    2.477820] console [ttyS0] enabled
[    2.491689] brd: module loaded
[    2.499907] loop: module loaded
[    2.503590] sata_mv f10a0000.sata: version 1.28
[    2.503752] sata_mv f10a0000.sata: slots 32 ports 1
[    2.509612] scsi host0: sata_mv
[    2.513042] ata1: SATA max UDMA/133 irq 28
[    2.518665] m25p80 spi0.0: mx25l8005 (1024 Kbytes)
[    2.523522] 1 ofpart partitions found on MTD device spi0.0
[    2.529032] Creating 1 MTD partitions on "spi0.0":
[    2.533863] 0x000000000000-0x000000100000 : "u-boot"
[    2.540481] libphy: Fixed MDIO Bus: probed
[    2.544634] tun: Universal TUN/TAP device driver, 1.6
[    2.549707] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    2.556032] ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[    2.564117] ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[    2.573205] libphy: orion_mdio_bus: probed
[    2.579318] mvneta f1074000.ethernet eth0: Using hardware mac address 00:10:75:58:85:a6
[    2.587485] PPP generic driver version 2.4.2
[    2.591898] PPP Deflate Compression module registered
[    2.597005] PPP MPPE Compression module registered
[    2.601824] NET: Registered protocol family 24
[    2.606712] aoe: cannot create debugfs directory
[    2.611488] aoe: AoE v85 initialised.
[    2.615566] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    2.633527] md: linear personality registered for level -1
[    2.639046] md: raid0 personality registered for level 0
[    2.644404] md: raid1 personality registered for level 1
[    2.649745] md: raid10 personality registered for level 10
[    2.655512] md: raid6 personality registered for level 6
[    2.660851] md: raid5 personality registered for level 5
[    2.666202] md: raid4 personality registered for level 4
[    2.671684] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com
[    2.680403] device-mapper: multipath: version 1.11.0 loaded
[    2.686028] device-mapper: multipath round-robin: version 1.1.0 loaded
[    2.692601] device-mapper: multipath queue-length: version 0.2.0 loaded
[    2.699251] device-mapper: multipath service-time: version 0.3.0 loaded
[    2.705955] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    2.712083] device-mapper: raid: Loading target version 1.7.0
[    2.718576] ledtrig-cpu: registered to indicate activity on CPUs
[    2.724902] marvell-cesa: probe of f1090000.crypto failed with error -22
[    2.731764] hidraw: raw HID events driver (C) Jiri Kosina
[    2.737504] Netfilter messages via NETLINK v0.30.
[    2.742243] nfnl_acct: registering with nfnetlink.
[    2.747100] nf_conntrack version 0.5.0 (7969 buckets, 31876 max)
[    2.753772] ipip: IPv4 over IPv4 tunneling driver
[    2.759244] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.764798] NET: Registered protocol family 10
[    2.770181] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    2.775806] sit: IPv6 over IPv4 tunneling driver
[    2.781052] NET: Registered protocol family 17
[    2.785585] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    2.798282] Bridge firewalling registered
[    2.802319] NET: Registered protocol family 5
[    2.806831] Key type dns_resolver registered
[    2.811595] registered taskstats version 1
[    2.816691] console [netcon0] enabled
[    2.820373] netconsole: network logging started
[    2.825443] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    2.832378] rtc-mv f1010300.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.032446] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    3.043247] ata1.00: ATA-9: ST3000VN000-1HJ166, SC60, max UDMA/133
[    3.049461] ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    3.076908] ata1.00: configured for UDMA/133
[    3.081552] scsi 0:0:0:0: Direct-Access     ATA      ST3000VN000-1HJ1 SC60 PQ: 0 ANSI: 5
[    3.090671] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[    3.098477] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    3.103957] sd 0:0:0:0: [sda] Write Protect is off
[    3.108777] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.108862] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.196269]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
[    3.203451] sd 0:0:0:0: [sda] Attached SCSI disk
[    3.208150] md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
[    3.242647] EXT4-fs (sda7): mounting ext3 file system using the ext4 subsystem
[    3.250739] EXT4-fs (sda7): INFO: recovery required on readonly filesystem
[    3.257668] EXT4-fs (sda7): write access will be enabled during recovery
[    3.472880] EXT4-fs (sda7): recovery complete
[    3.512487] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[    3.520219] VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
[    3.527205] Freeing unused kernel memory: 228K (c0801000 - c083a000)
[    3.533596] This architecture does not have kernel memory protection.
[    3.872308] EXT4-fs (sda7): warning: maximal mount count reached, running e2fsck is recommended
[    3.902496] EXT4-fs (sda7): re-mounted. Opts: (null)
[    4.685752] usbcore: registered new interface driver usbfs
[    4.691322] usbcore: registered new interface driver hub
[    4.696751] usbcore: registered new device driver usb
[    4.703802] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.710928] ehci-orion: EHCI orion driver
[    4.715156] orion-ehci f1050000.usb: EHCI Host Controller
[    4.720606] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
[    4.728334] orion-ehci f1050000.usb: irq 26, io mem 0xf1050000
[    4.752436] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
[    4.758518] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    4.765354] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.772619] usb usb1: Product: EHCI Host Controller
[    4.777520] usb usb1: Manufacturer: Linux 4.6.6 ehci_hcd
[    4.782865] usb usb1: SerialNumber: f1050000.usb
[    4.787997] hub 1-0:1.0: USB hub found
[    4.791793] hub 1-0:1.0: 1 port detected
[    4.808918] usbcore: registered new interface driver usb-storage
[    4.825960] usbcore: registered new interface driver usblp
[    4.856731] Loading iSCSI transport class v2.0-870.
[    4.866037] iscsi: registered transport (tcp)
[    5.225963] EXT4-fs (sda5): mounting ext3 file system using the ext4 subsystem
[    5.332725] EXT4-fs (sda5): warning: maximal mount count reached, running e2fsck is recommended
[    5.362792] EXT4-fs (sda5): 2 orphan inodes deleted
[    5.367698] EXT4-fs (sda5): recovery complete
[    5.472488] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[    5.544601] random: mkswap urandom read with 66 bits of entropy available
[    5.585965] Adding 524284k swap on /dev/sda3.  Priority:-1 extents:1 across:524284k
[   17.637243] udevd (312): /proc/312/oom_adj is deprecated, please use /proc/312/oom_score_adj instead.
[   17.646613] udev: starting version 130
[   18.042761] random: nonblocking pool is initialized
[   18.367532] xhci_hcd 0000:01:00.0: xHCI Host Controller
[   18.372854] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[   18.440739] xhci_hcd 0000:01:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x00000010
[   18.744921] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   18.751768] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   18.759048] usb usb2: Product: xHCI Host Controller
[   18.763958] usb usb2: Manufacturer: Linux 4.6.6 xhci-hcd
[   18.769296] usb usb2: SerialNumber: 0000:01:00.0
[   18.775174] hub 2-0:1.0: USB hub found
[   18.779446] hub 2-0:1.0: 2 ports detected
[   18.783956] xhci_hcd 0000:01:00.0: xHCI Host Controller
[   18.789221] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[   18.796767] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[   18.805003] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[   18.811827] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   18.819095] usb usb3: Product: xHCI Host Controller
[   18.824004] usb usb3: Manufacturer: Linux 4.6.6 xhci-hcd
[   18.829347] usb usb3: SerialNumber: 0000:01:00.0
[   18.835086] hub 3-0:1.0: USB hub found
[   18.839350] hub 3-0:1.0: 2 ports detected
[   26.091791] EXT4-fs (sda8): warning: maximal mount count reached, running e2fsck is recommended
[   26.806909] EXT4-fs (sda8): recovery complete
[   26.832504] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: user_xattr,acl,nodelalloc
[   28.132714] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   31.133247] mvneta f1074000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[   31.141441] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@nas-mimismo:/ # ls -l /sys/devices/platform
total 0
drwxr-xr-x  3 root root    0 2018-01-01 12:00 alarmtimer
drwxr-xr-x  4 root root    0 1999-12-31 19:00 Fixed MDIO bus.0
drwxr-xr-x  4 root root    0 1999-12-31 19:00 gpio-keys
drwxr-xr-x  4 root root    0 1999-12-31 19:00 gpio-leds
drwxr-xr-x  3 root root    0 2018-01-01 12:00 gpio_poweroff
drwxr-xr-x  4 root root    0 1999-12-31 19:00 leds-ns2l
drwxr-xr-x  3 root root    0 2018-01-01 12:00 pmu
drwxr-xr-x  2 root root    0 2018-01-01 12:01 power
drwxr-xr-x  4 root root    0 1999-12-31 19:00 reg-dummy
drwxr-xr-x  5 root root    0 1999-12-31 19:00 regulators
drwxr-xr-x  3 root root    0 2018-01-01 12:00 regulatory.0
drwxr-xr-x  4 root root    0 1999-12-31 19:00 serial8250
drwxr-xr-x  7 root root    0 1999-12-31 19:00 soc
-rw-r--r--  1 root root 4096 2018-01-01 12:01 uevent
root@nas-mimismo:/ # ls -l /sys/devices/platform/leds-ns2l
total 0
lrwxrwxrwx  1 root root    0 2018-01-01 12:01 driver -> ../../../bus/platform/drivers/leds-ns2l
-rw-r--r--  1 root root 4096 2018-01-01 12:01 driver_override
drwxr-xr-x  3 root root    0 1999-12-31 19:00 leds
-r--r--r--  1 root root 4096 2018-01-01 12:01 modalias
lrwxrwxrwx  1 root root    0 2018-01-01 12:01 of_node -> ../../../firmware/devicetree/base/leds-ns2l
drwxr-xr-x  2 root root    0 2018-01-01 12:01 power
lrwxrwxrwx  1 root root    0 2018-01-01 12:01 subsystem -> ../../../bus/platform
-rw-r--r--  1 root root 4096 2018-01-01 12:00 uevent
m1m1sm1t1c0
 
Posts: 42
Joined: Tue Jun 28, 2016 12:50 pm

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby Jocko » Fri Feb 08, 2019 8:21 am

Hi

So it seems there is now something new...

Please to post
Code: Select all
ls -l /sys/devices/platform/leds-ns2l/leds
ls -l /sys/devices/platform/leds-ns2l/leds/*/*


and also
Code: Select all
ls -l /sys/class/leds
ls -l  /sys/class/leds/*
ls -l  /sys/class/leds/*/*
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby fvdw » Fri Feb 08, 2019 1:09 pm

:thumbup indeed so driver (leds-ns2l) seems to be loaded, proven by the line lrwxrwxrwx 1 root root 0 2018-01-01 12:01 driver -> ../../../bus/platform/drivers/leds-ns2l in this ouptut
Code: Select all
root@nas-mimismo:/ # ls -l /sys/devices/platform/leds-ns2l
total 0
lrwxrwxrwx  1 root root    0 2018-01-01 12:01 driver -> ../../../bus/platform/drivers/leds-ns2l
-rw-r--r--  1 root root 4096 2018-01-01 12:01 driver_override
drwxr-xr-x  3 root root    0 1999-12-31 19:00 leds
-r--r--r--  1 root root 4096 2018-01-01 12:01 modalias
lrwxrwxrwx  1 root root    0 2018-01-01 12:01 of_node -> ../../../firmware/devicetree/base/leds-ns2l
drwxr-xr-x  2 root root    0 2018-01-01 12:01 power
lrwxrwxrwx  1 root root    0 2018-01-01 12:01 subsystem -> ../../../bus/platform
-rw-r--r--  1 root root 4096 2018-01-01 12:00 uevent

I was already the case in kernel 8 but kernel 9 is little more sophisticate so lets continue with that for the moment
The probing of the driver gives no output if succesfull therefor no sign of it in dmesg

Anyhow, in folder /sys/devices/platform/leds-ns2l/leds there should be a folder (kernel #9) with name srn21c:white:sata0
In that folder several files should be present enabling us to change settings of the led

As I see Jocko already asked to post the content of that folder,
interesting will be the content of the file
/sys/devices/platform/leds-ns2l/leds/trigger
You can get content by using for example this command
Code: Select all
cat /sys/devices/platform/leds-ns2l/leds/trigger
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby m1m1sm1t1c0 » Fri Feb 08, 2019 1:43 pm

Code: Select all
login as: root
root@192.168.221.6's password:
root@nas-mimismo:/ # ls -l /sys/devices/platform/leds-ns2l/leds
total 0
drwxr-xr-x  3 root root 0 1999-12-31 19:00 srn21c:white:sata0
root@nas-mimismo:/ # ls -l /sys/devices/platform/leds-ns2l/leds/*/*
-rw-r--r--  1 root root 4096 2019-02-08 08:38 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/brightness
lrwxrwxrwx  1 root root    0 2019-02-08 08:38 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/device -> ../../../leds-ns2l
-r--r--r--  1 root root 4096 2019-02-08 08:38 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/max_brightness
-rw-r--r--  1 root root 4096 2019-02-08 08:38 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/sata
lrwxrwxrwx  1 root root    0 2019-02-08 08:38 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/subsystem -> ../../../../../class/leds
-rw-r--r--  1 root root 4096 2019-02-08 08:38 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/trigger
-rw-r--r--  1 root root 4096 2018-01-01 12:00 /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/uevent

/sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/power:
total 0
-rw-r--r--  1 root root 4096 2019-02-08 08:38 autosuspend_delay_ms
-rw-r--r--  1 root root 4096 2019-02-08 08:38 control
-r--r--r--  1 root root 4096 2019-02-08 08:38 runtime_active_time
-r--r--r--  1 root root 4096 2019-02-08 08:38 runtime_status
-r--r--r--  1 root root 4096 2019-02-08 08:38 runtime_suspended_time
root@nas-mimismo:/ # ls -l /sys/class/leds
total 0
lrwxrwxrwx  1 root root 0 1999-12-31 19:00 cumulus:red:sata0 -> ../../devices/platform/gpio-leds/leds/cumulus:red:sata0
lrwxrwxrwx  1 root root 0 1999-12-31 19:00 srn21c:white:sata0 -> ../../devices/platform/leds-ns2l/leds/srn21c:white:sata0
root@nas-mimismo:/ # ls -l /sys/class/leds/*
lrwxrwxrwx  1 root root 0 1999-12-31 19:00 /sys/class/leds/cumulus:red:sata0 -> ../../devices/platform/gpio-leds/leds/cumulus:red:sata0
lrwxrwxrwx  1 root root 0 1999-12-31 19:00 /sys/class/leds/srn21c:white:sata0 -> ../../devices/platform/leds-ns2l/leds/srn21c:white:sata0
root@nas-mimismo:/ # ls -l /sys/class/leds/*/*
-rw-r--r--  1 root root 4096 2019-02-08 08:39 /sys/class/leds/cumulus:red:sata0/brightness
lrwxrwxrwx  1 root root    0 2019-02-08 08:39 /sys/class/leds/cumulus:red:sata0/device -> ../../../gpio-leds
-r--r--r--  1 root root 4096 2019-02-08 08:39 /sys/class/leds/cumulus:red:sata0/max_brightness
lrwxrwxrwx  1 root root    0 2019-02-08 08:39 /sys/class/leds/cumulus:red:sata0/subsystem -> ../../../../../class/leds
-rw-r--r--  1 root root 4096 2019-02-08 08:39 /sys/class/leds/cumulus:red:sata0/trigger
-rw-r--r--  1 root root 4096 2018-01-01 12:00 /sys/class/leds/cumulus:red:sata0/uevent
-rw-r--r--  1 root root 4096 2019-02-08 08:38 /sys/class/leds/srn21c:white:sata0/brightness
lrwxrwxrwx  1 root root    0 2019-02-08 08:38 /sys/class/leds/srn21c:white:sata0/device -> ../../../leds-ns2l
-r--r--r--  1 root root 4096 2019-02-08 08:38 /sys/class/leds/srn21c:white:sata0/max_brightness
-rw-r--r--  1 root root 4096 2019-02-08 08:38 /sys/class/leds/srn21c:white:sata0/sata
lrwxrwxrwx  1 root root    0 2019-02-08 08:38 /sys/class/leds/srn21c:white:sata0/subsystem -> ../../../../../class/leds
-rw-r--r--  1 root root 4096 2019-02-08 08:38 /sys/class/leds/srn21c:white:sata0/trigger
-rw-r--r--  1 root root 4096 2018-01-01 12:00 /sys/class/leds/srn21c:white:sata0/uevent

/sys/class/leds/cumulus:red:sata0/power:
total 0
-rw-r--r--  1 root root 4096 2019-02-08 08:39 autosuspend_delay_ms
-rw-r--r--  1 root root 4096 2019-02-08 08:39 control
-r--r--r--  1 root root 4096 2019-02-08 08:39 runtime_active_time
-r--r--r--  1 root root 4096 2019-02-08 08:39 runtime_status
-r--r--r--  1 root root 4096 2019-02-08 08:39 runtime_suspended_time

/sys/class/leds/srn21c:white:sata0/power:
total 0
-rw-r--r--  1 root root 4096 2019-02-08 08:38 autosuspend_delay_ms
-rw-r--r--  1 root root 4096 2019-02-08 08:38 control
-r--r--r--  1 root root 4096 2019-02-08 08:38 runtime_active_time
-r--r--r--  1 root root 4096 2019-02-08 08:38 runtime_status
-r--r--r--  1 root root 4096 2019-02-08 08:38 runtime_suspended_time
root@nas-mimismo:/ #
m1m1sm1t1c0
 
Posts: 42
Joined: Tue Jun 28, 2016 12:50 pm

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby m1m1sm1t1c0 » Fri Feb 08, 2019 1:49 pm

Code: Select all
root@nas-mimismo:/ # cat /sys/devices/platform/leds-ns2l/leds/trigger
cat: /sys/devices/platform/leds-ns2l/leds/trigger: No such file or directory
m1m1sm1t1c0
 
Posts: 42
Joined: Tue Jun 28, 2016 12:50 pm

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby fvdw » Fri Feb 08, 2019 2:04 pm

oops my fault should be

Code: Select all
cat /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/trigger
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby m1m1sm1t1c0 » Fri Feb 08, 2019 2:07 pm

Code: Select all
root@nas-mimismo:/ # cat /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0
/trigger
[none] kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock nand-disk timer heartbeat cpu0 default-on
m1m1sm1t1c0
 
Posts: 42
Joined: Tue Jun 28, 2016 12:50 pm

Re: FVDW-SL on a Seagate Personal Cloud - additional steps

Postby fvdw » Fri Feb 08, 2019 2:29 pm

:thumbup
there is also this file
Code: Select all
/sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/sata

what is the content, (I guess it is zero)
Code: Select all
cat /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/sata

try to write the value 1 to it and see if the white led comes on and reacts on sata activity
Code: Select all
echo 1 > /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/sata


To switch it off write the value 0
Code: Select all
echo 0 > /sys/devices/platform/leds-ns2l/leds/srn21c:white:sata0/sata
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Seagate personal cloud

Who is online

Users browsing this forum: No registered users and 1 guest

cron