IG-88

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

Recommended Posts

15 hours ago, sarieri said:

Should this method help resolving the no SMART info issue of mpt3sas in extra.lzma v0.1 for dsm6.23?

it DOES, if someone is impatient he can create his own extra/extra2 until i upload 0.11 (later this evening)

 

6 hours ago, staratlas said:

Today, I tried this method, SMART info are fixed and were appeared in dsm, Thank you !

you will get the new mpt3sas.ko with 0.11

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
13 hours ago, ewgennt said:

A regular non-multiplex controller (Espada PCIe4SATA3ASM) is inserted into the PCI-E 2.0 slot of the motherboard. But the system sees only 4 disks, 2 connected to the motherboard and 2 connected to the controller. If you connect one disk to the controller in turn in each slot, then it is visible in the system

 

the board say's SU-SA3004 and if i look that one up at amazone i find that it is a ASM1061 + 1093 Chipset

ASM1061 is a 2 port controller and 1093 is a port muliplier, so its exactly what your results imply, you will only see the ports of the asm1061

https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=166&item=118

https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=138&item=141

 

 

  • Thanks 1

Share this post


Link to post
Share on other sites

I know this is a 1.04b thread,  but I have 1.03b/3615 system that after the update to 6.2.3 and reverting to Jun's  original 1.03b extra.lzma will no longer hibernate its drives or turn off (WOL is enabled). This was working fine with 6.2.2 and the v0.5_test drivers. Any chance to release an up-to-date driver set for 6.2.3? Thx

 

Share this post


Link to post
Share on other sites
6 hours ago, IG-88 said:

you will get the new mpt3sas.ko with 0.11

 

Thank you for your reply and uploading 0.11, and I tested your 0.11 on my xpenology, SMART info is OK.
 

Test enveronment:
VM on ESXi 6.7, LSI(Avago) HBA SAS3008 (9300-8I) (paththrough), 2 x VMXNET 3

dmesg about mpt3sas:

[    1.711502] mpt3sas version 27.00.01.00 loaded
[    1.713052] mpt3sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8169472 kB)
[    1.789491] mpt3sas_cm0: IOC Number : 0
[    1.789494] mpt3sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
[ .... ]
[    2.106582] mpt3sas_cm0: port enable: SUCCESS

 

Share this post


Link to post
Share on other sites
7 hours ago, IG-88 said:

it DOES, if someone is impatient he can create his own extra/extra2 until i upload 0.11 (later this evening)

 

you will get the new mpt3sas.ko with 0.11

Tried v0.11. SMART info is now correct. Thank You!

Share this post


Link to post
Share on other sites

extra918plus_v0.11 working like a charm. Smart info looking nice!

 Next step:  cpufreq_ondemand.ko 😅  I'll play ASAP.

 

Thanks indeed.  You are great.

Share this post


Link to post
Share on other sites
20 hours ago, richv31 said:

. Any chance to release an up-to-date driver set for 6.2.3? Thx

yes, in the next days

Share this post


Link to post
Share on other sites
5 hours ago, Eduardo said:

Next step:  cpufreq_ondemand.ko 😅  I'll play ASAP.

 

what are your plans on how to use it?

synology loads cpufreq* modules by itself but how are you intent to use the new module?

Share this post


Link to post
Share on other sites
Posted (edited)

HI,

I'm trying to get H/W transcoding up and running, but without success.

Configuration: Baremetal Supermicro X11SSZ-TLN4F + Intel Xeon E3-1245 v5, DSM 6.2.3-25423, Jun's Loader v1.04b.

I have tried both extra.lzma/extra2.lzma v0.10 and v0.11 and zImage and rd.gz from "DSM_DS918+_25423.pat, with same outcome:

1. /dev/dri - missing

2. Codecs activated manually "synocodectool --activate_codec hevc_dec --pkgname videostation"

