On Thu, Feb 12, 2015 at 6:30 AM, John Jasen <jja...@gmail.com> wrote:
> > > Date: Wed, 11 Feb 2015 20:47:15 +0000 > > From: Steven Hartland <kill...@multiplay.co.uk> > > To: freebsd-net@freebsd.org > > Subject: Re: FreeBSD 10.1: Intel dual port 10GbE card (82599EB): > > second port not present? > > Message-ID: <54dbbfd3.7010...@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 mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
