Jump to content
XPEnology Community

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


Recommended Posts

9 hours ago, Zemmy said:

It seems not working with my Acer desktop PC.

I plan to try it on another DIY PC (work place) when pandemic lockdown is over.

I‘ll feedback to you as soon as possible.

can you write the pci vendor and device id here? (use lspci)

if you have a primary nic (10G only additional)  and can access the dsm system and look into the logs, there should be messages when loading the driver

Link to comment
Share on other sites

19 hours ago, IG-88 said:

can you write the pci vendor and device id here? (use lspci)

if you have a primary nic (10G only additional)  and can access the dsm system and look into the logs, there should be messages when loading the driver

Luckily, I took a screenshot when it was installed on a ProxmoxVE machine last time. The pci vendor of BCM57416 NIC is [14e4:16d8].

19 hours ago, IG-88 said:

if you have a primary nic (10G only additional)  and can access the dsm system and look into the logs, there should be messages when loading the driver

OK. I will try.

Link to comment
Share on other sites

3 hours ago, Zemmy said:

Luckily, I took a screenshot when it was installed on a ProxmoxVE machine last time. The pci vendor of BCM57416 NIC is [14e4:16d8].

the driver should work with the following devices (kernel 4.4.59 driver for 918+)

14E4:16D3
14E4:16CB
14E4:16D2
14E4:16D1
14E4:16CA
14E4:16C9

so it looks like your nic might be to new for that old kernel 4.4.59 synology uses

we would need driver source from broadcom that compiles with 4.4.x kernel

 

looks like you hardware was introduduced with kernel 4.8

https://cateee.net/lkddb/web-lkddb/BNXT.html

 

lkddb pci 14e4 16d8 .... .... ...... : CONFIG_BNXT CONFIG_ETHERNET CONFIG_NET_VENDOR_BROADCOM : drivers/net/ethernet/broadcom/bnxt/bnxt.c # in 4.8–4.20, 5.0–5.16, 5.17-rc+HEAD

 

i have not found driver for older kernel by looking a little with a search engine

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

4 hours ago, Jack223 said:

intel-N6005(4e71)  with DSM-7.01 ,but graphic card not working . i still can find (/dev/dri) in the ‎terminal‎‎, but can't transcode any movies

 

the topic here states this thread is about dsm 6.2.3 not 7.0, so please open a new top in another area for further discussion

 

your jasper lake iGPU (4e71) would not work with a default 6.2.3 i915 driver as that driver is to old (12/2017), 7.01 uses the same old driver source (i checked the i915.ko of 7.01) so there should be no drvices shown under /dev/dri (without patching a driver)

 

apart from that, beside devices under /dev/dri you also need to patch files too when using hardware transcoding without a valid serial

https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/?do=findComment&comment=222476

 

Link to comment
Share on other sites

Hi there fellow xpenologists.

Can someone pls pinpoint into the direction of what I should do next?

I have GA-C1037UN-EU board with STlab A-230 PCI sata raid card (with via VT6421 chip) and my DSM doesn't see the HDDs connected to it.

I've used extra.izma, rd.gz and zImage as instructed here with my loader. DSM (fresh install 3617xs) is 25426 Update 3.

How do I dig for the root of the problem here?

 

Edited by Valk
Link to comment
Share on other sites

8 hours ago, Valk said:

GA-C1037UN-EU

ivy brige cpu, i guess you already know 918+ is not going to work with that (as you already use 3617)

8 hours ago, Valk said:

STlab A-230 PCI sata raid card (with via VT6421 chip)

not ahci compatible, pata and other special sata drivers dont work anymore with 6.2.x

https://ata.wiki.kernel.org/index.php/SATA_hardware_features

 vt642x -> sata_via.ko

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

 

!!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!!

 

thats valid for 6.1 and 6.2, so if you want that hardware to be using dsm you would need to fix the synology kernel driver code or use older 1.01 driver with 6.0

you would need to use a pci card with ahci capable chip, kind of hard to come by i guess, most if not all chips seem to be pcie and even when taking other drivers with sas/sata into account there is nearly nothing, maybe lsi 1064/1068 but these have a hardware flaw only limiting disk size to ~2.5TB (afair)

best shot it to use a board that has pcie so you can use the usual marvell/asm or jmb ahci capable chips

Link to comment
Share on other sites

11 hours ago, IG-88 said:

ivy brige cpu, i guess you already know 918+ is not going to work with that (as you already use 3617)

not ahci compatible, pata and other special sata drivers dont work anymore with 6.2.x

