Hello, so i manage to install debian and Open Media Vault on the MCHD. Right now it works but have some problems because i reuse the system of the MCH, this are the problems that right now i found:
-power off button don´t work.
- boot takes a lot of time because of some scripts that try to mount MCH partitions(i need to delete those scripts).
- I have less than 40 mb of space on the usr partition, because of the original partition layout of the 4 GB eMMC of the MCHD.
Beware that i’m not an expert, i´m not a programmer or a developer, so be careful, you can convert your device into a brick. BEFORE you do any of my steps, make a full backup of your emmc, if you don’t know how to do it, i recommend to stop right now and wait for a simpler and safer method of installation.
What I did step by step (I put a link to the required files at the end):
-First I compiled a new bootloader from the source deactivating the firmware checksum
-You need to connect the device to UART and powered off, open boot_recovery.exe from kylin_bootcode_recovery_tool_v1.4.
- “lk option” must be unchecked, select “RTD1296_hwsetting_BOOT_2DDR3_4Gb_s1600_DDRSS.config” as the HW setting file and “wd_pelican.uboot32.fb.dvrboot.exe.bin” as dvrboot.bin file, press write button (with device always off)
- Now you can power on the device, the process is automatic, and on the end you must receive an ok message. THIS CHANGE YOUR BOOTLOADER!!!
-Now you can boot into recovery with the usb files that i post, in recovery you need to write the new kernel (compiled with PARANOID_ANDROID option deactivated), new rootfs (modified to pass the root to debian), and format the required partitions and untar the files of the new operating system (this files are from forth32 debian installer for the MCH). I wrote the kernel and rootfs on the first addres that i think it was located (by the boot log from UART) and also on the recovery address, i already have done it because I was trying different methods, but maybe you just need to write it to the load address, and don´t need to write to recovery. CHECK THE MEMORY ADDRESSES with your boot log, on the section that says “LOAD NORMAL FW TABLE”, I don´t know if always are the same between firmware versions.
Commands to copy:
kernel: busybox dd if=Image of=/dev/mmcblk0 seek=50331648 bs=1 conv=notrunc
kernel recovery: busybox dd if=Image of=/dev/mmcblk0 seek=80674816 bs=1 conv=notrunc
Rootfs: busybox dd if=rootfs.bin of=/dev/mmcblk0 seek=35651584 bs=1 conv=notrunc
Rootfs recovery: busybox dd if=rootfs.bin of=/dev/mmcblk0 seek=97452032 bs=1 conv=notrunc
Formating filesystem:
make_ext4fs -L debian /dev/mmcblk0p2
make_ext4fs -L var /dev/mmcblk0p5
make_ext4fs -L usr /dev/mmcblk0p6
create new folder or reuse the existing ones on the /mnt/ folder to mount the 3 partitions, and untar with this command “tar zxf” every file on their corresponding partition:
- 20-root.tar.gz on mmcblk0p2
-21-var.tar.gz on mmcblk0p5 - 22-usr.tar.gz on mmcblk0p6
Done, unmount the partitions, and restart your device, after a few minutos you can access to OpenMediaVault (admin/admin) and connect via ssh (root/root).
I think that maybe writing a full raw eMMC image you can achieve the same result, but I don’t know, because i think that the mac address and serial number are stored on a different chip, and no directly on the eMMC, but i don´t share a image until someone who knows more about this can confirm that.
In the next days i´m gonna mess with the partitions, to see if stils boots making mmcblk0p2 one big partition, to have more space for updates and plugins. Sorry for my english, and if anyone that understand about this more that i do want to create an script, or improve the OS, please do it. This device with open media vault is a snappy compact nas.
Files: 581.17 MB folder on MEGA
