So I changed over the holidays a few things in the initrd: check my github Dropbear: + changed port to 2222 + readded fingerprint + pubkey unlock possible: stored on nand Crypto: add key unlock from nand / usb: +nand /dev/mtd5: /initrd/key.luks +usb LABEL=key: /key.luks Initrd + changing and save/store root-password on nand + resuming boot-script (buggy /switch_root not workby Peacemaker - Debian
As I'm not using (and never realy had used) LVM, I'm not realy into the problems there. I'll look into it tomorrow or you can just make a commit :-) Cheers Carlby Peacemaker - Debian
hey Martin, I add crypt-lvm support, so it should boot now your system, and as written above ssh PATH is now right. For writing things in "config" and provide "key" options might be good idea. I'll think about it. The most beautiful way, would be a small webserver for key insert and configuration, but this is to much effort for this project. So your right, keep it sby Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > thanks, I'm testing it at the moment. > cryptsetup is working and so is lvm. god to hear :-) > What is missing is mke2fs in the "real" version, > which can also make ext4-filesystems. OOps, I see its allready in (twice) as mkfs.ext3 / mkfs.ext4, but I'll change that. > Also isthby Peacemaker - Debian
So small update on initrd: +scp now working +crypto / LUKS working and has to be unlocked by key via dropbear +LVM ( but not tested) TODO: - dropbear has wrong PATHby Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > Have you made any progress on the init-stuff > (raid, crypto, ssh)? I updated my github, but git and empty folders are not the best friends :-|, but the uInitrd is also uploaded + raid works(mdadm + btrfs). + If it can't boot it drops to a ssh shell. crypto I'm working on. Futher problems: ssh/scby Peacemaker - Debian
I change the mcm-daemon in my github: - removed shutdown - tweaked the fan a bit So the mcm-daemon works with the your patched kernel. QuoteThe fan can't get turned of on halt as the cpu and the disks would be left running anyways. hm,.. but disk's and cpu should be powered down on "halt", and my old nas rn102 did so, but I can live with this :-)by Peacemaker - Debian
Again, great work! Reboot & Poweroff is working :-), but halt did not turn off the fan :-/by Peacemaker - Debian
Great work ! I'll test this soon and deleat the reboot / powerdown from the mcm-daemon Just a remarks on naming: I'm wondering if ex2u is the right name for "this" device. As the mcm2 and ex2u is basicly the same device so i thought wd-385 might be better. But I'm open with naming, but think consist naming is a good idea.by Peacemaker - Debian
Okay, this makes sens and seems to be right: With kernelsetting: optimized for size it's booting :-) Cheers Carlby Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > Hi Carl, > > I got my second ex2u modified for serial console > and started to try booting flashed kernels. > > With that I experienced the same problem as when > booting from usb, that the kernel size matters if > it succeeds or not. > > You can check if the kernel would work from flasby Peacemaker - Debian
For normal use the rtc in the mcu does not matter, so you a right. But to get the alarmclock / rtc-wakeup working the mcu-rtc has to work, and be set correct.by Peacemaker - Debian
Hey Martin, I didn't do much for the NAS this weekend as well :-) (fixing my crappy pogoplug was enough). QuoteMM * What can be done in userspace should be done in userspace. * We have a working driver which already claims the device and controls it correctly (aka serial_io). * serial access from within the kernel over the existing driver is possible but cumbersome as one would need toby Peacemaker - Debian
QuoteMM I guess the direction to continue is to make the device shutdown or reboot reliable in debian and forget about the wol stuff for now. Yes, I fully agree to you. I see 2 - 3 ways to do so. 1. quick and dirty: 2 bash-scripts add them to the systemd shutdown and reboot command. Maybe I'll do it for first to get shit down :-) + combine this with a new and better fan script and geby Peacemaker - Debian
Woow, nice work with the soldering :-), I'll upload the mcm-daemon to my github (you'll be welcome to contribute there:-)) QuoteI also observed, that when executing "service mcm-daemon stop" in Debian, the device immediatelly shuts off. I know, thats why it should be killed as the last process. Somehow there might be a delay in the code, but this delay is not working :-/by Peacemaker - Debian
good to know. And thanks, I'll add your patch to my kernel and update my github. Now the reset and WoL is missing :-) Cheers Carlby Peacemaker - Debian
hm,.. strange. Bytes transferred = 2806891 (2ad46b hex) ## Booting image at 01200000 ... ## Booting kernel from Legacy Image at 01200000 ... Image Name: 385-WD Created: 2016-12-01 20:04:18 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3734188 Bytes = 3.6 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ##by Peacemaker - Debian
Hey are you sure, that the armada-wd-385.dtb is build correct? It looks that there might be a problem, cheersby Peacemaker - Debian
Hey Martin, I updated the kernel and it boot's like charm. So you can do this your own export ARCH=arm make CROSS_COMPILE=arm-linux-gnuabihf- cp armada-385-wd.dts arch/arm/boot/dts/ make menuconfig make zImage make armada-385-wd.dtb cat arch/arm/boot/zImage arch/arm/boot/dts/armada-385-wd.dtb > zImage+dts mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000by Peacemaker - Debian
Hey, no as its for the mainline / stabile kernel from kernel.org. I just used the gcc-linux-gunaebihf compiler with the debian toolchain. So nothing from WD or Marvell.by Peacemaker - Debian
So I attached dts and .config for the mainline-kernel to this post. Couldn't test the kernel today or provide a patch.by Peacemaker - Debian
I'll upload later this week the .config and the DTS for the mainline kernel to my github. But I can recompile the Kernel with nfs as well. Cheersby Peacemaker - Debian
> I just wanted to try the debian and obtain some > performance figures. Can you tell me more? > I also read the WOL message from the serial > terminal, but was not able to wake it up, even > with the original firmware. Didn't try that > Have you documented somwhere how you prepared > kernel, ramdisk and root-filesystem and what > changes you had to dby Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > Hi Peacemaker, > > thanks a lot. > > I tried it and it worked. I put your kernel and > ramdisk on partition 1 on a fat-filesystem in > /boot/uramdisk and /boot/uimage and your tar file > on partition 2 with an ext4 filesystem together on > an usb-stick. > > I can boot it by pressinby Peacemaker - Debian
Sooooo,...finaly I would say BETA :-) You can find in my Dropbox: WD Folder + Ramdisk / uInitrd + 4.8.6 Kernel + Rootfs (MCMgen2-jessie-basic-armhf.tar.xz) Short howto: + Create a partiton labeled "rootfs" and extract rootfs as root or sudo sudo tar -xJvf MCMgen2-jessie-basic-armhf.tar.xz sync You can use USB-Drive or HDD; ext3/4, btrfs, xfs are supportedby Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > fancontrol (on original firmware is) > echo -e "\372\2\0\0\0\0\373" > /dev/ttyS1 # for > minimum speed > echo -e "\372\2\0\377\0\0\373" > /dev/ttyS1 # for > maximum speed > > speed is encoded in 4th byte from 0 to 255 > > tested on an Mycloud EX2 ultra > >by Peacemaker - Debian
Small update: MCU is attached to ttyS1 @ 19200 Powerled & Hardreset like MCM gen1 # Led on: "\\xfa\\x03\\x06\\x01\\x00\\x01\\xfb" # Led off: "\\xfa\\x03\\x06\\x00\\x00\\x01\\xfb" # Led blink: "\\xfa\\x03\\x06\\x02\\x00\\x01\\xfb" # Hard shutdown: "\\xfa\\x03\\x03\\x01\\x01\\x14\\xfb" Fan seams to be different.by Peacemaker - Debian
So update :-) I fixed these problems with new dts file and can boot debian. .dts and .config for a 4.6.7 kernel is attached Problems left: - uBoot not writeable / need to change bootarg's every boot - fan control not working -> fan only 100% rpm - Ethernet is renamed every boot (?!) -> Done - CPU-load from kworker/1:2 - only one instead of 7 mtd-partitons So my "by Peacemaker - Debian
Okay for now I managed to boot a 4.6 Kernel with vendors *.dtb So I've tried to port the vendors *.dts to the mainline kernel. But I ran into some trouble: peacemaker@debianvm:/media/data/linux-4.6.7$ make -j8 zImage armada-385-ex2.dtb CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h DTC archby Peacemaker - Debian
Building / Recompiling UBoot is quite easy with the gpl-sources. But I didn't found out how to boot or restore uBoot over UART / Xmodem or so if sth. went wrong. Any idea or experience how to do so on a 38x ? Compiling a 4.4 oder 4.6 Kernel was not so easy, and I had no sucess in booting this image. Recompile vendors 3.10.38 Kernel was there better, could add modules for dvb, wirelesby Peacemaker - Debian