IG-88

Driver extension jun 1.02b/DSM6.1.x for 3615xs / 3617xs / 916+

Recommended Posts

There is no explicit AMD support OR hyper-v. That needs a different (newly compiled) kernel and thats not the way jun's approach works, it uses the kernel that comes with DSM, this package is only about kernel modules that can be loaded with the original Synology kernel.

 

The extra.lzma ramdisks have been tested to load on DSM 6.1.3 (15152 kernel source available), but I expect it also to work with 6.1.4 (15217, no source available yet) as it uses the same kernel (3.10.102) as base.

To check if the hardware is supported with a driver, use a running DSM installation or boot a live Ubuntu from usb. In console type the following:

lspci -k | grep 'Kernel driver'

That command will list the used kernel modules for the hardware. Modules for network and storage will be listed. Compare that with the list of modules that comes with the extra.lzma ramdisks provided below.

I'm trying to keep the same supported hardware for all the three supported DSM images, namely DS3615xs, DS3617xs and DS916+.
I will list if there is something less/more in one. Most likely it will be 916+ as the kernel seems to be compiled with less options then the other two (mostly in the network driver section. If the kernel internal driver cannot be compiled (like missing kernel options) or does not work (like newer hardware revisions not working - the 3.10.102 kernel is kind of "old") I will try to use external sources. If you are able to provide source or a link do so, that might speed up the process of supporting hardware.

Some of the network drivers for 916+ had missing kernel options and as I expected them to fail when loaded as module I did not made them (for now) some of those where provided in jun's extra.lzma and are also in, but i'm not sure if they ever worked, so we will see how the feedback for the 916+ network drivers is.

For now the 916+ does not contain the following drivers/modules:
 

be2net.ko
dca.ko

 

For the forcedeth.ko module, I dont see how to get external source for it. If someone with this hardware wants to try it with a "maybe not working" module then PM me I will make a test version.

added atl2.ko, cxgb.ko, cxgb3.ko, cxgb4.ko, forcedeth.ko for testing in v 4.2, also LSI MPT SAS Controller should work now

 

Below are the custom ramdisks for each version. Modules within them  are not interchangeable so don't start playing smart by moving modules between them. It will not work. You also need to de-zip the downloaded file before adding the ramdisk inside the loader.

extra.lzma for ds3615 v4.2
http://s000.tinyupload.com/?file_id=52946263108903140844

extra.lzma for ds3617 v4.2
http://s000.tinyupload.com/?file_id=07615192947370548683

extra.lzma for ds916+ v4.2

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


If you wish to make a driver request do so in the topic linked below:

 

 

If you wish to discuss problems about modules in these ramdisks then drop a post below.

Please be specific about what version and for what model you have feedback, like "4.1 for ds3617".

 

The driver list with related hardware is based on the older list for 5.2 and 6.0 so thanks goes to Trantor/Quicknick and all others who helped to build the older list for 5.2 and 6.0.

 

(…) Not compiled for now, ask for it

[…] Confirmed by users that it is not working, not supported for DSM 6.1 (kernel 3.10.102) or does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added

 

 
NETWORK DRIVERS LIST - Click here to see  

NETWORK

 

AMD

pcnet32: AMD PCnet32 PCI

 

Agere Systems

et131x: Agere Systems ET-131x PCI-E Gigabit Ethernet (staging driver)

 

Asix

asix: ASIX AX88xxx Based USB 2.0 Ethernet Adapters

ax88179_178a: ASIX USB 2.0/3.0 Gigabit Ethernet Controller

 

Atheros

atl1: Atheros/Attansic L1 Gigabit Ethernet

atl1c: Atheros L1C Gigabit Ethernet

atl1e: Atheros L1E Gigabit Ethernet

atl2: Atheros L2 Fast Ethernet


Broadcom

[b44: Broadcom 440x/47xx]

bnx2: Broadcom NetXtremeII BCM5706/BCM5708/5709/5716, firmware needed

bnx2x: Broadcom NetXtremeII 10Gb BCM57710/BCM57711/BCM57711E/BCM57712, Firmware needed

cnic: Broadcom NetXtreme II CNIC Driver

tg3: Broadcom Tigon3 BCM5705/BCM5703/BCM5702/BCM5701/BCM5700/BCM5721/BCM5751/BCM5788/BCM5704/BCM5752/BCM5789/BCM5723/BCM5761/BCM5787/BCM5755/BCM5722/BCM5754/BCM57781/BCM57785/BCM5718BCM57765/BCM57761/BCM5719/BCM5725/BCM5762/BCM5720/BCM57790/BCM57795/BCM57766/BCM57780

 

Brocade

(bna: Brocade 1010/1020 10Gb Ethernet)

 

Conexant

cx82310_eth: Conexant CX82310 USB ethernet

 

Chelsio

cxgb: Chelsio 10Gb Ethernet T210

cxgb3: Chelsio Communications T3 10Gb, firmware needed, N310E/B320E/S302E

cxgb4: Chelsio Communications T4 Ethernet, firmware needed, T420/T440/T422/T404/B420/B404

 

Cisco

(enic: Cisco VIC Ethernet NIC)

 

D-Link

(dl2k: D-Link DL2000-based Gigabit Ethernet Adapter)

 

Emulex

be2net: Emulex OneConnect Skyhawk/Emulex OneConnect Skyhawk-VF/Emulex OneConnect Lancer/Emulex BladeEngine2 10Gb Gen2 PCIe/Emulex BladeEngine3 10Gb/Gen2 PCIe/Emulex OneConnect OCe10100/OCe10102 Series 10 GbE/Emulex OneConnect 10Gb NIC (be3)

 

HP

(hp100 : HP 10/100VG PCLAN (ISA, EISA, PCI))

 

Intel

e100: Intel PRO/100+ (firmware needed)

e1000: Intel PCI/PCI-X Gigabit Network Adapters Intel PRO/1000 CT/F/GT/MF/MT/T/XF/XT 82573L/82572EI/82571EB/82573E/82573V/82567/82574L/82566MM/82566MC

e1000e: Intel PCIe PRO/1000 82563/82566/82567/82571/82572/82573/82574/82577/82578/82583

Gigabit CT Desktop Adapter/PRO/1000 PT/PF/I217-LM/V/I218-V/LM/I219 LM/V

i40e: Intel 40 Gigabit X710-AM2/XL710-AM1/XL710-AM2/X710-DA2/X710-DA4/XL710-QDA1/XL710-QDA2

ib_addr, ib_cm, ib_core, ib_mad, ib_netlink, ib_sa, iw_cm: Infiniband

igb: Intel Gigabit Ethernet 82575/82576/82580/I350/I210/I211

igbvf: driver supports 82576 virtual functions, only for KVM

ixgbe: Intel 10 Gigabit AF DA/AT/AT2/CX4/XF LR/XR/82599EB/82598EB/82599ES/82599EN, X540-T1/X540-T2/540-AT2/X520-SR1/X520-SR2/X520-DA2/X520-LR1/X520-DA1/X520-DA4/X520-QDA1/X520-T2 X550-BT2/AT/AT2 X550-T1/T2, X552, X553, X557

external source from Intel used (ixgbe-5.3.3.tar.gz) from Intel Ethernet Adapter Connections CD 22_9

ixgbevf: supports 82599, X540 and X550 virtual functions, only for KVM

external source from Intel used (ixgbevf-4.3.2.tar.gz)

pch_gbe: Intel PCH EG20T Gigabit ethernet driver

ptp_pch: Intel PCH EG20T as PTP clock

 

JMicron

jme: JMicron PCIe Gigabit


Nvidia

forcedeth: Nvidia nForce Ethernet

 

Marvell

mvmdio: Marvell MDIO interface

sky2: Marvell Yukon 2 Gigabit Ethernet 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21

 

Mellanox

mlx_compat, mlx4_core, mlx4_en, mlx4_ib, mlx5_core, mlx5_ib:

Mellanox MT25400/MT27500/MT27520/MT25408/MT25418/MT25448/MT25408/MT26418/MT26428/MT26438/MT26448/MT25408/MT26468/MT26478/MT27600/MT27700/MT27710/MT27800/MT28800/MT28908/MT416842

 

Pegasus

(pegasus: Pegasus/Pegasus II USB ethernet driver)

 

Prolific

plusb: Prolific PL-2301/2302/25A1 based

 

QLogic

netxen_nic: QLogic/NetXen NIC

qla3xxx: QLogic QLA3XXX Network driver

qlcnic: QLOGIC QLCNIC 1/10Gb Converged Ethernet

qlge: QLogic QLGE 10Gb Ethernet

 

Qualcomm

alx: Qualcomm Atheros AR816x/AR817x

 

Realtek

(r8101: 10/100 Realtek PCIe FE Family RTL8100E/RTL8101E/RTL8102E-GR/RTL8103E(L)/RTL8102E(L)/RTL8101E/RTL8103T/RTL8401/RTL8401P/RTL8105E/RTL8402/RTL8106E/RTL8106EUS/RTL8107E)

r8152: RTL8152/RTL8153 Based USB 2.0/3.0 Ethernet Adapters

r8168: Realtek PCIe GBE Family Controller (driver from external source, Realtek.com.tw) RTL8111B/RTL8168B/RTL8111/RTL8168/RTL8111C/RTL8111CP/RTL8111D(L)/RTL8168C/RTL8111DP/RTL8111E/RTL8168E/RTL8111F/RTL8411/RTL8111G/RTL8111GUS/RTL8411B(N)/RTL8118AS/RTL8111H(S)/RTL8118/RTL8119i

r8169: kernel provided driver for Realtek PCIe GBE Family Controller, as this is provided with 3.10.102 (DSM 6.1) its older then r8168 (source from 2017) and may not support newer hardware revisions of the Realtek nic‘s? (on „newer kernels“ this is the better choice as its safer to use)

rtl8150: USB RTL8150 based USB Ethernet Adapter


Silan

(sc92031: Silan SC92031 PCI Fast Ethernet Adapter driver)

 

SIS

(sis900: SiS900/7016)

(sis190: SiS190/SiS191)

 

Solarflare

sfc: Solarflare NIC 10Gb/s

 

Sundance Technology

ipg: Sundance Technology IPG Triple-Speed Ethernet IC PLUS IP1000 NIC, Sundance Technology ST2021 based NIC, Tamarack Microelectronics TC9020/9021 based, D-Link NIC IP1000A

 

SysKonnect

skge: SysKonnect, Marvell Yukon Gigabit Ethernet


Tehuti

tn40xx: Tehuti 10GbE NIC driver MV88X3120/QT2025/TLK10232/AQ2104/AQR105

 

VIA

(via-rhine: VIA Rhine)

(via-velocity: VIA Velocity)

 

VMware

vmxnet3: VMware vmxnet3 virtual NIC

Hide  

 

STORAGE DRIVERS LIST - Click here to see  

STORAGE

nvme: NVMe driver

3ware

(3w-xxxx: 3ware 5/6/7/8xxx ATA-RAID support)

3w-9xxx: 3ware 9xxx SATA-RAID support

3w-sas: 3ware 97xx SAS/SATA-RAID support

 

Adaptec

aacraid: Adaptec AACRAID support (Dell PERC2, 2/Si, 3/Si, 3/Di, HP NetRAID-4M, IBM ServeRAID & ICP SCSI), HBA 1000 series

aic94xx: Adaptec AIC94xx SAS/SATA support

 

ARECA

arcmsr: ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter


BusLogic

buslogic: BusLogic SCSI

 

HighPoint

hptiop : HighPoint RocketRAID 3xxx/4xxx Controller support

 

HP

[hpsa: Smart Array P212 P410 P410i P411 P812 P712m P711m ; (Gen6/7 Controllers) Smart Array P222 P420 P420i P421 P822 P220i P721 ; (Gen8 Controllers) Smart Array P430 P430i P431 P830 P830i P831 P731m P230i P530 P531 ; (Gen8.5 Controllers) Smart Array P440 P441 P840 P440ar P244br H240 H241 H240ar H244br ; (Gen9 Controllers) HP StorageWorks 1210m P1224 P1228 P1228m P1224e P1228e P1228em]

(cciss: old Smart Array driver up to P420, Gen7)

 

IBM

(ips: IBM ServeRAID support)

 

Intel

ata_piix: Intel IDE/PATA driver PIIX3/PIIX4/ICH0/ICH/ICH2/ICH3/C-ICH/ICH4/ICH5/6300ESB/ICH6/ICH7/ICH8M, SATA in IDE mode: ICH5/6300ESB/ICH6/CE3100/ICH7/NM10/631xESB/632xESB/ICH8/ICH9/ICH10/IIC

(gdth : Intel/ICO RAID controller support)

isci : Intel C600 Series Chipset SAS Controller


LSI

megaraid: LSI MegaRAID legacy

megaraid_mbox: LSI MegaRAID Mailbox

megaraid_mm: LSI MegaRAID Management Module

megaraid_sas: LSI MegaRAID SAS 9361-8i/9361-4i9341-8i/9341-4i/9380-8e/9380-4i4e/9270-8i9271-4i/9271-8i/9271-8iCC/9286-8e/9286CV-8e/9286CV-8eCC/9265-8i/9285-8e/9240-4i/9240-8i/9260-4i/9260CV-4i/9260-8i/9260CV-8i/9260DE-8i/9261-8i/9280-4i4e/9280-8e/9280DE-8e/9280-24i4e/9280-16i4e/9260-16i/9266-4i/9266-8i/9285CV-8e

mptsas: LSI MPT SAS1064/SAS1068/SAS1064ET/SAS1068E/SAS8208ELP/8208ELP/SAS1078

mpt2sas: LSI MPT SAS 6Gb/s Host Adapters SAS2004/SAS2008/SAS2108/SAS2116/SAS2208/SAS2308/SSS6200

mpt3sas: LSI MPT SAS 12Gb/s Host Adapters SAS3004/SAS3008/SAS3108

 

Marvel

mvsas: Marvell PCIe 88SE64XX (3Gb/s) and 88SE94XX 6Gbs) SAS/SATA support

