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


Recommended Posts

58 minutes ago, Mapleaj said:

 

Thank you very much!!!

I tried to edit rc.modules, add my new driver module name into it,but when system reboot,it did not work. Ethernet did not show in Web UI. 

I will read your articles about how to make it,thanks again!

 

try /etc.defaults/r.modules

Link to post
Share on other sites
On 1/1/2019 at 7:19 PM, IG-88 said:

 

try /etc.defaults/r.modules

I just want to upgrade Brocade driver to 3.2.7.2.

 

I didn't use linux-3.10.x.txz to build drivers on another machine.

If I  use linux-3.10.x to build ,also bfa have the same errors like below,

bna can be build successful,but when insmod bna.ko will have errors like :

root@DiskStation:/usr/src/bna# insmod bna.ko 
insmod: ERROR: could not insert module bna.ko: Unknown symbol in module

dmesg

[ 6781.814664] bna: Unknown symbol kmem_cache_alloc_trace (err 0)
[ 6781.814683] bna: Unknown symbol kmalloc_order_trace (err 0)
[ 6781.814745] bna: Unknown symbol alloc_pages_current (err 0) 

 

What my other way to try on real DSM is like this: 

Build with  "/usr/local/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build”  which decompressed from  ds.x64-6.1.dev.txz 

 

The driver has two parts,one is bna,and one is bfa.

bna can be built successfully,but when I build bfa ,it got errors like:

