Jump to content
XPEnology Community

IG-88

Developer
  • Posts

    4,645
  • Joined

  • Last visited

  • Days Won

    212

Everything posted by IG-88

  1. a serial console, after initial booting dsm switches the output to the serial port 1.03b loader needs a classic bios or csm mode (when its uefi bios) so you might switch csm on and need to select the non uefi usb boot device (there are usually 2 uefi boot devived and one for csm mode) and soem systems need a mbr loader https://xpenology.com/forum/topic/20270-dsm-62-loader-with-mbr-partition-table/
  2. nothing special about it, r8168 driver is present and recent, if something not working then its not about the nic driver
  3. csm might be on by default, so look in bios for usb boot devices, there should be two for uefi and one generic/bios also some hp systems might need a special MBR version of the loader https://xpenology.com/forum/topic/20270-dsm-62-loader-with-mbr-partition-table/ atm i'd asume the system does not boot at all, only way to be certain is a serial console and most people don't know about serial cables/null modem cables so look for the selection of boot devices and try the mbr version of the loader
  4. no, i dont have any new backported source jun used so a cant recompile or anything you can test the version as it s now and try to confirm its working or not, preferably someone with a serial console would be good for this as he could see whats going on when booting
  5. why not? it seems to be one chip and its named "Marvell 88SE9215" in the product name -> https://www.marvell.com/documents/fygjojpnztocvwktbmpr/ one pcie 2.0 lane to 4 sata port controller so its ok
  6. no if you upload the 6.2.0 pat file when installing it should work without this as you gave no precise information i might have to guess about whats the most probable reason if you where using 6.2.0 then it might be that 1.03b need CSM mode (and csm mode boot device when selectiong the usb boot device) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/
  7. you left out you cpu but your board only support 2nd and 3rd gen intel cpu, loader 918+ 1.04b needs a 4th gen cpu as min. so thats not going to work for you (same for 916+) id suggest reading this https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ also the faq section and the tutorial when "practicing" installing you might keep to the 1st 6.2 version if you want to go to 6.2.2 it needs more preparations as it needs different drivers, so you need to copy additional files to the loader https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/
  8. mal davon abgesehen ob man wirklich hardware transcoding braucht wo doch die meiste hardware mit 4k streams umgehen kann ist es möglich geworden das auch ohne sn und mac zu aktivieren https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/
  9. 1st post in this thread, there is a section with additional information about gpu, so you can see J5005 gemini lake "... the often seen Gemini Lake GPU's might work with "std", pretty sure not with "syno", most (all?) testers with gemini lake where unsuccessful with "std" so if you don't like experimenting and need hardware transcoding you should wait with the version you have ..." so i'd unlikely to maybe, if you want to test use a new usb and a empty disk fot a test install, don't try to install your running 6.2, its very likely to fail
  10. that depends on what 6.2 version you are talking about the latest is 6.2.2 is that much different that the drivers from the loader (made for 6.2.0) do not match anymore you need to install the first 6.2 version to get it properly working or if using 6.2.2 dsm *.pat file to install you need matching drivers https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ 2nd half is about 3615/17
  11. 2 x tehuti (eine davon mit dem synology dsm eigenen treiber lauffähig) 1 x broadcam 2 port (bnx2x treiber) letztere steckt im nas und versorgt desktop und backup (des nas) mit 10G ohne das man einen switch braucht für die 2. tehuti karte mit marvel phy musste ich gegenüber dem 2018 benutzten treiber etwas nachrüsten, man bekommt meist nur treiber source der für einen phy ist und muss versuchen sich die firmwre aus verschiedenen quellen zusammenzusuchen, aber aktuell sollte eigentlich alles mit tehuti chip und den mögliche phys laufen für aqunatia gibts auch einen treiber aber da ist der neueste bei einem tester abgestürzt, da habe ich auf eine etwas ältere version des source zurückgegriffen (das war bei kernel 3.10.x für 3515/17, evtl. würde es ja mit kernel 4.4.x der 818+ gehen aber da braucht man die hardware oder willige tester) - wäre also denkbar das man die neuesten karten eines noname herstellers nicht damit gehen, das feld kann aber erst bearbeitet werden wenn es bedarf/tester gibt, nur damit andere es nutzen können gebe ich keine 100€ für eine karte aus die ich nicht brauche (evtl. stirbt ja auch eine meiner karten und dann wird es evtl. eine neue auantia)
  12. if the usb is working for update 6.2.0 to 6.2.2 then it should also be possible to install with it directly (using the 6.2.2 *.pat file)
  13. WOL, that needs the real mac as in sleep the real mac is active also some licensing features of dsm compare sn and mac the later one could be solved by defining a unused mac slot with a sn matching mac but thats history now, there is a patch that will change the licensing module in a way that it always comes out with a positive result
  14. no, should work without it (at least it did on my system)
  15. 1st post, "... !!! still network limit in 1.04b loader for 918+ !!! ..." there is even a link to the old thing about how to edit synoinfo.conf for more nic's can't be the 1st post in this thread it states clearly to copy (overwritte) extra/extra2 not just one of them AND !!! you need to place the zImage and rd.gz from the 24922 *.pat file at the same location the driver is working, i do have a e1000e and igb card for testing and as the driver where the latest from 12/2019 it sure should work with any card/chip even the newest
  16. it does use the cores, you can check log/dmesg for "dynamic" cpu gui output you can read here https://xpenology.com/forum/topic/13030-dsm-5x6x-cpu-name-cores-infomation-change-tool/
  17. there is also open media vault, also lots of options
  18. beside M.2 nvme support in 918+ there is not much difference when using 3615 image
  19. i inserted a part about it "This is the new 2nd test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2, network drivers for intel and realtek are now all latest and the same as in 3615/17 from mid. december (also broadcoam tg3 driver is working),..." but there was already a entry in the driver list " drivers included (Reveal hidden contents)" for tg3 when not using hardware transcoding or M.2 ou could migrate to 3615/17, 918+ has a newer kernel and one or the other driver might me slightly newer in kernel 4.4..x but in terms of usage there might be no difference i changed the text slightly for better instructions
  20. i can only encourage you to try there are alternatives to DSM too, if you want to try something different then open media vault is a good option, you can boot up from 1 additional/external media and it will recognize the dsm raid partitions (synology uses mdadm and lvm, thats normal linux software raid), it should be using the btrfs file system (but will not offer btrfs when creating a new, but that can be done manually if needed) it's my fallback option if dsm fails and a really want to access my data over network (omv does support all the basic nas stuff dsm does and has plugins too, much less hassle when it comes to drivers as its just a normal open source linux distribution - xpenology is a hacked dsm appliance and has its shortcomings and synology is not offering proper kernel source for its gpl based system)
  21. with the link above there is no past 6.2, you will have to use the driver (that are mode for 6.2.2) copy the zImage and rd.gz from 6.2.2 (from *.pat file v24222) to the loader and you hve to install 6.2.2/v24922 pat file, no steps or anything the drivers in that extra.lzma will only work with 6.2.2 anr the same goes for the drivers jun packt with loader 1.03b, they are not working with 6.2.2 you should at least be able to boot and find it in network and synology assistant should show as version a 24922 (i cant see storage you use but i guess when its working with 6.1 it should work with 6.2.2 too)
  22. new drivers up - lets see who bricks his unit first because of not reading properly (yes i know its a lot of text)
  23. in general a driver pack that is made for 6.2.2 should fix it, when its 3615/17 then its already available, if its 918+ it will be in a few hours just copy the new extra.lzma to the usb (the new kernel zImage and rd.gz should already be the one of 6.2.2 as you have installed it already)
  24. ist es denn aktiviert bei deinem system? beim erzeugen eines shares kann/sollte man das aktivieren 3. tab bei einem share (advanced) https://blog.synology.com/how-data-scrubbing-protects-against-data-corruption/ soweit ich das nachlesen konnte würde man das in dem paket "Log Center" nachher finden
  25. the hack/loader is individual for a model so someone would need to do it, jun is not active in this way, he might be again when dsm 7.0 (beta) is out and what system he gives a closer look might depend on what he thinks is interesting dva might not be that interesting for most here as its not made for multimedia use and i guess it will not support using the nvidia card for transcoding
×
×
  • Create New...