falconhk2007

Warning: use at your own risk https://www.dropbox.com/s/0g7t16qconftb ... 2.bin?dl=0

cannot upload attachment here. quota reached.

I didn't flash the rom, I just follow the Mellanox manual (MFT) to customize the firmware for OEM card by editing the INI and use the MLX file for flashing.

Hi Spyrule, Thanks for the information. I finally flashed the firmware to 2.9.1200 successfully. Referenced your thread information and other thread, I did not use the switch of --ALLOW_PSID_CHANGE. I modified the generic firmware INI file so that the HP PSID (HP_0F60000010) is kept. After flashing the new firmware, it now can passthrough the Mellanox ConenctX-2 card to VM running DSM 5.1 & 5.2 under ESXI 6.0. There is no more error message, and IP address can be configured manually in DSM. Both bare metal and VM are tested in 5.1 & 5.2 version, both are OK. The file copying operation is not that impressive, around 150MB - 250MB per second. Thanks again for all you guys' help.

My ESXI version is 6.0.

My system supports passthrough, I tried passthrough for dual port network card, display card successfully to VM before. I am using HP Microserver Gen 8 with E3-1265Lv2 CPU. I rebooted after setting passthrough and in vSphere screen showed passthrough had been in effect. I did not add any special setting, just add the PCI device for the Mellanox ConnectX-2 to the VM for DSM 5.1 or DSM 5.2. As you can see from the output of lspci, it shows, 03:00.0 Class 0200: Device 15b3:6750 (rev b0) I am thinking if it was due to the firmware of the ConnectX-2 is not upgraded to latest (2.9.1200), current on card is 2.9.1000. Since it is an HP OEM card from Mellanox which I am still searching where to download the required firmware from HP. Please let me know if any hint on where to download the required firmware. It stated in VMware website that the required firmware for ConnectX-2 should be 2.9.1200 for ESXI 5.5Ux.

Hi Trantor, I did try manually insmod the two ko files in 5.1. No error for executing the insmod commands, but error in dmesg as follows, [ 309.891940] mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000 [ 309.891941] mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000 [ 309.891942] mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000 [ 309.891943] mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000 [ 309.891944] mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000 [ 309.891945] mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000 [ 309.899328] mlx4_core 0000:03:00.0: NOP command failed to generate interrupt (IRQ 77), aborting. [ 309.899330] mlx4_core 0000:03:00.0: BIOS or ACPI interrupt routing problem? [ 309.908571] mlx4_core 0000:03:00.0: PCI INT A disabled [ 309.908581] mlx4_core: probe of 0000:03:00.0 failed with error -16 there were a lot of "mlx4_core 0000:03:00.0: Completion event for bogus CQ 00000000" message which I just cut a few lines to show here. I tried both 5.1 & 5.2 VM failed, bare-metal only tried 5.1 successful but not tried 5.2 as I think it should be ok.