root@DiskStation:/usr/src/bfa# make
make -C /usr/local/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build M=`pwd` CONFIG_DEBUG_INFO= 
make[1]: Entering directory `/volume1/Share/ds6.1dev/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build'
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "scsi_is_fc_rport" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_get_event_number" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_vport_terminate" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remote_port_rolechg" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_vport_create" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_host_post_vendor_event" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_release_transport" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remote_port_delete" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remove_host" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remote_port_add" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_attach_transport" [/usr/src/bfa/bfa.ko] undefined!

 

First I prepared bromolow-gcc493_glibc220_linaro_x86_64-GPL.txz 

tar -Jxvf bromolow-gcc493_glibc220_linaro_x86_64-GPL.txz

export PATH=/volume1/Share/x86_64-pc-linux-gnu/bin:$PATH
export TOOLCHAIN=/volume1/Share/x86_64-pc-linux-gnu/
ln -s /volume1/Share/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-gcc /usr/bin/gcc
ln -s /volume1/Share/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ar /usr/bin/ar
ln -s /volume1/Share/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ld /usr/bin/ld

 

Then I edited the Makefile of bna and bfa (See blow: brocade_driver_linux-3.2.7.2_src.tar.gz), and changed KERNEL_DIR to “/usr/local/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build”  which decompressed from ds.x64-6.1.dev.txz.I also made a link like this:

root@DiskStation:/usr/src/bfa# ls /usr/local/x86_64-pc-linux-gnu
sys-root
root@DiskStation:/usr/src/bfa# ls -lh /usr/local/
total 28K
lrwxrwxrwx  1 root root  109 Jan  2 20:12 x86_64-pc-linux-gnu -> /volume1/Share/ds6.1dev/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu

 

Because bfa.ko is failed,so I tried to put  bna.ko in extra.lzma,but it still didn't work.DSM can not init the Ethernet when it's booting.

dmesg like this:

[Wed Jan  2 20:27:24 2019 <    0.005737>] QLogic BR-series 10G Ethernet driver - version: 3.2.7.2 01/27/2017 15.49.07
[Wed Jan  2 20:27:24 2019 <    0.000033>] bnad_pci_probe : (0xffff88020d3f9800, 0xffffffffa09a7180) PCI Func : (2)
[Wed Jan  2 20:27:24 2019 <    0.000022>] BFA[info] log: init OK, msg total count 110
[Wed Jan  2 20:27:24 2019 <    0.000092>] bna 0000:01:00.2: ioremap for bar0 failed
[Wed Jan  2 20:27:24 2019 <    0.005122>] bna: probe of 0000:01:00.2 failed with error -12
[Wed Jan  2 20:27:24 2019 <    0.000005>] bnad_pci_probe : (0xffff88020d3f9000, 0xffffffffa09a7180) PCI Func : (3)
[Wed Jan  2 20:27:24 2019 <    0.000065>] bna 0000:01:00.3: ioremap for bar0 failed
[Wed Jan  2 20:27:24 2019 <    0.005125>] bna: probe of 0000:01:00.3 failed with error -12

 

Could you give me some advice? I also checked your bna.ko.It's different ,your bna used a firmware like :

[root@localhost ~]# modinfo nas-ultra/usr/lib/modules/bna.ko 
filename:       /root/nas-ultra/usr/lib/modules/bna.ko
firmware:       ct2fw-3.1.0.0.bin
firmware:       ctfw-3.1.0.0.bin
version:        3.1.2.1
description:    Brocade 10G PCIe Ethernet driver
license:        GPL
author:         Brocade
srcversion:     02F8BB3E6DC8BB2E016FDB6
alias:          pci:v00001657d00000022sv*sd*bc02sc00i*
alias:          pci:v00001657d00000014sv*sd*bc02sc00i*
depends:        
intree:         Y
vermagic:       3.10.102 SMP mod_unload 
parm:           bnad_msix_disable:Disable MSIX mode (uint)
parm:           bnad_ioc_auto_recover:Enable / Disable auto recovery (uint)
parm:           bna_debugfs_enable:Enables debugfs feature, default=1, Range[false:0|true:1] (uint)

here is mine:

[root@localhost ~]# modinfo nas/usr/lib/modules/bna.ko 
filename:       /root/nas/usr/lib/modules/bna.ko
version:        3.2.7.2
description:    QLogic BR-series 10G PCIe Ethernet driver
license:        GPL
author:         Brocade
srcversion:     E43385231C32C74BC9F3424
alias:          pci:v00001657d00000022sv*sd*bc02sc00i*
alias:          pci:v00001657d00000014sv*sd*bc02sc00i*
depends:        
vermagic:       3.10.102 SMP mod_unload 
parm:           bnad_gro_disable:Disable GRO (uint)
parm:           bnad_multi_buffer_rx:Multi-buffer Rx; 1 - en(default), 0 - dis (uint)
parm:           bnad_msix_disable:Disable MSIX mode (uint)
parm:           bnad_log_level:Log level (uint)
parm:           bnad_ioc_auto_recover:Enable / Disable auto recovery (uint)
parm:           bna_debugfs_enable:Enables debugfs feature, default=1, Range[false:0|true:1] (uint)
parm:           bna_veb_enable:Enable VEB, default=0, Range[false:0|true:1] (uint)

For those differents,I checked Brocade website,and I didn't find any useful informations.  http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProduct.aspx?ProductCategory=322&amp;Product=1214&amp;Os=65 

brocade_driver_linux-3.2.7.2_src.tar.gz

Edited by Polanskiman
Added code tags and formatted post
Link to post
Share on other sites
20 hours ago, rok1 said:

Do we know if the LSI 3108 is good with this yet? I have a Dell PERC H730P which is based on that controller that has a HBA mode. It is not seen by the driver. Do you need hardware IDs to make it work?

i had only the older LSI 9211 controller for tests, in theory it should work with the mpt3sas module

whats in the log when the diver is loaded?

whats the id with lspci?

Link to post
Share on other sites

I just bought this network card, https://www.uptimed.nl/producten/netwerkkaarten/10g-workstation-rj45-netwerkkaart.

I got ds3617xs loader from JUN 1.02b 6.1.7.

 

The topic start says this card should work with de extra.lzma so i downloaded extra.lzma for ds3617 v4.8 and placed this on the USB stick. But when i boot it`s not showing the extra network card in DSM networks. Is there somthing i do wrong?

 