mvumi: Marvell UMI driver

 

Promise

sx8: Promise SATA SX8 support

 

VMware

vmw_pvscsi: VMware Paravirtual SCSI Controller

Hide  

 

 

 

Change log  

[27/11/2017] Topic reformatted + slight corrections by Polanskiman

[30/11/2017]  uploaded v4.1 for all versions, recopyed drivers from jun's extra.lzma and only replaced tg3 and r8152 afterwards (proven to support newer hardware in former 3615 releases)

[09/12/2017] uploaded v4.2 for all versions

- replaced ixgbe.ko with newest from intel to support newer X55x for all three ramdisks

- replaced alt1c.ko in all three ramdisks with fresh compiled ones from 15152 as i got feedback that this modules where not working in jun's version

- NVMe driver added, supportnvme="yes" in synoinfo.conf seems not enough to get NVMe working as SSD withn WebGUI, 918+ image (open with 7zip) might gives hints how to do it properly, there are also some additional tools for nvme in this image like "nvme" and "synonvme", people wth NVMe will have to do more tinkering to find out what else to do to get it fully working in xpenology

- as someone wrote me about mlx4 working for him on 916+ image even if kenel option was not active in 916+ kernel config i made the following modules now part of the 916+ release for testing: atl2.ko, cxgb.ko, cxgb3.ko, cxgb4.ko, forcedeth.ko - we will see it they work