3. activation.conf - available "more /usr/syno/etc/codec/activation.conf" --->> {"success":true,"activated_codec":["vc1_dec","vc1_enc","h264_dec","h264_enc","mp
                                                                                                                                               eg4part2_dec","hevc_dec","ac3_dec","aac_dec","aac_enc"],"token":................................}

4. Cleared the update lib.: /usr/lib/modules/update/

 

Any advice for me!?

 

Edited by cosmindnl

Share this post


Link to post
Share on other sites
Posted (edited)

 

43 minutes ago, cosmindnl said:

Any advice for me!?

try loader 1.04b with jun's original extra/extra2 and dsm 6.2(.0)

https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS918+_23739.pat

and see if you get /dev/dri (as long as you don't have it you might not try to activate any codecs, without /dev/dri hardware transcoding is not working)

Edited by IG-88

Share this post


Link to post
Share on other sites
6 hours ago, IG-88 said:

 

what are your plans on how to use it?

synology loads cpufreq* modules by itself but how are you intent to use the new module?

 

Actually I don't think wee could achive an automatic frequency scaling. Only powersave performance userspace here.
There are some scripts over there to adjust frequency when in userspace. I used one of them some time ago. But couldn't we get a new ondemand governor with  cpufreq_ondemand.ko?

Share this post


Link to post
Share on other sites

hello, you are planning to release Driver extension jun 1.03b for DSM6.2.3 for 3615xs / 3617xs?

Share this post


Link to post
Share on other sites
10 hours ago, IG-88 said:

 

try loader 1.04b with jun's original extra/extra2 and dsm 6.2(.0)

https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS918+_23739.pat

and see if you get /dev/dri (as long as you don't have it you might not try to activate any codecs, without /dev/dri hardware transcoding is not working)

I’m afraid of downgrade because I use NvME SSD cache an most probably I will lose it. 
I will do a test setup in few days 

Share this post


Link to post
Share on other sites
9 hours ago, dmtg said:

hello, you are planning to release Driver extension jun 1.03b for DSM6.2.3 for 3615xs / 3617xs?

to lazy to read just 5 posts above?

 

there is not that much need as the original driver from jun are working again, just some people with newer hardware and some 10G nic's will really need this

beside, there where no additional drivers for 6.2.2 for about one year ...

 

Share this post


Link to post
Share on other sites
2 hours ago, cosmindnl said:

I’m afraid of downgrade because I use NvME SSD cache an most probably I will lose it. 
I will do a test setup in few days 

it was meant for a test, using a new usb and a empty disk

you did not say anything about your update path and it was working an a lower DSM version number

Share this post


Link to post
Share on other sites
56 minutes ago, IG-88 said:

it was meant for a test, using a new usb and a empty disk

you did not say anything about your update path and it was working an a lower DSM version number

I'm new to Xpenology, I did fresh install with 6.2.2 and immediately upgraded to 6.2.3 and from hear fun starts for me.

Upgrade from 6.2.2 to 6.2.3 was flawless, works with no issues and after that I have added NvME cache.   

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, cosmindnl said:

I'm new to Xpenology, I did fresh install with 6.2.2 and immediately upgraded to 6.2.3

 

so if you cant say if /dev/dri was there with 6.2.2 (same driver from jun as for 6.2.0) you cant be sure if its possible to work at all with your cpu

difference to 6.2.3 is that it uses synology's new own i915 driver that is a few month older from the source then jun's bur your xenon device ID

0x191D - Xeon E3-1245v5

is in synologys i915 driver, so it should show up with 6.2.3

anything in the log (dmesg), what does lspci show?

Edited by IG-88

Share this post


Link to post
Share on other sites
Posted (edited)
12 minutes ago, IG-88 said:

 

so if you cant say if /dev/dri was there with 6.2.2 (same driver from jun as for 6.2.0) you cant be sure if its possible to work at all with your cpu

difference to 6.2.3 is that it uses synology's new own i915 driver that is a few month older from the source then jun's bur your xenon device ID

0x191D - Xeon E3-1245v5

is in synologys i915 driver, so it should show up with 6.2.3

anything in the log (dmesg), what does lspci show?

I have did the test installation using .pat sent by you and original jun's boot loader 1.04b, no luck.

 

root@nas:~# ls /dev/dri
ls: cannot access /dev/dri: No such file or directory

 

What commands should I use to get "dmesg" 
 

Edited by cosmindnl

Share this post


Link to post
Share on other sites
19 minutes ago, cosmindnl said:

What commands should I use to get "dmesg" 

its a file in /var/log but you can also type it as a command in the console (you can try to find things in a search engine like google)

 

Share this post


Link to post
Share on other sites

i looked a little into the differences in devices supported by synology's and jun's i915 driver and there seems only to be differences in never produced ice lake gpu's planed in 2018 (gpu gen 10/11)

gpu's from i3 9100 is still the same device id as for i3 8100 (gpu gen 9.5, up to coffee lake and gemini lake)

anything new that comes out in a few weeks/month is presumably not supported by the driver so if hardware transcoding is to be used nothing newer then a 9th gen cpu is to use (new 10th gen desktop cpu's announced lately might not work with synology's driver)

 

this can be used to have a look about cpu gen's and gpu gen's from intel

https://en.wikichip.org/wiki/intel/microarchitectures

Share this post


Link to post
Share on other sites
Posted (edited)

This is dmesg log

Spoiler

Fri May  1 06:09:39 2020] Initializing cgroup subsys cpuset
[Fri May  1 06:09:39 2020] Initializing cgroup subsys cpu
[Fri May  1 06:09:39 2020] Initializing cgroup subsys cpuacct
[Fri May  1 06:09:39 2020] Linux version 4.4.59+ (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #23739 SMP PREEMPT Tue Jul 3 19:51:03 CST 2018
[Fri May  1 06:09:39 2020] Command line: syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1 root=/dev/md0 sn=********** mac1=*********** netif_num=1 vid=0x0781 pid=0x5583
[Fri May  1 06:09:39 2020] KERNEL supported cpus:
[Fri May  1 06:09:39 2020]   Intel GenuineIntel
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[3]:  960, xstate_sizes[3]:   64
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[4]: 1024, xstate_sizes[4]:   64
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR'
[Fri May  1 06:09:39 2020] x86/fpu: Enabled xstate features 0x1f, context size is 1088 bytes, using 'standard' format.
[Fri May  1 06:09:39 2020] x86/fpu: Using 'eager' FPU context switches.
[Fri May  1 06:09:39 2020] e820: BIOS-provided physical RAM map:
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000000100-0x0000000000057fff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000100000-0x000000008827ffff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000088280000-0x0000000088280fff] ACPI NVS
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000088281000-0x00000000882cafff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x00000000882cb000-0x000000008e982fff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000008e983000-0x000000008ed10fff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000008ed11000-0x000000008f1a9fff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000008f1aa000-0x000000008f530fff] ACPI NVS
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000008f531000-0x000000008fffefff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000008ffff000-0x000000008fffffff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000090000000-0x0000000097ffffff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000100000000-0x0000000465bfffff] usable
[Fri May  1 06:09:39 2020] NX (Execute Disable) protection: active
[Fri May  1 06:09:39 2020] e820: update [mem 0x00100000-0x0010000f] usable ==> usable
[Fri May  1 06:09:39 2020] extended physical RAM map:
[Fri May  1 06:09:39 2020] reserve setup_data: [mem 0x0000000000000100-0x0000000000057fff] usable
[Fri May  1 06:09:39 2020] reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved

 

UPDATE after restart

iFri May  1 06:09:39 2020] Initializing cgroup subsys cpuset
[Fri May  1 06:09:39 2020] Initializing cgroup subsys cpu
[Fri May  1 06:09:39 2020] Initializing cgroup subsys cpuacct
[Fri May  1 06:09:39 2020] Linux version 4.4.59+ (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #23739 SMP PREEMPT Tue Jul 3 19:51:03 CST 2018
[Fri May  1 06:09:39 2020] Command line: syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1 root=/dev/md0 sn=****** mac1=***** netif_num=1 vid=0x0781 pid=0x5583
[Fri May  1 06:09:39 2020] KERNEL supported cpus:
[Fri May  1 06:09:39 2020]   Intel GenuineIntel
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[3]:  960, xstate_sizes[3]:   64
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[4]: 1024, xstate_sizes[4]:   64
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR'
[Fri May  1 06:09:39 2020] x86/fpu: Enabled xstate features 0x1f, context size is 1088 bytes, using 'standard' format.
[Fri May  1 06:09:39 2020] x86/fpu: Using 'eager' FPU context switches.
[Fri May  1 06:09:39 2020] e820: BIOS-provided physical RAM map:
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000000100-0x0000000000057fff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[y  1 06:09:39 2020] Initializing cgroup subsys cpuset
[Fri May  1 06:09:39 2020] Initializing cgroup subsys cpu
[Fri May  1 06:09:39 2020] Initializing cgroup subsys cpuacct
[Fri May  1 06:09:39 2020] Linux version 4.4.59+ (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #23739 SMP PREEMPT Tue Jul 3 19:51:03 CST 2018
[Fri May  1 06:09:39 2020] Command line: syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1 root=/dev/md0 sn=******* mac1=******* netif_num=1 vid=0x0781 pid=0x5583
[Fri May  1 06:09:39 2020] KERNEL supported cpus:
[Fri May  1 06:09:39 2020]   Intel GenuineIntel
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[3]:  960, xstate_sizes[3]:   64
[Fri May  1 06:09:39 2020] x86/fpu: xstate_offset[4]: 1024, xstate_sizes[4]:   64
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds registers'
[Fri May  1 06:09:39 2020] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR'
[Fri May  1 06:09:39 2020] x86/fpu: Enabled xstate features 0x1f, context size is 1088 bytes, using 'standard' format.
[Fri May  1 06:09:39 2020] x86/fpu: Using 'eager' FPU context switches.
[Fri May  1 06:09:39 2020] e820: BIOS-provided physical RAM map:
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000000100-0x0000000000057fff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[Fri May  1 06:09:39 2020] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
"dmesg" 3710L, 299317C                                                                   

 


 

Edited by cosmindnl

Share this post


Link to post
Share on other sites

just a warning, looks like synology retracted 6.2.3, i updated the 1st post

 

 

Share this post


Link to post
Share on other sites
8 minutes ago, IG-88 said:

this is the version of the kernel source used so you are running dsm 6.2(.0) not 6.2.3 and the dmesg log should be much longer, containing messages about drivers

have a look at this example

https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=142160

 

I’m running now test setup with 6.2.0 sent by you

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.