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


Recommended Posts

21 minutes ago, Eeso said:

Would you mind help me and try to compile 918+ with that flag set?

 

we cant use a different kernel the loader circumvents synology's protections so dsm as its running still "believes" its on a original hardware, dsm won't run off a different kernel so we are bound to use the kernel as it comes and make the drivers around that - to state in bluntly, xpenology is a hacked dsm and the easiest way seems to be to emulate features of the original hardware and navigate around one or the other thing

that was different in the past (dsm 5.x?) but at least since 6.x we cant have a kernel as we like, main reason why there is no amd or hyper-v support, its not in the kernel and you can't add support afterwards by loading modules

33 minutes ago, Eeso said:

CONFIG_X86_X2APIC seems to be valid for 4.4 as well

sure but its not in the .config synology published

Link to post
Share on other sites
1 minute ago, IG-88 said:

 

we cant use a different kernel the loader circumvents synology's protections so dsm as its running still "believes" its on a original hardware, dsm won't run off a different kernel so we are bound to use the kernel as it comes and make the drivers around that - to state in bluntly, xpenology is a hacked dsm and the easiest way seems to be to emulate features of the original hardware and navigate around one or the other thing

that was different in the past (dsm 5.x?) but at least since 6.x we cant have a kernel as we like, main reason why there is no amd or hyper-v support, its not in the kernel and you can't add support afterwards by loading modules

 

sure but its not in the .config synology published

Aha okey, such a shame

 

I guess I have to get 3617 running then, do you know if any grub debug can be enabled as it tries to unpack and load the kernel and initrd?

 

What is it the with the different zImage I changed on my usb then? If it can't be/no point in being changed I mean, it's a bit confusing

 

 

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

I guess I have to get 3617 running then, do you know if any grub debug can be enabled as it tries to unpack and load the kernel and initrd?

 

on my system the reason was that i booted uefi (csm present) and after changing to the "old" non uefi boot device it worked (there where 3 usb boot devices present)

i'd guess if you have the csm optin enabled you should see different types of the same usb device

if you just see a unicode 2592 character on your serial console then its the same problem as mine, uefi instead of bios/csm used and nothing wrong with the loader

i dont know why loader 1.03b does only support bios/csm mode (and i dont care tbh i have enough to do with the driver, as long as it works for me and i can test the stuff i'm creating  i will not dig deeper into it)

 

Quote

What is it the with the different zImage I changed on my usb then? If it can't be/no point in being changed I mean, it's a bit confusing

 

you copied the dsm original file from the *.pat file, that file would also be copied to usb when installing dsm update trough the web gui (the original synology systems have a internal usb module that hold the loader in the same way as we use the usb flash drive)

 

Edited by IG-88
Link to post
Share on other sites
5 minutes ago, IG-88 said:

 

on my system the reason was that i booted uefi (csm present) and after changing to the "old" non uefi boot device it worked (there where 3 usb boot devices present)

i'd guess if you have the csm optin enabled you should see different types og the same usb device

if you just see a unicode 2592 character on your serial console then its the same problem as mine, uefi instead of bios/csm used and nothing wrong with the loader

i dont know why loader 1.03b does only support bios/csm mode (and i dont care tbh i have enough to do with the driver, as long as it works for me and i can test the stuff i'm creatig  i will not dig deeper into it)

Okey actually you were right, it boots now, seems to have been when I changed from UEFI to legacy also.. Didn't test 3617 until now on that configuration

I thought it wasn't the problem when all the others were working, I'm assuming too much, I can see it is a great deal of hacking for it to run

Well that is good, I will try to load the drivers now :) 

 

5 minutes ago, IG-88 said:

you copied the dsm original file from the *.pat file, that file would also be copied to usb when installing dsm update trough the web gui (the original synology systems have a internal usb module that hold the loader in the same way as we use the usb flash drive)

Ah alright :)

Link to post
Share on other sites
7 часов назад, IG-88 сказал:

 

on my system the reason was that i booted uefi...

 

 

Eh .. can I hope for an IDE drive driver in the pack? I have a good motherboard from HP with Xeon processor (ML110 Gen 5) :) I do not want to throw it away :)  It can't AHCI :(

 

WBR, Man

Link to post
Share on other sites

Great work @IG-88!!

Thanks to you I now have my HP ProLiant MicroServer Gen8 with DSM 6.2.2-24922 Update 4. Both built-in NICs are recognized and functional.
I have done a fresh installation, simply replacing your files ('extra.lzma' -v0.5_test-, 'rd.gz' and 'zImage') on the 2nd partition (30MB) of Jun's Loader v1.03b (DS3615xs).

But I have a problem that I can't solve and I need help:
I have the PCI card DVBSky S952 v2. I have already compiled all the necessary modules that it needs. All load well except one, the last one that needs to be loaded: cx23885.ko
When executing the 'insmod cx23885.ko' command, it keeps thinking for a while and a few seconds later returns this message: Killed.

As I have seen here, to find out where it fails I have used the following command: dmesg
And here is the problem:

[ 5019.869526] cx23885 driver version 0.0.3 loaded
[ 5019.869551] ------------[ cut here ]------------
[ 5019.869558] WARNING: at include/linux/kref.h:52 kobject_get+0x42/0x60()
[ 5019.869559] Modules linked in: cx23885(OF+) dvbsky_m88ds3103(OF) snd_pcm snd_timer snd soundcore snd_page_alloc rc_core(OF) cx2341x(OF) v4l2_common(OF) videodev(OF) videobuf_dma_sg(OF) btcx_risc(OF) tveeprom(OF) videobuf_dvb(OF) videobuf_core(OF) tda18271(OF) altera_ci(OF) dvb_core(OF) bridge stp aufs macvlan veth xt_conntrack xt_addrtype nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables cifs udf isofs loop tcm_loop(O) iscsi_target_mod(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) hid_generic
[ 5019.869587]  usbhid hid usblp bromolow_synobios(PO) xgmac(F) s2io(F) rtl8150(F) r8152(OF) plusb(F) pegasus(F) mcs7830(F) i40evf(OF) et131x(FC) cx82310_eth(F) asix(F) aqc111(OF) vxge(F) bna(F) cxgb4(F) cxgb3(F) cxgb(F) forcedeth(F) ixgb(F) e100(F) atl2(F) evdev(F) button(F) ax88179_178a(F) usbnet(F) tg3(OF) r8169(OF) r8125(OF) r8101(OF) ixgbevf(OF) igbvf(OF) bnx2(F) 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) jme(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(F) libcrc32c(F) mdio(F) mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(OF) r8168(OF) tn40xx(OF) i40e(OF) ixgbe(OF) be2net(F) igb(OF) i2c_algo_bit
[ 5019.869622]  e1000e(OF) dca(F) vxlan fuse vfat fat crc32c_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t(F) crc_ccitt(F) quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd nvme(F) hpsa(F) isci(F) arcmsr(F) mvsas(F) mvumi(F) 3w_xxxx(F) 3w_sas(F) 3w_9xxx(F) aic94xx(F) aacraid(F) sx8(F) mpt2sas(OF) megaraid_sas(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci(F) ehci_hcd(F) usbcore usb_common cepsw(OF) [last unloaded: dvbsky_m88ds3103]
[ 5019.869658] CPU: 0 PID: 24251 Comm: insmod Tainted: PF        C O 3.10.105 #24922
[ 5019.869660] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
[ 5019.869661]  ffffffff814c5a5d ffffffff810355c6 ffff8800c5362008 ffff880105846098
[ 5019.869664]  ffff880105846000 ffffffffa13f9040 ffff8800c5362008 ffffffff81275b42
[ 5019.869666]  ffff8801058460a8 ffffffff8130655e ffffffffa0af13d5 ffff880105846090
[ 5019.869668] Call Trace:
[ 5019.869674]  [<ffffffff814c5a5d>] ? dump_stack+0xc/0x15
[ 5019.869677]  [<ffffffff810355c6>] ? warn_slowpath_common+0x56/0x70
[ 5019.869680]  [<ffffffff81275b42>] ? kobject_get+0x42/0x60
[ 5019.869684]  [<ffffffff8130655e>] ? get_device+0xe/0x20
[ 5019.869689]  [<ffffffffa0af13d5>] ? v4l2_device_register+0x55/0xf0 [videodev]
[ 5019.869696]  [<ffffffffa13dfe9a>] ? cx23885_initdev+0x4a/0x1170 [cx23885]
[ 5019.869700]  [<ffffffff8116c8d4>] ? sysfs_do_create_link_sd+0xc4/0x1f0
[ 5019.869703]  [<ffffffff8129f810>] ? pci_device_probe+0x60/0xa0
[ 5019.869706]  [<ffffffff8130aace>] ? driver_probe_device+0x7e/0x3e0
[ 5019.869709]  [<ffffffff8130aeeb>] ? __driver_attach+0x7b/0x80
[ 5019.869712]  [<ffffffff8130ae70>] ? __device_attach+0x40/0x40
[ 5019.869714]  [<ffffffff81308b23>] ? bus_for_each_dev+0x53/0x90
[ 5019.869717]  [<ffffffff8130a148>] ? bus_add_driver+0x1c8/0x280
[ 5019.869719]  [<ffffffff8130b4d8>] ? driver_register+0x68/0x150
[ 5019.869726]  [<ffffffffa13ff000>] ? 0xffffffffa13fefff
[ 5019.869728]  [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180
[ 5019.869733]  [<ffffffff8108b63c>] ? load_module+0x1d0c/0x2360
[ 5019.869737]  [<ffffffff8128feb0>] ? ddebug_proc_write+0xe0/0xe0
[ 5019.869741]  [<ffffffff810f9663>] ? vfs_read+0xf3/0x160
[ 5019.869744]  [<ffffffff8108bdf5>] ? SYSC_finit_module+0x75/0xa0
[ 5019.869748]  [<ffffffff814ccdc4>] ? system_call_fastpath+0x22/0x27
[ 5019.869749] ---[ end trace 9ed748a2788c3ee3 ]---
[ 5019.869756] BUG: unable to handle kernel NULL pointer dereference at           (null)
[ 5019.907575] IP: [<ffffffffa0af1403>] v4l2_device_register+0x83/0xf0 [videodev]
[ 5019.942743] PGD c512e067 PUD e09c8067 PMD 0
[ 5019.963145] Oops: 0000 [#1] SMP
[ 5019.978571] Modules linked in: cx23885(OF+) dvbsky_m88ds3103(OF) snd_pcm snd_timer snd soundcore snd_page_alloc rc_core(OF) cx2341x(OF) v4l2_common(OF) videodev(OF) videobuf_dma_sg(OF) btcx_risc(OF) tveeprom(OF) videobuf_dvb(OF) videobuf_core(OF) tda18271(OF) altera_ci(OF) dvb_core(OF) bridge stp aufs macvlan veth xt_conntrack xt_addrtype nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables cifs udf isofs loop tcm_loop(O) iscsi_target_mod(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) hid_generic
[ 5020.327357]  usbhid hid usblp bromolow_synobios(PO) xgmac(F) s2io(F) rtl8150(F) r8152(OF) plusb(F) pegasus(F) mcs7830(F) i40evf(OF) et131x(FC) cx82310_eth(F) asix(F) aqc111(OF) vxge(F) bna(F) cxgb4(F) cxgb3(F) cxgb(F) forcedeth(F) ixgb(F) e100(F) atl2(F) evdev(F) button(F) ax88179_178a(F) usbnet(F) tg3(OF) r8169(OF) r8125(OF) r8101(OF) ixgbevf(OF) igbvf(OF) bnx2(F) 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) jme(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(F) libcrc32c(F) mdio(F) mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(OF) r8168(OF) tn40xx(OF) i40e(OF) ixgbe(OF) be2net(F) igb(OF) i2c_algo_bit
[ 5020.665151]  e1000e(OF) dca(F) vxlan fuse vfat fat crc32c_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t(F) crc_ccitt(F) quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd nvme(F) hpsa(F) isci(F) arcmsr(F) mvsas(F) mvumi(F) 3w_xxxx(F) 3w_sas(F) 3w_9xxx(F) aic94xx(F) aacraid(F) sx8(F) mpt2sas(OF) megaraid_sas(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci(F) ehci_hcd(F) usbcore usb_common cepsw(OF) [last unloaded: dvbsky_m88ds3103]
[ 5020.997978] CPU: 0 PID: 24251 Comm: insmod Tainted: PF       WC O 3.10.105 #24922
[ 5021.033652] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
[ 5021.068338] task: ffff88010598c040 ti: ffff8800e09bc000 task.ti: ffff8800e09bc000
[ 5021.104807] RIP: 0010:[<ffffffffa0af1403>]  [<ffffffffa0af1403>] v4l2_device_register+0x83/0xf0 [videodev]
[ 5021.152597] RSP: 0018:ffff8800e09bfc38  EFLAGS: 00010286
[ 5021.177959] RAX: 0000000000000000 RBX: ffff8800c5362008 RCX: 0000000000000006
[ 5021.213901] RDX: ffffffffa0afba5f RSI: 0000000000000024 RDI: ffff8800c5362022
[ 5021.247987] RBP: ffff880105846098 R08: ffffffff8183a600 R09: 000000000000fffe
[ 5021.283746] R10: 0000000000000000 R11: 0000000000000459 R12: ffff880105846000
[ 5021.317977] R13: ffffffffa13f9040 R14: ffff8800c5362008 R15: ffffffffa13fa200
[ 5021.352947] FS:  00007ff7520eb700(0000) GS:ffff88010ba00000(0000) knlGS:0000000000000000
[ 5021.392514] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5021.419841] CR2: 0000000000000000 CR3: 00000000c464e000 CR4: 00000000001607f0
[ 5021.454973] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 5021.489549] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 5021.524634] Stack:
[ 5021.534184]  ffff880105846090 ffff8800c5362000 ffffffffa13dfe9a ffffffff8116c8d4
[ 5021.570823]  00000000ffffffff ffff880105846098 ffff880105846090 ffffffffa13f90a8
[ 5021.606562]  ffff880105846000 ffffffffa13f9040 0000000000000001 ffffffffa13fa200
[ 5021.643598] Call Trace:
[ 5021.655086]  [<ffffffffa13dfe9a>] ? cx23885_initdev+0x4a/0x1170 [cx23885]
[ 5021.687897]  [<ffffffff8116c8d4>] ? sysfs_do_create_link_sd+0xc4/0x1f0
[ 5021.719379]  [<ffffffff8129f810>] ? pci_device_probe+0x60/0xa0
[ 5021.747877]  [<ffffffff8130aace>] ? driver_probe_device+0x7e/0x3e0
[ 5021.777623]  [<ffffffff8130aeeb>] ? __driver_attach+0x7b/0x80
[ 5021.806853]  [<ffffffff8130ae70>] ? __device_attach+0x40/0x40
[ 5021.834135]  [<ffffffff81308b23>] ? bus_for_each_dev+0x53/0x90
[ 5021.862621]  [<ffffffff8130a148>] ? bus_add_driver+0x1c8/0x280
[ 5021.890428]  [<ffffffff8130b4d8>] ? driver_register+0x68/0x150
[ 5021.919177]  [<ffffffffa13ff000>] ? 0xffffffffa13fefff
[ 5021.944175]  [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180
[ 5021.971963]  [<ffffffff8108b63c>] ? load_module+0x1d0c/0x2360
[ 5021.999276]  [<ffffffff8128feb0>] ? ddebug_proc_write+0xe0/0xe0
[ 5022.027551]  [<ffffffff810f9663>] ? vfs_read+0xf3/0x160
[ 5022.053584]  [<ffffffff8108bdf5>] ? SYSC_finit_module+0x75/0xa0
[ 5022.082162]  [<ffffffff814ccdc4>] ? system_call_fastpath+0x22/0x27
[ 5022.112424] Code: 48 89 2b 74 53 80 7b 1a 00 75 2a 4c 8b 45 50 4d 85 c0 74 64 48 8b 85 90 00 00 00 48 8d 7b 1a 48 c7 c2 5f ba af a0 be 24 00 00 00 <48> 8b 08 31 c0 e8 33 bb 78 e0 48 89 ef e8 eb 8e 81 e0 48 85 c0
[ 5022.204806] RIP  [<ffffffffa0af1403>] v4l2_device_register+0x83/0xf0 [videodev]
[ 5022.239300]  RSP <ffff8800e09bfc38>
[ 5022.255682] CR2: 0000000000000000
[ 5022.271686] ---[ end trace 9ed748a2788c3ee4 ]---
[ 5022.293644] [sched_delayed] sched: RT throttling activated


But I don't know how to interpret all this code. If you could help me I would appreciate it very much ☺️

I THINK (but I don't know) the problem is because it conflicts with any of the new 6.2.2 drivers. Because in DSM 6.1 with Jun's Loader v1.02b (DS3615xs) everything works fine and I have no problems loading this module.
I have searched and read some similar case in this forum and I think I have understood the same thing that I say, that there is a conflicting driver and if I delete it my module will work fine. For example in this thread you mention it: https://xpenology.com/forum/topic/24220-shutdownreboot-not-working/?do=findComment&comment=130036

The problem is that I have no idea what the conflicting module will be, to be able to erase it.

In case it helps you, I attach a compressed file with all the necessary modules (and firmware) already compiled for DSM 6.2.X
The correct order to load them is (remember that the problematic module is only the last one, but to load it depends on all the previous ones):

insmod videobuf-core.ko
insmod videobuf-dma-sg.ko
insmod rc-core.ko
insmod dvb-core.ko
insmod altera-ci.ko
insmod videodev.ko
insmod v4l2-common.ko
insmod cx2341x.ko
insmod /lib/modules/soundcore.ko
insmod /lib/modules/snd.ko
insmod /lib/modules/snd-page-alloc.ko
insmod /lib/modules/snd-timer.ko
insmod /lib/modules/snd-pcm.ko
insmod tveeprom.ko
insmod videobuf-dvb.ko
insmod btcx-risc.ko
insmod tda18271.ko
insmod dvbsky_m88ds3103.ko
insmod cx23885.ko


Thank you very much for your fantastic work!
Regards!

DVBSky-S952-v2_DSM-v6.2-bromolow.tar.gz

  • Like 1
Link to post
Share on other sites
9 hours ago, man67 said:

Eh .. can I hope for an IDE drive driver in the pack? I have a good motherboard from HP with Xeon processor (ML110 Gen 5) :) I do not want to throw it away :)  It can't AHCI

 

the chipset intel 3200 is paired with ich9 so its capable of ahci

if if does not work because of the bios is missing options to switch you can still use dsm 6.1 or older when needed or add a ahci or mpt2 (6Gbit) sas controller both are pretty cheap

atm i've given up on additional storage drivers as the kernel source available seems not to work with the kernel of dsm 6.2.2 we have to use

if someone can present code/path or a better kernel i will try to do something, i have one or two ideas what i can test but that has a very low possibility of working and would consume more time then i'm able to invest

also its like with the 100mbit nic's, very few people need it and you can use something to mitigate like a adding a card for a few bugs

 

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

But I have a problem that I can't solve and I need help:
I have the PCI card DVBSky S952 v2. I have already compiled all the necessary modules that it needs. All load well except one, the last one that needs to be loaded: cx23885.ko

 

dvb drivers are not part of my package

please open a new thread for this kind of problem

 

you should ask the person who made this modules (presumably for dsm 6.2.0) if he is willing to redo the drivers for 6.2.2

i've already documented the change thats needs to be done when compiling new drivers for 6.2.2

https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/?do=findComment&comment=122631

 

  • Thanks 1
Link to post
Share on other sites
On 10/6/2019 at 9:07 PM, IG-88 said:

This is the first (experiential?) test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2

packages for 1.03b and 3615/3617 are coming (need to get an "older" hardware tor testing, my new B360M/G5400 test system did seem to freeze when loading the kernel with 1.03b, even no serial console output after starting loading the kernel)

 

Tested as fresh install with 1.04b loader with DSM 6.2.2, there are extra.lzma and extra2.lzma in the zip file - you need both - the "extra2" file is used when booting the 1st time and under normal working conditions the extra.lzma is used  (i guess also normal updates - jun left no notes about that so i had to find out and guess).

Hardware in my test system used additional driver: r8168, igb, e1000e, bnx2x, tn40xx, mpt2sas

The rest of the drivers just load without any comment on my system, i've seen drivers crashing only when real hardware is present so be warned

 

extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.2 v0.6_test

http://s000.tinyupload.com/?file_id=29784352988385987676

 

!!! still network limit in 1.04b loader for 918+ !!!

atm 918+ has a limit of 2 nic's (as the original hardware)
If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation
You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8  and keep in mind when doing a major update it will  be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0)
I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17)

 

