merve04
-
Posts
328 -
Joined
-
Last visited
-
Days Won
4
Posts posted by merve04
-
-
On 7/12/2022 at 5:51 PM, noosphere said:
Hi,
Any news abbout this? If i buy a original licence will work on Xpenology?
I don't think you'll find too many folks recommending to buy a license to apply on an xpenology install, as I think you have one shot with the license so if something "bad" happens you'll be sol. I also recall reading years ago, that you need legit SN\Mac. An alternative would be looking at using DVA3221 or DVA1622 loaders which include 8 camera licenses with surveillance station by default.
-
Happy to report this updated progress on the dva1622 loader now works on my system. Although it once again reset DSM forcing me reload all my packages and scrub my data, its a small price to pay to have all of my cameras working and plex transcoding for remote users.
Many thanks to @pocopico and others who have put the time and effort into making this happen.
-
1
-
-
Well i'll give up on this dva1622 dream for now, i just dont understand where it went wrong. It seemed just the drives on the jmb585 cards wouldn't load but where visible in a sense that when i did the ssh command, i could see them.
I also tried the ARPL loader, i eventually got it working after tinkering in the bios, but it gave me a worse result only showing 2 hdd's.
I also thought could it be the expander cards the issue as far as compatibility, well i took one card out and plunked it in another pc i got and plugged 1 hdd on it and it showed up in dsm, so i figure that rules it out.
I've rebuilt a usb loader for ds918+, all drives show up and is repairing now, the down fall is i've taken a step back with my surveillance setup.
hopefully the dva1622 loader can be polished a bit more to allow more hdd's in my setup.
-
ok so i used filezilla to upload the file, check in tcrp, terminal vi dva1622.dts, everything was there, rebooted and back in dsm, still only 6 hdd's
I tried removing the ",00.0" on each port of the expansion cards, no change.
Could having mutliple DTS files in the directory cause an issue? I notice theres a ds1621p.dts and ds920p.dts file
-
I'm assuming this like?
/dts-v1/;
/ {
compatible = "Synology";
model = "synology_geminilake_dva1622";
version = <0x01>;
syno_spinup_group = <0x01 0x01>;
syno_spinup_group_delay = <0x0b>;
syno_hdd_powerup_seq = "true";
syno_cmos_reg_secure_flash = <0x66>;
syno_cmos_reg_secure_boot = <0x68>;internal_slot@1 {
protocol_type = "sata";
power_pin_gpio = <0x16 0x00>;
detect_pin_gpio = <0x25 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:17.0";
ata_port = <0x00>;
};led_green {
led_name = "syno_led0";
};led_orange {
led_name = "syno_led1";
};
};internal_slot@2 {
protocol_type = "sata";
power_pin_gpio = <0x17 0x00>;
detect_pin_gpio = <0x26 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:17.0";
ata_port = <0x01>;
};led_green {
led_name = "syno_led2";
};led_orange {
led_name = "syno_led3";
};
};
internal_slot@3 {
protocol_type = "sata";
power_pin_gpio = <0x18 0x00>;
detect_pin_gpio = <0x27 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:17.0";
ata_port = <0x02>;
};led_green {
led_name = "syno_led4";
};led_orange {
led_name = "syno_led5";
};
};
internal_slot@4 {
protocol_type = "sata";
power_pin_gpio = <0x19 0x00>;
detect_pin_gpio = <0x28 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:17.0";
ata_port = <0x03>;
};led_green {
led_name = "syno_led6";
};led_orange {
led_name = "syno_led7";
};
};
internal_slot@5 {
protocol_type = "sata";
power_pin_gpio = <0x20 0x00>;
detect_pin_gpio = <0x29 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:17.0";
ata_port = <0x04>;
};led_green {
led_name = "syno_led8";
};led_orange {
led_name = "syno_led9";
};
};
internal_slot@6 {
protocol_type = "sata";
power_pin_gpio = <0x21 0x00>;
detect_pin_gpio = <0x30 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:17.0";
ata_port = <0x05>;
};led_green {
led_name = "syno_led10";
};led_orange {
led_name = "syno_led11";
};
};
internal_slot@7 {
protocol_type = "sata";
power_pin_gpio = <0x22 0x00>;
detect_pin_gpio = <0x31 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:01.0,00.0";
ata_port = <0x00>;
};led_green {
led_name = "syno_led12";
};led_orange {
led_name = "syno_led13";
};
};internal_slot@8 {
protocol_type = "sata";
power_pin_gpio = <0x23 0x00>;
detect_pin_gpio = <0x32 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:01.0,00.0";
ata_port = <0x01>;
};led_green {
led_name = "syno_led14";
};led_orange {
led_name = "syno_led15";
};
};
internal_slot@9 {
protocol_type = "sata";
power_pin_gpio = <0x24 0x00>;
detect_pin_gpio = <0x33 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:01.0,00.0";
ata_port = <0x02>;
};led_green {
led_name = "syno_led16";
};led_orange {
led_name = "syno_led17";
};
};
internal_slot@10 {
protocol_type = "sata";
power_pin_gpio = <0x25 0x00>;
detect_pin_gpio = <0x34 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:01.0,00.0";
ata_port = <0x03>;
};led_green {
led_name = "syno_led18";
};led_orange {
led_name = "syno_led19";
};
};
internal_slot@11 {
protocol_type = "sata";
power_pin_gpio = <0x35 0x00>;
detect_pin_gpio = <0x36 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:01.0,00.0";
ata_port = <0x04>;
};led_green {
led_name = "syno_led20";
};led_orange {
led_name = "syno_led21";
};
};
internal_slot@12 {
protocol_type = "sata";
power_pin_gpio = <0x37 0x00>;
detect_pin_gpio = <0x38 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:1b.4,00.0";
ata_port = <0x00>;
};led_green {
led_name = "syno_led22";
};led_orange {
led_name = "syno_led23";
};
};
internal_slot@13 {
protocol_type = "sata";
power_pin_gpio = <0x39 0x00>;
detect_pin_gpio = <0x40 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:1b.4,00.0";
ata_port = <0x01>;
};led_green {
led_name = "syno_led24";
};led_orange {
led_name = "syno_led25";
};
};
internal_slot@14 {
protocol_type = "sata";
power_pin_gpio = <0x41 0x00>;
detect_pin_gpio = <0x42 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:1b.4,00.0";
ata_port = <0x02>;
};led_green {
led_name = "syno_led26";
};led_orange {
led_name = "syno_led27";
};
};
internal_slot@15 {
protocol_type = "sata";
power_pin_gpio = <0x43 0x00>;
detect_pin_gpio = <0x44 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:1b.4,00.0";
ata_port = <0x03>;
};led_green {
led_name = "syno_led28";
};led_orange {
led_name = "syno_led29";
};
};
internal_slot@16 {
protocol_type = "sata";
power_pin_gpio = <0x45 0x00>;
detect_pin_gpio = <0x46 0x01>;
led_type = "lp3943";ahci {
pcie_root = "00:1b.4,00.0";
ata_port = <0x04>;
};led_green {
led_name = "syno_led30";
};led_orange {
led_name = "syno_led31";
};
};
usb_slot@1 {vbus {
syno_gpio = <0x1d 0x01>;
};usb2 {
usb_port = "1-1";
};usb3 {
usb_port = "2-1";
};
};usb_slot@2 {
vbus {
syno_gpio = <0x1e 0x01>;
};usb2 {
usb_port = "1-2";
};usb3 {
usb_port = "2-2";
};
};
}; -
I also notice that the pci address differs from when I ssh vs building key
-
I'm sorry, but when i got in tcrp, terminal, i type vi dva1622.dts and all i get is ~ going down the length of screen followed by dva1622.dts 1/1 100%
-
Do i need to upload a file or just edit the existing one?
would i look like this;
internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x16 0x00>; detect_pin_gpio = <0x25 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0";
pcie_root = "00:01.0,00.0"
pcie_root = "00:1b.4,00.0"
ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; -
4 minutes ago, merve04 said:
it says connection closed.
admin@DiskStation:/$ cat /sys/block/sata*/device/syno_block_info
pciepath=00:17.0
ata_port_no=0
driver=ahci
pciepath=00:17.0
ata_port_no=1
driver=ahci
pciepath=00:17.0
ata_port_no=2
driver=ahci
pciepath=00:17.0
ata_port_no=3
driver=ahci
pciepath=00:17.0
ata_port_no=4
driver=ahci
pciepath=00:17.0
ata_port_no=5
driver=ahci
pciepath=00:01.0,00.0
ata_port_no=0
driver=ahci
pciepath=00:01.0,00.0
ata_port_no=1
driver=ahci
pciepath=00:1b.4,00.0
ata_port_no=3
driver=ahcii just used temrinal and ssh in if that works?
-
13 minutes ago, pocopico said:
Please run
./rploader.sh update
./rploader.sh fullupgrade
and then after you create your loader using redpill-dtb-static which is added automatically, rploader will try to patch the DTS file for you. If this doesnt work for you, you will have to edit manually.
When you boot into install, you can login from your browser to http://ip:7681 and run the
cat /sys/block/sata*/device/syno_block_info
to collect your drives pciepath and ata_port settings and edit the DTS file manually. You need to put the edited DTS file under custom-module and recreate the loader.
it says connection closed.
-
-
6 minutes ago, pocopico said:
If you are using jumkeys redpill-qjs-dtb then it should on the fly patch the DTS.
Otherwise on your loader boot into install, login and run
cat /sys/block/sata*/device/syno_block_info
to collect your drives pciepath and ata_port settings and edit the DTS file.
I'm using this file, https://github.com/pocopico/tinycore-redpill/blob/develop/tinycore-redpill.v0.9.0.2.img.gz?raw=true
I tried the ARPL alpha 02 image but it doesnt boot?
do i access this cat /sys/block/sata*/device/syno_block_info in terminal when booted in tiny core image build?
-
1 minute ago, pocopico said:
SataPortMap has no effect on platforms that use DTS. If you use JUNs mode, then the disks should be added automatically. If you want to manually edit the DTS file then you can use the redpill-dtb-static.
Maybe you also want to try the ARPL it DVA1622 builds and run OK on my test system
thanks for the reply, i just downloaded the file from the first post and followed the instructions, did not try using my own dts, nor would i know how to, and if the file i downloaded doesnt have juns mode then i need to restart
-
I tried rebuilding usb key using satamap and it does detect the mobo 6 port controller followed but the 2x pci-e 5port jmb585 controllers, i think it did satamap655 and disk like 0006b or something weird,, maybe it needs to be modified?
-
well i proceeded with the upgrade as it seems booting once with the new loader rendered juns loader not working. the problem i have now is only 6 hdd's were detected. what should i try?
-
think im safe to upgrade?
just so you know, i didnt do ./rploader.sh satamap because it seems to give me problems when i do so building the loader.
ok im starting to get nevervous, because i wasnt sure if it was safe to proceed i shutdown and booted with my original key, my sever isnt coming back!
-
4 hours ago, apriliars3 said:
I haven´t any camera ip. I can´t test with AI functions on Surveillance Station.
Out of curiosity, why run dva1622? Why not ds3615 or the like?
-
1 hour ago, phone guy said:
Which server box is it? 🤩
Just a server I built using a gigabyte b365 board with a pair of jmb585 cards, all housed in a somewhat generic 16bay hot-swap chassis I got from alibaba
-
2 hours ago, pocopico said:
The DTS file for DVA1622 has been increased from 8 to 16 drives and all drives are visible in storage manager.
@merve04 you can test if you like
You’re my hero! I will try when I’m back from vacation. Will report.
-
1
-
-
33 minutes ago, dimakv2014 said:
Thanks so much for your hard work
SUCCESS:
Baremetall on Notebook Asus X556UQ with Core i3-6100U cpu.
8 camera licenses (used SerMac Gen for DVA3221)
AI Face Recognition works, tested with mp4, no drivers needed to be installed,
AI worked out of box, just steps 1-5.
After I got image on display "DVA 1622 the local installation will take about 6 minutes to install" I went to web browser find.synology.com, it found ip, when it asked for .PAT file, downloaded DSM_DVA1622_42661.pat (the one with Update) and done.
How many HDDs you have in your setup? I’m going to give this shot when I’m back home in a week. I really gotta ensure this can support my 16bay drive server.
-
7 hours ago, pocopico said:
The 1622 DTS file now supports up to 8 internal drives.
Is there back end work involved to support more HDD's? Its not just changing a value in one of the config files? I seem to recall seeing once a lines something about maxdisk=16, not sure if thats all theres too it. supporting 8 drives wont cut it for me unfortunately.
-
can this support 16 disks?
-
3 hours ago, error403 said:
1622 supports less AI tasks at once I think because of weaker onboard GPU.
That’s ok, I like the fact it also includes 8 licenses but would allow hw transcoding for plex.
-
On 6/20/2022 at 9:28 PM, bluecatus said:
How to use tinycore loader for DVA1622? Please give me instructions.
i'd like to know this too! Does DVA1622 come with more than 2 licenses by default? I imagine with the celeron gpu it would allow plex hardware transcoding.
Got my first answer; 4. The DVA1622 comes with 8 camera licenses. Support for more cameras requires additional licenses.
just tried building a tcrp 0.8.0.0 usb key, booted in, fullupdate but dva1622 is not reconized\supported. Maybe one day if its not too hard to implement, this model could be added?
Surveillance Station License Mod?
in Software Modding
Posted
Sure, I use plex to decode hvec files. I don’t use photo station, video station or really any other built in dsm apps to do media viewing, that’s what client pcs are for. One draw back may be if you wanted to use hvec compatible security cameras, imo storage space is cheap in the grand scheme of things.