Jump to content
XPEnology Community

Driver extension jun 1.03b/1.04b for DSM6.2.3 for 918+ / 3615xs / 3617xs


Recommended Posts

39 minutes ago, smartire said:

Live Linux did the trick

no, thats not the dmesg of the dsm system, you would need to mount the system partiton (raid1) if using a live linux

but why a live linux? you did say you have 3617 installed on a ssd on the sata cdrom connector and the sata/sas on the perc h330 is not detected

so you just boot up that 3617, ssh into it and copy the /var/log/dmesg to a share (like /volume1/data/) or to a usb you connect (if you can use winscp then this is ok too)

Link to comment
Share on other sites

I'm sorry for the confusion I had tried to install the 918+ again, so I just installed the DS3716 again. I really appreciate all the help.

if you think buying the a CPU 4th Gen would resolve the  error 13 I would prefer to install the 918+ since the 3716 reset the BIOS time every reboot. I'm willing  to buy one, I found one for $115 it more than I was planning to spend but once I get it up and running I will back my data and sell the R420. I hope I got it right this time. 

dmesg.txt

Link to comment
Share on other sites

I try to boot with Jun loader 1.03b 3615xs with extra.lzma by IG-88 with my new motherboard H410M-K but I cannot find the device on my LAN. The ethernet controller on that mb is not supported? May be there are some other driver needed?

 EDIT: I try to run a kive linux distro SLAX and the network is not reachable.

The RTL8111H controller has not the good linux driver?

 

Edited by Markvs
Link to comment
Share on other sites

22 hours ago, smartire said:

if you think buying the a CPU 4th Gen would resolve the  error 13 I would prefer to install the 918+

you cpu is already 4th gen (haswell) and error 13 is not related to cpu,

the cpu thing is about: is it booting (starting the kernel) or not, if you can find it in network the kernel came up and loaded drivers

 

sadly your dmesg file is not what we are looking for, it looks like a screenshot from a ssh session, there are only about 10 lines of the dmesg

you need to copy the dmesg file itself to a location like u usb that dsm will mount automatically

and after that you can eject the usb by thwe webgui and use it on you computer to attach it here

 

usb drive is usually /volumeUSB1/usbshare/ , that would be the destination when copying the file

 

7 hours ago, Markvs said:

extra.lzma by IG-88 with my new motherboard H410M-K but I cannot find the device on my LAN. The ethernet controller on that mb is not supported?

it is supported

 

7 hours ago, Markvs said:

The RTL8111H controller has not the good linux driver?

the chip is pretty old and is usually working with any drivers, there are problems here and there when it comes to performance but usually its at least working

 

8 hours ago, Markvs said:

I try to boot with Jun loader 1.03b 3615xs

with a 10th gen cpu you should use 1.04b 918+

3615/17 is more tricky as it needs csm mode in uefi bios and you need to boot from the non-uefi usb boot device

918+ can do uefi and csm

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

 

if 3615/17 does not boot the right way (csm mode and the right usb device selection) it will not start and the only way you would see the difference between not starting the kernel and driver not working would be to have a serial console connected (null-modem cable)

 

if a live linux does not work i'd say check your network cable and switch

Link to comment
Share on other sites

10 hours ago, smartire said:

I my CPU is the 4th gen (haswell) that means I should be able to install DS918+?

ok, i know i don#t write in my native language and i repeat myself  (3rd time writing this) - when it boots and you find it in network the cpu can be excluded, if the cpu would be to old then it would not boot at all because the kernel would not start, no kernel, no drivers, not found in network

the positive proof that its found in network is enough to for the conclusion that that the cpu is fine for 1.04b 918+

 

the next point for you (see above) was to deliberately change the usb vid/pid to not match the real values and test if you can install without error 13

quick glance at the dmesg, there are 4 + 6 sata ports found and a lsi sas controller would only be left with 2 ports usable as 3615/17 default config is max. 12 disks - but there does not seem to be such controller, mpt drivers are loaded (raid and non raid) without showing that a valid hardware is found

 

[Tue Apr 27 13:33:54 2021] pci 0000:01:00.0: [1000:005f] type 00 class 0x010400

thats a lsi MegaRAID SAS-3 3008 [Fury]

https://pci-ids.ucw.cz/read/PC/1000/005f

 

 