- got all sas drivers load in 916+ without unknown symbols (also mptsas/mpt2sas/mpt3sas) - lets see if they work when loaded with hardware present

 

Hide  
Edited by IG-88
  • Like 5

Share this post


Link to post
Share on other sites

First of all: Thanks for your work :)

 

I just tried the extra.lzma.

 

My network adapter is: AT2 X550-T1/T2 and it seems it is not working.

(as we wrote via pm, my brother tried to build the kernel modules (ixgbe) himself but seems the results are the same). I thought it was our fault because we made something wrong while compiling. 

 

Installing via USB Level One adapter works, but the LSI * adapter does not work too....only SSDs connected thru SATA ports are detected.

 

lspci shows: https://pastebin.com/Njd1HuPi

dmesg https://pastebin.com/AUPTXN7N (many errors [err 0] it seems)

lsmod: https://pastebin.com/uFTRZFNb

 

Any more info you guys may need? Otherwise it will re-install the box with 3617-image :-S

Edited by smokers

Share this post


Link to post
Share on other sites
4 hours ago, smokers said:

First of all: Thanks for your work :)

 

I just tried the extra.lzma.

My network adapter is: AT2 X550-T1/T2 and it seems it is not working.

 

I have the same problem with my NIC, have been tinkering around for the past few days. Glad I'm not alone.