Tehuti
tn40xx: Tehuti 10GbE NIC driver MV88X3120/QT2025/TLK10232/AQ2104/AQR105, ASUS XG-C100F, Buffalo LGY-PCIE-MG, D-Link DXE-810T/S, Edimax 10G, IEI Mustang-200, TN9030, TN9210, TN9310, TN9510, TN9610, TN9710P, TN9710Q

 

 

Edited by rikadoo
Link to post
Share on other sites
27 minutes ago, rikadoo said:

I just bought this network card, https://www.uptimed.nl/producten/netwerkkaarten/10g-workstation-rj45-netwerkkaart.

I got ds3617xs loader from JUN 1.02b 6.1.7.

 

The topic start says this card should work with de extra.lzma so i downloaded extra.lzma for ds3617 v4.8 and placed this on the USB stick. But when i boot it`s not showing the extra network card in DSM networks. Is there somthing i do wrong?

 

atm we use the driver that comes from synology, most common reason newer chip revision or new phy chip

the driver that comes with dsm 6.1 is v0.3.6.12.3

the newest driver from the tehuti page is tn40xx-0.3.6.17.tgz and contains a release_notes file

your link is good, it states

"Tehuti Networks TN4010 Controller

Marvell Alaska® X3310P PHY"

 

from the release_notes:

"Version 0.3.6.14 2017/03/08
===========================
- Support for Pele 88X3310P and 88E2010P PHYs"

 

so looks like a newer driver is needed for this card

 

in the extra.lzma thread for dsm 6.2 i commented for tehuti

"(v0.3.6.16.1 from external source, might not work, at least did not on my test system, irq problems, feedback needed)"

 

so i can try the latest driver but it might not work, i plan to work a little on a refreshed extra.lzma for dsm 6.1 so i will try to insert the latest tehuti driver and you are the tester that can give us feedback if its working, atm i dont have baremetal test system so the only thing i can test is if the driver loads without kernel errors without the hardware present (in a virtualbox vm)

if you have a free disk and a usb stick you can try to disconnect all disks and you normal usb stick, connect a empty disk and a stick with loader 1.03, my extra.lzma for 1.03 and try dsm 6.2(.0) then we know that the newer driver is at least working (even if it did not on my test system back then)

Link to post
Share on other sites
On 1/2/2019 at 9:03 PM, Mapleaj said:

I just want to upgrade Brocade driver to 3.2.7.2.

 

I didn't use linux-3.10.x.txz to build drivers on another machine.

If I  use linux-3.10.x to build ,also bfa have the same errors like below,

bna can be build successful,but when insmod bna.ko will have errors like :

root@DiskStation:/usr/src/bna# insmod bna.ko 
insmod: ERROR: could not insert module bna.ko: Unknown symbol in module

 

dmesg

[ 6781.814664] bna: Unknown symbol kmem_cache_alloc_trace (err 0)
[ 6781.814683] bna: Unknown symbol kmalloc_order_trace (err 0)
[ 6781.814745] bna: Unknown symbol alloc_pages_current (err 0)
 

 

What my other way to try on real DSM is like this: 

Build with  "/usr/local/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build”  which decompressed from  ds.x64-6.1.dev.txz 

 

The driver has two parts,one is bna,and one is bfa.

bna can be built successfully,but when I build bfa ,it got errors like:


root@DiskStation:/usr/src/bfa# make
make -C /usr/local/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build M=`pwd` CONFIG_DEBUG_INFO= 
make[1]: Entering directory `/volume1/Share/ds6.1dev/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build'
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "scsi_is_fc_rport" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_get_event_number" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_vport_terminate" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remote_port_rolechg" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_vport_create" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_host_post_vendor_event" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_release_transport" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remote_port_delete" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remove_host" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_remote_port_add" [/usr/src/bfa/bfa.ko] undefined!
WARNING: "fc_attach_transport" [/usr/src/bfa/bfa.ko] undefined!

 

 

 

