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


Recommended Posts

On 11/5/2019 at 4:39 AM, sunshine said:

 

Sorry for my stupid question. How use/handle I this driver extension file after download and unzip?

 

How to put it it on booting usb stick ? I use Synologolgy/Xpenology a longer time but I have no Idea how and where to add driver extension file.

 

 

 

I would recommend you use Linux live CD/USB drive to modify your DSM "image" partition.
There is high risk of bricking your device. You must understand what you are doing...

 

Steps:
1.Boot your device with Linux live media.(or SSH into your DSM)
2.Open a terminal and check your "image" partition id with the command "blkid".
3.Locate your boot and image partition,then use command "mount" to mount it.
4.(Optional) Backup whole DSM boot drive into image. "dd if=/dev/hda of=/root/synoboot.img"
5.Now you can copy your new driver extension file to the image partition.

2019-11-06_110035.png

Link to post
Share on other sites
15 hours ago, LanciWolf said:

4.(Optional) Backup whole DSM boot drive into image. "dd if=/dev/hda of=/root/synoboot.img"

 

i dont think its a good idea to put a backup on a computer that in case of a problem does not starting anymore

not that it would help much if you have a backup but i'd suggest using the same program as used in the tutorial, Win32DiskImager

https://sourceforge.net/projects/win32diskimager/files/latest/download

that 1.0 version also can detect the only a small part of the usb flashdrive is used and only backs up this part

 

for mounting the boot media directly on the running dsm i find the following method easier to handle

 

mkdir -p /mnt/synoboot1
mkdir -p /mnt/synoboot2

echo 1 > /proc/sys/kernel/syno_install_flag
mount /dev/synoboot1 /mnt/synoboot1
mount /dev/synoboot2 /mnt/synoboot2

and if there is a windows 10 computer near you can just stick the usb flashdrive into it and the 2nd partition (with the extra/extra2.lzma on it) will be there as a drive letter

 

i really don't recommend someone who even don't knows the basics to mess around with experimental stuff - i have not seen or received much feedback about the 1.04b extra.lzma, so i still see it as more or less untested

 

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

mlx4/mlx5 from the kernel is present, ixgbe (latest) for intel, also bnx2x, aquantia and tehuti

i had hardware for bnx2x and tehuti 10G for testing

so yes 10G is supposed to work but i haven't seen much feedback here

 

Edited by IG-88
Link to post
Share on other sites
1 hour ago, richv31 said:

follow the instructions to place the files on the USB flash drive - correct?

yes, but i'd suggest to do a 1st test with a fresh install to a single empty disk and check that all hardware is working with 6.2.2

 

Link to post
Share on other sites

does it make sense to use Driver extension if system is also running without extra.lzma ?

 

i my case 3615xs - 6.2.2 U3 is running fine with LSI 9211 HBA and Mellanox X2 dual port Nic

( HP z230cmt )

 

does the Driver extension have newer drivers with eg besser performance ?

 

mfg

 

 

Link to post
Share on other sites
36 minutes ago, norman said:

does it make sense to use Driver extension if system is also running without extra.lzma ?

in general i'd say no

 

36 minutes ago, norman said:

i my case 3615xs - 6.2.2 U3 is running fine with LSI 9211 HBA and Mellanox X2 dual port Nic