Using X553/X557-AT from a Supermicro A2SDi-H-TF. 

I have tried adding the extra.lzma to 3615 and 3617 as well.

 

edit*

X553/X557-AT does not appear to be in the supported list..

Edited by MBchristoff

Share this post


Link to post
Share on other sites

I`m using ds3617, with the original extra.lzma is does work, but when i replace the extra.lmza from you (extra.lzma for ds3617 v4.0) my M1015 sas card is not showing my drives anymore.

 

With your drivers:

rikadoo@NAS:/$ lspci -k | grep 'Kernel driver'

        Kernel driver in use: pcieport
        Kernel driver in use: xhci_hcd
        Kernel driver in use: ehci-pci
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: ehci-pci
        Kernel driver in use: ahci
        Kernel driver in use: cxgb3
        Kernel driver in use: r8168
        Kernel driver in use: mpt2sas
rikadoo@NAS:/$

 

Original drivers

rikadoo@NAS:/$ lspci -k | grep 'Kernel driver'

        Kernel driver in use: pcieport
        Kernel driver in use: xhci_hcd
        Kernel driver in use: ehci-pci
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: ehci-pci
        Kernel driver in use: ahci
        Kernel driver in use: r8168
        Kernel driver in use: mpt2sas
rikadoo@NAS:/$

 

Any idea?

Share this post


Link to post
Share on other sites
12 hours ago, rikadoo said:

I`m using ds3617, with the original extra.lzma is does work, but when i replace the extra.lmza from you (extra.lzma for ds3617 v4.0) my M1015 sas card is not showing my drives anymore.

