hean01
Re: Zyxel NAS326 - Debian / Boot from USB? October 31, 2016 03:58PM |
Okt 30 23:45:27 nas kernel: m25p80 spi0.0: > unrecognized JEDEC id bytes: ff, ff, ff> Maybe there's still something missing in the dts
CONFIG_SECCOMP=y> Otherwise journald fails to start.
Tasks: 57 total, 2 running, 55 sleeping, > 0 stopped, 0 zombie > %CPU0 : 0,0 us, 95,0 sy, 0,0 ni, 5,0 id, 0,0 > wa, 0,0 hi, 0,0 si, 0,0 st > KiB Spch: 511008 total, 445124 free, 15260 > used, 50624 buff/cache > KiB Swap: 2097148 total, 2097148 free, 0 > used. 484112 avail Spch > > PID USER PR NI VIRT RES SHR S > %CPU %MEM ZEIT+ BEFEHL > > > 233 root 20 0 0 0 0 R > 95,0 0,0 9:35.55 kworker/0:1> I have between 60% and 95% cpu last on this worker
musv
Re: Zyxel NAS326 - Debian / Boot from USB? October 31, 2016 05:34PM |
setenv bootargs "console=ttyS0,115200 root=/dev/sda1 init=/usr/lib/systemd/systemd" mw.l f1018100 20420000 mw.l f1018140 003ca800 usb reset scsi init ext4load usb 0:1 0x02000000 /boot/zImage_dtb bootz 0x02000000scsi init finds the sata harddisk. But I'm not able to boot from the hdd. "sata" gives me: bad device. I would like to get rid of the USB stick.
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 01, 2016 02:49AM |
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 01, 2016 02:18PM |
Marvell>> scsi reset Reset SCSI scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: WDC WD20EFRX-68E Rev: 82.0 Type: Hard Disk Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512) Found 1 device(s).
Marvell>> scsi part Partition Map for SCSI device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 2048 1951744 dcb760b0-01 83 2 1953792 19531776 dcb760b0-02 83 3 21485568 -409423872 dcb760b0-03 8e
Marvell>> ext2ls scsi 0:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found 153655 config-3.16.0-4-armmp 3186376 vmlinuz-3.16.0-4-armmp <SYM> 16 vmlinuz <SYM> 25 initrd.img 12528480 vmlinuz-3.10.39+ 2410201 System.map-3.16.0-4-armmp <SYM> 20 vmlinuz.old 13629076 initrd.img-3.16.0-4-armmp 1606946 System.map-3.10.39+ 77013 config-3.10.39+ 12528480 vmlinuz-3.10.39+.old 1606946 System.map-3.10.39+.old 77006 config-3.10.39+.old 3165230 initrd.img-3.10.39+
Marvell>> ext2load scsi 0:1 0x100000 vmlinuz 12528480 bytes read in 252 ms (47.4 MiB/s)
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 01, 2016 02:55PM |
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 01, 2016 03:44PM |
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 01, 2016 06:14PM |
Quote
hean01
How do you merge initrd with kernel image ?
Quote
hean01
Yes, I have the same problem, might be a kernel parameter to set a MAC ?
musv
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 12:59AM |
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 01:04AM |
Admin Registered: 14 years ago Posts: 19,533 |
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 01:09AM |
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 05:32AM |
Quote
musv
What do you need an initrd / initramfs for?
Quote
musv
I'm running Gentoo. And it's running fine so far.
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 11:15AM |
ethernet@70000 { status = "okay"; phy = <&phy0>; phy-mode = "rgmii"; };
ethernet@70000 { status = "okay"; phy-mode = "rgmii"; fixed-link { speed = <1000>; full-duplex; }; };
musv
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 11:23AM |
ext4ls scsi 0:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <DIR> 566 bin <DIR> 738 boot ...works fine. But
Marvell>> ext4ls scsi 0:1 boot < ? > 0 PHASES=install prepare test DEPEND=dev-scheme/gauche virtual/libffi Marvell>> ext4ls scsi 0:1 /boot < ? > 0 PHASES=install prepare test DEPEND=dev-scheme/gauche virtual/libffi Marvell>> ext4ls scsi 0:1 /boot/ < ? > 0 PHASES=install prepare test DEPEND=dev-scheme/gauche virtual/libffiIt seems ext4ls / ext4load has a problem with subdirectories on scsi devices.
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 12:23PM |
Quote
rr4m
So, we missed phy = <&phy0>; - that must be the case?
Quote
rr4m
And why the port speed is hardcoded?
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 12:49PM |
eth0: ethernet@70000 { compatible = "marvell,neta"; reg = <0x70000 0x4000>; interrupts-extended = <&mpic 8>; clocks = <&gateclk 4>; tx-csum-limit = <9800>; status = "disabled"; mac-address = [ 00 nn nn nn nn 01 ]; eth,port-num = <0>; eth,port-mtu = <1500>; };
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 01:08PM |
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 03:29PM |
Admin Registered: 14 years ago Posts: 19,533 |
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 04:14PM |
Quote
bodhi
Try removing it from the DTS, and harcode the MAC address in /etc/network/interfaces (or some systemd's equivalent network target if running systemd). That way the DTS is more resilient and does not cause problem in different box.
Re: Zyxel NAS326 - Debian / Boot from USB? November 02, 2016 05:06PM |
Admin Registered: 14 years ago Posts: 19,533 |
musv
Re: Zyxel NAS326 - Debian / Boot from USB? November 04, 2016 05:53PM |
setenv bootargs "console=ttyS0,115200 root=/dev/sda2 init=/usr/lib/systemd/systemd" setenv bootcmd "mw.l f1018100 20420000; mw.l f1018140 003ca800; scsi init; ext2load scsi 0:1 0x02000000 /zImage_dtb; bootz 0x02000000" saveenv reset
printenv bootargs bootargs=console=ttyS0,115200 root=/dev/sda2 init=/usr/lib/systemd/systemd printenv bootcmd bootcmd=nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000"
Re: Zyxel NAS326 - Debian / Boot from USB? November 04, 2016 09:13PM |
Admin Registered: 14 years ago Posts: 19,533 |
setenv bootargs "console=ttyS0,115200 > root=/dev/sda2 init=/usr/lib/systemd/systemd" > setenv bootcmd "mw.l f1018100 20420000; mw.l > f1018140 003ca800; scsi init; ext2load scsi 0:1 > 0x02000000 /zImage_dtb; bootz 0x02000000" > saveenv > reset>
printenv bootargs > bootargs=console=ttyS0,115200 root=/dev/sda2 > init=/usr/lib/systemd/systemd > > printenv bootcmd > bootcmd=nand read 0x2000000 0x08700000 0xF00000 && > bootz 0x2000000">
hean01
Re: Zyxel NAS326 - Debian / Boot from USB? November 05, 2016 03:46AM |
Quote
musv
Seems, every environment variable will be stored persistently except bootcmd. For some reason bootcmd will be reset to the default value.
Any idea how to get bootcmd changed in order to survive the next reboot?
Re: Zyxel NAS326 - Debian / Boot from USB? November 05, 2016 04:28AM |
Admin Registered: 14 years ago Posts: 19,533 |
help
musv
Re: Zyxel NAS326 - Debian / Boot from USB? November 05, 2016 04:08PM |
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 05, 2016 10:41PM |
Quote
musv
Seems, every environment variable will be stored persistently except bootcmd. For some reason bootcmd will be reset to the default value.
Re: Zyxel NAS326 - Debian / Boot from USB? November 06, 2016 04:17PM |
Admin Registered: 14 years ago Posts: 19,533 |
musv
Re: Zyxel NAS326 - Debian / Boot from USB? November 11, 2016 01:04PM |
Nov 11 19:54:09 nas kernel: NFSD: unable to generate recoverydir name (-2). Nov 11 19:54:09 nas kernel: NFSD: disabling legacy clientid tracking. Reboot recovery will not function correctly! Nov 11 19:54:14 nas kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x41d0000 action 0xe frozen Nov 11 19:54:14 nas kernel: ata1: irq_stat 0x80000040, connection status changed Nov 11 19:54:14 nas kernel: ata1: SError: { PHYRdyChg CommWake 10B8B Dispar DevExch } Nov 11 19:54:14 nas kernel: ata1: hard resetting link Nov 11 19:54:15 nas kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 19:54:15 nas kernel: ata1.00: configured for UDMA/133 Nov 11 19:54:15 nas kernel: ata1: EH complete Nov 11 19:54:19 nas systemd-timesyncd[2222]: Synchronized to time server 192.168.109.1:123 (192.168.109.1). Nov 11 19:54:19 nas systemd[1]: Time has been changed Nov 11 19:54:36 nas kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x41d0000 action 0xe frozen Nov 11 19:54:36 nas kernel: ata1: irq_stat 0x80000040, connection status changed Nov 11 19:54:36 nas kernel: ata1: SError: { PHYRdyChg CommWake 10B8B Dispar DevExch } Nov 11 19:54:36 nas kernel: ata1: hard resetting link Nov 11 19:54:37 nas kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 19:54:37 nas kernel: ata1.00: configured for UDMA/133 Nov 11 19:54:37 nas kernel: ata1: EH complete Nov 11 19:55:12 nas kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x41d0000 action 0xe frozen Nov 11 19:55:12 nas kernel: ata1: irq_stat 0x80000040, connection status changed Nov 11 19:55:12 nas kernel: ata1: SError: { PHYRdyChg CommWake 10B8B Dispar DevExch } Nov 11 19:55:12 nas kernel: ata1: hard resetting link Nov 11 19:55:13 nas kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 19:55:13 nas kernel: ata1.00: configured for UDMA/133 Nov 11 19:55:13 nas kernel: ata1: EH complete Nov 11 19:55:46 nas systemd[1]: Mounting /usr/portage Squash-Portage... Nov 11 19:55:46 nas systemd[1]: Mounted /usr/portage Squash-Portage. Nov 11 19:55:46 nas systemd[1]: Starting Squash Portage... Nov 11 19:55:46 nas systemd[1]: Started Squash Portage. Nov 11 19:56:00 nas kernel: ata1: limiting SATA link speed to 3.0 Gbps Nov 11 19:56:00 nas kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x41c0000 action 0xe frozen Nov 11 19:56:00 nas kernel: ata1: irq_stat 0x80000040, connection status changed Nov 11 19:56:00 nas kernel: ata1: SError: { CommWake 10B8B Dispar DevExch } Nov 11 19:56:00 nas kernel: ata1: hard resetting link Nov 11 19:56:01 nas kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 11 19:56:01 nas kernel: ata1.00: configured for UDMA/133 Nov 11 19:56:01 nas kernel: ata1: EH complete
musv
Re: Zyxel NAS326 - Debian / Boot from USB? November 12, 2016 03:21PM |
echo 'min_power' > /sys/class/scsi_host/host[01]/link_power_management_policySeems, the SATA controller doesn't like a power save modus. After changing it back to max_perfomance the errors disappeared.
CONFIG_SECCOMP=y # needed by systemd CONFIG_TASKSTATS=y # needed by iotop CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_IO_ACCOUNTING=y CONFIG_IKCONFIG=y # /proc/config.gz CONFIG_IKCONFIG_PROC=y CONFIG_SLUB=y CONFIG_SLUB_CPU_PARTIAL=n CONFIG_CC_STACKPROTECTOR_STRONG=y CONFIG_EFI_PARTITION=y # GPT-Support CONFIG_MACH_ARMADA_370=n # no need as we have a 380. CONFIG_MACH_ARMADA_375=n CONFIG_MACH_ARMADA_39X=n CONFIG_MACH_ARMADA_XP=n CONFIG_MACH_DOVE=n CONFIG_BLK_DEV_LOOP=y # Loopback-Device CONFIG_IP_MULTICAST=y # Multicast-Support (Minidlna) CONFIG_IP_MROUTE=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y CONFIG_WLAN=n # no wifi CONFIG_WIRELESS=n CONFIG_TRIM_UNUSED_KSYMS=y # Trim Modules
General Setup -> Timers subsystem: Timer tick handling: HZ_PERIODIC, NO_HZ_IDLE, NO_HZ_FULLI didn't find anything about this. Does ARM / Armada support dynticks? Currently we use HZ_PERIODIC.
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 13, 2016 08:33AM |
Quote
armada 370 datasheet, page 44
The key power save options provided by the devices include:
The device also provides many wake-up options from the power save modes. These include:
- CPU Idle (dynamic clock gating)
- L2 Idle (dynamic clock gating)
- CPU Deep Idle (CPU and L2 are powered down, context is stored in the DRAM and coherent I/O transactions are routed directly to the DRAM)
- DRAM self refresh and power down modes
- EEE (Energy Efficient Ethernet) and LPI (Low Power Idle) support
- SERDES power down options
- USB interface placed in suspend mode
- Shutdown or clock gating of non-used units and interfaces
- PCIe power save states
- An extended Wake On LAN (WOL) definition
- Wake on USB
- Wake by a System Timer / RTC Alarm
- Wake on GPIO interrupt
For further information about the Power Management capabilities, see Section 28, Power Management, on page 383.
'sudo reboot' works for me - as I said, my kernel+initramfs flashed to NAND, so default bootcmd just works - system boots/reboots itself without requiring any manual action.Quote
musv
Things, that aren't working yet:
shutdown and reboot: The device stops, but the LEDs remain shining.
rr4m
Re: Zyxel NAS326 - Debian / Boot from USB? November 13, 2016 08:40AM |
/dev/sda { apm = 126 spindown_time = 240 } /dev/sdb { apm = 126 spindown_time = 240 }