bodhi don't take me wrong, you are doing an awesome job here. I never said kernel was unstable, just my specific installation on my device behaved not very good. Random lockups, freezes and therefore data corruption. Openvpn and OMV will run on it, of course. But the performance will be poor, especially openvpn, I could not get above 5Mbits/s bandwidth (on my wrt1200ac I get above 100MBps)by mgx - Debian
well, the extras you need is exactly the performance demanding things, especially openvpn. I would not go with this, this hardware is way too old to give you openvpn performance. But you could want to see yourself, it's worth the experience I thinkby mgx - Debian
Sheevaplug is not suitable for this device when flashed. Only uart works, I can paste my notes if you want. But I don't remember exact details, you have to elaborate yourself I have ended up with stock u-boot, linux kernel flashed to flash and rootfs was on local disk. But Debian was unstable, not able to handle high load, not very good for production use. So I threw away the board and puby mgx - Debian
yeah all sorted, thanks :)by mgx - Debian
Aaaah yes, that's perfect, thanks a lot! You are the king! but there is a problem with module: root@iomega:~# modprobe cifs modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.10.7-kirkwood-tld-1/modules.dep.bin' modprobe: FATAL: Module cifs not found in directory /lib/modules/5.10.7-kirkwood-tld-1 root@iomega:~# cd /liby mgx - Debian
Thanks bodhi, Just one question: is it possible the latest kernel does not include support for cifs? Cannot map any smb Can I fix it somehow on my end? Thanks a lotby mgx - Debian
okay so here is a bit longer post. Here is what I did. It does not really matter how the device is booting at the beginning. On the end it will boot linux from NAND. so as I said the main goal was to install e2fsprogs and fuse. But that generated new initrd, so let's start with this #install fuse and e2fsprogs will generate new initramfs root@iomega:~# sudo apt install --reinstallby mgx - Debian
yah understood. Now I'm preparing 5.10.7-kirkwood-tld-1 kernel and initrd for booting and once I have it ready I will paste here what I'm doing. Thanks a lot for response, I appreciateby mgx - Debian
Hi bodhi, thanks for the response. Well, now I have only one problem I cannot live with: initrd does not contain fuse and e2fsck and I don't really know how I could produce new initrd that could be used for booting. I have followed your instructions to build the kernel image and initrd here: https://forum.doozan.com/read.php?2,12096 I used method 4B, to include DTB file in the keby mgx - Debian
Hello, i have bought a faulty iomega ix4-200d which got the NAND flash erased. long story short, following this topic https://forum.doozan.com/read.php?3,25120 I have now fully working iomega ix4-200d grandpa. Problem was, that SHEEVAPLUG U-Boot could not be booted off the flash and the mtd0.bin file I have found in that thread did not recognize USB devices, so current status is: kernel: Liby mgx - Debian
well looks like I have found a way: 1. erased flash completely 2. loaded one of stock u-boots into flash 3. added DTS to kernel 4. tftpbooted u-boot into memory and nand write.e ADDR 0x0 blablabla the uboot location 5. reboot, tftpboot kernel and initrd 6. wrote kernel and initrd into flash (since the uboot does not know "usb" command) 7. rootfs is on a 20GB ext2 partition on 3by mgx - uBoot
Hi there, I am reading this all over and over again but cannot get out of the hell. I have bought ix4-200d without drives. I managed to install the recovery OS but did not like it at all, so I have started fiddling with Debian. I managed to get it running via serial kwboot (Sheevaplug u-boot 2015 and 2017, both are working), so I decided to flash the mtd0 - and this is where it went off.by mgx - uBoot