Ok, so what is your advice ? uImage and uRam in a tftp server, rootfs in a usb and data in a Raid ?by i5Js - Debian
Hi, I found why it was not working with the kernel 6, it was the kernel config. I have it up and running: root@wdmycloud:~# uname -a Linux wdmycloud 6.0.10+ #1 SMP Tue Nov 29 14:49:09 CET 2022 armv7l GNU/Linux The sizes are perfect for the nand. @bodhi, any tip to flash it? Then I should modify the envs to get the rootfs from the hard drive.by i5Js - Debian
Ok, I will update the uRamdisk. I have also compiled a new Kernel 6 and uRamdisk, but I don't understand what means the lines after "Starting kernel..." but it stops there: Marvell>> setenv fdt_skip_update yes Marvell>> setenv bootargs console=ttyS0,1152by i5Js - Debian
With K6, can't detect or mount sda2 Marvell>> setenv fdt_skip_update yes Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda2 Marvell>> setenv initrd_high 0xffffffff Marvell>> setenv ipaddr 192.168.1.110; setenv serverip 192.168.1.23; tftp 0xa00000 uimagek6; tftp 0x1200000 uramdisk Using egiga2 device TFTP from server 192.168.1.23; our IP address iby i5Js - Debian
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns futex hash taby i5Js - Debian
Game, Set and Match!!! Marvell>> setenv fdt_skip_update yes Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda2by i5Js - Debian
I do not understand why it can't mount /dev/sda2, It's ext3, but at least, I know the uImage works!!!! Can we get with that log a memory address to load uImage an uRamdisk?by i5Js - Debian
lMovable zone start for each node Early memory node ranges node 0:by i5Js - Debian
@bodhi, you are a fucking genius!!! Marvell>> setenv fdt_skip_update yes Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda2by i5Js - Debian
Thanks, I will try with tftp. About the post, i read it too. And it seems, but I don’t know really, or how to test it, that the boxes that were in WD Cloud 5, have the same behavior. Regardsby i5Js - Debian
Thanks, but.... Marvell>> usb start (Re)start USB...by i5Js - Debian
Marvell>> usb start (Re)start USB... USB0:by i5Js - Debian
I have created two partitions, because for some strange reason, at marvel prompt, it doesn’t recognize the ext3 partition. So there are two: one in fat32 with uFiles and ext3 with the rootfs. I can try ext2load and see….by i5Js - Debian
This is the out put of my cpuinfo root@MyCloudEX2Ultra root # cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 1 (v7l) BogoMIPS : 2655.84 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x4 CPU part : 0xc09 CPU revision : 1 processor : 1 model name : ARMv7 Processor rev 1 (v7l) BogoMIPS : 26by i5Js - Debian
I have testes with an smaller Ramdisk, but... same Marvell>> setenv fdt_skip_update yes Marvell>> setenv initrd_high 0xffffffff Marvell>> setenv bootargs root=/dev/sda2by i5Js - Debian
I have also tried with another address, without luck Marvell>> setenv fdt_skip_update yes Marvell>> setenv initrd_high 0xffffffff Marvell>> setenv bootargs root=/dev/sdaby i5Js - Debian
Hey Bodhi, Thanks for your answer, it didn't work Marvell>> setenv fdt_skip_update yes Marvell>> setenv initrd_high 0xffffffff Marvell>> setenv bootargs root=/dby i5Js - Debian
Testing with one of your kernels Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00by i5Js - Debian
I think it is my exactly same situation.. totally silence. Marvell>> fatload usb 0:1 0x02000000 boot_mio/uImage reading boot_mio/uImage 3886355 bytes read in 153 ms (24.2 MiB/s)by i5Js - Debian
and another Marvell>> fatload usb 0:1 0x00a00000 boot_mio/uimage reading boot_mio/uimage 3886355 bytes read in 154 ms (24.1 MiB/s)by i5Js - Debian
New attempt, with different memory address to load the uRam and the uImage Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 1 Iby i5Js - Debian
Bumping this topic to avoid create more. I have the Ex2 Ultra, with the uart working, I have created my own uImage and uRamdisk, basically using theses steps: https://github.com/Heisath/wdmc2-kernel but using the 385 file for the ultra I found here in other thread. I have also patched the u-boot. I'm trying to boot from usb first, to test them, but doesn't works: Marvell>by i5Js - Debian
As expected, flashing the latest stock firmware didn’t fix or enable the uart :)by i5Js - Debian
Hi all, I have a WD EX2 Ultra, and I need the help who has the same box, and the u-boot updated. I’ve solder the uart interface but it doesn’t work. I don’t know why, but I don’t get anything when the nas boot up. I press space, 1, all the combinations available,but nothing works. I have tested the connections several times, and it seem they are fine. WIth a multi tester I see therby i5Js - Debian
I was meaning to get the WD firm back to get the console enable.. because it’s very strange that it doesn’t work at all. I was thinking it was because of the firmware and the chance it had not enable by defaultby i5Js - Debian
Hey, Many thanks for your advice. Honestly I think the best options is ask for a dump, because I don’t know what I can check to figure out why the console is not working. Perhaps I need to go to the orignal WD firmware? I will try to contact CyperPK or vzhilov and let’s see if they can dump their u-boot. Thanks again for all your time and advices with my issue. Bestby i5Js - Debian
Reading and reading, I think the problem here, perhaps, is the u-boot: 1) Update u-boot. It is needed to adjust load addresess for new Kernel and Ramdisk. See UBoot folder for details. Checking this: https://github.com/vzhilov/WDMC-Ex2-Ultra/tree/master/1.UBoot I have dumped the u-boot and the size is significantly different: -rwxr-xr-x 1 root 0 5.0M Jan 1 00:03 uby i5Js - Debian
last test: new uImage, old RamDisk in USB1 + USB2 attached -> Doesn't boot new uImage, new RamDisk in USB1 + USB2 attached -> Doesn't boot new uImage, new RamDisk, renamed as uInitrd in USB1 + USB2 attached ->It boots but in WD recovery, no ssh access just web to upload a firmware new uImage, old RamDisk in USB1+hardrive with rootfs -> Doesn't boot new uImage,by i5Js - Debian
bodhi Wrote: ------------------------------------------------------- > i5Js , > > Follow the instruction and create the released > rootfs > Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 > on a different USB drive. > > You need to do Step 3 and use > armada-385-wd-ex2-ultra.dtb > > Quote3. Create uImage with DTB appended. I am > using the Zyxelby i5Js - Debian
We are close: Bonus: new kernel+new Ramdisk, but remain the name as uInitrd -> The box boot it up in safe mode, I can access to the web interface to flash whatever. Bonus2: new kernel+old Ramdisk, but remain the name as uInitrd -> The box boot it up in safe mode, I can access to the web interface to flash whatever.by i5Js - Debian