yes, I am using ESXI with the ConnectX-2 card passthrough to VM running DSM 5.1. Both mlx4_core.ko and mlx4_en.ko not loaded even I edited the rc file. I can see the card present in the VM through lspci command the mlx4_core.ko and mlx4_en.ko could be loaded with xpenology 5.2 boot image here is the log extracted in 5.2 boot image lspci 02:00.0 Class 0200: Device 8086:100f (rev 01) 03:00.0 Class 0200: Device 15b3:6750 (rev b0) dmesg|grep mlx4 [ 30.892904] mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011) [ 30.892906] mlx4_core: Initializing 0000:03:00.0 [ 33.201898] mlx4_core 0000:03:00.0: irq 72 for MSI/MSI-X [ 33.201933] mlx4_core 0000:03:00.0: irq 73 for MSI/MSI-X [ 33.201983] mlx4_core 0000:03:00.0: irq 74 for MSI/MSI-X [ 33.202002] mlx4_core 0000:03:00.0: irq 75 for MSI/MSI-X [ 33.202021] mlx4_core 0000:03:00.0: irq 76 for MSI/MSI-X [ 33.202040] mlx4_core 0000:03:00.0: irq 77 for MSI/MSI-X [ 33.313248] mlx4_core 0000:03:00.0: NOP command failed to generate MSI-X interrupt IRQ 77). [ 33.313252] mlx4_core 0000:03:00.0: Trying again without MSI-X. [ 33.426408] mlx4_core 0000:03:00.0: NOP command failed to generate interrupt (IRQ 73), aborting. [ 33.426410] mlx4_core 0000:03:00.0: BIOS or ACPI interrupt routing problem? [ 34.437841] mlx4_core: probe of 0000:03:00.0 failed with error -16 ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0C:29:64:F4:8E inet addr:192.168.0.124 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe64:f48e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:779 errors:0 dropped:0 overruns:0 frame:0 TX packets:362 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:233280 (227.8 KiB) TX bytes:57723 (56.3 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3023 (2.9 KiB) TX bytes:3023 (2.9 KiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) But when I boot in bare metal, everything works well. The ConnectX-2 recognized in DSM and can communicate with Win7 PC.

i installed the connectx-2 card but got error code during boot up, any idea whats worng? i tested in both 5.1 and 5.2 xpenology with rc file modified under ESXI VM with the card passthru. Both failed, nothing can be seen in ifconfig -a

Below is the dmesg information after i plugged in the Contex DTV-01 USB stick but the DSM Panel still doesn't show any external usb device is connected: [ 525.247101] usbcore: deregistering interface driver dvb_usb_cxusb [ 528.348829] dsmnotify.cgi[6374]: segfault at 0 ip 000000000804ccb8 sp 00000000ffe65c30 error 6 [ 528.797115] usb 1-3: new high-speed USB device number 4 using ehci_hcd [ 529.203259] dvb_usb_cxusb: probe of 1-3:1.0 failed with error -22 [ 529.203383] usbcore: registered new interface driver dvb_usb_cxusb BTW, I found the firmware for "LGS8GL5" chipset of this DMB-TH USB stick Contex DTV-01: https://github.com/cernekee/linux-firmw ... lgs8g75.fw I tried to put it in volume1/@appstore/VideoStation/etc/KernelFirmwares/ folder but the USB stick still cannot be detected. Can anyone help with this issue? I encountered the same problem in DSM5.0. I tried to use Sancome's NanoBoot x64 lately, it works with DTV-01. But I do not know the stabiility of NanoBoot. You may take it a shot. http://nas1.cn/thread-83382-1-1.html

I copied the same content from your /etc/rc.local, the last few rows of dmesg as follows (unplugged and plug in again, end with error -22 in dvb_usb_cxusb) [ 55.168185] findhostd uses obsolete (PF_INET,SOCK_PACKET) [ 58.232132] dvb_usb_cxusb: probe of 1-3:1.0 failed with error -22 [ 58.232804] usbcore: registered new interface driver dvb_usb_cxusb [ 180.661859] usb 1-3: USB disconnect, device number 2 [ 180.812444] usbcore: deregistering interface driver dvb_usb_cxusb [ 192.578114] usb 1-3: new high-speed USB device number 4 using ehci_hcd [ 193.017368] dvb_usb_cxusb: probe of 1-3:1.0 failed with error -22 [ 193.017482] usbcore: registered new interface driver dvb_usb_cxusb any idea? the lsmod |grep dvb_usb_cxusb returned dvb_usb_cxusb 64754 0 dib0070 8680 1 dvb_usb_cxusb dib7000p 29487 1 dvb_usb_cxusb dvb_usb 15274 6 dvb_usb_cxusb,dvb_usb_nova_t_usb2,dvb_usb_dibusb _common,dvb_usb_technisat_usb2,dvb_usb_pctv452e,dvb_usb_cinergyT2 usbcore 158988 33 dvb_usb_cxusb,dvb_usb_nova_t_usb2,dvb_usb_techni sat_usb2,dvb_usb_pctv452e,dvb_usb_cinergyT2,ttusb_dec,pvrusb2,em28xx_dvb,em28xx_ alsa,em28xx,hdpvr,dvb_ttusb_budget,dvb_usb,snd_usb_audio,snd_usbmidi_lib,zd1211r w,rtl8187,rtl8192cu,rtl_usb,mwifiex_usb,libertas_tf_usb,ar5523,carl9170,ath9k_ht c,usbhid,usblp,usb_storage,uhci_hcd,etxhci_hcd,xhci_hcd,ohci_hcd,ehci_hcd

Did you load the drivers in /etc/rc.local? Thanks for your reply. I have added the driver modules into the rc.local #!/bin/sh # Optware setup [ -x /etc/rc.optware ] && /etc/rc.optware start source /etc/rc.subr source /.gnoboot/modules.d/03-wifi.conf source /.gnoboot/modules.d/05-media.conf SYNOLoadModules $WIFI_MOD SYNOLoadModules $MEDIA_MOD SYNOLoadModules $VMWARE exit 0 The lsmod showing the following:- usbcore 158988 32 dvb_usb_nova_t_usb2,dvb_usb_technisat_usb2,dvb_usb_pctv452e,dvb_usb_cinergyT2,ttusb_dec,pvrusb2,em28xx_dvb,em28xx_alsa,em28xx,hdpvr,dvb_ttusb_budget,dvb_usb,snd_usb_audio,snd_usbmidi_lib,zd1211rw,rtl8187,rtl8192cu,rtl_usb,mwifiex_usb,libertas_tf_usb,ar5523,carl9170,ath9k_htc,usbhid,usblp,usb_storage,uhci_hcd,etxhci_hcd,xhci_hcd,ohci_hcd,ehci_hcd But still there is no dvb dongle exist in video station. When I unplug the stick, dmesg shows [ 512.953063] usb 1-2.1: USB disconnect, device number 5 When I plug in the stick, dmesg shows [ 629.320965] usb 1-2.1: new high-speed USB device number 6 using xhci_hcd After plug in the stick, the information under DSM show the following:- USB Stick - Conexant Systems (Rockwell), Inc. Thanks. Hi mcdull, I am using Contex DTV-01 (Conexant Systems) too but cannot get it works in DSM 5.0, are you using DSM5.0 with your Magic Pro PCTV USB? I can use my Contex DTV-01 in DSM 4.3 (same alpha 10.5 image) without any creation of file /etc/rc.local. do you have any idea?

Its easy. Install Trantor's 4.3 test build (with newer bzImage), then login into ssh and copy /proc/bus/pci into for example /root/pci and append content of my file /root/pci/devices-append to your /root/pci/devices. Then edit /etc/rc and insert mount --rbind /root/pci/ /proc/bus/pci/ after "export HOME PATH". Reboot and it should work. I followed all the steps against a physical PC (not VM), which can install DSM 4.2 before, but the hard disk still not mounted. Is it expected? or the steps are only true for VM environment?

Any x64 version of DSM 4.2 3211 release here?