From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Forster Subject: Re: Question about unsupported transceivers Date: Thu, 15 Oct 2015 14:46:29 +0000 Message-ID: References: <561D6AD2.9000308@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: Alexander Duyck Return-path: Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0077.outbound.protection.outlook.com [65.55.169.77]) by dpdk.org (Postfix) with ESMTP id 9C2AF91B3 for ; Thu, 15 Oct 2015 16:46:31 +0200 (CEST) In-Reply-To: <561D6AD2.9000308@gmail.com> Content-Language: en-US Content-ID: <217F0E8C99D63B48A53E86E5E69FFF12@namprd06.prod.outlook.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 10/13/15, 4:34 PM, "Alexander Duyck" wrote: >If you are using Intel's out-of-tree ixgbe driver I believe the module >parameters are comma separated with one index per port. So if you have >two ports you should be passing "allow_unsupported_sfp=3D1,1", and for 4 >you would need four '1's. This seemed very promising. I compiled and installed the out of tree ixgbe driver and set the option in /etc/modprobe.d/ixgbe.conf. dmesg shows all eight "allow_unsupported_sfp enabled" messages but the last four ports still error out with the unsupported SFP message when running the tests. Before I start arbitrarily trying to patch out parts of the SFP verification code in ixgbe, are there any other tips I should know? Alex Forster