I will extend here to what is in the old thread for 6.2 had but atm i'm more willing to add 3615/17 support

Basically what is on the old page is valid, so no sata_*, pata_* drivers

Here are the drivers in the test version listed as kernel modules:

  drivers included (Reveal hidden contents)

network:

alx

aqc111 - new, Aquantia 111U 1/2.5/5G USB nic
asix
atl1
atl1c
atl1e
atl2
atlantic - latest !!!
ax88179_178a
be2net
bna
bnx2
bnx2x
cx82310_eth
cxgb
cxgb3
cxgb4
dl2k
e100
e1000
e1000e - latest
enic
forcedeth
igb - latest driver crashed
ixgbe - latest
jme
mcs7830
mii
mlx_compat
mlx4_core
mlx4_en
mlx5_core
mvmdio
netxen_nic
pcnet32
pegasus
plusb
qla3xxx
qlcnic
qlge
r8168 - latest driver crashed, still jun's
r8169
rtl8150
sc92031
sfc
skge
sky2
tg3
tn40xx - latest !!! (also support for MV phys)
vmxnet3
vxlan


storage:

3w-9xxx
3w-sas
aacraid
aic94xx
arcmsr
BusLogic
gdth
hpsa
hptiop
ips
isci
megaraid
megaraid_mbox
megaraid_mm
megaraid_sas
mpt2sas
mpt3sas
mptsas
mvsas
mvumi
sx8
vmw_pvscsi

 

