Jan_Grz1, > there a way to switch off the hard drives when > they are not in use? Or can I set this in the web > interface? Use Debian hdparm for a simple solution. It's in the Wiki thread QuoteLinux Tools Debian hdparm (HDD spin down) Hard Drive Idle Tool (an alternative to the standard Debian hdparm)by bodhi - Debian
Alex, > Is it, again, an issue of initializing it in the > u-boot? No, u-boot does not have anything to do with kernel DKMS. No idea why, but seems there is more info: QuoteConsult /var/lib/dkms/r8168/8.051.02/build/make.log for more information.by bodhi - Debian
lazy, > Can someone advice any steps to bring sound on > Armada 510 for stock 4.19.0-21-armmp kernel in > Debian 10? I've came from era of PCI sound cards > and bit surprised there is no just kernel module > to load :) I think to make sounds works on the Cubox, we will need to update the kernel DTS. Similar to what I did for the HP T5325. I've explained it abby bodhi - Debian
Jan_Grz1, > is it that what i see in the wiki for the backup? Yes. QuoteBackup and Cloning rootfs Back up a live rootfs using rsync Backup/Restore rootfs using tar command - Backup/Restore rootfs using tar command: Shutdown the NAS, bring the USB rootfs to another Linux box and create tarball. - Back up a live rootfs using rsync: a. Scheduled backup: If there isby bodhi - Debian
Jan_Grz1, > Now it works again with the USB stick inside, > thank you. Congrats! > But how do I now get access to the NAS > to save things on it? How can I change settings on > it? Is there a web interface? This is a headless box so you would SSH in using a terminal like you did using serial console. And install Debian packages. Network file sharing to other Linuby bodhi - Debian
Here is how to back up the rootfs using tar command: https://forum.doozan.com/read.php?2,12096,24034#msg-24034by bodhi - Debian
Jan_Grz1, > but now when i unplugged the usb stick and cold > started it, it wouldn't start again. it was only > when the usb stick was back in. Yes. it's normal. You are running Debian on USB rootfs. So the USB rootfs must be attached. The USB rootfs is your entire GNU Linux system. > rootfs: Clearing orphaned inode 51454 (uid=0, > gid=0, mode=0100755, size=1by bodhi - Debian
ErGatto, > I did what you suggested but nothing changed. OK. I'll post a different flashing procedure.by bodhi - uBoot
root@archiso /mnt/boot # mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt uImage ^C 130 root@archiso /mnt/boot # ls System.map-6.5.7-kirkwood-tld-1 uImage.orig config-6.5.7-kirkwood-tld-1 uInitrd dts vmlinuz-6.5.7-kirkwood-tld-1 initrd.img-6.5.7-kirkwood-tld-1 zImage.fdt linux-headers-6.5.7-kirkwood-tld-1_1_armel.debby bodhi - Debian
ZooMoo, > Do you think the problem lies in the DTS (missing > some parameter setting or adjustment) or it's a > problem with the kernel/driver? I don't think it is the kernel driver. This could either be hardware issue, or something specific to this box that we don't know about (which needed to be specified in the DTS). I guess we should start with comparing theby bodhi - Debian
ZooMoo, > Is there additional debugging / flags I can turn > on to show where the problem could be? Unfortunately, this network driver has no debug print that we can turn on. And there is no specific device with this SoC supported in mainline Linux (other than the Reference Board). We've added support for the WD MyCloud Gen2 here, and that's the only Armada 375 SoC device rby bodhi - Debian
Jan_Grz1, You need to recreate the rootfs using the kirkwood-lenovo-ix2-ng.dtb in Step 4. https://forum.doozan.com/read.php?2,12096 Quote4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time, or running kwboot with latest uby bodhi - Debian
> Reinstalled everything on 6.7.5 then upgraded to > 6.12.6 and everything is working Cool!by bodhi - Debian
> Have you verified the uImage file is actually > there? I haven't seen anything in the thread > showing it existing. Likewise I don't see output > from the mkimage command etc. This looks more like > the file just not being present than some sort of > IO error at first glance. It was loaded successfully once up here: https://forum.doozan.com/read.php?2,1392by bodhi - Debian
wheeler, Quoteroot@debian:~# modprobe mvneta modprobe: FATAL: Module mvneta not found in directory /lib/modules/6.12.6-mvebu-370xp-tld-1 Kernel 6.12.6-mvebu-370xp-tld-1 looks OK to me. So I think either your rootfs is bad or kernel 6.12.6-mvebu-370xp-tld-1 was not completely installed. Check it using dpkg dpkg -l | grep linux-image Try install kernel 6.12.6-mvebu-370xp-tld-1. You canby bodhi - Debian
Jan_Grz1, > > Hit any key to stop autoboot: 0 > > > usb start > sleep 3 > usb info > usb part > ext2ls usb 0:1 /boot > > > If all went well above Output of ext2ls was not good. /boot/uImage was not listed. This u-boot seems flaky. "usb start" spins up the drive, but it seems to take a long time. Try this help usb start echby bodhi - Debian
diappollo, > It doesn't seem to boot from the USB drive? Any > envs to modify? Yes. You need to repeat the same procedure you did for the Stora.by bodhi - Debian
wheeler, > Rebuilt a usb stick with kernel 6.7.5 and the > networks come up, boot log attached Cools! perhaps I've missed something in kernel 6.12.6-mvebu-370xp-tld-1. I'll take a look.by bodhi - Debian
Jan_Grz1, > Hit any key to stop autoboot: 0 usb start sleep 3 usb info usb part ext2ls usb 0:1 /boot If all went well above setenv bootcmd 'run usb_bootcmd; usb stop; reset' bootby bodhi - Debian
wheeler, > Running local boot scripts (/etc/rc.local) > Cannot read environment, using default > Cannot read default environment from file > <13>Mar 12 02:35:52 root[2219]: Cannot read u-boot > env ethaddr Remove the script execution. chmod -x /root/set_persistent_mac_address As described in the rootfs instruction Quotehttps://forum.doozan.com/read.php?2by bodhi - Debian
Bay, > I did test your last commands but unfortunately my > u-boot is missing the "run" command. Damn! this u-boot is pathetic :) you also don't have the "source" command! You could try this. If this u-boot accepts a long string for env then it's better (copy and paste one command instead of several envs). setenv bootcmd 'setenv bootargs consoby bodhi - Debian
ZooMoo, Here is the updated DTB. See if eth1 is correct. QuoteU-Boot 2013.01-g5d1ab78 (Oct 27 2015 - 11:38:34) Marvell version: 2014_T2.0p3 Board configuration detected: RGMII0 Module on MAC0 PON ETH SERDES on MAC1 SERDES configuration: Lane #0: PCIe0 Lane #1: SATA1 Lane #2: SATA0 Lane #3: USB3 <snip> Net: egiga0, egiga1 syno: network status self-checkingby bodhi - Debian
Bay, So this stock u-boot does not support USB or IDE command (not possible to boot with USB or SATA storage device). Continuing using stock u-boot means you'll need to set up to boot permanently with tftp, until I can roll a new u-boot for it. Not hard, but I can only do it when I have time. To prepare for a permanent envs setting. Do this test boot a few times setenv ipaddr 192.by bodhi - Debian
ZooMoo, We'll try another test. I'll post an updated DTB soon.by bodhi - Debian
wheeler, The network driver was not running at all. It behaves like there is no Ethernet cable connected. If the Ethernet cable is connected, unplug it. And plug it in again. And see if dmesg show anything dmesg | tail -50 ifconfig -aby bodhi - Debian
Jan_Grz1, Power up, interrupt u-boot countdown and modify the bootcmd setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset' And then bootby bodhi - Debian
Bay, So your current envs for booting is Marvell>> setenv ipaddr 192.168.1.128 Marvell>> setenv serverip 192.168.1.180 Marvell>> setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' Marvell>> mw 0x800000 0 1 Marvell>> tftpboot 0x800000 uImage Marvell>> tftpboot 0x2100000 uInitrd Marvell>> bootm 0by bodhi - Debian
Tbd6, > Could be default environment issue, that prevents > port working? No. In the 2017.07 u-boot, the default envs have notthing to do with the USB port. The Cruzer Fit is a good USB thumbdrive for this plug. I never see it fail to spin up in this Pogo Mobile. And that was both in u-boot and Linux. Especially in Linux, if the drive is not showing up in Linux, chance is great thby bodhi - uBoot
Jan_Grz1, Right at the beginning, the USB drive failed to spin up. What happend after that is irrelevant. > Marvell>> boot > (Re)start USB... > USB: scanning bus for devices... 2 USB Device(s) > found > Waiting for storage device(s) to settle before > scanning... > 1 Storage Device(s) found > > ** Unable to read "/boot/uImage" from usb 0by bodhi - Debian
Jan_Grz1, The iomega_ix2_200.dtb is the wrong one. https://wikidevi.wi-cat.ru/Iomega Rootfs /boot/dts -rw-r--r-- 1 root root 11964 Feb 12 10:00 kirkwood-iomega_ix2_200.dtb -rw-r--r-- 1 root root 13124 Feb 12 10:00 kirkwood-lenovo-ix2-dl.dtb -rw-r--r-- 1 root root 13053 Feb 12 10:00 kirkwood-lenovo-ix2-ng.dtb Try the kirkwood-lenovo-ix2-ng.dtb.by bodhi - Debian