This looks like the mp2sas.ko module within the custom ramdisk is causing problems. Why are you using the custom ramdisk anyway if you have your disk controller working with the default ramdisk of the loader?

 

Another comment (to @IG-88), why is the mpt2sas.ko even in the your custom ramdisk. That module is already part of DSM.

Share this post


Link to post
Share on other sites

hi,

 

 i uploaded new 4.1 versions

change is mainly that i took whats already was in 4.0 and copy over the freshly extracted drivers from jun's 1.02b loader

in case I've overwritten some drivers with newly compiled ones or accidentally copied a wrong version

 

i added modules like mpt2sas/mpt3sas because they where in rc.modules but not present in jun's extra.lzma (extracted them from dsm 6.1.3)

 

in that process i was overthinking what can go wrong and also started comparing jun's three loaders with each other and compared rc.modules with whats in the extra.lzma

 

when it comes to installing dsm it does not matter whats inside the dsm file itself, if the loader it booted only drivers in that loader (and the extra.lzma) will be able to detect hardware, leaving drivers network and storage drivers that are part of the dsm file out of the loader would result in cases where the hardware is not detected by the loader but if dsm is already running then the hardware will be detected

 

example:

dsm for 3615 contains bnx2x.ko and no driver for e1000.ko

the loader only provides e1000.ko (as there seems no need for bnx2x,ko as its already part of dsm)

result will be a system with a onboard intel nic and additional boradcom netxtreme II will be able to install dsm as the intel is found and after installation the broadcom driver is loaded and you will see the 2nd nework adapter

in case there is only a broadcom netextreme II (like hp or dell server having them as onboard) the booting the loader will not find the nic and you can't install dsm at all

the same gos for storage drivers so mpt*.ko has to be part of the bootloader

 

 

also there may be errors in the whole approach in using the source of 6.1.3 as jun's loader s is based on 6.1.0 (15047) my drivers are compiled with the source of 6.1.3 (15152), when looking for the "destination" of using 6.1.3 that's good but it might collide with the base of the bootloader as there are differences in source that can matter (like unknown symbols when loading a driver from 6.1.3 on a 6.1.0 base/kernel)

 

 

