Jump to content
XPEnology Community

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


Recommended Posts

hi i have searched and found this in ethtool.eth2.result

 

Settings for eth2:
    Supported ports: [ TP ]
    Supported link modes:   100baseT/Full
                            1000baseT/Full
                            10000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Advertised link modes:  100baseT/Full
                            1000baseT/Full
                            10000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Speed: Unknown!
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: external
    Auto-negotiation: on
    MDI-X: Unknown
    Supports Wake-on: g
    Wake-on: d
    Link detected: no

 

and this in ethtool_info.eth2.result

 

driver: atlantic
version: 2.0.10.0
firmware-version: 3.1.30
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

 

if you want more info let me know which files

 

thanks eric

 

Link to comment
Share on other sites

6 minutes ago, xp_1409 said:

and this in ethtool_info.eth2.result

 

driver: atlantic
version: 2.0.10.0
firmware-version: 3.1.30
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

 

so it is recognized, but there is a problem getting it to work properly

 

6 minutes ago, xp_1409 said:

if you want more info let me know which files

 

as said dmesg, either call it in a shell or copy the file /var/log/dmesg

 

btw the driver synology provides in 3615/17 only is 2.0.5.0 so its even older

i did try a newer a while ago but got feedback it did not work and until now no one had problems with 2.0.10

i could see if i can make a new from more recent source but i would need feedback from you when testing it

Link to comment
Share on other sites

Il y a 18 heures, Pandadoo a dit :

Hello everybody,

 

Any luck to have storage driver for HP Smart Array P222 ?

Ooops i found a thread where Polanskiman says : Hardware Raid cards are not handled by DSM.

 

So I don't understand why on HP Gen8 Microserver DSM is working with onboard HP B120i raid chipset but not with additionnal card HP P222..?

 

I'm missing something but i can't touch it...

Link to comment
Share on other sites

Le 21/05/2020 à 00:26, IG-88 a dit :

yes, and slight correction, the (new) i915 driver is a "native" driver from synology originally made for geminilake units like the new DS x20+

the 0.11 extra/extra2 makes sure jun's i915 (not compatible with 6.2.3) gets deleted so the native driver from synology is loaded

Big thx ! @IG-88 , update successful https://xpenology.com/forum/topic/29401-dsm-623-25426/page/5/?tab=comments#comment-148499

 

Link to comment
Share on other sites

On 5/30/2020 at 6:09 PM, xp_1409 said:

i have attached the dsemg.file

 

thanks eric

 

1st thing, the atlantic driver is not loaded in dmesg, looks like i forgot to add it in rc.modules

edit: checked rc.modules in the extra/extra2 and its there, must be something else

i will send you a link to a new version that will load it the way it is intended and it will be a driver from latest source

 

2nd thing - you need to modify your synoinfo.conf to get more then two nic's working, the build in default for 918+ is two

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

 !!! 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) and here

https://xpenology.com/forum/topic/12679-progress-of-62-loader/?do=findComment&comment=92682

 

 

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

3 hours ago, Pandadoo said:

HP B120i raid chipset

thats not really a raid chipset, afir it just intels onboard sata chipset with a HPE name

the SA Pxxx series is different, has different chips on it (more dedicated to raid, like true hardware raid), needs a special driver (hpsa.ko) and depending of the controller it can be switched to hba/it mode to have single disks that can be used for synology's software raid

3 hours ago, Pandadoo said:

onboard HP B120i raid chipset but not with additionnal card HP P222..

ahci driver vs. hpsa.ko driver and there are no tools in dsm to manage any hardware raid, dsm is build around mdadm software raid

maybe a JMB585 based 5port sata controller is a good alternative? it supports pcie 3.0 and can deliver up to ~2000MB/s with its two pcie 3.0 lanes

Link to comment
Share on other sites

1 hour ago, Pandadoo said:

My only left choice is a vm via ESXi.

 

there is more. you can get a cheap reflashed oem version of a lsi 9211-8i or a P420 (or newer) they do support IT/HBA mode

