Olegin

Tutorial: installing 918+ 6.2.X DSM on 1.04b loader (transcoding)

Recommended Posts

The jun's r8168 driver panic > [    5.449298] in your boot log

 

Since there's no new compiled driver for realtek and most of the realtek NIC stop to work since the 6.2.2-24922 update, you have to attach another NIC to your motherboard.

 

For note In your boot log, DSM is booting fine (but no lan)

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

It's been a while since I was here on this forum. I'm currently running DSM 6.1 on the DS3215xs 1.02b loader and would like to upgrade to 6.2 but also take the avantage of HW decoding from the DS918+ loader as it is mostly used as a Plex media server. 
I have read this thread but some things are still not quiet clear to me before proceeding.
I have the following hardware:

CPU:  Intel core I7-6700T (Skylake)
MB:   ASRock E3C236D2I
NIC1: Intel i210
NIC2: Intel i219

 

Could someone be so kind to confirm if I'm correct that in order to get HW transcoding to work:
- A valid synology serial number is required but should it be unique? By that I mean that in this thread someone posted 2 valid serials. Can these be used or MUST the S/N be unique and not shared by others?

- The NICs mac address must match the serial number?
- Is it correct that the Intel i219 NIC is not supported in this loader? I use one of the NIC for IPMI which is I think is nice and would like to keep this functionality.

 

Thanks.

Edited by mattail

Share this post


Link to post
Share on other sites
Posted (edited)

I am getting invalid serial when looking at var/log/messages with the the serial listed in this thread, so i am looking for a real working one as well :(

 

with that being said, you can you install just fine with it, but a few features does not work.

Edited by NooL

Share this post


Link to post
Share on other sites
Posted (edited)

I just realized how difficult it is to find a PCIE 1x Intel NIC (my motherboard has just 1 PCIE1x slot)

Even using an older DSM would still result in the 1.04 bootloader lacking the NIC driver using your extra.lzma on 1.04.. so I think I'm really out of options here..

No one else here using a J4105 or a J5005 who can confirm about the impossibility of having a working transcoding?

 

Edited by ilgrank

Share this post


Link to post
Share on other sites

In order to be able to 100% spoof a real 918.. Does one need to burn a new MAC to the NIC? Is the loader MAC sufficient or does Synology license management look through it?

Share this post


Link to post
Share on other sites

Quick question - well, sort of :)

 

I have my main rig, still running 1.02b loader as 916+ with DSM v6.1.4-15217 (ASRock N3150). For testing purposes I've bought a ASRock N3050 which is from architectural standpoint basically the same.

 

When I try loader 1.04b for 918+ I couldn't install anything else but v6.2-23739. I couldn't install v6.2.2-24922 straight away (not sure why). To update, what is the currently recommended method? Download the latest via Control Panel > DSM Update? Or manually install a pack via Control Panel > DSM Update? Or during boot select 'reinstall' option then in the installation menu select 'migrate'? I've spent 2.5 days trying various methods but I think I'm missing something rather simple.

Share this post


Link to post
Share on other sites
On 8/5/2019 at 6:49 PM, NooL said:

In order to be able to 100% spoof a real 918.. Does one need to burn a new MAC to the NIC? Is the loader MAC sufficient or does Synology license management look through it?

Loader MAC is enough for my 918+.

Share this post


Link to post
Share on other sites

Everything is now working as intended, except for WOL - It wont seem to wake-up when it goes to sleep.. Anyone else had issues with this? It's enabled on both NIC's in DSM

Share this post


Link to post
Share on other sites

@bearcat

 

I have 2 real MAC's specified in the grug config.

 

It seems to only be applied to one though, the second one is seem with its original mac. So as i see it, i have 1 spoofed NIC and 1 non-spoofed.

 

I tried hitting it on both internal ip's but none of the NIC's made it wake up.

Edited by Polanskiman
quote

Share this post


Link to post
Share on other sites

@bearcat Well to be honest, i didnt really try sending "Magic Packets" as such.

 

My previous setup was a genuine DS413j, that would wake from sleep automatically when/if i tried to access it either via Web (Both LAN/WAN), via DLNA or via CIFS, so no specific magic packet was needed? I was under the impression that i could get the new Xpenology box to work the same way, maybe this is not the case?

 

