Thanks Bodhi, Checking the logs, I get everything you've listed above except for ethact and ethprime. $ cat synology_ds215j_eth1_v2025-03-12.log | grep -E "RGMII0|PON|SERDES|Lane |Net:|syno:|Using egiga|ethact|ethprime" RGMII0 Module on MAC0 PON ETH SERDES on MAC1 SERDES configuration: Lane #0: PCIe0 Lane #1: SATA1 Lane #2: SATA0 Lane #3: USB3 Net: egiga0,by ZooMoo - Debian
I've tried the latest version, but you were correct, it didn't fix this problem: root@debian:~# dmesg | grep eth mvpp2 f10f0000.ethernet: using 3 shared buffers mvpp2 f10f0000.ethernet eth0: Using hardware mac address 00:00:00:00:00:04 mvpp2 f10f0000.ethernet eth0: validation of mii with support 00,00000000,00000000,000066ff and advertisement 00,00000000,00000000,000066ff failedby ZooMoo - Debian
Hi Bodhi, I just compared this latest DTS (armada-375-synology-ds215j_mii.tar (20 KB)) with the version from 20th Jan, and they are the same. They both contain phy-mode = "rgmii-id"; . Should it be phy-mode = "mii"?by ZooMoo - Debian
Here are the results for using the DTS from https://forum.doozan.com/read.php?2,138851,138913#msg-138913. According to ethtool the ports show three options, TP, MII and Fibre whilst the Synology DSM OS only has TP/MII. Eth0 then wrongly sets the port to Fibre when an ethernet cable is plugged in. In the WD MyCloud Gen2 (Glacier, Armada 375) thread (https://forum.doozan.com/read.php?2,94839)by ZooMoo - Debian
> It does look like SGMII is incorrect. We shoul dgo back to the previous DTB, with RGMII-ID. I've used the following dtb file from your download: armada-375-synology-ds215j_rgmii.tar (20 KB) This is the correct one? Once booted, I get the following output from ifconf and ethtool. The following message appears when disconnected the ethernet cable: mvpp2 f10f0000.etheby ZooMoo - Debian
I've compared the output of ifconfig, ethtool, etc between the stock DSM OS and debian. Booting the stock DSM OS I can connect to the network so it's not a network issue. DSM $ sudo ifconfig -a eth0 Link encap:Ethernet HWaddr <MACADDRESS> inet addr:192.168.1.238 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: <IP6 ADDRESSS>/64by ZooMoo - Debian
Sorry, there was a problem between keyboard and seat. I used the wrong kernel (6.12.6) to build the image, instead of the correct kernel (6.6.2). ~# sudo su - ~# cd /media/user1/usb_stick/boot/ /media/user1/usb_stick/boot# cp -a zImage-6.6.2-mvebu-tld-1 zImage.fdt /media/user1/usb_stick/boot# cat ./dts/armada-375-synology-ds215j_gmii/armada-375-synology-ds215j.dtb >> zImage.fdtby ZooMoo - Debian
Thanks Bodhi, I've tried each DBT version, but in all three cases, eth0 was missing. Below is the kernel log for gmii, but I've compared the logs for the other two versions and they are the same. The likely error is the following in the logs: Configuration file wrong or corrupted <13>Feb 25 02:06:59 root[2084]: Cannot read u-boot env ethaddr Creation of the bootby ZooMoo - Debian
I still cannot find the u-boot source... this will help right? I'll contact Synology to ask where it is.by ZooMoo - Debian
> Try using a different ethernet cable and/or plug it in to a different switch. Shouldn't the router and cable be ok? The router and cable are the same ones I used when you got me to "setenv ipaddr" whilst in u-boot. ping worked in the case of u-boot. Even if ping works within u-boot, could something else be wrong with the router/cable? Strangely, when I unplug the ethby ZooMoo - Debian
The above output was after a reboot with the MAC hardcoded. The LAN is okay as other machines can ping each other, but just not the NAS. Maybe something is wrong with my network..? Just re-running commands: # cat /etc/network/interfaces auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.1.201 netmask 255.255.255.0 gateway 192.168.1.1 hwaddress ether 00by ZooMoo - Debian
After reboot: # dmesg | grep -i mvpp [ 2.714153] mvpp2 f10f0000.ethernet: using 3 shared buffers [ 2.732709] mvpp2 f10f0000.ethernet eth0: Using hardware mac address 00:00:00:00:00:04 [ 399.997021] mvpp2 f10f0000.ethby ZooMoo - Debian
> Did this work? Updating the /etc/network/interfaces file and restarting the network didn't work. # cat /etc/network/interfaces #rename /end0=eth0 #auto lo eth0 #allow-hotplug eth0 #iface lo inet loopback #iface eth0 inet dhcp auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.1.201 netmask 255.255.255.0 gateway 192.168.1.1 hwaddress ether 00by ZooMoo - Debian
I've booted up with your latest armada-375-synology-ds215j-jan-20.dtb file, but the MAC address is still invalid according to the logs. Kernel Log: ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-6.6.2-mvebu-ds215j Created: 2025-01-21 8:01:44 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5192401 Bytes = 5 MiBby ZooMoo - Debian
> setenv ipaddr <the static IP address of this NAS, whatever you want it to be in your network> > ping <the router IP address> > ping <the IP address some other box in your network> Yes, this works: Marvell>> setenv ipaddr 192.168.1.100 Marvell>> ping 192.168.1.1 Using egiga1 device host 192.168.1.1 is alive Marvell>> ping 192.168.1.28 Uby ZooMoo - Debian
> I'm wondering if there is GPL source for Synology Armada-375 u-boot? Good question. Whilst trying to solve this myself earlier, I found the advice given on this forum not to "saveenv" as Synology's u-boot is broken for users. For example the post from Lonestar: Quotelonestar https://forum.doozan.com/read.php?2,133377,133858#msg-133858 *** getting this to boot wby ZooMoo - Debian
Right of the bat, Ethernet needs to be fixed. Try log into DSM OS again, and get some info. Hope they did not remove this command :) ethtool eth0 Logged into DSM 6.2: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Fullby ZooMoo - Debian
BTW, in DSM, see if the device tree is at a different location: ls -l /sys/firmware/devicetree/base The directory does not exist, searching /sys yields no results: $ sudo find /sys/ -iname "*tree*" /sys/module/rcutree /sys/module/quota_tree 1. Boot with my updated DTB. Usby ZooMoo - Debian
DSM is missing /proc/device-tree. # ls -l /proc/device* -r--r--r-- 1 root root 0 Jan 17 10:47 /proc/devices # cat /proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 ttyS 5 /dev/tty 5 /dev/console 5 /dev/ptmx 10 misc 13 input 21 sg 89 i2c 90 mtd 128 ptm 136 pts 180 usb 189 usb_device 201 synobios 254 bsg Block devices: 1 ramdisk 259 blkextby ZooMoo - Debian
1.a It might show the DTB name in one of the envs. And also get some info in u-boot. According to printenv, the stock u-boot refers to the stock dtb file: fdtfile=armada-375-db.dtb U-boot start up log: BootROM - 1.51 Booting from SPI flash General initialization - Version: 1.0.0 High speed PHY - Version: 0.1.1 (COM-PHY-V20) USB2 UTMI PHY initialized succesfully USB2 Uby ZooMoo - Debian
I just tried both DTB files with the 6.12.6 kernel, but without success, same kernel panic with null pointers. Although there is an error regarding NAND controller for the stock DTB (armada-375-db.dtb). Rechecking the previous kernel logs, it also occures with the 6.6.2 kernel. [ 3.303617][ T1] marvell-nfc f10d0000.nand-controller: probe with driver marvell-nfc failed with error -11by ZooMoo - Debian
Thank's Bodhi. I repeated the rootfs procedure using ./dts/armada-375-wd-mycloud-gen2.dtb as you suggested, but got the same kernel panic. # cd /media/user1/usbstick/boot # cp -a uImage.orig uImage # replace uImage with the original. # cp -a zImage-6.6.2-mvebu-tld-1 zImage.fdt # cat ./dts/armada-375-wd-mycloud-gen2.dtb >> zImage.fdt # mkimage -A arm -O linux -T kernel -Cby ZooMoo - Debian
Hi, I'm want to install Debian on the Synology DS215j. I'm not an expert and have tried to follow the other threads on installing Debian on the DS214 and DS216j but without success. Refs: Debian on Synology DS214 Posted by lonestar https://forum.doozan.com/read.php?2,133377 Debian on Synology DS216 Posted by Robin https://forum.doozan.com/read.php?2,137280 So far I&by ZooMoo - Debian