First I prepared bromolow-gcc493_glibc220_linaro_x86_64-GPL.txz 
 


tar -Jxvf bromolow-gcc493_glibc220_linaro_x86_64-GPL.txz

export PATH=/volume1/Share/x86_64-pc-linux-gnu/bin:$PATH
export TOOLCHAIN=/volume1/Share/x86_64-pc-linux-gnu/
ln -s /volume1/Share/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-gcc /usr/bin/gcc
ln -s /volume1/Share/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ar /usr/bin/ar
ln -s /volume1/Share/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ld /usr/bin/ld

 

Then I edited the Makefile of bna and bfa (See blow: brocade_driver_linux-3.2.7.2_src.tar.gz), and changed KERNEL_DIR to “/usr/local/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-6.1/build”  which decompressed from ds.x64-6.1.dev.txz.I also made a link like this:

 


root@DiskStation:/usr/src/bfa# ls /usr/local/x86_64-pc-linux-gnu
sys-root
root@DiskStation:/usr/src/bfa# ls -lh /usr/local/
total 28K
lrwxrwxrwx  1 root root  109 Jan  2 20:12 x86_64-pc-linux-gnu -> /volume1/Share/ds6.1dev/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu

 

Because bfa.ko is failed,so I tried to put  bna.ko in extra.lzma,but it still didn't work.DSM can not init the Ethernet when it's booting.

dmesg like this:


[Wed Jan  2 20:27:24 2019 <    0.005737>] QLogic BR-series 10G Ethernet driver - version: 3.2.7.2 01/27/2017 15.49.07
[Wed Jan  2 20:27:24 2019 <    0.000033>] bnad_pci_probe : (0xffff88020d3f9800, 0xffffffffa09a7180) PCI Func : (2)
[Wed Jan  2 20:27:24 2019 <    0.000022>] BFA[info] log: init OK, msg total count 110
[Wed Jan  2 20:27:24 2019 <    0.000092>] bna 0000:01:00.2: ioremap for bar0 failed
[Wed Jan  2 20:27:24 2019 <    0.005122>] bna: probe of 0000:01:00.2 failed with error -12
[Wed Jan  2 20:27:24 2019 <    0.000005>] bnad_pci_probe : (0xffff88020d3f9000, 0xffffffffa09a7180) PCI Func : (3)
[Wed Jan  2 20:27:24 2019 <    0.000065>] bna 0000:01:00.3: ioremap for bar0 failed
[Wed Jan  2 20:27:24 2019 <    0.005125>] bna: probe of 0000:01:00.3 failed with error -12

Could you give me some advice? I also checked your bna.ko.It's different ,your bna used a firmware like :

 


[root@localhost ~]# modinfo nas-ultra/usr/lib/modules/bna.ko 
filename:       /root/nas-ultra/usr/lib/modules/bna.ko
firmware:       ct2fw-3.1.0.0.bin
firmware:       ctfw-3.1.0.0.bin
version:        3.1.2.1
description:    Brocade 10G PCIe Ethernet driver
license:        GPL
author:         Brocade
srcversion:     02F8BB3E6DC8BB2E016FDB6
alias:          pci:v00001657d00000022sv*sd*bc02sc00i*
alias:          pci:v00001657d00000014sv*sd*bc02sc00i*
depends:        
intree:         Y
vermagic:       3.10.102 SMP mod_unload 
parm:           bnad_msix_disable:Disable MSIX mode (uint)
parm:           bnad_ioc_auto_recover:Enable / Disable auto recovery (uint)
parm:           bna_debugfs_enable:Enables debugfs feature, default=1, Range[false:0|true:1] (uint)

here is mine:


[root@localhost ~]# modinfo nas/usr/lib/modules/bna.ko 
filename:       /root/nas/usr/lib/modules/bna.ko
version:        3.2.7.2
description:    QLogic BR-series 10G PCIe Ethernet driver
license:        GPL
author:         Brocade
srcversion:     E43385231C32C74BC9F3424
alias:          pci:v00001657d00000022sv*sd*bc02sc00i*
alias:          pci:v00001657d00000014sv*sd*bc02sc00i*
depends:        
vermagic:       3.10.102 SMP mod_unload 
parm:           bnad_gro_disable:Disable GRO (uint)
parm:           bnad_multi_buffer_rx:Multi-buffer Rx; 1 - en(default), 0 - dis (uint)
parm:           bnad_msix_disable:Disable MSIX mode (uint)
parm:           bnad_log_level:Log level (uint)
parm:           bnad_ioc_auto_recover:Enable / Disable auto recovery (uint)
parm:           bna_debugfs_enable:Enables debugfs feature, default=1, Range[false:0|true:1] (uint)
parm:           bna_veb_enable:Enable VEB, default=0, Range[false:0|true:1] (uint)

For those differents,I checked Brocade website,and I didn't find any useful informations.  http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProduct.aspx?ProductCategory=322&amp;Product=1214&amp;Os=65 

brocade_driver_linux-3.2.7.2_src.tar.gz

 

I fixed those problem,in fact I built drivers successful even bfa had warnings.After put bfa.ko and bna.ko into extra.lzma together,DSM can init the ethernet when booting.

 

Thanks again!!!!

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

 

atm we use the driver that comes from synology, most common reason newer chip revision or new phy chip

the driver that comes with dsm 6.1 is v0.3.6.12.3

the newest driver from the tehuti page is tn40xx-0.3.6.17.tgz and contains a release_notes file

your link is good, it states

"Tehuti Networks TN4010 Controller

Marvell Alaska® X3310P PHY"

 

from the release_notes:

"Version 0.3.6.14 2017/03/08
===========================
- Support for Pele 88X3310P and 88E2010P PHYs"

 

so looks like a newer driver is needed for this card

 

in the extra.lzma thread for dsm 6.2 i commented for tehuti

"(v0.3.6.16.1 from external source, might not work, at least did not on my test system, irq problems, feedback needed)"

 

so i can try the latest driver but it might not work, i plan to work a little on a refreshed extra.lzma for dsm 6.1 so i will try to insert the latest tehuti driver and you are the tester that can give us feedback if its working, atm i dont have baremetal test system so the only thing i can test is if the driver loads without kernel errors without the hardware present (in a virtualbox vm)

if you have a free disk and a usb stick you can try to disconnect all disks and you normal usb stick, connect a empty disk and a stick with loader 1.03, my extra.lzma for 1.03 and try dsm 6.2(.0) then we know that the newer driver is at least working (even if it did not on my test system back then)

 

Ah that explanes a lot, i will try to test with the Jun's Loader v1.03b DS3617xs loader. I will let you know if this works. 

 

When you have the new extra.lzma package ready with the new Tehuti drivers i will test if it works and give feedback.

Link to post
Share on other sites

Any chance i can get some help with "Realtek 8111C-GR" (according to system spec sheet from HP)? it is detected under 6.1 and 6.2 with and without the extra driver extension but i'm getting full 100 MB UP and around 2 MB Down! i'm sure of the Gigabit speed system and network capabilities as i was running the system under Ubuntu server for a while without a hiccup.  any help would be appreciated.

 

Current setup, HP DX2400 Microtower, intel E7600, 4 GB Ram, 1 TB Drive for testing.

 

Below the output i could pull from my box:

 

1- ethtool eth0 output:

Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup

 

2- dmesg |grep eth0 output:

[   28.057505] eth0: 0xffffc9001170c000, 00:22:64:c0:e5:21, IRQ 18
[   28.085655] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   29.338180] init: dhcp-client (eth0) main process (8745) killed by TERM signal
[   31.091525] r8168: eth0: link up
[   31.091544] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   32.218219] init: dhcp-client (eth0) main process (9060) killed by TERM signal

 

