Jump to content
XPEnology Community

infonator8

Member
  • Posts

    32
  • Joined

  • Last visited

Posts posted by infonator8

  1. On 2/11/2021 at 6:03 PM, IG-88 said:

    YES, the 6.2.3 comes with its own newer i915 driver for intel quick sync video on gemini lake and the kernel changes synology made will have the i915 driver jun made not working

    my extra/extra2 for 918+ takes care of this (there is some more description about that in the 1st post)

    https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/

     

     

    Hmm, did it but still no success. Still no activation.conf and on Video Station I can only select the "Prohibit Transcoding" transcoding option.

  2. - Outcome of the update:  SUCCESSFUL

    - DSM version prior update: DSM 6.2-23739

    - Loader version and model: Jun's Loader v1.04b DS918+

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - Signature.

    - Additional comments: No trouble.

     

  3. So, I had HW transcoding working just fine on my box. Got a valid serial/mac, etc.

     

    I had to reinstall DSM just recently, was configuring everything, when suddenly I have no activation.conf.

     

    My grub.cfg is just fine. Serial registered on synology. I'm on DSM 6.2.3-25426 Update 3.

     

    Any ideas? I read this topic but couldn't find any clues... maybe extra.lzma?

  4. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.1-23824 Update 4

    - Loader version and model: Jun's Loader v1.04b - DS918+

    -  Using custom extra.lzma: NO

    - Installation type: BAREMETAL - Hardware on my signature

    - Additional comments: Updated from DSM Control Panel, no reboot necessary

  5. On 12/25/2018 at 11:17 AM, Olegin said:

    cd /dev/dri

    I have this folder with two files: card0 and renderD128

     

    But, as for this file:

    On 12/25/2018 at 11:17 AM, Olegin said:

    cat /usr/syno/etc/codec/activation.conf

    I haven't. The command results in "No such file or directory".

     

    Does anyone have any idea why?

     

    Also, while migrating from ds3615xs in DSM 6.1.7 I didn't erase settings and etc.

  6. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.2-23824 with Jun's Loader v1.04b - DS918+
    - Loader version and model: Jun's Loader v1.04b - DS918+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Hardware on my signature
    - Additional comments: Reboot Required.

  7. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.7-15284 with Jun's Loader v1.02b - DS3615xs
    - Loader version and model: Jun's Loader v1.04b - DS918+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Hardware on my signature
    - Additional comments: Reboot Required. Just ran migration process from 6.1.7 ds3615x to 6.2 ds918+ and everythin went fine.

  8. Hi everybody,

     

    I'm planning to do a new build of a xpenology server. The one I have right now is pretty good, works just as I want, but I can't let it 24/7 because of power usage.

     

    I manly use it as a backup server and PLEX streaming. I'm using DS3615x.

     

    My actual specs are: Intel Pentium G4560, MSI B250M PRO-VH, 4GB DDR4 Crucial RAM, 2x2TB HDs and a Corsair 450w PSU.

     

    I was thinking about migrating to a AsRock J3355B-ITX (has a built-in Intel Celeron J3355 CPU). I have found one thread about this CPU in the forums, from a guy trying to get DS916+ loader working.

     

    What do you guys think? Should I migrate or stay as things are?

  9. Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.1.4-15217 Update 5

    - Loader version and model: JUN'S LOADER v1.02b - DS3615xs

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - Specs in signature.

    - Additional comments: REBOOT REQUIRED

  10. 7 hours ago, abced said:

    When I plugin the boot USB, I have three options for boot in UEFI (partition 1, partition 2 an USB device or something). What's the one I should put on the first place?

     

    Select partition 1 because it'll recall the other needed files.

  11. 2 hours ago, Polanskiman said:

     

    You CANNOT use the ramdisk I posted in the tutorial aimed at Jun's loader v1.01 with Jun's loader v1.02b. DSM 6.0 and DSM 6.1 have a different kernel version and modules compiled for DSM 6.0 will simply not work with DSM 6.1. That's why I asked if you used the default or customised ramdisk. If you used the customized ramdisk then you can't upgrade to DSM 6.1 unless you or someone compiles the atl2.ko module for DSM 6.1 and then add it to Jun's loader v1.02b. There is a guide in the forum on how to do that.

     

    Thank you a thousand times @Polanskiman! I compiled the driver and everything worked fine! :smile: Updated to 6.1!

    • Like 1
×
×
  • Create New...