Jump to content
XPEnology Community

IG-88

Members
  • Posts

    4,386
  • Joined

  • Last visited

  • Days Won

    204

Everything posted by IG-88

  1. at least there are some rumors about "the other" kernel 5.x based unit - the rtd1619 https://nascompares.com/rumour/synology-ds423-4-bay-nas-drive-rumour-mill/ "he architecture of which is incredibly likely to be for the DS223j, DS223 and DS423:" also interesting is the rumored 923+, most likely not a rtd1619 but also surly not a epyc7002 maybe the 923+ will be the icelake we have seen in the kernel config, maybe this cpu? https://ark.intel.com/content/www/us/en/ark/products/197122/intel-core-i31000g1-processor-4m-cache-up-to-3-20-ghz.html its tdp might fit the power consumption of a nas but the price point might be a problem but a r1000 base is also possible but we have not seen anything from synology using the amd gpu's for transcoding (and the plus in the name indicates that feature)
  2. there seems to be no unit yet released based on that epyc7002, might happen later this year, maybe with with dsm 7.2? synology usually does not release the kernel for the recent dsm version (atm 7.1, kernel source from syno only for 7.0 available) so we dont expect the syno kernel source for 5.x available soon but nic drivers should be possible to build from the vanilla kernel.org source so IF there is a dsm *.pat file for a epyc7002 (released) unit available the repill loader could be extended to support that unit (if there are no new obstacles in terms of protection) - its just guessing from how things where going the last years but at least its kind of a logical chain how things might work out as a time frame (at best) i would not expect anything usable before december anyone in need of kernel 5.x now might consider open media vault or any other nas system out there its possible to set up a xpenology dsm system the normal way (to be ready when kernel 5.x is available) and then boot that system with a different boot media using OMV, the raid set of dsm should be usable with omv (even SHR sets should work) and its possible to boot dsm at any time by removing the omv boot media (my use case is the other way around, omv is my fallback if dsm cant be used anymore, https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475) - kind of a xpenology ready OMV nas system (dsm uses a 2GB and 2.4GB partition on every disk as raid1 for system and swap and installing dsm before using it with omv makes shure there is everything in place to run dsm later without the need changing anything on the disks as dsm 7.2(?) later will install on the already present system partition and leave the raid set untouched - but a backup of the data on the raid would be good, just in case)
  3. ich würde da kein hindernis sehen, dein altsystem is avoron (64bit atom) und deine zielplattform ist je nach loader und modell Apollolake, Broadwell, Broadwellnk, Bromolow, ... https://kb.synology.com/en-global/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_HDD limits sollte es da keine wesentlichen geben da du auch x86_64 bleibst https://kb.synology.com/en-global/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later#x_anchor_id7 allerdings ist ein umstieg auf dsm 7 mit ein paar haken verbunden da es u.a. bei den 3rd party paketen dann auch neue versionen für 7.x benötigt, ist aber kein xpenology problem, das haben alle die von 6.x auf 7.x updaten (würdest du auch haben wenn du deine 415+ auf 7.1 umstellst während des umstiegs auf xpenology sollte man nicht unbedingt ein downgrade versuchen (das offiziell von syno nicht unterstützt wird), dicht an den szenarien bleiben die syno selbst vorsieht, dann kann man auch deren tools und KB benutzen, denn abgesehen vom loader ist das installierte dsm "ganz normal" so wie auf einem orginalen system
  4. versuch mal die ip adresse des nas auf dem du installierst am router für internet zu blockieren oder trenne internet per kabel das pat file kommt dann von lokal auf dem pc und er kann nichts im internet nachladen
  5. the drivers will only work for 6.2.3 but there are patches and driver for newer DSM Versions https://xpenology.com/forum/topic/59909-i915ko-backported-driver-for-intel-10th-gen-ds918-ver-701-up3/
  6. extra/extra2 from 1st page, that will remove jun's special i915 driver that does not work anymore with 6.2.3, synology has a new i915 with 6.2.3 that is more or less the same as jun's driver your J3710 is a braswell and will not be able to encode hevc (h.265), so if you do reencoding use avc (h.264) https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video
  7. usually limits with DSM are about cpu gen's like min 4th gen for 918+, with just the cpu its usually about two possible gen's (intel, tick-tock), 2nd and 3rd was for one socket/chipset so even when downgrading the cpu one gen with the same board its not possible to make things not work (you cant downgrade below 4th gen with just a cpu swap) one of the pitfalls can be the number of supported cpu cores (including HT), when having more "threads" then the max cpu in the kernel then it will "cut off" whats behind the max. cpu and its usually a real cpu core and after that a "HT virtual" core and those HT "virtual cores" only have ~25% of a real core in your case its only 8 threads and the 3622 has max. 24 threads (https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/) but that's "only" about the cpu performance
  8. eigentlich sollte das automatisch gehen bei deinen schritten aber du kannst ja mal einen anderen laoder versuchen https://xpenology.com/forum/topic/63486-automated-redpill-loader/
  9. finger for vibrations and ear for noise, even on a 2.5" hdd you will recognise if the spindle motor is running or starts to spin up config SYNO_SATA_JMB585_FIX bool "Fix JMicron issues" default n select SYNO_SATA_CONTROLLER_INFO help <DSM> #120513 Fix JMicron JMB585 interrupt issues config SYNO_SATA_JMB585_DUBIOUS_IFS_FIX bool "Fix JMicron 585 raise IFS on device error" default n select SYNO_SATA_CONTROLLER_INFO help <DSM> #127949 Fix JMicron 585 raises IFS on device error. Determine the actual error by reading disk ncq log. config SYNO_SATA_JMB585_GPIO_LED_CTRL bool "Interfaces For Jmicron JMB585 GPIO Control" default n depends on SYNO_OF help <DSM> #131900 Provides the infterfaces to operate the GPIO pins on JMB585. config SYNO_SATA_ASM116X_CONTROL bool help <DSM> No bug entry asmedia 116X register read / write function. config SYNO_SATA_ASM116X_AMP_ADJUST bool "adjust amplitude and de-emphasis for asmedia 1061 sata signal" default n select SYNO_SATA_ASM116X_CONTROL help <DSM> No bug entry adjust amplitude and de-emphasis for asmedia 116X sata signal config SYNO_SATA_ASM116X_GPIO_LED_CTRL bool "Interfaces For Asmedia 116X GPIO Control" depends on SYNO_OF default n select SYNO_SATA_ASM116X_CONTROL help <DSM> # Provides the infterfaces to operate the GPIO pins on Asmedia 116X.
  10. https://archive.synology.com/download/ToolChain/toolchain/7.1-42661 edit: there is little more in the config files EPYC7002 = AMD EPYC Embedded 7002 https://www.amd.com/en/processors/embedded-epyc-7002-series from kernel config CONFIG_NR_CPUS=24, so its a 12 core unit and there seems to be ony one with 12 cores from AMD AMD EPYC Embedded 7272, max. 3.2GHz, base 2.9GHz, 120W ICELAKED = Intel Icelake-D https://www.intel.com/content/www/us/en/products/platforms/details/ice-lake-d.html both look like as for syno business units so nothing new as a replacement for 920+ (intel qsv support) but at least kernel 5.10.55 will add intel igc support (2.5Gbit nic) and if the "old" units get kernel 5.10 (witn dsm 7.2?) we will have better intel qsv support
  11. did you do a pci pass trough for the controller in the vm's configuration? whats the pci id und sub id's of the controller the driver would be aacraid and that driver is part of the additional/extended extra.lzma beside pci device passtrough its also passible to use rdm mapping of the disks into the vm, that way you woud not need a extra driver
  12. thats something synology should be answering in its spec's (for amd based units) or knowledge base as xpenology users we are not excluded from syno's web resources as long as its a generic function (things like adding nvidia support to 3615/3617 as done with 6.2.3 will not be covered by syno's kb)
  13. the way we talked about to use wch382l with the loader was as pcie card, the other end does not matter how the serial connection is done (the part where the terminal program is running), imho you will not succeed with any usb adapter because there usb stack is not running at this point (syno's kernel loaded without any additional modules), the way you could do that is a m.2 nvme to pcie adapter with a pcie card (or a m.2 nvme card with serial port - if such a thing exists) but i guess in most cases people will use a m.2 nvme (pcie 4x) to pcie as a extension for more sata ports or to even get sata ports (as with my test notebook that did not have sata ports, just nvme) we need to use whats livable in syno's dsm kernel for the serial connection for now, i don't know if there is any way to do anything additional using the rp kernel module to inject code that would add anything useful here, thats kind of a brainteaser for the people adapt in kernel hacking
  14. suggested driver to add (often asked/used) -aqc111 - usb adapter 2.5/5 GBbit -mlx_compat mlx4_core mlx4_en mlx5_core -aacraid -tn40xx - tehuti 10G nic's (can be tricky to have all firmware files integrated for all phy's, i do have as source that usually works for all cards as i added from different sources) -9p for virtio drivers (9pnet 9pnet_virtio 9p virtio) -ixgbevf, igbvf,,i40evf for virtio
  15. both plex and jellyfin dont depend on serial or syno's codecs so its kind of driver/kernel/hardware related only thing that comes to mind would be to change the state of vt-d for the iGPU in bios
  16. the driver mentioned is only usable with dsm 6.2 dsm 7.0 has a different kernel version and that will prevent the driver to work if you use tinycore rp loader and let it detect you hardware then the card should work the driver is present in pocopicos extension repository https://github.com/pocopico/rp-ext/tree/main/atlantic
  17. driver should be ok as you have devices in /dev/dri videostation us usually usable with a patch https://xpenology.com/forum/topic/49961-synocodectool-patch-for-dsm-70/ but plex should be working with just the driver and plexpass (license needed to use hardware transcoding with plex) maybe try this instead of plex https://synocommunity.com/package/jellyfin that should also work with just the i915 driver and hardware transcoding is free ootb to use
  18. J5040 would be kind of ideal for dva1622 as this system uses ai ss with the intel internal gpu (original unit from synology is also gemin lake refresh but J4125) the dva3221 comes in original with a cpu that does not have a internal gpu and a nvidia gpu, so a internal gpu would be of no use und only a nvidia gpu would work for the ai stuff in ss afair dva3221 can serve 16 cams and dva1622 8 cams you need to look closer, the tinycore rp loader does support multiple units (and there is a newer developer version too that was announced about 4 weeks ago her in the developer area you can test https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ https://xpenology.com/forum/topic/62871-tinycore-redpill-loader-tcrp-development-release-09/ https://github.com/pocopico/tinycore-redpill/tree/develop there is also a new loader (should also support dva1622) https://xpenology.com/forum/topic/63486-automated-redpill-loader
  19. there are some newer developments around these problems like the mode used in newer system 920+ called device tree, for handling disks and ports i guess this will find its way to the actual loader shortly beside this there is e new loader https://xpenology.com/forum/topic/63486-automated-redpill-loader not all the drivers yet as with tc loader but i guess that can be changed quickly as the structure of the drivers is less complicated to handle manually but using a hypervisor might not be that bad is it offers more options in the long run (but it also more complex to handle, i still prefer baremetal and a single purpose system but when having to juggle more vm's then just DSM and docker then i would switch to a hypervisor too)
  20. and there was a list of selections, you might have overlooked the "DS3622xs+" its often used without the "+" or "p" and that can be confusing, there is no "DS3622xs" from synology its always the "DS3622xs+" even if its writen DS3622xsp or DS3622xs, the "+" might be avoided here an there as its not a letter or number https://www.asrock.com/mb/Intel/J5005-ITX/index.asp#Specification - 2 x SATA3 6.0 Gb/s Connectors, support NCQ, AHCI and Hot Plug - 2 x SATA3 6.0 Gb/s Connectors by ASMedia ASM1061, support NCQ, AHCI and Hot Plug so its two sata controllers, 920+ uses a different way then the older units and the new way needs to be matched to the hardware (device tree) my guess its that you only see the 1st controller and the other two drives are on the 2nd there is a way to redo the default tree file to match the hardware, in the later iterations of the tc rp loader it should be done when building the loader in auto mode but i cant say much about that from memory as i have not used it yet, look in the forum for "device tree dts", the automation might be newer stuff that is not yet in the normal tc rp loader (yet)
  21. the picture shows a pcie 1x card (now?), if thats real then only one pcie lane out of two would be used and thats not desirable the one i have looks the same but has a pcie 4x connector (as there is no 2x defined in the standard - at least not as a slot, but i've also seen cards with a 2x connector cards) the pcb has no vendor but a number marking PCE6SAT-A01, VER006S mine is like this https://www.amazon.de/-/en/BEYIMEI-Support-Devices-Distribution-ASM1166-PCI-4X-6SATA/dp/B08DFK4LZ7/ and i did only test it briefly, its laying around for over a year as i was using jmb585/582 (and a older pcie 1x marvell) in my normal systems so i cant say much about it other then it worked for testing with a few different disks but i guess by now there should be more reports about asm1166 based cards, so you should use a search engine to get some more information
  22. i exchanged the sata cables to get rid of this use dmesg to check the log if there is anything unusual or related in the time to the failure of the raid
  23. i usually suggest pcie 3.0 capable ahci controller like jmb585 or asm1166 because of the double bandwidth of pcie 3.0 and the limit of all there (cheaper) controllers to two pcie lanes i use jmb585 (with dsm 6.2.3) without any problems but as can be seen here (link below), there might be some trouble with jmb585 as synology has some special fixes build into dsm 7.x for that one (needs further inspection, couls still be some special problem of the single system) https://xpenology.com/forum/topic/63475-dsm-7-proxmox-hdd-hibernation-issue/#comment-288716
  24. where does that come from? the files used for update are named geminilake (as th cpu used in th dva1622) https://global.download.synology.com/download/DSM/criticalupdate/update_pack/42661-2/synology_geminilake_dva1622.pat
  25. because all systems use dts config (device tree) now?
×
×
  • Create New...