3- lspci -k | grep 'Kernel driver' output: 

Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: ehci-pci
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: ehci-pci
        Kernel driver in use: lpc_ich
        Kernel driver in use: ahci
        Kernel driver in use: r8168

 

Edited by Polanskiman
Added code tags.
Link to post
Share on other sites
9 hours ago, Ronnie_frown said:

Any chance i can get some help with "Realtek 8111C-GR" (according to system spec sheet from HP)? it is detected under 6.1 and 6.2 with and without the extra driver extension but i'm getting full 100 MB UP and around 2 MB Down! i'm sure of the Gigabit speed system and network capabilities as i was running the system under Ubuntu server for a while without a hiccup.  any help would be appreciated.

 

i don't know what driver ubuntu uses, you can check and report back

ubuntu might be using the kernel build in driver of the actual kernel

dsm for 3615/17 uses an older kernel 3.10.10x and jun's and my extra lzma contain the driver that realtek provides

as your hardware is pretty old the kernel the build in kernel driver might work for you, it is possible to make a special version that contains the kernel driver instead of the realtek driver but that would be just for testing and not permanently supported

best way would be to add a nic as pci/pcie card and use that

Edited by IG-88
Link to post
Share on other sites
On 1/4/2019 at 5:40 PM, rikadoo said:

I just tested the Jun 1.03 loader for ds3716xs and the Tehuti network is still not working, i could`nt find any extra.lzma package for this loader.

just the parallel thread for loader 1.03 (dsm. 6.2)

 

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

 

i don't know what driver ubuntu uses, you can check and report back

ubuntu might be using the kernel build in driver of the actual kernel

dsm for 3615/17 uses an older kernel 3.10.10x and jun's and my extra lzma contain the driver that realtek provides

as your hardware is pretty old the kernel the build in kernel driver might work for you, it is possible to make a special version that contains the kernel driver instead of the realtek driver but that would be just for testing and not permanently supported

best way would be to add a nic as pci/pcie card and use that

 

@IG-88 Thanks allot for your feedback, at the moment i'm testing a DS3615xs, DSM 6.1-15047 and loader 1.02b with extra lzma. what i noticed is that sometimes the kernel/system picks up the right driver at boot with a cold start or i have to keep restarting till i get lucky. i was planning on building a new box after i'm done toying around with this old rusty one but for the time being, is it secure to run on 6.1? i use Plex remotely and this exposes my box to the internet in a way. are there any network adapters proven to play well with synology?

 

again, many thanks for the assist.

Link to post
Share on other sites
  • 2 weeks later...

@IG-88 hey again, i followed your advice and picked up a TP-Link TG-3468 (has an r8169 controller adn kinda the only NIC i can find at our crappy local PC HW stores), installed DS3615xs, DSM 6.1-15047, loader 1.02b with extra lzma. got the same weird issue! checked the kernel and for some reason it is loading the driver for the r8168 :/ 

 

reverted to my Ubuntu Server setup (which works perfectly fine with the new and the old NIC) to find out what driver the kernel is loading, got the following output:

 

 

00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
    Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) SMBus Controller
    Flags: medium devsel, IRQ 18
    Memory at feaffc00 (64-bit, non-prefetchable)
    I/O ports at 0400
    Kernel driver in use: i801_smbus
    Kernel modules: i2c_i801

 

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
    Subsystem: TP-LINK Technologies Co., Ltd. TG-3468 Gigabit PCI Express Network Adapter
    Flags: bus master, fast devsel, latency 0, IRQ 16
    I/O ports at e800
    Memory at febff000 (64-bit, non-prefetchable)
    Memory at fdffc000 (64-bit, prefetchable)
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 01
    Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
    Capabilities: [d0] Vital Product Data
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number 90-2e-00-00-68-4c-e0-00
    Kernel driver in use: r8169
    Kernel modules: r8169

 

i'm wondering why the "extra lzma" isn't fixing the issue of the missing DSM/Loader driver! :/

Link to post
Share on other sites
  • 4 weeks later...
On 1/3/2019 at 10:58 PM, IG-88 said:

 

atm we use the driver that comes from synology, most common reason newer chip revision or new phy chip

the driver that comes with dsm 6.1 is v0.3.6.12.3

the newest driver from the tehuti page is tn40xx-0.3.6.17.tgz and contains a release_notes file

your link is good, it states

"Tehuti Networks TN4010 Controller

Marvell Alaska® X3310P PHY"

 

from the release_notes:

"Version 0.3.6.14 2017/03/08
===========================
- Support for Pele 88X3310P and 88E2010P PHYs"

 

so looks like a newer driver is needed for this card

 

in the extra.lzma thread for dsm 6.2 i commented for tehuti

"(v0.3.6.16.1 from external source, might not work, at least did not on my test system, irq problems, feedback needed)"

 

so i can try the latest driver but it might not work, i plan to work a little on a refreshed extra.lzma for dsm 6.1 so i will try to insert the latest tehuti driver and you are the tester that can give us feedback if its working, atm i dont have baremetal test system so the only thing i can test is if the driver loads without kernel errors without the hardware present (in a virtualbox vm)

if you have a free disk and a usb stick you can try to disconnect all disks and you normal usb stick, connect a empty disk and a stick with loader 1.03, my extra.lzma for 1.03 and try dsm 6.2(.0) then we know that the newer driver is at least working (even if it did not on my test system back then)

 

Did you already started with update/rework the extra.lmza package? I`m waiting for the driver package tot est the Tehuti drivers for mine 10Gb adapter to get this working :)

