falconhk2007

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About falconhk2007

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Warning: use at your own risk https://www.dropbox.com/s/0g7t16qconftb ... 2.bin?dl=0
  2. 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.
  3. 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 co
  4. 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),
  5. 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 fo
  6. 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
  7. 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
  8. 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 thi
  9. 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
  10. 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_a
  11. 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?
  12. nas1.cn不接受注冊, 有nas1.cn賬號的,能犮一個鍵結給我下載那軟件嗎?falconhk2007@yahoo.com.hk