...
[Tue Apr 27 19:49:24 2021] ahci 0000:00:11.4: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0xf impl SATA mode
...
[Tue Apr 27 19:49:24 2021] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
...
[Tue Apr 27 19:49:28 2021] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
[Tue Apr 27 19:49:28 2021] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
[Tue Apr 27 19:49:28 2021] Fusion MPT base driver 3.04.20
[Tue Apr 27 19:49:28 2021] Copyright (c) 1999-2008 LSI Corporation
[Tue Apr 27 19:49:28 2021] Fusion MPT SPI Host driver 3.04.20
[Tue Apr 27 19:49:28 2021] Fusion MPT SAS Host driver 3.04.20
[Tue Apr 27 19:49:28 2021] Fusion MPT misc device (ioctl) driver 3.04.20
[Tue Apr 27 19:49:28 2021] mptctl: Registered with Fusion MPT base driver
[Tue Apr 27 19:49:28 2021] mptctl: /dev/mptctl @ (major,minor=10,220)
[Tue Apr 27 19:49:28 2021] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013
[Tue Apr 27 19:49:28 2021] mpt2sas version 20.00.00.00 loaded
[Tue Apr 27 19:49:28 2021] mpt3sas version 22.00.02.00 loaded
...

 

i guess jun used the kernel default drivers and 1000:005f is not supported in kernel 3.10 but is in 4.4 (918+)

so 918+ detects the controller and 3617 does not

its "megaraid_sas.ko" - thats a raid driver so you controller is in wrong mode aka IR mode not  IT firmware its IR firmware and you would need to reflash it to IT firmware

AND we already had this covered

https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/?do=findComment&comment=202009

if you reflash to IT firmware the better/newer mpt3sas.ko would kick in and detect the controller

 

Edited by IG-88
Link to comment
Share on other sites

Thank you very much IG-88, just wanted let you know that you are one of the greatest asset for this forum. BTW your English is pretty good you to have to be sorry, English is not my primary language either.  I just bought a R530 last night with 8 bays, probability I will be selling the R430. Helpfully I don't have the same issue with it, if I do I may buy the  E5-2630L v4 to see I can pass the error 13. I really want to load the DS918, but if after that still no possible and than I go with the DS3716. I will keep you posted.

Link to comment
Share on other sites

did you test to not match the usb vid/pid as i wrote above?

On the R430 yes I did try not match and 0000 and 1111 however on the R530 no yet, I just got it, I'm not home right now as soon I get home, I will try it.


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

No lucky so far, I've tested with no matching USB and matching VID/PID in thefollowing scenarios:

1 SSD in the CD-ROM adapter | UEFI and BIOS | DSM_DS918+ extra918plus_v0.4 | DSM_DS918+_23739.pat (error 13)

1 SSD in the CD-ROM adapter | UEFI and BIOS | DSM_DS918+ extra918plus_v0.12.1 | DSM_DS918+_23739.pat or DSM_DS918+_25426.pat (error 13)

1 SSD in the CD-ROM adapter | UEFI and BIOS | DSM_DS918+ extra918plus_v0.13.3 | DSM_DS918+_23739.pat,  DSM_DS918+_23739.pat or DSM_DS918+_25426.pat (error 13)

----------------------------------------------------------------

1 SSD in the CD-ROM adapter | BIOS | DSM_DS3617xs extra3617_v0.11.2_test | DSM_DS3617xs_25426 installed successful just reset the BIOS time.
I'm adding the dmesg and a screenshot from the DS3617 install, if I can't get the DS918 installed,  I believe that if I will need to change a congratulation file  so can detect all the 8 bays, if I'm not wrong I had that same issue when I installed on the R420.

2021-05-01_19-56-11.jpg

dmesg

Link to comment
Share on other sites

Just an update on the dilemma of trying to install DS918 on R530.

 

Since every attempt trying to install it on the server was a disaster, I tried to install it on a laptop with i7-6700 and it worked with the following:

DSM_DS918+_23824 | extra918plus version 3,4,5,8,12.1 and 13.3

DSM_DS918+_24922| extra918plus version 3,4,5,8,12.1 and 13.3

DSM_DS918+_25423| extra918plus version 3,4,5,8,12.1 and 13.3

DSM_DS918+_25426| extra918plus version 3,4,5,8,12.1 and 13.3

 

However when I moved the SSD and the USB to the server the only two version the worked.

DSM_DS918+_23824 | extra918plus version 3 but did not detect the hard drives on the RAID so I replaced the USB extra.lzma/extra2.lzma with the v013.3 and it worked perfectly. Well, I had to edit the synoinfo.conf to detect all the HHDs.

 

In the other versions when I move the SSD and USB to the server there is no Network, it seems that the CPU E5-2670 v3 and  E5-2630L v3 that I have tested are too old.