https://ata.wiki.kernel.org/index.php/SATA_hardware_features

 vt642x -> sata_via.ko


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

 


!!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!!

 

thats valid for 6.1 and 6.2, so if you want that hardware to be using dsm you would need to fix the synology kernel driver code or use older 1.01 driver with 6.0

you would need to use a pci card with ahci capable chip, kind of hard to come by i guess, most if not all chips seem to be pcie and even when taking other drivers with sas/sata into account there is nearly nothing, maybe lsi 1064/1068 but these have a hardware flaw only limiting disk size to ~2.5TB (afair)

best shot it to use a board that has pcie so you can use the usual marvell/asm or jmb ahci capable chips

Thx for the detailed answer and for all the work u've done for this community! I am a lil bit confused still though. So if I want to use my current hardware I can but latest DSM would be 6.0? What loader should I use? I don't remember seeing jun's 1.01 anywhere...

Link to comment
Share on other sites

  • 2 weeks later...
On 1/27/2022 at 3:29 AM, IG-88 said:

i have not found driver for older kernel by looking a little with a search engine

OK. I think it is time to give up and use x540-t2 to replace. :)

many thanks!

 

Just found out that the PCI vendor of BCM57406 is 14E4:16D2. But it still not been recognized by the new driver.

 

Is the log in /var/log/messages file?


2022-02-07T11:50:18+08:00 DS918 kernel: [   26.186022] bnxt_en 0000:01:00.0 (unnamed net_device) (uninitialized): HWRM interface 1.8.0 does not match driver interface 0.7.8.
2022-02-07T11:50:18+08:00 DS918 kernel: [   26.186027] bnxt_en 0000:01:00.0 (unnamed net_device) (uninitialized): Please update driver or firmware with matching interface versions.
2022-02-07T11:50:18+08:00 DS918 kernel: [   26.193866] bnxt_en 0000:01:00.1 (unnamed net_device) (uninitialized): HWRM interface 1.8.0 does not match driver interface 0.7.8.
2022-02-07T11:50:18+08:00 DS918 kernel: [   26.193869] bnxt_en 0000:01:00.1 (unnamed net_device) (uninitialized): Please update driver or firmware with matching interface versions.

 

2022-02-07T11:50:20+08:00 DS918 kernel: [   28.512700] bnxt_en 0000:01:00.0 eth1: Error (timeout: 500) msg {0xffff00b0 0xffff000f} len:0
2022-02-07T11:50:20+08:00 DS918 kernel: [   28.550541] bnxt_en 0000:01:00.0 eth1: hwrm req_type 0x60 seq id 0x2d error 0x2
2022-02-07T11:50:20+08:00 DS918 kernel: [   28.557871] bnxt_en 0000:01:00.0 eth1: hwrm_ring_grp alloc failure: 2
2022-02-07T11:50:20+08:00 DS918 kernel: [   29.001879] bnxt_en 0000:01:00.0 eth1: Error (timeout: 500) msg {0xffff0061 0xffff005f} len:0
2022-02-07T11:50:20+08:00 DS918 kernel: [   29.012692] bnxt_en 0000:01:00.0 eth1: bnxt_init_nic err: 2
2022-02-07T11:50:21+08:00 DS918 kernel: [   29.503496] bnxt_en 0000:01:00.0 eth1: Error (timeout: 500) msg {0xffff00b0 0xffff007f} len:0
2022-02-07T11:50:21+08:00 DS918 kernel: [   29.541163] bnxt_en 0000:01:00.0 eth1: hwrm req_type 0x60 seq id 0x85 error 0x2
2022-02-07T11:50:21+08:00 DS918 kernel: [   29.548490] bnxt_en 0000:01:00.0 eth1: hwrm_ring_grp alloc failure: 2
2022-02-07T11:50:21+08:00 DS918 kernel: [   29.993551] bnxt_en 0000:01:00.0 eth1: Error (timeout: 500) msg {0xffff0061 0xffff00bf} len:0
2022-02-07T11:50:21+08:00 DS918 kernel: [   30.004512] bnxt_en 0000:01:00.0 eth1: bnxt_init_nic err: 2

messages

Edited by Zemmy
more info
Link to comment
Share on other sites

15 hours ago, Zemmy said:

2022-02-07T11:50:18+08:00 DS918 kernel: [   26.186022] bnxt_en 0000:01:00.0 (unnamed net_device) (uninitialized): HWRM interface 1.8.0 does not match driver interface 0.7.8.

that was what i would have been looking for, driver ist loaded but there are other problems (pci id is ok)

in theory you could downgrade the (flashed) firmware of the card but thats often not possible