Edited by IG-88
  • Like 2

Share this post


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

when it comes to installing dsm it does not matter whats inside the dsm file itself, if the loader it booted only drivers in that loader (and the extra.lzma) will be able to detect hardware, leaving drivers network and storage drivers that are part of the dsm file out of the loader would result in cases where the hardware is not detected by the loader but if dsm is already running then the hardware will be detected

 

Indeed I overlooked that part.

In any case since the mp2sas.ko module is already in the PAT file it might be better to take it from there than compiling it.

Share this post


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

This looks like the mp2sas.ko module within the custom ramdisk is causing problems. Why are you using the custom ramdisk anyway if you have your disk controller working with the default ramdisk of the loader?

 

Another comment (to @IG-88), why is the mpt2sas.ko even in the your custom ramdisk. That module is already part of DSM.

I was using the extra.lmza because of the drivers for the Chelsio 10GB card (Kernel driver in use: cxgb3)

Share this post


Link to post
Share on other sites

to make sure the drivers in extra.lzma are working with the the loader (dsm 6.1.0, 15047) i made test vm's with dsm 6.1.0 and booted with the new 4.1

3615 seemed ok

3617 nearly good, just the melanox drivers not loading

916+ still problems with all sas storage drivers, not just lsi mpt* drivers also mvsas, aic94xx and isci, network not loading for ixgbe and melanox

 

next will be to get ixgbe working and trying to find out whats wrong with sas on 916+

 

  • Like 1

Share this post


Link to post
Share on other sites
57 минут назад, IG-88 сказал:

next will be to get ixgbe working and trying to find out whats wrong with sas on 916+

 

Tnx.

Share this post


Link to post
Share on other sites

Excuse my ignorance, but can I add the ramdisk to my USB stick after already installing DSM? (And presumably rebooting).

 

I'd like to use an Intel NIC I have installed on my already working ds3615 system. Would adding the ramdisk foobar my system?

Share this post


Link to post
Share on other sites
On 11/30/2017 at 9:09 AM, Polanskiman said:

 

Indeed I overlooked that part.

In any case since the mp2sas.ko module is already in the PAT file it might be better to take it from there than compiling it.

 

my approach for 4.1 was (priority highest to lowest):

- my driver from external source if they where proofed to do better then jun's and dsm's (r8152 and tg3 for now)

- jun's driver (he might have used newer source the whats inside dsm or if he used his own/newer driver instead of using one from dsm there might be a reason i dont know about)

- driver from dsm

- newly compiled driver from synology kernel source  dsm 6.1.3 (15152)

 

 

there is a version conflict in all this (fixed) loader + dsm approach

jun's loader comes with kernel and drivers for dsm 6.1.0 (15047) when you boot up the first time, on installing you overwrite the original dsm 6.1.0 booting kernel with the dsm version you are installing, but the drivers in the extra.lzma are still the same so after installing dsm you use dsm 6.1.3/4 with drivers for 6.1.0

my extra.lzma will mixing in drivers compiled with the source for dsm 6.1.3 (15152), when looking to the resulting system after installation (dsm 61.3/4) better suited but they can be in conflict with the kernel in jun's 1.02b (dsm 6.1.0) that is used for 1st boot to install dsm

also there is was and is the risk that drivers for dsm 6.1.0 do work on 1st boot, land in /lib/modules/update and will be used with the newer installed dsm version and fail with the newer dsm version (same main version of kernel but differences in code as they have a newer revision 15047 -> 15152).

 

there are ways to deal with it

 

1. leave it that way, i can't remember a case where someone had a working nic/storage on 1st boot (6.1.0) and failed booting after installation of dsm (6.1.1/2/3/4)

2. compiling additional drivers with source for dsm 6.1.0 (15047) and stay on the road of jun's loader

3. compiling with the newest source (6.1.3 atm) and not just replacing extra.lzma on jun's loader, also replacing zImage and rd.gz from the newest dsm (even it its 6.1.4, the source of 6.1.3 is "closer" to 6.1.4 then the source of 6.1.0)

 

