MCX342A driver "mlx4_core" issues about rp-ext HOT 16 CLOSED

mlx4_core：Handles low-level functions like device initialization and firmware commands processing. Also controls resource allocation so that the InfiniBand, Ethernet and FC functions can share a device without interfering with each other.
mlx4_en：Handles Ethernet specific functions and plugs into the netdev mid-layer.
This network card is divided into ib mode and Ethernet mode. The official document points out that mlx4_core seems to be used in ib mode, so whether it is possible to add mlx4_en for Ethernet mode

from rp-ext.

Added mlx4_en to the same extension. Now mlx4_core includes also mlx4_en

from rp-ext.

After two days of testing, I found out that I don’t know what the reason is. My MCX312B-XCCT does not work properly on DS3615xs-7.0.1-42218, but it is on the official support list of Synology. Use the mlx4_core of your DS918+. Can't work, it all goes well in windows

from rp-ext.

Well generally speaking 918 doesn’t support any pci-e network adapter. I’m afraid that you should stick on ds3615xs loader. And can you please send here a

dmesg | grey mlx
lsmod
Ip a
ethtool -I ethx
lspci -nq

from rp-ext.

I will check its usage on DS3615xs today, at least I hope it works normally on DS3615xs, so that I can continue to test DS918+

from rp-ext.

from rp-ext.

I am sure that my hardware ID is 15b3:1003, I also loaded mlx4_core.ko and mlx4_en.ko, and it seems to be successful, but it does not appear in my network card list

from rp-ext.

ethtool -I ethx
The magic is that although it is not in the list, it can be viewed through the tool

from rp-ext.

Very good, now it can work on DS918+7.0.1-42218, I did the following:
insmod /usr/lib/modules/mlx4_core.ko
insmod /usr/lib/modules/mlx4_en.ko(must)
ifconfig eth1 up(must)
ifconfig eth2 up(must)
If I don’t do the following, it will be displayed using ethtool as in my previous answer, but it will not appear in the ifconfig list.
There is another problem. Since you updated the mlx4_core file 14 hours ago, an error will be prompted during compilation.
The only problem now is to let mlx4_core.ko and mlx4_en.ko be automatically loaded at boot, and automatically ifconfig eth1 up and ifconfig eth2 up

from rp-ext.

from rp-ext.

There is a missing ","
I can compile successfully after repairing locally, but ds918+ is installed in an infinite loop

from rp-ext.

Then that’s great news. I’ll update the extension.

from rp-ext.

Unfortunately the modules were built with binutils 2.31 and were failing to load with error Unknown Rela 4.

When any extension fail to load it will exit with error core 99 which is then misinterpreted as exit 99 by DSM and will fall into an install loop.

Fixed the extension typo and added an script on_os_load to try to bring mlx4 interfaces up. Please update how this works for you.

from rp-ext.

I used a new driver, DS918+ still cannot be searched, I guess it may be because there is no ifcofnig up

from rp-ext.

Please be aware that on_os_boot script that will bring the interfaces up, will not run on the installation phase but only after successful install and OS boot

from rp-ext.

What should I do, is there a way to use it during installation

from rp-ext.