Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 06/09/2020 in all areas

  1. Hola Mary Andrea, Para instalar un dsm 6.x debes editar la imagen del bootloader con los datos de tu usb o de tu lector de tarjetas sd (que también tiene PID i VID). Yo también uso OSX, pero instalé un windows en virtualbox para poder usar los programas de la guia (osfmount, notepad++, windisk32imager, etc) Yo creo que con el hardware que tienes, el boot 1.03b y el dsm 6.2.3. 25426 para 3615m o el boot 1.04b y el dsm 6.2.3 25426 para ds918+ deberían funcionarte, pero claro siempre editando el boot con tus valores de pid/vid, serial, Mac Address, sataportmap, etc.... Suerte!
    1 point
  2. good, anything above 1GBit networks is really a must have for now days nas (i prefer 10G but even 2.5G would be a noticeable step up for must people no, i dont see a reason to put anymore work into this (would be better to spend more time in documentation about the state of the drivers for 6.2.3) kind of a closed chapter now as synology is back to "normal" with 6.2.3 (and having three different extra version for 918+ was not really that nice, having a "universal" i915 driver make things much easier) i will do the same realtek drivers for 3615 and 3617 and 6.2.3 this weekend
    1 point
  3. Found it: 1) Enable SSH and ssh into your DiskStation 2) Become root ( sudo -i ) 3) Make a mount point ( mkdir -p /tmp/mountMe ) 4) cd into /dev ( cd /dev ) 5) mount synoboot2 to your mount point ( mount -t vfat synoboot2 /tmp/mountMe ) Now I see the extra.lzma modified that has 4MiB in size so now I just replace the file with the original from 1.03b that has some 1,8MiB ? Then I use the web interface to manually install the DSM_DS3615xs_25426.pat? Please correct me if I am wrong.
    1 point
  4. the "X" is important here it its 6.2.2 and you used a special extra.lzma the you will need to replace it, as 6.2.2 drivers (in the extra.lzma) will not with 6.2.3 so check you documentation ... not when you already have loader 1,03b and DSm 6.2.x, in worst case you need to replace the extra.lzma with jun's original (can be extracted from the img with 7zip or osfmount) or use a newer one from here https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ i'd use jun's extra.lzma and if that makes any problem then you can try a newer one if you come from 6.2.0 or never replaced jun's extra.lzma you can just update to 6.2.3 (as 6.2.2 was new there was a lack of drivers and lots of jun's drivers did not work, some did not update, other bought "native" hardware that have drivers in dsm itself so they could update, keep jun's extra.lzma and still had a working nic )
    1 point
  5. jun's original extra.lzma is working again with 6.2.3 and contains the tg3.ko driver already it "broke" when synology introduced a kernel config change in 6.2.2, as as they reverted it in 6.2.3 ... "dont use" means they are using jun's old/original extra.lzma, would be more precise to ask about the "replacement" of extra.lzma if people did not care about the "lost" bcm nic in 6.2.2 because they had a additional intel nic that still worked after update to 6.2.2, and did not install a 6.2.2 aware driver set, then theey still have the original extra.lzma and that one is working again with 6.2.3 because of the reverted change in kernel config from synology -> tg3.ko working again, onboard bcm nic is "back"
    1 point
×
×
  • Create New...