(it has sas connector as P222 and there are also at least two sata 8port controllers with these connectors but both are limited to 1000MB/s as of pcie 2.0 and two lanes)

 

there are also less favorable (dangerous)  options like creating a raid0 set with every single disk and combine these "disks" in dsm to a raid or creating a raid5/6 in the controller over all disks and get this big disk as one "basic" disk in dsm

in both cases you dont have temp. or smart info's in dsm and it might be harder to see what disk failed in case of a disk error (but should be seen in controller bios or when booting a hpe iso from usb for maintenance)

 

you can look into the section where people flag there update success about different dsm versions and find lots of hpe gen8 microserver and some might have something about additional hardware in the comments - but why not using the internal ports? imho all should  be able to deliver a good performance

Link to comment
Share on other sites

@IG-88: Thank you so much.

Pressed "update" yesterday evening (some kind of fool...)

Thanks to your work my NAS is back up and running this morning.

 

Running DSM 6.2.3-25426 on a HP Microserver Gen8 (G1610T, 2GB, 4*4 TB HDD) bare metal without additional hardware.

😃👍

 

Edited by wengi
Link to comment
Share on other sites

39 minutes ago, wengi said:

Running DSM 6.2.3-25426 on a HP Microserver Gen8 (G1610T, 2GB, 4*4 TB HDD) bare metal without additional hardware.

as you dont have any too special hardware jun's original extra.lzma from the loader 1.03b would also have done the job (can be extracted with 7zip and just needs to copied to the 2nd partition of the usb in use)

  • Like 1
Link to comment
Share on other sites

1 hour ago, IG-88 said:

as you dont have any too special hardware jun's original extra.lzma from the loader 1.03b would also have done the job (can be extracted with 7zip and just needs to copied to the 2nd partition of the usb in use)

 

@IG-88 Only extra.lzma?

But what about extra2.lzma?

original? 0.10? 0.11?

 

Thanks

Link to comment
Share on other sites

13 minutes ago, _ReaL_ said:

Only extra.lzma?

But what about extra2.lzma?

 

that only on 1.04b for 918+, your gen8 can only handle 2n and 3rd gen intel cpu's, to old for 918+

 

Quote

original? 0.10? 0.11?

the one that is already in the loader as it comes from jun, the extra.lzma contains the driver (beside other stuff) and jun already delivers a good amount of drivers by default

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

Il y a 7 heures, IG-88 a dit :

 

there is more. you can get a cheap reflashed oem version of a lsi 9211-8i or a P420 (or newer) they do support IT/HBA mode

(it has sas connector as P222 and there are also at least two sata 8port controllers with these connectors but both are limited to 1000MB/s as of pcie 2.0 and two lanes)

 

Thanks a lot for that information, i just ordered a LSI 9211-8i already in IT mode by the seller. 1000MB/s will be fine

 

Il y a 7 heures, IG-88 a dit :

 

but why not using the internal ports? imho all should  be able to deliver a good performance

 

Because the mini-sas connector has bad contacts, if i touch the cable, 2 hdd are recognized, if a touch again, one more, i touch again, none.. lol..

I saw prices for motherbard replacment, they are totally out of reality..

Link to comment
Share on other sites

2 minutes ago, Pandadoo said:

hanks a lot for that information, i just ordered a LSI 9211-8i already in IT mode by the seller. 1000MB/s will be fine

the lsi sas will have full speed for all ports, the 1000MB/s would have been the 8port sata/ahci controller with 2 x miniSAS onboard, the same as with the lsi sas controller

sata/ahci can a advantage as it does not need any additional drivers, the ahci support in dsm is kernel build in it will always work (on 3615/17 the lsi sas driver is part of dsm aka native driver but on 918+ its not)

as you are unable to use 918+ on that hardware the lsi sas is a safe choice, 3615 might phase off but 3617 will still get updates for years and afair it will also be a system getting dsm 7.0