on a original synology system that problem does not exist, on versions with a new kernel revision there is always a complete dsm file (200MB) with boot kernel and all drivers, the kernel is written to the usb boot device and dsm is installed to disk, no conflict at all

 

as i have seen differences in loading divers i compiled from synology source and the same drivers jun provided (presuming he also used the synology source v15047) , i will need to do some testing to see if the difference comes from the kernel revision number or something else (any differences in how the drivers where compiled like kernel options)

 

as 3. seems to be the cleanest (and easy) way when providing a complete loader with extended extra.lzma and newest kernel from dsm, i will not do this for legal  reasons, providing compiled drivers from source code that is available for everyone is not really a problem, but releasing code that is owned by synology (like taking the compiled kernel out of dsm and re releasing it with jun's hack to get into dsm) is a different matter and i don't want to get in a situation to spend money on lawyers to deal with the legal division of a company that has much more money to spent then one person (legal hard working and tax paying) can afford

so my way would still be just releasing a extra.lzma as i do it now as 3. is just an additional step to 1. and also can be solved by adding steps to the howto for installing xpenology/dsm, atm there is no justification for such additional steps that will make the hurdle to install xpenology/dsm even higher

so i as long as i can't find any gain in using older source it will be 1. and 3. is a option that can be used

 

ps: sorry if i don't answer every pm, some of them are kind of answered with the information in this thread and new released extra.lzma, the time i can spare is limited so i have to share it between writing text (writing so everyone can read is preferable to pm, on long term there is more gain to expect if more people can read it) and working on newer extra.lzma and improving linux skills

 

  • Like 1

Share this post


Link to post
Share on other sites
14 hours ago, Bohemian said:

can I add the ramdisk to my USB stick after already installing DSM? (And presumably rebooting).

 

i don't see why not, if things go wrong you can re insert the old extra.lzma and if nothing happens at all (against what i expect) you could still extract the driver in question and copy it manually to your system (/lib/modules/update/) and add the needed entry to /etc/rc.modules

 

if you have win10 somewhere it's supposed to be easy, as the 2nd partition of the usb stick (thats where extra.lzma is located) should get a drive letter too if connected so it's just copying the new extra.lzma and boot dsm with the modified stick

Share this post


Link to post
Share on other sites

ixgbe works now with newer hardware (new driver will be in on all three platforms)

mptsas/mpt2sas/mpt3sas now load on 916+ in VM so i expect it to work on real hardware too

both will be in 4.2 availible

 

still open are mellanox (mlx4) drivers on 916+, if there is someone with this hardware and willing to test some drivers please pm me

 

anything else to do for 4.2?

Share this post


Link to post
Share on other sites

Hey IG-88,

I've come back to Xpenology after a long duration away from it (since 5.2 got released, to now).

 

However, I have noticed that the HP Driver for the P410i does not load as you have specified, has there been/will there be any progress on this, or should i just install FreeNAS or simalar for now?

Share this post


Link to post
Share on other sites

nice coincidence, a few weeks ago i've given up on that but last week i stumbled across a old p400 at work (in the recycling bin)

as i still have a old pc for data recovery with ide, sata, pci and pcie i can now test the hpsa.ko driver myself

main problem was that the compile switches the make/compiling process uses by finding out on what driver it is compiles (3.10.102)  did not work, there are some switches 0/1 that are set according to kernel version and my guess is that some of the back porting/modification synology did does interfere with that simple kernel detection (it does not check the functions in kernel source, just the kernel number and does extra checks for suse and red hat by version number)

the source is from here http://cciss.sourceforge.net

the switches are in hpsa_kernel_compat.h

kernel class comes from Makefile, it will be 3B for kernel 3.10.102

to test changing these switches one can tinker in the 3B section starting with

#elif defined(KCLASS3B)/************ Kernel Class 3B ************/

the first two in the default seem to collide with "our" kernel with the set default to 0 (indicated by collision warnings wehen compiling with the default settings)

#define KFEATURE_HAS_WAIT_FOR_COMPLETION_IO_TIMEOUT 1
#define KFEATURE_HAS_WAIT_FOR_COMPLETION_IO 1

 

 

if someone else finds out under what conditions it does deliver a working driver i would redo it with this settings and hpsa,ko would be in

so if you have time and its important for you feel free to try to build a working driver

 

about possible alternatives, imho open media vault is more like dsm/xpenology

 

Share this post


Link to post
Share on other sites

im using the latest version available 15152, thats closer to the destination we want to use (6.1.3/6.1.4)

but for testing 15047 will be ok, also juns loader uses kernel from dsm 15047

 

as i was reading the hpsa driver doku again i found out my p400 is not supported so good thing if you can test

 

i will go for the older cciss driver that supports only up to p420 but works for my p400 and i did not test it the last time(?), also all questions about p4xx where p410 and p420 so if cciss driver work most people will be happy i geuss

 

Share this post


Link to post
Share on other sites

Sure no problem ref testing, i've built a driver build env so i can build drivers when i need.

 

I will try an earlier version, but unsure how well it will go - will post findings.

Edited by AlienX

Share this post


Link to post
Share on other sites

Update:
I've tried a load of different versions of the hpsa driver, none of them seem to work correctly as described.

Weirdly, they do detect the logical volumes, but writing/reading to the disks is impossible.

 

I've attempted to use different flags as described in the KCLASS3B section, but as you say it's very kernel specific and changing these flags causes the driver to not compile for various reasons.

 

It could be useful to get the source code to the 5.2 XPEnoboot loader, so the working driver in that binary can be inspected, but I dont think this is an option.

 

I am also not too sure if I can enable SSH during the kernel boot/install time, do i have to plug a serial connection into the box to view the Kernel output / view logs?

Edited by AlienX

Share this post


Link to post
Share on other sites
18 minutes ago, AlienX said:

I am also not too sure if I can enable SSH during the kernel boot/install time, do i have to plug a serial connection into the box to view the Kernel output / view logs?

 

yes serial cable is needed to see it during boot but if the system can be reached in network and has a working disk with dsm (like on sata ahci), ssh should be enough to get the logs (hp controller only as "additional" with one disk for testing), might be easier then just one disk on hp controller and trying to install dsm on this disk

Share this post


Link to post
Share on other sites

Hey all,

 

I'm trying to work out how to get PCIE sound cards working with Xpenology installed on my HP N40L Microserver. I've got an Asus Xonar DX 7.1 sound card that I want to use to run Shairport-Sync on for a multi-room setup (ie 8 audio channels -> 4x discrete stereo sound outputs -> 4x pairs configured in ALSA with 4x instances of Shairport-Sync).

 

As far as I can work out, I just need to follow this guide https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/ to compile the sound card drivers and all ALSA related components, and inject them in?

 

I believe Xonar DX is natively supported in Linux 2.6+ and ALSA, so it should work?

 

Is there anything else that I need to do to my Xpenology install to get ALSA and the sound card drivers installed and working?

 

Thanks :)

