Thank you. Ok, I will take your last version of .dts file for Ex2-Ultra, config from @bodhi and will recompile the kernel again. Do I have to do below before I compile: patch -p1 -d linux-stable < GrandTeton-20170708.patch to patch U-Boot and unblock `setev`? For the uRamdisk I still would like to have Busybox with minimal setup which only decrypts the HDDs and switches the booby vzhilov - Debian
Ok, I gave up trying to squize evertying into nand and decided to boot from flash drive as all you guys do. When I boot from USB with reset button pressed I get kernel panic with VFS: Cannot open root device "ram" on unknown-block(1,0) But I still can boot with usb start fatload usb 0:1 0xa00000 boot\uImage fatload usb 0:1 0x2000000 boot\uRamdisk bootm 0xa00000 0x2000by vzhilov - Debian
QuoteYou can try to assign another memory location for the uRamdisk, please try at 0x2000000 Yes, that worked! I will try now your instructions to make it persistent. But what is the reason for Quoteoverlaps in-use memory region - disabling initrd Does it mean that Kernel is still too big? Or I need to make uRamdisk smaller? Or the only solution is to patch the U-Boot?by vzhilov - Debian
I'm attaching my config file, slightly changed from bodhi to make the size of kernel a bit less. Here is the .dts file from Fox I'm using: /* * Device Tree file for Marvell Armada 375 evaluation board * (DB-88F6720) * * Copyright (C) 2014 Marvell * * Gregory CLEMENT <gregory.clement@free-electrons.com> * Thomas Petazzoni <thomas.petazzoni@free-electrons.cby vzhilov - Debian
I'm not bricked. I can boot with my old parameters without having rootfs on USB. I'm going to boot BusyBox from nand partition. I'm looking to avoid using USB drive for booting. I do have my own Initrd and rootfs. But I really suffer from having old kernel as I can't update cryptsetup in Initrd. And the one you have (5.5.3) doesn't boot with my setup giving the aboveby vzhilov - Debian
QuoteYou'are very close to get it booted. This problem "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)" is easy to solve. Is there anything I could do?by vzhilov - Debian
QuoteI point you that our devices have an hw crypto engine (CESA) that can be used to improve disk encryption Interesting, I probably should re-encrypt by HDD raid then. Thank you for this. QuoteAlso, note that this device has the same hardware of WD My Cloud Mirror Gen 2 I have tried the .dts file from that device but I still have no luck to boot. But I think I do have correct .dtsby vzhilov - Debian
My kerlen is /dev/mtdblock1 (5Mb), my initrd is /dev/mtdblock2 (5Mb). Then I have two HDD 5Tb plugged. It is raid /dev/md0. Initrd decrypts /dev/md0: cryptsetup luksOpen /dev/md0 cryptroot --key-file luks.key lvm vgscan --mknodes lvm vgchange -a ly lvm vgscan Cryptroot is LVM and it has /dev/MyVolGroup/root (4Gb), /dev/MyVolGroup/swap (512Mb) and /dev/MyVolGroup/data (4.5Tb). Rootfs iby vzhilov - Debian
Thank you very much for paying attention to my question. Your Initrd is too big for my /dev/mtdblock2 (5Mb). My flow is that I boot from custom Initrd just to decrypt the HDD raid and switch futher booting to HDD where I have the full Debian 10. So I use Busybox for Initrd with a very minimal amount of scripts + TFTP support to download encryption key file + cryptsetup to decrypt HDD raid.by vzhilov - Debian
By now I have found your config file for the kernel in you .deb arhive and compiled .dtb and new uImage file. The uImage was still slightly bigger than 5Mb and was not fitting to /dev/mtdblock1. So I took all TV/Radio/Video modules off from your kernel config (put "=m"). Then the kernel got less and did fit. But I can't boot. I get QuoteKernel panic VFS: Unable to mount rby vzhilov - Debian
Thank you. I did that. As I understood I store RAM Disk in /dev/mtdblock2 and kernel in /dev/mtdblock1. The device wouldn't be able to start without those. Where else I can put the kernel?by vzhilov - Debian
Hello! I've got WD MyCloud EX2 Ultra, a device with 1Gb of RAM and 2 slots for HDDs. I do have access to the serial console. I attach screenshot of my boot log. I have actually collected different pieces of data into my github with customized uImage and uInitrd. But I would like to update cryptsetup version for whole disk encryption which requires new glibc 2.25 which requires new kernby vzhilov - Debian
Thank you. Great Job! I couldn't find DTB for armada-385-wdmc-Ex2-Ultra in your DTS folder in linux-5.5.3-mvebu-tld-1-bodhi.tar.bz2 so I tried armada-375-wd-mycloud-gen2.dtb - but it didn't boot. Then I tried armada-385-wd-ex2100.dtb but it made uImage greater that 5Mb in size and didn't fit into the ROM. Is it possible to make such a DTB file or give instuctions hby vzhilov - Debian