Link to comment
Share on other sites

I updated my 918+ to DSM 6.2.3-25426 using 1.04b with 0.11 extra.lzma and extra2.lzma.

 

I have some problems when turning off and sometimes after turning it on it takes a long time to be operational.

 

I am having problems with the USB DVB tuner. I get these messages in dmesg:

Quote

 


[222361.579556] DiB0070 I2C read failed
[222361.579952] DiB0070 I2C write failed
[222362.743529] DiB0070 I2C read failed
[222362.743944] DiB0070 I2C write failed
[222363.905522] DiB0070 I2C read failed
[222363.905936] DiB0070 I2C write failed
[222365.070512] DiB0070 I2C read failed
[222365.070906] DiB0070 I2C write failed
[222366.234481] DiB0070 I2C read failed
[222366.234879] DiB0070 I2C write failed
[222367.400468] DiB0070 I2C read failed
[222367.400875] DiB0070 I2C write failed
[222368.564469] DiB0070 I2C read failed
[222368.564893] DiB0070 I2C write failed
[222369.728488] DiB0070 I2C read failed
[222369.728905] DiB0070 I2C write failed
[222370.893504] DiB0070 I2C read failed
[222370.893933] DiB0070 I2C write failed
[222372.054385] DiB0070 I2C read failed
[222372.054748] DiB0070 I2C write failed
[222373.217445] DiB0070 I2C read failed
[222373.217863] DiB0070 I2C write failed
[222374.381420] DiB0070 I2C read failed
[222374.381833] DiB0070 I2C write failed
[222375.544391] DiB0070 I2C read failed
[222375.544783] DiB0070 I2C write failed
[222376.707425] DiB0070 I2C read failed
[222376.707842] DiB0070 I2C write failed
[222377.871337] DiB0070 I2C read failed
[222377.871765] DiB0070 I2C write failed
[222379.034412] DiB0070 I2C read failed
[222379.034806] DiB0070 I2C write failed
[222380.197379] DiB0070 I2C read failed
[222380.197797] DiB0070 I2C write failed
[222381.361375] DiB0070 I2C read failed
[222381.361772] DiB0070 I2C write failed
[222382.532370] DiB0070 I2C read failed
[222382.532785] DiB0070 I2C write failed
[222383.696362] DiB0070 I2C read failed
[222383.696779] DiB0070 I2C write failed
[222384.859352] DiB0070 I2C read failed
[222384.859749] DiB0070 I2C write failed
[222386.023360] DiB0070 I2C read failed
[222386.023764] DiB0070 I2C write failed
[222387.187288] DiB0070 I2C read failed
[222387.187712] DiB0070 I2C write failed
[222388.350349] DiB0070 I2C read failed
[222388.350752] DiB0070 I2C write failed
[222389.514292] DiB0070 I2C read failed
[222389.514722] DiB0070 I2C write failed
[222390.678320] DiB0070 I2C read failed
[222390.678717] DiB0070 I2C write failed
[222391.842275] DiB0070 I2C read failed
[222391.842688] DiB0070 I2C write failed
[222393.007271] DiB0070 I2C read failed
[222393.007681] DiB0070 I2C write failed
[222393.015224] divide error: 0000 [#1] PREEMPT SMP
[222393.015656] Modules linked in: mt2060 s5h1411 lgdt3305 mt2266 tuner_xc2028 xc5000 mxl5007t dib8000 xc4000 dvb_usb_dib0700 dib7000p dib3000mc dib0070 dib0090 dvb_usb rc_core dib9000 dvb_core dib7000m dibx000_common kvm irqbypass vhost_scsi(O) vhost(O) xt_ipvs ip_vs_rr ip_vs xt_mark iptable_mangle br_netfilter bridge stp aufs macvlan veth xt_conntrack xt_addrtype nf_conntrack_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat iptable_nat nf_nat_ipv4 nf_nat_redirect nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables x_tables tun 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)
[222393.022330]  syno_extent_pool(PO) rodsp_ep(O) hid_generic usbhid hid usblp uhci_hcd ehci_pci ehci_hcd openvswitch gre nf_defrag_ipv6 nf_conntrack apollolake_synobios(PO) aqc111(OE) et131x(E) vxge(E) s2io(E) r8152(OE) via_velocity(E) via_rhine(E) sc92031(E) rtl8150(E) plusb(E) pegasus(E) mvmdio(E) mcs7830(E) enic(E) e100(E) dl2k(E) cxgb4(E) cxgb3(E) cxgb(E) cx82310_eth(E) bna(E) atl2(E) asix(E) evdev(E) ax88179_178a(E) tg3(E) r8101(OE) bnx2(E) vmxnet3(E) pcnet32(E) e1000(E) sfc(E) netxen_nic(E) qlge(E) qlcnic(E) qla3xxx(E) sky2(E) skge(E) jme(E) uio(E) alx(E) atl1c(E) atl1e(E) atl1(E) r8169(OE) usbnet(E) libphy(E) mii(E) exfat(O) btrfs i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight
[222393.028992]  button(E) synoacl_vfs(PO) hfsplus md4 hmac bnx2x(E) mlx5_core(E) mlx4_en(E) mlx4_core(E) mlx_compat(OE) atlantic(OE) r8168(OE) tn40xx(OE) i40e(E) ixgbe(OE) be2net(E) igb(OE) i2c_algo_bit e1000e(OE) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t(E) crc_ccitt(E) quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd sx8(E) aic94xx(E) mvumi(E) mvsas(E) isci(E) hptiop(E) hpsa(E) gdth(E) arcmsr(E) aacraid(E) 3w_sas(E) 3w_9xxx(E) rtc_cmos(E) mdio(E) mpt3sas(E) mptsas(E) megaraid_sas(E) megaraid(E) mptctl(E)
[222393.035680]  mptspi(E) mptscsih(E) mptbase(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) raid_class(E) libsas(E) scsi_transport_sas(E) scsi_transport_spi(E) usb_storage xhci_pci xhci_hcd ohci_hcd(E) usbcore usb_common cos(OE) [last unloaded: xc4000]
[222393.037727] CPU: 3 PID: 31551 Comm: kdvb-ad-0-fe-0 Tainted: P           OE   4.4.59+ #25426
[222393.038416] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H270M-ITX/ac, BIOS P2.50 03/16/2018
[222393.039224] task: ffff8802400a5180 ti: ffff880248968000 task.ti: ffff880248968000
[222393.039843] RIP: 0010:[<ffffffffa16dc20d>]  [<ffffffffa16dc20d>] dib7000p_set_frontend+0x8cd/0x1060 [dib7000p]
[222393.040679] RSP: 0018:ffff88024896b9e0  EFLAGS: 00010246
[222393.041125] RAX: 0000000004000000 RBX: ffff88006ea84000 RCX: 0000000010624dd3
[222393.041717] RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88006ea85aa0
[222393.042308] RBP: ffff88024896ba38 R08: 0000000000000000 R09: 0000000000000000
[222393.042900] R10: ffff88006ea85a88 R11: 0000000000000001 R12: ffff88006ea84000
[222393.043492] R13: 000000002bfcfc80 R14: 0000000000000000 R15: ffff88006ea84000
[222393.044083] FS:  0000000000000000(0000) GS:ffff88026ed80000(0000) knlGS:0000000000000000
[222393.044751] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[222393.045231] CR2: 00007fb131fd7000 CR3: 000000025af72000 CR4: 00000000003606f0
[222393.045823] Stack:
[222393.046004]  ffff88024896ba40 ffffffffa0016979 0000000000000000 0000000000000000
[222393.046672]  0000000000000000 2bfcfc804896ba00 ffff8802524b9800 0000000000000002
[222393.047339]  000000002bfcfc80 ffff88006ea84340 ffff88006ea84000 ffff88024896bc40
[222393.048007] Call Trace:
[222393.048227]  [<ffffffffa0016979>] ? usb_start_wait_urb+0x99/0xe0 [usbcore]
[222393.048799]  [<ffffffffa165d70c>] dvb_frontend_swzigzag_autotune+0xec/0x2f0 [dvb_core]
[222393.049454]  [<ffffffffa165e3df>] dvb_frontend_swzigzag+0x2cf/0x380 [dvb_core]
[222393.050053]  [<ffffffff81085579>] ? cpuacct_charge+0x49/0x50
[222393.050527]  [<ffffffff81074658>] ? update_curr+0x88/0xd0
[222393.050979]  [<ffffffff81077f7a>] ? dequeue_task_fair+0x5ea/0x10f0
[222393.051494]  [<ffffffff8107a685>] ? pick_next_task_fair+0x165/0x470
[222393.052017]  [<ffffffff81069cdb>] ? finish_task_switch+0x8b/0x2a0
[222393.052526]  [<ffffffff810a0ee0>] ? lock_timer_base.isra.23+0x50/0x70
[222393.053062]  [<ffffffff810a0fa5>] ? try_to_del_timer_sync+0x45/0x60
[222393.053584]  [<ffffffff810a1003>] ? del_timer_sync+0x43/0x50
[222393.054058]  [<ffffffff8157651f>] ? schedule_timeout+0x11f/0x1b0
[222393.054558]  [<ffffffff810a0e80>] ? cascade+0x80/0x80
[222393.054984]  [<ffffffffa165ee24>] dvb_frontend_thread+0x4f4/0x520 [dvb_core]
[222393.055571]  [<ffffffff8157323f>] ? __schedule+0x2af/0x730
[222393.056032]  [<ffffffff81080050>] ? wait_woken+0x80/0x80
[222393.056478]  [<ffffffffa165e930>] ? dvb_frontend_release+0xb0/0xb0 [dvb_core]
[222393.057071]  [<ffffffff810652d6>] kthread+0xc6/0xe0
[222393.057481]  [<ffffffff81065210>] ? kthread_create_on_node+0x180/0x180
[222393.058024]  [<ffffffff815777ff>] ret_from_fork+0x3f/0x80
[222393.058477]  [<ffffffff81065210>] ? kthread_create_on_node+0x180/0x180
[222393.059019] Code: 89 45 c4 8d 06 c1 f8 1f 41 89 c1 41 31 f1 41 29 c1 48 8d 3b 44 89 4d cc e8 91 c1 ff ff 44 8d 00 31 d2 b8 00 00 00 04 44 8b 4d cc <41> f7 f0 41 89 c2 48 8b 83 38 05 00 00 44 8b 68 14 8b 05 20 24
[222393.061455] RIP  [<ffffffffa16dc20d>] dib7000p_set_frontend+0x8cd/0x1060 [dib7000p]
[222393.062102]  RSP <ffff88024896b9e0>
[222393.062437] ---[ end trace dbed3c4664072d59 ]---

 

The model I have is the 

PCTV Diversity Stick Solo

image.png.888857b2d94a8c90c9791331cd7821be.png

When that happens TVheadend stops working.

 

Thanks.

 

 

 

Edited by _ReaL_
Link to comment
Share on other sites

Platform: ASUS strix B250 ITX,   i3 8100T, 16G RAM 

PVE v6.2  , 1.04b boot loader for 6.2.3-25426 virtualized

physical passthrough  TPlink 2.5G NIC  ( RTL8125 chip) 

 

I saw RTL8125 is in supported driver list , but I'd no way to recongize my 2.5G NIC when boot with another NIC (virutalized E1000E  NIC ) 

I  checked /usr/lib/modules/update/*, there is no r8125.ko

Is there a typo for r8152 ?

Since a lot of Intel 10th gen CPU MB will use 2.5G NIC and mainly use rtl8125 chip , could rtl8125 also support in future ?

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