Share this post


Link to post
Share on other sites
4 hours ago, moda said:

Hey all,

 

I'm trying to work out how to get PCIE sound cards working with Xpenology installed on my HP N40L Microserver. I've got an Asus Xonar DX 7.1 sound card that I want to use to run Shairport-Sync on for a multi-room setup (ie 8 audio channels -> 4x discrete stereo sound outputs -> 4x pairs configured in ALSA with 4x instances of Shairport-Sync).

 

As far as I can work out, I just need to follow this guide https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/ to compile the sound card drivers and all ALSA related components, and inject them in?

 

I believe Xonar DX is natively supported in Linux 2.6+ and ALSA, so it should work?

 

Is there anything else that I need to do to my Xpenology install to get ALSA and the sound card drivers installed and working?

 

Thanks :)

I'm not sure this will work for you exactly, but have you looked at Audio Station and setting up multiple devices for multi room setup? Might be easier than compiling etc

Share this post


Link to post
Share on other sites

it does not have to be on windows 10, you also can use a chroot enviroment on the nas or in a vm

 

even if you get the driver to work, you also have to create the alsa stuff (does not look like as there is enough in dsm like alsactl or alsamixer, aplay, ...) and you will have to compile and install shairpoint-sync, also configuring and using that without a gui(?) or is there a plugin doing this multiroom over alsa?

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now