While i have you here - is the general consensus that NVME on Baremetal xpenology installation is no-go? I have 2xNVME slots installed in the motherboard, they are seem by bios and i suppose by the OS, but i get this in /var/log/messages:

 

2019-08-17T18:25:08+02:00 DiskStation synostoraged: nvme_dev_port_check.c:29 Failed to get slot informtion of nvme0n1

2019-08-17T18:25:08+02:00 DiskStation synostoraged: nvme_dev_port_check.c:29 Failed to get slot informtion of nvme1n1

 

Is there any way to fix it?

Edited by NooL
Quote + addition

Share this post


Link to post
Share on other sites
15 minutes ago, NooL said:

@bearcat Well to be honest, i didnt really try sending "Magic Packets" as such.

 

My previous setup was a genuine DS413j, that would wake from sleep automatically when/if i tried to access it either via Web (Both LAN/WAN), via DLNA or via CIFS, so no specific magic packet was needed? I was under the impression that i could get the new Xpenology box to work the same way, maybe this is not the case?

 

While i have you here - is the general consensus that NVME on Baremetal xpenology installation is no-go? I have 2xNVME slots installed in the motherboard, they are seem by bios and i suppose by the OS, but i get this in /var/log/messages:

 

2019-08-17T18:25:08+02:00 DiskStation synostoraged: nvme_dev_port_check.c:29 Failed to get slot informtion of nvme0n1

2019-08-17T18:25:08+02:00 DiskStation synostoraged: nvme_dev_port_check.c:29 Failed to get slot informtion of nvme1n1

 

Is there any way to fix it?

 

I know this is not the answer to your question but I'm very curious whether you got hardware transcoding to work or not?

Share this post


Link to post
Share on other sites

@mattail I did get transcoding to work yes, it did take a few attempts with combinations of serial/mac and reinstallations as follows - but that was as much me wanting to learn what triggered what in the installation process.

 

So yeah its working and you just need to INSTALL it with a valid SN/mac combination to have it working, i dont recommend changing it after installation.

 

To be able to spoof it 100%, quickconnect Et al. - you need to install it with a REAL sn/mac, but this is a bit unethical so not recommended on the forum.

 

{"success":true,"activated_codec": ["h264_dec","h264_enc","mpeg4part2_dec","hevc_dec","aac_dec","aac_enc","vc1_dec","vc1_enc"],"token":"token"}

 

I also noticed that the codecs in the activated list seem to appear as files are converted. So in my case it started by only showing h264_dec","h264_enc, then i downloaded a test WMV (VC1) codec file, uploaded that to Photostation, waited until it was converted and then "vc1_dec","vc1_enc" was added to the list as well.
 

I hope this helps you :)

 

 

Edited by NooL

Share this post


Link to post
Share on other sites

@mattail np, let us know how it turns out :)

 

5 hours ago, NooL said:

@bearcat Well to be honest, i didnt really try sending "Magic Packets" as such.

 

My previous setup was a genuine DS413j, that would wake from sleep automatically when/if i tried to access it either via Web (Both LAN/WAN), via DLNA or via CIFS, so no specific magic packet was needed? I was under the impression that i could get the new Xpenology box to work the same way, maybe this is not the case?

 

While i have you here - is the general consensus that NVME on Baremetal xpenology installation is no-go? I have 2xNVME slots installed in the motherboard, they are seem by bios and i suppose by the OS, but i get this in /var/log/messages:

 

2019-08-17T18:25:08+02:00 DiskStation synostoraged: nvme_dev_port_check.c:29 Failed to get slot informtion of nvme0n1

2019-08-17T18:25:08+02:00 DiskStation synostoraged: nvme_dev_port_check.c:29 Failed to get slot informtion of nvme1n1

 

Is there any way to fix it?

 

Quoting myself as it got buried a bit :)

Share this post


Link to post
Share on other sites

Could someone suggest me the process on what to do if my system WAS hw transcoding with Real SN/MAC but after i changed hardware now its not showing hw transcoding?

 

Photo Station is NOT making thumbnails for Videos anymore. 😓

 

Look at the attached images of my ssh. Does this mean i have hardware Transcoding Working but software Transcoding NOT Working?

 

 

 

 

DEV DRI FOR XPEN.PNG

 

putty #2.PNG

Edited by Captainfingerbang

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.