bodhi, I found I made a mistake in the MAC address. it should have been 00:01:DB:1E:24:F2 (instead of 00:01:DB:1E:24:C2). But even after changing that, there is still no eth0. The original kernel does activate the network without any problems, however. :(by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > One more test. This time I would like you to boot > back with the NSA325 DTB embedded (instead of the > new DTB), and plug in the ethernet cable before > powering up. And the hwaddr needs to be hardcoded > inside /etc/network/interfaces. > > If the behavior is what I thinkby garagoyun - Debian
bodhi, I have tried the new DTB, same results: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > Strange, It acts like there is no power on the > NIC, or cable is not plugged in. > > > [ 8.843591] mv643xx_eth: MV-643xx 10/100/1000 > ethernet driver version 1.4 > > > What I am trying to do is avoid the ethaddr > issue. > > So we can see if the Nby garagoyun - Debian
bodhi, Results with the new DTB and amended /etc/network/interfaces : Marvell>> setenv mtdparts 'mtdparts=orion_nand:0x000a0000@0x0(uboot),0x00040000@0x000a0000(param),0x00280000@0x000e0000(preroot),0x00380000@0x00360000(uimage),0x076e0000@0x006e0000(rootfs),0x00240000@0x07dc0000(misc),128m@0x0(flash)' Marvell>> setenv set_bootargs 'setenv bootargs console=ttyby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > And then > > fw_printenv > > Please post the listing here. > > And if the listing looks good (same as in stock), > you can reboot right away and see if ethernet is > working after the system coming up. In the original listing: ethaddr=00:01:DB:1E:24:C2 Currently: ethaddr=00:00:by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > This box also has a hardware monitoring chip: > adt7473. Yes, that's the one. Regards, garagoyunby garagoyun - Debian
bodhi, I have amended /etc/fw_env.config. See the output for fw_printenv below: root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0 0x20000 0x20000 root@debian:~# fw_printenv Warning: Bad CRC, using default environment bootargs= bootcmd= bootdelay=2 bby garagoyun - Debian
Below the output with the silverstore dtb: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) |by garagoyun - Debian
bodhi, QuoteDid the box power down completely after this? No, it did not. I will check the DTB version shortly. Regards, garagoyunby garagoyun - Debian
bodhi, Previous tests were done just with the motherboard without the SATA drive and internet attached. Below is the output with a drive and internet connection: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _by garagoyun - Debian
Quote[ 0.000000] OF: fdt: Machine model: D-Link DNS-325 NAS (Rev A1) My bad. Below output with correct DTB and the new adjustments: Marvell>> setenv mtdparts 'mtdparts=orion_nand:0x000a0000@0x0(uboot),0x00040000@0x000a0000(param),0x00280000@0x000e0000(preroot),0x00380000@0x00360000(uimage),0x076e0000@0x006e0000(rootfs),0x00240000@0x07dc0000(misc),128m@0x0(flash)'by garagoyun - Debian
bodhi, It gives kernel panic at the end: Marvell>> setenv mtdparts 'mtdparts=orion_nand:0x000a0000@0x0(uboot),0x00040000@0x000a0000(param),0x00280000@0x000e0000(preroot),0x00380000@0x00360000(uimage) 0x076e0000@0x006e0000(rootfs),0x00240000@0x07dc0000(misc),128m@0x0(flash)' Marvell>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs roby garagoyun - Debian
bodhi, It seems it did not boot from the usb for some reason. Bellow the results from the commands: Booting without USB rootfs: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | |by garagoyun - Debian
Hi bodhi, Just to double check with you, I have ordered the following UART converter, however, I am not sure if it is the correct one: https://www.ebay.co.uk/itm/Converter-Cable-UART-PL2303HX-USB-To-RS232-USB-to-COM-NEW-Adapter-TTL-Module/282966197680 Just in case I have ordered today another one: https://www.ebay.co.uk/itm/USB-2-0-to-TTL-UART-5PIN-Module-Serial-Converter-CP2102-STC-Pby garagoyun - Debian
bodhi, I actually used kirkwood-db-88f6282.dtb for step 4. I will overwrite it now with kirkwood-nsa325.dtb. In addition, to be able to boot that kernel I assume current envs should be amended or new ones added? Regards garagoyunby garagoyun - Debian
Hi bodhi, Appreciated. I was not expecting such an immediate reply. And apologies for the wrong subforum. I was not sure where to post. Please feel free to move it into an appropriate one. QuoteBy the look of info you got inside stock OS and the links, - I don't think u-boot is locked at all. - It has a different u-boot version from the NSA325. - u-boot envs can be modified to boby garagoyun - Debian
Hi, Quite recently I have acquired two NAS units "SiverStore 2" manufactured by Freecom. The units are EOL, so no updates on the software side since 2012. However, I have received the root password from the technical support at freecom and via ssh successfully installed Optware-ng and a chrooted debian wheezy. The units itself has a custom-made operating system with kernel 2.6.31, whby garagoyun - Debian