Leaderboard

Hi, Since I was not yet able to build a working cpufreq_ondemand.ko to allow automatic frequency scaling for JUN's loader 1.04b (DSM 6.2.2-24922 Update 2), i've written this script to allow dynamic CPU frequency scaling. It's hosted here : https://github.com/Trauma/cpufreq-userspace-scaler # cpufreq-userspace-scaler ##### Cpu frequency scaling script for cpufreq userspace governor ## If you're missing ondemand or conservative governors, this script is for you. This script is scaling cpu frequency according to current average load. You can set 3 frequency steps : low, mid, high. This 3 thresholds will automatically set cpu frequency accordingly : - the `lowload` threshold will set the cpu to his minimal frequency, unless you force it to `scalingminfreq` - the `midload` threshold will set the cpu to approximate mid range cpu frequency - the `highload` threshold will set the cpu to his maximal frequency, unless you force it to `scalingmaxfreq` If you set `scalingmaxfreq` and/or `scalingminfreq` the cpu will never override those values. ### Usage : ### Parameters : Variable name | Default | Type | Comments ----------------|---------|-----------------------------|----------- lowload | 050 | integer between 000 and 999 | 050 = load average : 0.50 midload | 065 | integer between 000 and 999 | 065 = load average : 0.65 highload | 085 | integer between 000 and 999 | 085 = load average : 0.85 scalingminfreq | auto | integer in hertz | 800000 = 800 Mhz scalingmaxfreq | auto | integer in hertz | 2500000 = 2,5 Ghz ### Default commande line : `./scaling.sh &` ### Custom command line example : `lowload=100 highload=200 scalingmaxfreq=2000000 scalingminfreq=1500000 ./scaling.sh &` Enjoy.

After upgraded to DSM 6.2.2 and moments 1.3.2, the face recognition is empty , and concept category only has child. I found thus shoud be a bug of photo detection plugin. So, there is the way to fix it: 1. enable SSH, and disable Moments. 2. replace /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so with my attachment. 3. enable Moments. (maybe need to reindex.) everything is fine. Enjoy~ libsynophoto-plugin-detection.so

Можно. Установите приложение webstation. + Пакеты апач и php. А Так же mariabd и phpmyadmin У самого на поддоменах крутится 3 сайта

you can open the update file (pat) with 7zip and have a look, the *.deb packages can be opened too flashupdate_*.deb is about the kernel that will go to usb linux*.deb uaually new kernel modules also looking for the size of the deb files can be used i still have two and they are sure to work properly in 3615/17 and replacing the sas cards depends an the drive count and whats use of the system a all flash (ssd) would still use a 12GBit SAS pcie 3.0 controller and high drive counts like 24 will be hard to realize with just 5 port cards (like 4 cards and 4port onboard and a 10G nic ...), also when using "older" sas shelfs a sas controller is needed but yes for most home use cases around 12 ports the new pcie 3.0 ahci cards are a good solution and when using 10-18 TB drives even high capacity's are no problem, no need for 24 disk monsters in most cases the sas problem is different as it originates from the "added" sas support in 918+, it does work reliable when using the scsi/sas files from synology but then smart, sn and temp. are missing and jun's files have the problem of mangling data with disk hibenation, its about the custom changes from synology, there might be something missing int the 918+ kernel to support smart, sn, temp with the synology scsi/sas kernel driver

Interestingly, my server writes that the connection is low speed. but downloads files from another nac-server at a speed of 600Mbps

https://www.ebay.com/itm/143604880894? https://www.ebay.com/itm/192300509354?

min. 4th gen intel cpu for 918+ it's documented here: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ you would need to use 3615 or 3617 for a 3rd gen cpu, and when using 3615/17 you need csm/legacy mode in the uefi bios and need to choose the non uefi usb boot device

