Search the Community

Release note from https://www.synology.com/en-global/releaseNote/DS3615xs Version: 6.1.5-15254 (2018-01-31) Important Note The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly. This update will restart your Synology NAS. What's New in DSM 6.1.5 Added support for editing permissions to multiple groups and users to a single folder or file simultaneously in File Station. Added Seagate IronWolf Health Management (IHM) support on DS118, DS218play, DS418j, DS418 and DS218. Fixed Issues Fixed an issue where the system may make a false alarm about hot spare disks when upgrading SHA. Fixed a domain issue by allowing Synology NAS to join an existing domain with an ASCII password. Enhanced system efficiency in calculating a large number of user and group privilege settings. Enhanced SSD cache reliability. Fixed the issue where setting notifications for low volume capacity is not available on 1-bay models. Fixed an issue where converting a single volume to support multiple volumes may be misidentified as a crashed volume. Fixed an issue where users may not be able to collapse and expand fieldsets on an SSD cache webpage with Safari 11 browser. Fixed a security vulnerability regarding Linux kernel (CVE-2017-16939). Fixed a security vulnerability regarding Samba (Synology-SA-17:72). - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3617xs - Installation type: Virtual ESX 6.5U1 - Additional comments: Requires reboot

Release note from https://www.synology.com/cs-cz/releaseNote/DS3617xs#ver_DSM 6.1.5-15254 - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02a2 - DS3617xs - Installation type: Baremetal / ASROCK AD510PV, Dual-Core Atom D510 (1.6 GHz) - Additional comments: No reboot needed

Hi, Well, I am a newbie here, and it is a bit off, so sorry for that. But I am looking for help with the DSM porting, and I thought this is the best place where I Can ask my questions. I have an ARMv5 NAS, and I decided to install the DSM-111's fw on it (6.1.5 extracted from the pat file). It boots up fine, and I Can see the Diskstation login: over serial console. But I have no NIC support. Maybe because the kernel doesn't support my RTL8168 NIC by default? I Could see these errors and informations in the console about the network: [ 10.950000] ERROR: sflash_probe - Failed to initialize the SFlash.Loading Marvell Ethernet Driver: [ 10.960000] o Cached descriptors in DRAM [ 10.960000] o DRAM SW cache-coherency [ 10.970000] o 2 Giga ports supported [ 10.970000] o Single RX Queue support - ETH_DEF_RXQ=0 [ 10.970000] o Single TX Queue support - ETH_DEF_TXQ=0 [ 10.980000] o TCP segmentation offload (TSO) supported [ 10.980000] o Receive checksum offload supported [ 10.990000] o Transmit checksum offload supported [ 10.990000] o SKB Recycle supported - (Enabled) [ 11.000000] o Rx descripors: q0=128 [ 11.000000] o Tx descripors: q0=532 [ 11.010000] o Loading network interface(s): [ 11.010000] o register under mv88fx_eth platform [ 11.020000] o eth0, ifindex = 2, GbE port = 0 [ 11.020000] o eth0, phy chipid = fffffff0, Support WOL = 0 [ 11.030000] [ 11.030000] Warning: Giga 1 is Powered Off cat: can't open '/proc/sys/kernel/syno_skip_vender_mac_interfaces': No such file or directory [ 21.930000] eth0: started udhcpc (v1.16.1) started eth0 Link encap:Ethernet HWaddr <removed> UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:532 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:11 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Also, I tried to compile the kernel module manually, but as I Could see, the magic numbers are differs. $ readelf -h ./8192cu.ko ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: REL (Relocatable file) Machine: ARM Version: 0x1 Entry point address: 0x0 Start of program headers: 0 (bytes into file) Start of section headers: 6346960 (bytes into file) Flags: 0x5000000, Version5 EABI Size of this header: 52 (bytes) Size of program headers: 0 (bytes) Number of program headers: 0 Size of section headers: 40 (bytes) Number of section headers: 5069 Section header string table index: 5066 $ readelf -h ./lib/modules/2.6.32.12/kernel/net/netfilter/nf_conntrack.ko ELF Header: Magic: 7f 45 4c 46 01 01 01 61 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: ARM ABI Version: 0 Type: REL (Relocatable file) Machine: ARM Version: 0x1 Entry point address: 0x0 Start of program headers: 0 (bytes into file) Start of section headers: 37228 (bytes into file) Flags: 0x600, GNU EABI, software FP, VFP Size of this header: 52 (bytes) Size of program headers: 0 (bytes) Number of program headers: 0 Size of section headers: 40 (bytes) Number of section headers: 265 Section header string table index: 262 The first one is the original one, and the second one is a manually compiled module using the Marvell 6281 6.1 GPL sources. I think it won't work because of the small difference... :\ Or will it? What I am doing wrong? Thanks a lot!