I have tried to set only 4 cores on the bios, disable  vt-x/vt-d, Hyper-threading in bios. Use only one CPU instead of 2.

I’m very motivated to buy and  E5-26xx v4 any thought?

 

 

Link to comment
Share on other sites

Hi IG-88, I know you very busy with so many people asking questions. Still, if you a free time and want to give help with this will be greatly appreciated.

 

I was able to install DSM_DS918+_24922 update 6 with extra918plus_v0.8_syno on the laptop moved to the server and worked but did not detect the hard drives, unlike the DSM_DS918+_23824 when I add the extra/extra2 from 13.3, and it won't detect the network. Any other newer than 23824 installs on the laptop fine, but when I move the USB, the SSD to the server no network.

I've already ordered an E5-2630L V4. I hope this helps me with this installation.

Notes: DSM_DS918+_23824 with extra918plus_v0.13.3 works, with the network connection and detect all the hard drives, had to change the synoinfo.conf to detect all the hard drives.

 

original:                                                  new:           

maxdisks="12"  maxdisks="24"
esataportcfg="0xff000" internalportcfg="0xffffff"
internalportcfg="0xfff" esataportcfg="0x0"
usbportcfg="0x300000" usbportcfg="0x3000000"
Link to comment
Share on other sites

  • 2 weeks later...

I wonder if it is necessary to replace also rd.gz and zImage from the original .pat file. I just replaced the extra.lzma itself and it worked (Juns 1.03b 3615xs loader + DSM 6.2.3U3 un HP MS Gen8 Baremetal) for me. My 10 Gig Asus NIC (Aquantia 107) is recoginzed.

Thanks for the driver package.

 

Edit. Somehow I have 41% Packetlos (480 pings send), when die Aquantia NIC is running on 1 Gbps. I haven't tried another link speed, since my switch isn't upgraded yet. But my current switch has no raising error counters. No matter if I set the interface to 100 Mb FD or 1000 Mb FD. No  issues with the onboard Broadcom NICs.
grafik.png.0eeff6336b68049037ecdc027a885102.png

 

 

Argh - call myself idiot. Accidentially a provided two different NIC of two different Xpenologies with the same MAC. Shame on me.

Edited by valix
Link to comment
Share on other sites

  • 2 weeks later...
On 5/1/2020 at 9:24 PM, IG-88 said:

 

edit: according to the manual you could check in bios for

Graphics Configuration

Primary Display -> IGFX

Internal Graphics -> Enable

