From owner-freebsd-infiniband@FreeBSD.ORG Fri May 29 16:47:47 2015 Return-Path: Delivered-To: freebsd-infiniband@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD3B1FD9 for ; Fri, 29 May 2015 16:47:47 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A2D80102D for ; Fri, 29 May 2015 16:47:47 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-07v.sys.comcast.net with comcast id Zsnj1q0062GyhjZ01snl8v; Fri, 29 May 2015 16:47:45 +0000 Received: from resmail-ch2-217v.sys.comcast.net ([162.150.48.251]) by resomta-ch2-09v.sys.comcast.net with comcast id Zsnl1q00A5RAVJS01snlL2; Fri, 29 May 2015 16:47:45 +0000 Date: Fri, 29 May 2015 16:47:45 +0000 (UTC) From: rondzierwa@comcast.net To: Vadim Alimov Cc: freebsd-infiniband@freebsd.org Message-ID: <27141688.23164574.1432918065254.JavaMail.zimbra@comcast.net> In-Reply-To: <556890F9.6040208@alimov.net> References: <556847FF.8000004@alimov.net> <1801993404.23038823.1432909934595.JavaMail.zimbra@comcast.net> <556890F9.6040208@alimov.net> Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 MIME-Version: 1.0 X-Originating-IP: [::ffff:50.241.136.195] X-Mailer: Zimbra 8.0.7_GA_6031 (ZimbraWebClient - FF28 (Win)/8.0.7_GA_6031) Thread-Topic: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Thread-Index: ndTMsW++G9sy7nET2ph2PAnc285lwQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1432918065; bh=ByeWZmaxmmYkIpYOwk6OlzzZDELQOcE9VcBuh8xEeWo=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=JlntPFFBv9HR2VDKRZm4JWh/s512omQm2ZaWrrYN4UChZVhbH3tpX4aweMlVd0sRo i9dj8u1c1Z5pWm6q81+vNBxBvTOGLJ4CmcheH8TrIWpHfeKZgtkf0zuUbUZvAtnLmP MeP4X65AouXziyHhLSkuwuQ3PMUhWAmCNuYtuVLe4tgH0fG/Mq1CdeTdI0miSkc4jZ OrRd6JAho95vSAn6ktFViw+D/ZVlQYhDqK3LeKDR6FJzFraZhwmsrcJ62jB670k8Ow VXfDpuNEzVAks5WypYLm78DgEODQWJkeOTZlEZiEGE5Jyud21HlRKlnAFegXdCAfo3 4SERNgmxBJqkw== Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 16:47:48 -0000 Sounds like either the cable is wrong, or the other end that its connected to isn't active. Try connecting both ports together. If the cable is right, they both should see carrier. Once the cable is connected, you might have to do an ifconfig on each one to turn it on. something like ifconfig mlxen0 192.168.20.1 netmask 255.255.255.0 up ifconfig mlxen1 92.168.20.2 netmask 255.255.255.0 up ron. ----- Original Message ----- From: "Vadim Alimov" To: rondzierwa@comcast.net Cc: freebsd-infiniband@freebsd.org Sent: Friday, May 29, 2015 12:16:57 PM Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Yeah, there are mlxen0 and mlxen1 devices, but they are "no carrier" whatever i do. As I guess, there are two possible reasons: 1) the qsfp cable i use is incompatible (has a wrong firmware) with mellanox chip 2) freebsd driver does not work I'll try to setup linux. If it goes the same i'll have to order native mellanox cable. I'll write you down the results. Thanks. Regards, Vadim. Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 On 05/29/2015 05:32 PM, rondzierwa@comcast.net wrote: You seem to have gotten further than I did, I could not get a driver to recognize the card I was trying to use. Our current approach has been to switch to Solaris. Our options are more plentiful there, and coverage for various hardware seems more complete. >From your dmesg output, it looks like the ethernet device should be there. Try "ifconfig -a". You should see a new device called mlxen0: My plan was to hard configure the IB links in the rc.conf file like: ifconfig_mlxen0="inet 192.168.22.1 netmask 255.255.255.0" ron. ----- Original Message ----- From: "Vadim Alimov" To: freebsd-infiniband@freebsd.org Sent: Friday, May 29, 2015 7:05:35 AM Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Hi. Did you manage to bring up a mellanox NIC with qsfp port as an ethernet device? I'm facing exactly the same issue. mlx4_core0: mem 0xfbd00000-0xfbdfffff,0xf9800000-0xf9ffffff irq 16 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v2.1 (May 28 2015) mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.1 (May 28 2015) mlxen0: Ethernet address: 00:21:cc:49:48:93 mlx4_en: mlx4_core0: Port 1: Using 8 TX rings mlx4_en: mlx4_core0: Port 1: Using 8 RX rings Forward thanks for help. Vadim. -- Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 _______________________________________________ freebsd-infiniband@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-infiniband To unsubscribe, send any mail to "freebsd-infiniband-unsubscribe@freebsd.org"