Edited by rikadoo
Link to post
Share on other sites
  • 4 weeks later...

Hi all. Thanks for all the great notes and guidance. Not to mention all the hard work pulling all this together.

 

I've got an N64L G7 which I've been running 5.2 on for years. Finally decided to update to 6.x.

 

I followed all the great instructions from @Polanskiman, triple checked my MAC address, booted up with @jun1.04b loader, but couldn't find the server on the network with find.synology or the assistant.

 

I did a little more looking on this thread and found that my NIC was tg3 so I needed @IG-88's extra.lzma.

  • HP NC107i PCIe Gigabit Server Adapter
  • BCM95723

No problem. I renamed the old extra.lzma, dropped this one into the second partition, booted up and... still can't see the server on the network.

 

The NIC light on the server is flashing away but my router doesn't see it.

 

So I'm stuck. Suggestions please??

Link to post
Share on other sites

Skiptar

 

Two Issues

 

First,  BCM95723 is no longer supported. So in bios disable onboard network card. Next, try a card (Intel CT PCIE Gigabit, HP NC360T)

Second, in bios disable CPU C1 power management setting

 

 

  • Thanks 1
Link to post
Share on other sites
  • 2 weeks later...

Hi all.

Need some help or advice.

I'm trying to install Xpenology on the Intel Server Board S2600GZ (intel c602 chipset, 4 nic intel I350) with Xeon E5-2609v2 CPU and 16GB DDR3-ECC RAM

I tried to use DS3615xs(DS3617xs) 6.1 Jun's Mod V1.02b(also mbr version) with extra.lzma (all version from this topic).

First part of installation looks great - loader starts, network is running, connected hard disk is detected. I can connect to server using Synology Assistant or find.synology.com. Then I choose pat-file (tried all versions starting 15047) and the installation passes without any errors. After reboot, the loader starts, but the server no longer responds to the network until switch boot mode to reinstall from loaders start menu. After that, the server appears on the network and I am offered a migration or a clean installation. It doesn't matter what to choose, there are no errors in the installation, but I get the same result - after rebooting the server no longer responds to the network...

Have no idea what to do next...

 

Ubuntu 18.04.2 livecd

dmesg

lspci

lspci_vvv

 

 

 

 

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