Date: Fri, 20 Feb 2015 12:13:43 -0500 From: John Jasen <jjasen@gmail.com> To: Jack Vogel <jfvogel@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: FreeBSD 10.1: Intel dual port 10GbE card (82599EB) second port not present? Message-ID: <54E76B47.8080907@gmail.com> In-Reply-To: <CAFOYbckKJWWQWVbaM0j%2BenB__du-YcgDh_YjWsA9364o339BUA@mail.gmail.com> References: <mailman.79.1423742401.43777.freebsd-net@freebsd.org> <54DCB8F2.5090809@gmail.com> <CAFOYbckKJWWQWVbaM0j%2BenB__du-YcgDh_YjWsA9364o339BUA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'll also note this seems to be somewhat unpredictable. I installed a dual port intel 10GbE card into one of the systems, I have not plugged SFP+ modules into them, and three out of four interfaces were available with the fourth completely AWOL. Rebooting with hw.ix.unsupported_sfp=1 presented all four, as expected. As for a use case as to why someone would want this, building out systems before deployment comes to mind. Thanks! On 02/12/2015 11:11 AM, Jack Vogel wrote: > > > On Thu, Feb 12, 2015 at 6:30 AM, John Jasen <jjasen@gmail.com > <mailto:jjasen@gmail.com>> wrote: > > > > Date: Wed, 11 Feb 2015 20:47:15 +0000 > > From: Steven Hartland <killing@multiplay.co.uk > <mailto:killing@multiplay.co.uk>> > > To: freebsd-net@freebsd.org <mailto:freebsd-net@freebsd.org> > > Subject: Re: FreeBSD 10.1: Intel dual port 10GbE card (82599EB): > > second port not present? > > Message-ID: <54DBBFD3.7010801@multiplay.co.uk > <mailto:54DBBFD3.7010801@multiplay.co.uk>> > > Content-Type: text/plain; charset=windows-1252; format=flowed > > <snip> > > > Your problem looks like its the SFP's which are "unsupported" to > which > > the attach will fail with error EIO (5). > > > > You can set hw.ix.unsupported_sfp=1 in /boot/loader.conf to enable > > unsupported SFP's but be aware you "doing so your on your own". > > Thanks! hw.ix.unsupported_sfp=1 corrected the immediate problem. > > The network port that didn't come up does not yet have an SFP module > installed > > It seems the default behavior in FreeBSD is to not have the interface > available until a SFP is inserted. While a corner case, this does make > configuration prior to installation a bit more annoying. > > > Well, exactly what use would there be in having it "available" > with no media, its like saying you want your car available with > no wheels :) The media can make operation quite different, it > could be copper it could be fiber, the driver won't know until > there is something actually present, hence it cannot really do > "init" until then. > > Jack > > > > > _______________________________________________ > freebsd-net@freebsd.org <mailto:freebsd-net@freebsd.org> mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to > "freebsd-net-unsubscribe@freebsd.org > <mailto:freebsd-net-unsubscribe@freebsd.org>" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54E76B47.8080907>