xpenology is based on the original kernel of synology and as synology does not use amd hardware consequently there is no explicit support in the kernel ryzen does work but you cant use hardware transcoding, thats intel quick sync exclusive if you have the choice go with a intel setup (i don't like it either, my desktop pc is ryzen based) also if you can choose a bigger board that has more pcie slots and mybe more sata ports (6 is often seen) i'm using a gigabyte B360M HD3, microATX, a 8th ot 9th gen intel cpu is a good choice, maybe a "T" model with lower TDP is a option when the system is running 24/7 dont use a "F" model, you need the intel gpu part if you want to use hardware transcoding one recipe is to stay close to the hardware of what imgae you are using, 918+ is the usual choice for new hardware (3615/17 is usually used for older hardware) depending on what future options you might have, enough sata ports and pcie slots come in usefull like 2xsata ssd for cache or pcie slots for a 10G nic or 4/8 port sata controller wifi is more or less not supported with dsm so you dont need it as onboard component my1st choice would have been a 9100T but intel has massive problems with that and it dos not look like they will e able to deliver in a foreseeable future

Si cela vous intéresse, je suis en train de vous préparer un tuto pour l'installation de DSM 6.1 sur Hyper-V.

Salut, Je n'ai toujours pas travailler pour la version 6.2 pour manque de temps. Dès que j'ai du nouveau, je mettrais à jours le post.

Download the loader, unzip it and put the image file (synoboot.img) directly on the desktop. 1 - If your flash drive is plugged, unplug it. 2 - Open terminal. Issue the following commands: cd / cd ~/Desktop diskutil list The last command should bring up the list of your drives. Below is what it shows on mine: TlMBP:Desktop Tl$ cd / TlMBP:/ Tl$ cd ~/Desktop TlMBP:Desktop Tl$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 200.3 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS Funky 298.8 GB disk0s4 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Yosemite *199.9 GB disk1 Logical Volume on disk0s2 CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD Unencrypted Now plug your flash drive and issue the diskutil list command again: TlMBP:Desktop Tl$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 200.3 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS Funky 298.8 GB disk0s4 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Yosemite *199.9 GB disk1 Logical Volume on disk0s2 CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD Unencrypted /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *31.0 GB disk2 1: DOS_FAT_32 41.1 MB disk2s1 2: DOS_FAT_32 49.4 MB disk2s2 You can see my flash drive (31GB) now with the identifier disk2. Note that your flash drive identifier could be something else (disk3, disk4...) so don't just copy paste. Now issue the following command: sudo diskutil unmountDisk /dev/disk2 You might be asked for your password. Here is what I get: TlMBP:Desktop Tl$ diskutil unmountDisk /dev/disk2 Unmount of all volumes on disk2 was successful Then issue the following command. Same comment: BE SURE TO USE THE RIGHT IDENTIFIER. There is no turning back on this one. If you mistakenly use the identifier of some other disk, it will overwrite it with the image. SO BE VERY CAREFUL. sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m You should see this: TlMBP:Desktop Tl$ sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m 50+0 records in 50+0 records out You are done. If you want to access the content of the drive you have to issue the following commands: Verify again your flash drive identifier. YES AGAIN. You will need the disk partition identifier this time: diskutil list You should get this: TlMBP:Desktop Tl$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 200.3 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS Funky 298.8 GB disk0s4 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Yosemite *199.9 GB disk1 Logical Volume on disk0s2 CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD Unencrypted /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *31.0 GB disk2 1: EFI NO NAME 31.5 MB disk2s1 2: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 15.7 MB disk2s2 3: Bios Boot Partition 4.2 MB disk2s3 Note the EFI NO NAME partition with the identifier disk2s1 of the flash drive. This is the one we want. If you are on MAC OS El Capitan or earlier then issue the following: mkdir /Volumes/efi If you are on MAC OS Sierra then issue the following: mkdir /tmp/efi (Since Sierra, /Volumes is no longer world-writeable. One needs to be root to create folders in /Volumes) Followed by: If you are on MAC OS El Capitan or earlier then issue the following: sudo mount -t msdos /dev/disk2s1 /Volumes/efi or If you are on MAC OS Sierra then issue the following: sudo mount -t msdos /dev/disk2s1 /tmp/efi Your flash drive is now mounted. Edit what you need and eject when done. If you need to mount the flash drive again issue the last 2 commands. Always beware of the disk ID.