kernel 4.4.180 used in dsm 7.0 is about two years newer but seem to contain the same driver v0.1.2.4, so its unlikely dsm 7.0 will help here

 

15 hours ago, Zemmy said:

OK. I think it is time to give up and use x540-t2 to replace

we have newer drivers form these models and can make newer if needed

 

Link to comment
Share on other sites

8 hours ago, IG-88 said:

in theory you could downgrade the (flashed) firmware of the card but thats often not possible

I successfully downgrade the firmware from 21.xxx to 20.06.04.03 with the install packages from Dell. (failed to downgrade further to 20.02.xx)

Still not working.

Anyway, many thanks.

9 hours ago, IG-88 said:

we have newer drivers form these models and can make newer if needed

It the new one supports ixgbevf?

Link to comment
Share on other sites

17 hours ago, Zemmy said:

It the new one supports ixgbevf?

that driver along with igbvf and i40evf are in the extra for a long time but are not loaded (same as virtio)

they can be tested by loading them on your own

i've started fixing some problems and add things with 3617 and will continue with the other extras

new 3617 will shortly be on the 1st page

from your messages file it looked like you had 20 cores and only using 8 as from the limit of 918+

if it comes to cpu usage 3617 is 16 threads in 6.2 and from the kernel config file it look like 24 threads in 7.0

 

Link to comment
Share on other sites

12 hours ago, IG-88 said:

that driver along with igbvf and i40evf are in the extra for a long time but are not loaded (same as virtio)

they can be tested by loading them on your own

i've started fixing some problems and add things with 3617 and will continue with the other extras

new 3617 will shortly be on the 1st page

from your messages file it looked like you had 20 cores and only using 8 as from the limit of 918+

if it comes to cpu usage 3617 is 16 threads in 6.2 and from the kernel config file it look like 24 threads in 7.0

 

Thanks for the advice! The 19-10900t es+Z490 platform was temporally set up for testing. :)

Edited by Zemmy
more info
Link to comment
Share on other sites

4 hours ago, Zemmy said:

One more question: If I turn off the Hyper-threading, does it still uses 8 cores of 10?

yes , now you might use 4 real cores and 4 as HT threads and as HT is just 20-25% of a real core, so now its like 5 real cores and when disabling HT its 8 real cores

  • Like 1
Link to comment
Share on other sites

7 minutes ago, DraganLegend said:

i have a killer lan E2500 . have any work driver on dsm 6.2.3 or 7.0.1 for killer lan E2500 ? i want to try .

i do have kernel patches for the Killer E2400 and E2500, the patches make the hardware treated like a normal atheros nic

https://xpenology.com/forum/topic/39797-msi-z270-m7

 

from what i can see in my kernel sources for 918+ only got for E2400, adding E2500 should be more or less the same as for E2400

as i'm already working on newer extra's (6.2.3) this weekend i will add that too

 

  • Like 1
Link to comment
Share on other sites

2 minutes ago, IG-88 said:

我確實有 Killer E2400 和 E2500 的內核補丁,這些補丁使硬件被視為普通的 atheros nic

https://xpenology.com/forum/topic/39797-msi-z270-m7

 

從我在我的內核源代碼中看到的 918+ 僅適用於 E2400,添加 E2500 應該或多或少與 E2400 相同

因為我本週末已經在處理更新的額外內容(6.2.3),所以我也會添加它

 

thank you ,I wait update. 

Link to comment
Share on other sites

On 2/12/2022 at 3:35 AM, Derrik said:

msi b460 mortar  8125b can not be drivered.

what loader and extra.lzma version did you use?

extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.6 got the latest 8125 driver, that one should work, if you used this one then add a 1G nic to get it working and provide a log (dmesg), i dont own a 8125 based card so i cant test

 

3615/17 is no joy as the newer realtek 8125 driver versions dont compile against kernel 3.10 so no newer driver then the one that already is there (newer card revisions dont work, presumably depending on phy chip)

Link to comment
Share on other sites

On 2/14/2022 at 5:46 AM, IG-88 said:

what loader and extra.lzma version did you use?

extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.6 got the latest 8125 driver, that one should work, if you used this one then add a 1G nic to get it working and provide a log (dmesg), i dont own a 8125 based card so i cant test

 

3615/17 is no joy as the newer realtek 8125 driver versions dont compile against kernel 3.10 so no newer driver then the one that already is there (newer card revisions dont work, presumably depending on phy chip)

I used the extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.6. I added  a 1G nic(intel i210)  and it can't be driven either.

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