(i'd expect it to work ootb when no extra graphics card installed but it cant hurt to try the settings above)

is a monitor connected to a video out of the board and is working?

 

 

 

 

Wow.  Scratching my head all day and your comment above brought it all to life.  Using a Supermicro X11SCH with Xeon 2124G and all I had to do was enable it in the BIOS and *pow* /dev/dri/card0 and renderD128 appeared.  Just before this step I did add the two extra v0.13.3 files mentioned in the top post to the "synoboot" USB, so this likely also helped.

 

admin@MEDIA:/$ lspci -k | grep 'Kernel driver'
Kernel driver in use: i915
 

 

Link to comment
Share on other sites

I have been happily running DS918+ DSM 6.2.3-25426 Update 3 on my four years old mini-ITX machine with Intel Core i5-7400 for some time now. Plex hardware transcoding worked. Unfortunately my MB was a bit limited on SATA ports (shared one SATA with M.2) so today I upgraded to a Asus Rog Strix B550-I Gaming Wifi MB with Core i5-11400 Rocket Lake processor. This MB has two M.2 slots + four Sata slots. The upgrade went fine. I deleted the volume (disk was already backed up to another NAS), swapped the MB+CPU and rebooted.

Then I tried Plex transcoding and saw that it does not use HW and I read in this thread that HW transcoding is only supported on older Intel CPU's.

 

Is there any plans to make HW transcoding working on newer, 11th gen, Intel CPU's?

 

Sorry. I didn't mean to hijack this thread!

Edited by atari
Link to comment
Share on other sites

On 6/2/2021 at 9:13 PM, atari said:

Is there any plans to make HW transcoding working on newer, 11th gen, Intel CPU's?

the proper way would be if someone backports a newer i915 driver to dsm's 6.2 kernel - synology is not likely to do that as every later x21 untis will have dsm 7.0 and if there is a newer driver by synology then not for 6.2 for sure, if synology drops transcoding later on with x21 units or if we will see a 7.0 loader is unknown, synology tends to use older patched kernels so using newer intel cpu's amd its gpu's is always extra backporting work and they might not continue in that directions, with 7.0 they drop a lot of older stuff (usb devices) for multimedia, they are more in the direction of clean NAS now and small/medium business as targets for DSM

 

only way open without that is to patch the i915 driver and trying to find out if the uhd730 of 11th gen can be used with the uhd630 driver of the i915 we have

newer and more different means less likely to work with the old driver we have, i dont have access to a 10th/11th gen intel desktop cpu so i can't test it myself and having other do it means lot of extra work and uncertainties as newbies might stumble across other problems when testing and give no reliable results (as seen before with 10th gen testing)

if its that important  to you than look into unpacking and repacking extra.lzma (its part of the driver tutorial and the steps are not that complex) and how to use a hex editor to path the i915 driver's device id's, just use the driver already in my extra.lzma

 

as already before 6.2.4/7.0 its important to select the hardware to use very careful when having special needs (like hardware transcoding), there is no "one fits all" build for xpenology that is maintained by anyone

Edited by IG-88
Link to comment
Share on other sites

On 1/23/2021 at 12:50 PM, IG-88 said:

 

no, i'm not using kvm/proxmox and dont test this and i have not seen a positive feedback of people loading the modules manually in integrated in the current releases of the extra.lzma

(you can open the extra.lzma with 7zip and extract the virtio modules to test them)

I am using proxmox with Intel X520-DA2 network card. It has 2 sfp+ (10Gb) on it.

If you pass through the card, it will word, just choose pci device.

I am using synology ds3617xs with jun 1.03b loader (no extra loaders).

 

It is working fine, just tested it today and the speed is 10Gbs.

 

Link to comment
Share on other sites

  • 2 weeks later...

Sorry to disturb you,

I use the i3-10100 + Colorful b460i + Intel i350t2 network card.

I can install Jun 1.04b+ for 6.23 for 918+,everything display normally,

However, by using SSH and enter "ls /dev/dri", display "No such file or directory",

There is no change in replacing "extra.lzma" and "extra2.lzma",

Replace i915's 9BC8 ds918-6.23up3, boot normal display, but can't find IP in the network

I've tried many times,but it still doesn't works.

How can I solve this problem?Thank you again, hope to reply.

Link to comment
Share on other sites

11 hours ago, XiaoyaoLinghao said:

However, by using SSH and enter "ls /dev/dri", display "No such file or directory",

There is no change in replacing "extra.lzma" and "extra2.lzma",

there is no i915 driver in extra/extra2 for 6.2.3 as this dsm version comes with its own renewed driver that has the same capability's as jun's driver we where using in 6.2.0-6.2.2 (-> 1st post about that)

 

11 hours ago, XiaoyaoLinghao said:

Replace i915's 9BC8 ds918-6.23up3, boot normal display, but can't find IP in the network

the change in behavior implies you changed the right file and now dsm loads the driver and try's to initialize the gpu and the fact that it does not show up in network implies the system freezed/crashed on boot, only thing you can do is delete the dsm system an reinstall or boot with a recoveryl linux, mount the 1st raid1 partitions of all disks and delete the non working i915 driver (you can later put back the original i915 file from the u3 *.pat file to get back the original state

your observation contradicts the observation from another user with that cpu (-> 1st post, "one user negative feedback for a i5-10500 (8086:9BC8) to get /dev/dri devices but no transcoding with emby" but same pci device of a 10600 worked for another user so it might have been a emby problem?)

 

if you delete the i915 with a recovery linux and your system is up again you can check /var/log/dmesg for the unsuccessful boot attempt(s), there should be a kernel panic related to i915.ko if that was the cause

without the dmesg log there is not much to guess, imho it should still boot as we do have positive feedback about that (twice),

you can try a testinstall with just 6.2.3 (without updates) and the replace the i915  with the older patched i915 that was made for the non updated 6.2.3

(i915 in "9BC8 - UHD 630 10th low end")

 

http://www.filedropper.com/918plusdsm623i915mod2

SHA256: 432F22AC7BD5111FCFC0586D9E173D843FA91E1235D843929BCEFCB635020B75

 

Link to comment
Share on other sites

I have tried to install the older version twice, but it's all the same, after I replace the file "i915.ko", I can't find the IP address on the network.

And I don't know how to replace the original file to my NAS which can not connect the network, so I failed to get my NAS running again.
Fortunately, I found the way to copy the file “/var/log/dmesg” from the the 1st hard disk, but I don't know how to use them.

Hope these two documents can help you find the problem, and may I ask you to point out the steps that I did wrong that led to the problem?

Thank you very much.

dmesg_1 dmesg_2

Link to comment
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.

×
×
  • Create New...