in the one i will release soon (i'm writing the text how to install and doculentation) both driver are from the kernel or from synology

had limited success on dsm 6.1 with newer mpt2sas/mpt3sas drivers and as my lsi sas controller does not work on my test hardware i dont want to add drivers that are likely to crash

maybe a can find a different old hardware later that does work with the sas controller

 

42 minutes ago, norman said:

does the Driver extension have newer drivers with eg besser performance ?

newer drivers for realtek, intel aquantia and tehuti, some people with performance problems on realtek cards might get better results but in general its more about getting newer hardware to work (newer chip revisions, different phy's)

but the 6.2.2 extra.lzma is atm mainly to support a wider base as 6.2.2 breaks the drivers that come in jun's extra.lzma so atm only people with hardware supported by dsm natively can rum 6.2.2

  • Like 1
Link to post
Share on other sites
2 hours ago, marcos_59143 said:

Hello, any news for ds3615xs ?

yes, discovered that lsi 9211 controller do not worked, only mpt2sas driver from dsm itself (6.2.2) does work atm (had to organize a new test computer to get the lsi 9211 with 3615/17 running), still looking whats the cause of the crash, driver loads when controller has no disks connected but crashes when disks are connected

also ata_piix, mptspi and mptsas driver do not work (mostly used for vmware and kvm i guess) , have removed them for now

but network drivers are mostly latest and working

Link to post
Share on other sites

I've tried the last set of extra/2.lzma and it works well for my DS918+ (6.2.2) on top of esxi 6.7. While it's running fine - I'm having issue with mptsas crashing on load when I enabled LSI SAS - is t his expected and similar to what is happening for the ds3615x ? Also I didn't find the mpt2sas in any of the extras bundle - I assume if the former is not working that won't help.

On a side note the atlantic driver also crashed when I tried passthrough of the xc card- not sure if it would work with SRIOV but it's not an option w/ esxi in my case anyway. The card works well with vmnet3 at 10gb under esxi so no biggy there ;)

Thanks!

-M

Edited by riftangel
Link to post
Share on other sites

1.03b loader - 3515xs 6.2.2

 

:: Loading module vmxnet3[    3.666370] BUG: unable to handle kernel paging request at 00000000ffffffff
[    3.667584] IP: [<ffffffffa0519232>] vmxnet3_probe_device+0xd2/0xa50 [vmxnet3]
[    3.668757] PGD 136866067 PUD 0
[    3.669328] Oops: 0000 [#1] SMP
[    3.669928] Modules linked in: vmxnet3(F+) pcnet32(F) e1000(F) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F) sky2(F) skge(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) libcrc32c ixgbe(O) igb(O) i2c_algo_bit e1000e(O) dca vxlan ip_tunnel vfat fat mdio sg etxhci_hcd mpt3sas(F) mpt2sas(O) megaraid_sas(F) mptctl(F) mptsas(F) mptspi(F) mptscsih(F) mptbase(F) scsi_transport_spi(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) vmw_pvscsi(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci ehci_hcd usbcore usb_common cepsw(OF) [last unloaded: bromolow_synobios]
[    3.679735] CPU: 0 PID: 4605 Comm: insmod Tainted: PF          O 3.10.105 #24922
[    3.680879] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015
[    3.682532] task: ffff880139c9d800 ti: ffff8801368d8000 task.ti: ffff8801368d8000
[    3.683688] RIP: 0010:[<ffffffffa0519232>]  [<ffffffffa0519232>] vmxnet3_probe_device+0xd2/0xa50 [vmxnet3]
[    3.685198] RSP: 0018:ffff8801368dbc50  EFLAGS: 00010206
[    3.686051] RAX: ffffffff8181fb40 RBX: 0000000000000002 RCX: 00000000ffffffff
[    3.687173] RDX: ffff88013677dc28 RSI: ffff88013677c000 RDI: ffff880139c13098
[    3.688284] RBP: ffff880139c13098 R08: 757120785220666f R09: 32203a2073657565
[    3.689407] R10: 757120785220666f R11: 32203a2073657565 R12: 0000000000000002
[    3.690566] R13: ffff880139c13000 R14: 0000000000000001 R15: ffff88013677c000
[    3.691688] FS:  00007f19b9378700(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000
[    3.692969] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[    3.693887] CR2: 00000000ffffffff CR3: 0000000136832000 CR4: 00000000001607f0
[    3.695023] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    3.696138] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    3.697243] Stack:
[    3.697597]  ffffffff8116c8d4 00000000ffffffff ffff880139c14898 ffff880139c13090
[    3.698833]  ffffffffa051d6a8 ffff880139c13000 ffffffffa051d640 0000000000000001
[    3.700104]  ffffffffa051d900 ffffffff8129f810 ffff880139c13090 ffffffffa051d6a8
[    3.701347] Call Trace:
[    3.701761]  [<ffffffff8116c8d4>] ? sysfs_do_create_link_sd+0xc4/0x1f0
[    3.702774]  [<ffffffff8129f810>] ? pci_device_probe+0x60/0xa0
[    3.703691]  [<ffffffff8130aace>] ? driver_probe_device+0x7e/0x3e0
[    3.704651]  [<ffffffff8130aeeb>] ? __driver_attach+0x7b/0x80
[    3.705562]  [<ffffffff8130ae70>] ? __device_attach+0x40/0x40
[    3.706474]  [<ffffffff81308b23>] ? bus_for_each_dev+0x53/0x90
[    3.707389]  [<ffffffff8130a148>] ? bus_add_driver+0x1c8/0x280
[    3.708297]  [<ffffffff8130b4d8>] ? driver_register+0x68/0x150
[    3.709205]  [<ffffffffa0520000>] ? 0xffffffffa051ffff
[    3.710104]  [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180
[    3.711060]  [<ffffffff8108b63c>] ? load_module+0x1d0c/0x2360
[    3.711977]  [<ffffffff8128feb0>] ? ddebug_proc_write+0xe0/0xe0
[    3.712920]  [<ffffffff8108bd24>] ? SYSC_init_module+0x94/0xf0
[    3.713870]  [<ffffffff814ccdc4>] ? system_call_fastpath+0x22/0x27
[    3.714852] Code: 0f 84 73 06 00 00 49 8b 85 c8 01 00 00 48 89 ef 48 85 c0 48 0f 44 05 8e d3 2f e1 48 8b 8f 00 01 00 00 48 85 c9 0f 84 66 05 00 00 <48> 83 39 00 0f 84 5c 05 00 00 4c 8b 10 4d 85 d2 0f 84 50 05 00
[    3.719290] RIP  [<ffffffffa0519232>] vmxnet3_probe_device+0xd2/0xa50 [vmxnet3]
[    3.720482]  RSP <ffff8801368dbc50>
[    3.721032] CR2: 00000000ffffffff
[    3.721588] ---[ end trace a3e87f015c929b01 ]---
 ... [FAILED]

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

1.03b loader - 3515xs 6.2.2

 

:: Loading module vmxnet3[    3.666370] BUG: unable to handle kernel paging request at 00000000ffffffff
[    3.667584] IP: [<ffffffffa0519232>] vmxnet3_probe_device+0xd2/0xa50 [vmxnet3]
[    3.668757] PGD 136866067 PUD 0
[    3.669328] Oops: 0000 [#1] SMP
[    3.669928] Modules linked in: vmxnet3(F+) pcnet32(F) e1000(F) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F)

 

if you still use jun's extra.lzma then thats kind to expect, after update you usb contains the 6.2.2 kernel and the extra.lzma for the old kernel 6.2.0

i'm looking for someone who can test my new drivers for the native vm-hardware vmxnet3, vmw_pvscsi on 6.2.2

atm mptspi, mptsas so lsi sas and lsi scsi from vmware will not work but hem native vm-hardware drivers should be able to replace them, that would be what you should test (added bonus that you can monitor serial to get console output)

Link to post
Share on other sites
11 hours ago, riftangel said:

mptsas crashing on load when I enabled LSI SAS

i did only test it on my new hardware so i could not test this

after receiving word that there is a problem with this on the 3615 extra.lzma i looked for a way to test this myself and found that i have the same virtual hardware as vmware in oracle virtual box (buslogic scsi, lsi scsi, lsi sas)

also foud out that the mpt2sas also does not work

11 hours ago, riftangel said:

? Also I didn't find the mpt2sas in any of the extras bundle -

on kernel 4.4.x (918+) there is only mpt3sas and it contains support for all mpt2 devices, i did test the 918+ with my lsi 9211 so it should work

 

11 hours ago, riftangel said:

On a side note the atlantic driver also crashed when I tried passthrough of the xc card- not sure if it would work with SRIOV

can't test this one, i plan to start from scratch with 918+ after doing 3615/17 so there will be a new version of the driver to test

 

 

Link to post
Share on other sites

i can test it if i only have to swap extra.lzma and debug via serial

 

3 hours ago, IG-88 said:

 

if you still use jun's extra.lzma then thats kind to expect, after update you usb contains the 6.2.2 kernel and the extra.lzma for the old kernel 6.2.0

i'm looking for someone who can test my new drivers for the native vm-hardware vmxnet3, vmw_pvscsi on 6.2.2

atm mptspi, mptsas so lsi sas and lsi scsi from vmware will not work but hem native vm-hardware drivers should be able to replace them, that would be what you should test (added bonus that you can monitor serial to get console output)

 

Link to post
Share on other sites
53 minutes ago, norman said:

i can test it if i only have to swap extra.lzma and debug via serial

ok i send you a link

ata_piix, mptspi, mptsas are not in that package

lsi scsi, lsi sas will not work and you have to change to vmw_pvscsi or buslogic (i tested buslogic driver with virtulabox)

 

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.