The old thread as reference

!!! especially read "Other things good to know about DS918+ image and loader 1.03a2:" its still valid for 1.04b loader !!!

 

 

 

This section is about drivers for ds3615xs and ds3617xs image/dsm version 6.2.2 (v24922)
Both use the same kernel (3.10.105) but have different kernel options so don't swap or mix, some drivers might work on the other system some don't at all (kernel oops)

 

Its a test version and it has limits in case of storage support, read careful and only use it when you know how to recover/downgrade your system
!!! do not use this to update when you have a different storage controller then AHCI, LSI MPT SAS 6Gb/s Host Adapters SAS2004/SAS2008/SAS2108/SAS2116/SAS2208/SAS2308/SSS6200 (mpt2sas) or LSI MPT SAS 12Gb/s Host Adapters SAS3004/SAS3008/SAS3108 (mpt3sas - only in 3617), instead you can try a fresh "test" install with a different usb flash drive and a empty single disk on the controller in question to confirm if its working (most likely it will not, reason below) !!!

 

The reason why 1.03b loader from usb does not work when updating from 6.2.0 to 6.2.2 is that the kernel from 6.2.2 has different options set witch make the drivers from before that change useless (its not a protection or anything), the dsm updating process extracts the new files for the update to HDD, writes the new kernel to the usb flash drive and then reboots - resulting (on USB) in a new kernel and a extra.lzma (jun's original from loader 1.03b for dsm 6.2.0) that contains now incompatible drivers, the only drivers working reliable in that state are the drivers that come with dsm from synology

 

Beside the different kernel option there is another thing, nearly none of the new compiled scsi und sas drivers worked
They only load as long as no drive is connected to the controller. ATM I assume there was some changes in the kernel source about counting/indexing the drives for scsi/sas, as we only have the 2.5 years old dsm 6 beta kernel source there is hardly a way to compensate

 

People with 12GBit SAS controllers from LSI/Avago are in luck, the 6.2.2 of 3617 comes with a much newer driver mpt3sas then 6.2.0 and 6.2.1 (13.00 -> 21.00), confirmed install with a SAS3008 based controller (ds3617 loader)

 

Driver not in this release: ata_piix, mptspi (aka lsi scsi), mptsas (aka lsi sas) - these are drivers for extremely old hardware and mainly important for vmware users, also the vmw_pvscsi is confirmed not to work, bad for vmware/esxi too
Only alternative as scsi diver is the buslogic, the "normal" choice for vmware/ESXi would be SATA/AHCI
I removed all drivers confirmed to not work from rc.modules so they will not be loaded but the *.ko files are still in the extra.lzma and will be copied to /usr/modules/update/ so if some people want to test they can load the driver manually after booting
These drivers will be loaded and are not tested yet (likely to fail when a disk is connected)
megaraid, megaraid_sas, sx8, aacraid, aic94xx, 3w-9xxx, 3w-sas, 3w-xxxx, mvumi, mvsas, arcmsr, isci, hpsa, hptio
(for some explanation of what hardware this means look into to old thread for loader 1.02b)

 

virtio driver: i added virtio drivers, they will not load automatically (for now), the drivers can be tested and when confirmed working we will try if there are any problems when they are loaded by default along with the other drivers
they should be in /usr/modules/update/ after install

 

To get a working loader for 6.2.2 it needs the new kernel (zImage and rd.gz) and a (new) extra.lzma containing new drivers (*.ko files)

zImage and rd.gz will be copied to usb when updating DSM or can be manually extracted from the 6.2.2 DSM *.pat file and copied to usb manually
and that's the point where to split up between cases/way's

case 1: update from 6.2.0 to 6.2.2
case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1


Case 1: update from 6.2.0 to 6.2.2
Basically you semi brick your system on purpose by installing 6.2.2 and when booting fails you just copy the new extra.lzma to your usb flash drive by plugging it to a windows system (witch can only mount the 2nd partition that contains the extra.lzma) or you mount the 2nd partition of the usb on a linux system
Restart and then it will finish the update process and when internet is available it will (without asking) install the latest update (at the moment update4) and reboot, so check your webinterface of DSM to see whats going or if in doubt wait 15-20 minutes check if the hdd led's are active and check the webinterface or with synology assistant, if there is no activity for that long then power off and start the system, it should work now

 

Case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1
Pretty much the normal way as described in the tutorial for installing 6.x (juns loader, osfmount, Win32DiskImager) but in addition to copy the extra.lzma to the 2nd partition of the usb flash drive you need to copy the new kernel of dsm 6.2.2 too so that kernel (booted from usb) and extra.lzma "match"
You can extract the 2 files (zImage and rd.gz) from the DSM *.pat file you download from synology
https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat
or
https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat
These are basically zip files so you can extract the two files in question with 7zip (or other programs)
You replace the files on the 2nd partition with the new ones and that's it, install as in the tutorial
In case of a "migration" the dsm installer will detect your former dsm installation and offer you to upgrade (migrate) the installation, usually you will loose plugins, but keep user/shares and network settings

 


DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test
http://s000.tinyupload.com/?file_id=87576629927396429210

 

DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test

http://s000.tinyupload.com/?file_id=80273327432412263889

 

FUNCIONA . . . . acabo de actualizar un HP Proliant gen8 a DSM6.2.2.29422 update4 copiando en la microSD los zImage y rd.gz del DSM_DS3617xs_24922.pat y el extra.Izma v0.5 . . . .

Link to post
Share on other sites
21 minutes ago, S__M said:

Hi! Is there a driver for the 3ware 9650SE in the package?

 

you might try it for 3615 or 3617 as a fresh install for a test but as stated in the lower 3615/17 section i treat all scsi/sas storage drivers as broken without testing them with a controller and a disk on the controller present - don't try it on a running system you have data on

Link to post
Share on other sites
7 minutes ago, luisrp said:

FUNCIONA . . . . acabo de actualizar un HP Proliant gen8 a DSM6.2.2.29422 update4 copiando en la microSD los zImage y rd.gz del DSM_DS3617xs_24922.pat y el extra.Izma v0.5 . . . .

 

i don't want to be rude but we converse in english here so please translate it and also you dont have to quote all of the 1st post, makes it really hard to read as you have to scroll all the way down, if you want to quote the keep it as short as possible or you can user the spoiler function (looks like a eye in the toolbar) to hide the text and anyone wanting to see it can click an it to open it

Link to post
Share on other sites

After 6 months I finally made an account on this forum.
My Intel C600 with DSM 6.2.2. Both built-in NICs are not recognized . simply replacing your files ('extra.lzma' -v0.5_test-, 'rd.gz' and 'zImage') on the 2nd partition (30MB) of Jun's Loader v1.03b (DS3615xs) but nothing shows up on the screen but booting is successful. I was using other person pre-packed bootloader  with your extra.lzma I can't find that link now so if you can help that will be huge help because I am stuck sort of bootloop please I Don't want to loose my data I knew this is test but latest security update bugs me alot Thanks a ton

nic :- Intel e1000e

storage:- isci

 

Link to post
Share on other sites
10 часов назад, IG-88 сказал:

 

the chipset intel 3200 is paired with ich9 so its capable of ahci

if if does not work because of the bios is missing options to switch you can still use dsm 6.1 or older when needed or add a ahci or mpt2 (6Gbit) sas controller both are pretty cheap

atm i've given up on additional storage drivers as the kernel source available seems not to work with the kernel of dsm 6.2.2 we have to use

if someone can present code/path or a better kernel i will try to do something, i have one or two ideas what i can test but that has a very low possibility of working and would consume more time then i'm able to invest

also its like with the 100mbit nic's, very few people need it and you can use something to mitigate like a adding a card for a few bugs

 

Unfortunately, HP was too lazy to implement AHСI on ML-110 gen 5 :( SATA IDE/RAID only. On the motherboard, only the PСI-E v1 x1 connectors ... A controller with 6 ports will work poorly. It's only 250 MB/s :(   = 40 MB/s per channel. But HDD 120-150 MB/s per one.

On the other side, network only 100-120 MB/s per chanel ...  For one or two connection it's maybe ok..

Maybe I'm wrong .. I'm overload :) 

Link to post
Share on other sites
7 hours ago, psychoboi32 said:

but nothing shows up on the screen

 

it never does after the message that states that

 

Quote

but booting is successful.

 

how do you know?

 

7 hours ago, psychoboi32 said:

stuck sort of bootloop

 

thats something different then t booting successful

when you cant see it in network then the best method would be a serial port on the nas and a null-modem cable to another computer, after the screen stops to give messages the output is send to the serial port so that way you could see what happens and if the system would boot successful you would see a login prompt and you would be able to login with you admin account to check the logs or do other things

 

i dont think it is the network driver, it's well tested, the isci storage driver is more likely a problem, the section about the storage driver is red and bold - what should i do more than that - if you know its isci then you should have been warned

 

or maybe you did use the wrong extra.lzma or your loader is not what it needs to be

read your usb loader with "Win32DiskImager 1.0" (activate "read only allocated partitions") into a image file, upload it somewhere and send me the link

 

7 hours ago, psychoboi32 said:

I Don't want to loose my data

 

at the moment you system does not boot all your data are still in the separate raid partitions of your disks

to recover the most likely successful way would be a downgrade

https://xpenology.com/forum/topic/12778-tutorial-how-to-downgrade-from-62-to-61-recovering-a-bricked-system/

 

isci is not a driver jun provides in his loader, so you former loader already had added drivers,  for a successful recovery you need to decide what loader and dsm version you want to use and then you need a extra.lzma for this to get you controller recognized

i would start by disconnection the "old" disks, make a new usb drive (keep the old one until its clear it will not be needed anymore), add a extra.lzma containing your drivers, have one empty disk on the isci controller and boot up, you should see it iin network and it should offer you to install to the disk (when just using jun's loder without extra drivers you would not see the disk)

 

a possible alternative is to install open media vault to a sepeate media (old disks not connected) and when its working boot up omv with the old disks connected too, usually omv can detect the raid of the data partitons (it did for my system when i tested it) - synology uses just the "normal" linux ways to create/run raids

 

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

What would be the easiest way to convert my system running 6.2.2 update 4 without an extra.lzma to use the extra.lzma.  I am running a Gigabyte GAp970a-ds3p board with a FX4300 and an add-on HP NC-360T nic using the 1.03b DS3615xs loader.  I would like to get the internal realtek nic working again using the extra.lzma.  Would I just shut my machine down put the usb stick in a windows machine and copy over the extra.lzma and the kernel files to the second partition?  Are there any risks associated with it as I have data on this machine.  It's not a huge deal to get the internal nic working as I already have a 2x1Gb LACP lag setup.

Edited by thadrumr
Link to post
Share on other sites
Quote

how do you know?

 

Means I tried before and it is like kernel panic and just reboot this time it doesn't reboot . one more thing Kernel is not decompressing this time

Quote

thats something different then t booting successful

when you cant see it in network then the best method would be a serial port on the nas and a null-modem cable to another computer, after the screen stops to give messages the output is send to the serial port so that way you could see what happens and if the system would boot successful you would see a login prompt and you would be able to login with you admin account to check the logs or do other things

 

i dont think it is the network driver, it's well tested, the isci storage driver is more likely a problem, the section about the storage driver is red and bold - what should i do more than that - if you know its isci then you should have been warned

 

or maybe you did use the wrong extra.lzma or your loader is not what it needs to be

read your usb loader with "Win32DiskImager 1.0" (activate "read only allocated partitions") into a image file, upload it somewhere and send me the link

 

I have serial port built in I will see how can I use it for recovery

 

Quote

isci is not a driver jun provides in his loader, so you former loader already had added drivers,  for a successful recovery you need to decide what loader and dsm version you want to use and then you need a extra.lzma for this to get you controller recognized

i would start by disconnection the "old" disks, make a new usb drive (keep the old one until its clear it will not be needed anymore), add a extra.lzma containing your drivers, have one empty disk on the isci controller and boot up, you should see it iin network and it should offer you to install to the disk (when just using jun's loder without extra drivers you would not see the disk)

 

I know isci not provided by jun that's why I was stick to old version of DSM btw I was using this  Bootloader  by @sbv3000. It just works

 

After so much trying here and there like I face 2 major issue
1. DSM found and ask me for migrate if I say yes and use latest version of .pat it gives me error 67% 'error 12 or 13 file is corrupt' even online

2. It successfully migrated and never shown up on network trying to ping it (I already bind my Mac address to router for static IP)

 

Quote

a possible alternative is to install open media vault to a sepeate media (old disks not connected) and when its working boot up omv with the old disks connected too, usually omv can detect the raid of the data partitons (it did for my system when i tested it) - synology uses just the "normal" linux ways to create/run raids

 

First I try downgrade method if that not worked I think this method is my last hope

 

Quote

i dont think it is the network driver, it's well tested, the isci storage driver is more likely a problem, the section about the storage driver is red and bold - what should i do more than that - if you know its isci then you should have been warned

I knew all that warning but I thought Let me jump to ship if It worked I will get latest security patches If not I have to loose data ( in my mind I agree ) but now I feel my pain because It is my centralized storage solution and now I can't transfer files between my hackintosh and my windows

Thanks for helping me I really tried to made my own extra.lzma but kernel sources are too old and when I tried latest DSM on VM it said Linux 4.0. So I give up on that. Thank you for making Extra.lzma hope I can help in any way.

Link to post
Share on other sites
7 hours ago, psychoboi32 said:

 

After so much trying here and there like I face 2 major issue
1. DSM found and ask me for migrate if I say yes and use latest version of .pat it gives me error 67% 'error 12 or 13 file is corrupt' even online

2. It successfully migrated and never shown up on network trying to ping it (I already bind my Mac address to router for static IP)

 


For 1., make sure that the VID and PID values on the USB stick in the grub.cfg file are correct. Normally “file is corrupt” message is related to those values not being correct. 
 

For 2., how did it successfully migrate if you got the file is corrupt message?

Edited by Decebalus
Link to post
Share on other sites
12 hours ago, thadrumr said:

 Would I just shut my machine down put the usb stick in a windows machine and copy over the extra.lzma and the kernel files to the second partition?

 

yes, the loader would recognize the new drivers and copy the new drivers to your disk to /lib/modules/update

 

12 hours ago, thadrumr said:

 Are there any risks associated with it as I have data on this machine.  It's not a huge deal to get the internal nic working as I already have a 2x1Gb LACP lag setup.

 

you can test the new driver and do it manally to minimize the risk by extracting the driver with 7zip from extra.lzma (r8168.ko) copy it to your system (like a network share) and check if it loads

with "rmmode r8168" to remove the old driver in case its loaded

and then load the new driver (with path and filename)  "insmod /volume1/data/r8168.ko

if that works without error you can check the log with "dmesg"

if it looks ok you copy the new driver to /lib/modules/update and reboot

i guess the loader should not overwrite the new file but there is no risk, if not the new driver will load and you will have a new nic, in worst case the loader overwrites it with the old one and everything is as it was before (you can check after boot, the new file has a different date)

 

 

 

 

 

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

 

yes, the loader would recognize the new drivers and copy the new drivers to your disk to /lib/modules/update

 

 

you can test the new driver and do it manally to minimize the risk by extracting the driver with 7zip from extra.lzma (r8168.ko) copy it to your system (like a network share) and check if it loads

with "rmmode r8168" to remove the old driver in case its loaded

and then load the new driver (with path and filename)  "insmod /volume1/data/r8168.ko

if that works without error you can check the log with "dmesg"

if it looks ok you copy the new driver to /lib/modules/update and reboot

i guess the loader should not overwrite the new file but there is no risk, if not the new driver will load and you will have a new nic, in worst case the loader overwrites it with the old one and everything is as it was before (you can check after boot, the new file has a different date)

 

 

 

 

 

The loader is overwriting the file on a reboot.  It successfully loads if I do it manually but doesn't show up as an available interface.  When I copy the file to /lib/modules/update the date shows as todays date but after a reboot it shows as aug 1st.  I guess I need to copy the file to the usb stick.

 

[  208.596009] r8168 Gigabit Ethernet driver 8.047.04-NAPI loaded
[  208.596009] r8168 0000:03:00.0: irq 75 for MSI/MSI-X
[  208.602006] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
[  208.603017] r8168  Copyright (C) 2019  Realtek NIC software team <nicfae@realtek.com>
                This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>.
                This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.

 

I got the interface to come up by doing the following just need to figure out how to make it permanent over a reboot.

modprobe -v r8168

ifconfig eth2 up

 

Edited by thadrumr
Link to post
Share on other sites
Quote

For 1., make sure that the VID and PID values on the USB stick in the grub.cfg file are correct. Normally “file is corrupt” message is related to those values not being correct. 

 

I am sure That is correct but I will upload If you have any doubts

 

Quote

For 2., how did it successfully migrate if you got the file is corrupt message?

 

I try again and again with some grub 1.03 sometimes 1.02 you know when you hit and try and onetime I got success but after nothing happen.

 

So I tried Unbrick guide (Downgrade guide)

 

1 . I tried re-install to spare drive add drive when server is running (nothing prompt), reboot back to recovery and 'you have to install latest version'

 

2. At same forum @sbv3000 said update to beta (idk?) but I update to 6.1.3 from 6.1 then poweroff, attach your drives and it will recover but I am running around circle same migration and you can't downgrade, you have to use latest version. format again my spare drive (FAT32) and my flash drive but same issue, 

 

17 hours ago, IG-88 said:

a possible alternative is to install open media vault to a sepeate media (old disks not connected) and when its working boot up omv with the old disks connected too, usually omv can detect the raid of the data partitons (it did for my system when i tested it) - synology uses just the "normal" linux ways to create/run raids

 

My drive in SHR. I have different HDD sizes I was familiar with OMV so this is my last option hope It worked and I can extract some important data.

usb.png

grub.cfg

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

I got the interface to come up by doing the following just need to figure out how to make it permanent over a reboot.

modprobe -v r8168

ifconfig eth2 up

 

if you are cautious to the extreme you can disconnect your disks (or the power of the disk), copy the new extra.lzma to your usb device (if you have e empty disk at hand connect it) and boot if it comes up in network then there is no obvious problem and when you had a disk connected you can see if the system is ready for install (because it found the disk) you don't need to install anything just a check that the controller(driver) and disk on it works, if that checks out you ran reconnect all your disks and start the system, it will copy the nee drivers to your disk and your realtek network should be up and running

(there is not much what would block a 3615/17 from booting, that's mainly a domain of the 918+ loader because of the i915 driver used for hardware transcoding)

 

Link to post
Share on other sites
22 часа назад, IG-88 сказал:

the specs from hp say something else

2 and 3 are pcie 1x slots - ok for 1Gbit nic

4 is a pcie 8x slot - a good one for storage and i guess thats the reason it is there

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c01271448

 

 

 

"Oh my god" :) This is age and eyes :)  Ok, this is the way. I will look for a SATA controller with 6 channels ... As I understand it, in AHCI mode, any one will be picked up by the drivers in 6.2? Or are there any restrictions? 

WBR, Man

 

UPD: I find a x4 card with using the ASM1062 chip and 2xASM1093 chips - it's fine for drivers? or look for something more serious?

Edited by man67
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.