Hi Martin, Hi Carl, you are far ahead of me in knowledge and tinkering-ability with this stuff, and i hardly understand what you do, but i'm happy that you do it. I just wanted to let you know, that i'm still interested and read all about your ups and downs and ups again :-). You are my heros! I also wanted to let you know, that i bought another WDMCMV2 in the meantime, because itby JanN - Debian
Peacemaker Wrote: ------------------------------------------------------- > Did you managed to write uBoot-env's? Sorry, Carl, but there was no progress on this project in the last weeks because i had holidays... I'll inform you, when i get news. Fox_exe (the russian WD-Hacker) found out, that "resetenv" and "saveenv" are deactivated by WD-developersby JanN - Debian
bodhi, > > Sure, you can load the kernel files (uImage and > uInitrd) from the FAT drive, no problem. Instead of uInitrd Fox_exe build a uramdisk, what is - as far as i understand - a compressed rootfs-image including the uInit, that should be installed in RAM. When i load the same files (uimage=kernel and uramdisk=ramdisk-rootfs) via TFTP into the RAM and boot them with bootm, itby JanN - Debian
bodhi, > 1. You can't boot Linux on the FAT drive. I didn't try to boot it on a FAT drive - i only read the image files from it into the RAM, from where i tried to boot the images. And that obviously works up to the moment when they should boot, as far as i understand it... > 2. Which rootfs are you trying to boot? I tried to boot the above mentioned rootfs, that the russiby JanN - Debian
Bodhi, > Format the USB drive as Ext3. And put the kernel > files on it and try again > ext2ls usb 0:1 / I'll do that later. I tried a bit more in the meantime: Marvell>> setenv usbActive 1 Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scby JanN - Debian
bodhi, the thumbdrive (USB 3) is fat formatted (and was obviously used for Windows before ;-)) - thats why i tried Marvell>> fatls usb 0:1 / 22851472 mbam-setup-2.2.1.1043.exe 1399 malwarescanreport.txt autoruns/ processexplorer/ system volume information/ 4883863 uimage 2682706 uramdisk 4 file(s), 3 dir(s) after ext2lby JanN - Debian
bodhi, i tried a bit ... Marvell>> setenv usbActive 1 Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Marvell>> uby JanN - Debian
bodhi, there are SATA-drives in the slots... Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found BR Janby JanN - Debian
bodhi, many thanks for your help. Results: Marvell>> ide reset Reset IDE: Marvell Serial ATA Adapter no device found Marvell>> ext2ls ide 0:1 / ** Bad device ide 0 ** :-( No active unit for ide-devices? Marvell>> active_units Active: cpu0, cpu1, pex0, egiga0, eby JanN - Debian
I'm in contact with fox_exe, the russian guy, who hacked different WD boxes. With his great help i managed to use the serial interface and to boot a kernel and rootfs that he compiled, via tftp with these commands: dhcp; setenv serverip 192.168.151.4; tftp 0xa00000 uImage; tftp 0xf00000 uRamdisk; bootm 0xa00000 0xf00000 It works, but there is a problem with the network interface, so i canby JanN - Debian
Hi all, a few weeks ago i got a WD My Cloud Mirror Gen2 (WDMCMG2) as the wrapping for two WD Red 6TB HDDs (complete system was cheaper, than the single disks ;-)). The factory firmware seems to be buggy and insufficient, but imho the hardware is worth to be hacked to run a clean debian with openmediavault, where i need and hope to get your help for. The box has an ARMv7 Armada 385 dualcoreby JanN - Debian
@bodhi Many thanks for your fast reply :-) Do you really think, the problem is related to the uBoot? Stock OS uses the same and gets the NIC initialized, so i think, it must be related with the envs and/or the OS. And booting works fine - i can shutdown the box with pressing the powerbutton - just no network ;-). But if you want me to test the new uBoot, i`ll do it for the community andby JanN - Debian
Hello tinkerer, I know, this thread is old, but its about my issues: my NSA320 with Debian wheezy and bodhis Kernel 3.18 doesn`t inititialize it`s NIC correctly. It comes up and works, when i cold boot the box after i unplugged the powerplug AND the serial-to-USB interface is connected to my PC. It doesn`t come up, when i restart the machine with serial connection, and it also doesn`t come upby JanN - Debian
bodhi Wrote: > Yes, there must have been a subtle change in 3.18 > that seems to affect stock u-boot only. > > In the following bootargs, try changing it as > followed (the bold part). And please do this in > serial console only (don't save). > > bootargs_sata1linux=console=ttyS0,115200 > mtdparts=orion_nand:0x100000(uboot),0x80000 > (uboot_env),0by JanN - Debian
bodhi Wrote: > Please post your dmesg output. The kernel command > line will show what is the actual mtd definition > being passed into the kernel. This is just a > precaution to cover all bases, (I've already > guessed what it looks like based on /proc/mtd). Hi bodhi, please excuse my late answer - i made some further experiments... Here is the serial bootlogby JanN - Debian
bodhi Wrote: > This is strange. Stock NSA320 mtds are: > > > Creating 9 MTD partitions on "nand_mtd": > 0x00000000-0x00100000 : "uboot" > 0x00100000-0x00180000 : "uboot_env" > 0x00180000-0x00200000 : "key_store" > 0x00200000-0x00280000 : "info" > 0x00280000-0x00c80000 : "etc" > 0x00c80000-0x01680by JanN - Debian
Many thanks again, bodhi. Green led burns now after booting. Btw.: Powerbutton worked with 3.17 and 3.16. ... Where are you, highly respected owners of the NSA-320? You have the chance to save my soul by answering my question ;-) BR Janby JanN - Debian
Hi bodhi, thanks for your fast reply. The leds: root@debian:~# ls -lR /sys/class/leds /sys/class/leds: total 0 drwxr-xr-x 2 root root 0 Feb 11 12:30 . drwxr-xr-x 38 root root 0 Feb 11 05:23 .. lrwxrwxrwx 1 root root 0 Feb 11 12:30 nsa320:green:copy -> ../../devices/gpio-leds/leds/nsa320:green:copy lrwxrwxrwx 1 root root 0 Feb 11 12:30 nsa320:green:hdd1 -> ../../devices/gpiby JanN - Debian
First i want to thank all contributing foristi, but especially bodhy very very much for your great phantastic help- and meaningful work!! Since weeks i'm reading here and try to understand and learn, how to install Debian on my Zyxel NSA-320. I really like this little boxes with their big potential, that is wasted with the original OS. I want to use the box with Debian and Openmediavaultby JanN - Debian