Neohunter
-
Posts
5 -
Joined
-
Last visited
Posts posted by Neohunter
-
-
@Neohunter : Did you try to swith mode to eth like siszlai said ?you can also flip from IB to Eth by setting this module parameter, write directly in procfs
echo eth > /sys/bus/pci/devices/0000\:20\:00.0/mlx4_port2
echo eth > /sys/bus/pci/devices/0000\:20\:00.0/mlx4_port1
No - because as i understand this command switch only in current session, after reboot its reset reinitialization by driver
If I understand correctly, the IB stack of the mellanox driver is useless in this setup ?
PnoT and you only use the ethernet part of your adapter.
Yes - in my case i need only Ethernet part
This driver depend on mlx_compat that is not compatible with compat driver.
You need to add rmmod=compat in your syslinux.cfg in order to prevent XPEnoboot to load it (no other driver use it. it's maybe for some wifi drivers)
You mean what change string in syslinux.cfg like this
LABEL xpenology
MENU LABEL XPEnology DSM 5.2-5565
KERNEL /zImage
APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=compat
correct ?
-
@Neohunter : Did you try to swith mode to eth like siszlai said ?you can also flip from IB to Eth by setting this module parameter, write directly in procfs
echo eth > /sys/bus/pci/devices/0000\:20\:00.0/mlx4_port2
echo eth > /sys/bus/pci/devices/0000\:20\:00.0/mlx4_port1
No - because as i understand this command switch only in current session, after reboot its reset reinitialization by driver
If I understand correctly, the IB stack of the mellanox driver is useless in this setup ?
PnoT and you only use the ethernet part of your adapter.
Yes - in my case i need only Ethernet part
This driver depend on mlx_compat that is not compatible with compat driver.
You need to add rmmod=compat in your syslinux.cfg in order to prevent XPEnoboot to load it (no other driver use it. it's maybe for some wifi drivers)
You mean what change string in syslinux.cfg like this
LABEL xpenology
MENU LABEL XPEnology DSM 5.2-5565
KERNEL /zImage
APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=compat
correct ?
-
Hello
My question is not quite InfiniBand - but about working Mellanox MHGH29-XTC (mode Ethernet 10GbE) As I understand it for running Ethernet 10GbE in XPEnoBoot 5.2-5565.2 all drivers (mlx4_core mlx4_en) are built, BUT!
On boot I see (in dmesg) adapter say - command 0xc failed: fw status = 0x40
This problem what driver non initialize adapter as Ethernet 10GbE (see https://community.mellanox.com/thread/1092)
It is necessary to initialize the driver stage is when loading DSM pass parameters - mlx4_core port_type_array = "2,2"
The question is how to do it?
Now I have added (on the advice of a reputable Trantor) in the / etc / rc and /etc.default/rc -
NET_DRIVERS = "dca e1000e i2c-algo-bit igb be2net ixgbe tn40xx mlx4_core mlx4_en"
But how to convey DSM boot option port_type_array = "2,2" - the driver
mlx4_core?
Please tell me how to do it?
p.s.
By the way, I checked the adapter job - after the download DSM
If unload the driver - rmmod mlx4_en mlx4_core
and then upload
insmod mlx4_core.ko port_type_array = "2,2"
insmod mlx4_en.ko
So on both adapters, the green LED
However, the network interface and the console DSM, and does not appear in the GUI
I think that if the driver is properly initialized at boot the DSM interface should appear in the console and GUI
-
Подскажите пожалуйста как можно указать что для определенного сетевого драйвера при загрузке нужно передать определенные параметры?
Дело в том, что в последней XPEnoBoot 5.2-5565.2 для работы Mellanox плат установлены драйвера mlx4_core и mlx4_en
В моем случае мне нужно чтобы они при запуске работали как Ethernet 10GbE(не Infiniband)
Для этого нужно сказать драйверу при загрузке - modprobe mlx4_core port_type_array="2,2"
тогда он настроит порты имено как Ethernet 10GbE
Вопрос - как это сделать ?
ps Для проверки уже при загруженном DSM в консоли
я выгружал оба драйвера - rmmod mlx4_en mlx4_core
затем
insmod mlx4_core.ko port_type_array="2,2"
insmod mlx4_en.ko
и по крайней мере на аппаратном уровне линк подымается - загорается зеленый индикатор на обеих платах и с другой стороны (ESXi 5.5) - Link UP
Но со стороны synology даже интерфейс не появляется - ни в консоли ни тем более в GUI
ifconfig - его не показывает. Я думаю что это из за того что нужно корректно инитить 10GbE именно на этапе загрузки DSM тогда и интерфейс скорее всего создасться
Вот только как этот параметр port_type_array="2,2" передать при загрузке драйверу mlx4_core - а то глянул в etc/RC и понял что разбираться можно долго
Заранее большое спасибо за любые советы
40GB InfiniBand Support at work on my Xpenology box!
in DSM 5.2 and earlier (Legacy)
Posted
Hm its very strange result - but step by step what i do
I copy mlx_compat mlx4_core_new mlx4_en_new in /lib/modules/
change /etc/rc & /etc.defaults/rc
NET_DRIVERS="dca e1000e i2c-algo-bit igb be2net ixgbe tn40xx mlx_compat mlx4_core_new mlx4_en_new"
add APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=compat in syslinux.cfg
and reboot
1 on DSM boot in console i see many failed on load some drivers
2 on the end of boot i see 2 string
updated mlx4_core - ok
updated mlx4_en - ok
and load on boot old mlx4_core & mlx4_en but not mlx4_core_new mlx4_en_new - why?
in dmg the same error
[ 7.137757] mlx4_core 0000:02:00.0: command 0xc failed: fw status = 0x40
[ 7.137887] mlx4_core 0000:02:00.0: command 0xc failed: fw status = 0x40
[ 7.150187] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.0 (Dec 2011)
After that i delete old mlx4_core & mlx4_en in lib/modules and rename mlx4_core_new mlx4_en_new to mlx4_core & mlx4_en
change /etc/rc & /etc.defaults/rc
NET_DRIVERS="dca e1000e i2c-algo-bit igb be2net ixgbe tn40xx mlx_compat mlx4_core mlx4_en"
and reboot
but loaded the same old mlx4_core & mlx4_en - why ? i delete old driver where loader find it ?
ps
update info about old version mlx4_core & mlx4_en
if i use it on boot and after that in console i enter
rmmod mlx4_en mlx4_core
insmod mlx4_core.ko port_type_array="2,2"
insmod mlx4_en.ko
and than /etc/rc.network restart
i see 2 new ethernet interface (in console and in GUI)
So may be we still use old version driver - because its work but not automatically in boot
one problem how add port_type_array="2,2" parameter on boot DSM ?