Date: Mon, 11 Aug 2008 13:40:32 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Markus Vervier" <markus@vervier.info> Cc: freebsd-stable@freebsd.org Subject: Re: em(4) on FreeBSD is sometimes annoying Message-ID: <2a41acea0808111340o7b506804u9e4c95f1af22b95c@mail.gmail.com> In-Reply-To: <48A0A1D9.8030601@vervier.info> References: <489C4129.4090303@vervier.info> <489C88DB.6030000@vervier.info> <2a41acea0808081131m1eddc4caib0963c8a5443afd2@mail.gmail.com> <200808110819.53914.josh@tcbug.org> <20080811140249.GA27379@eos.sc1.parodius.com> <2a41acea0808110928h10d54441o7d49b11a60406934@mail.gmail.com> <48A0A1D9.8030601@vervier.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 11, 2008 at 1:32 PM, Markus Vervier <markus@vervier.info> wrote: > Jack Vogel wrote: >> >> Seems possibly a BIOS thing, if not that bad cable, bad link partner >> maybe?? >> > > I had the problem with all sorts of switches / cables. How can I dump my > EEPROM settings if that helps? I didn't mean the NIC EEPROM, but the system BIOS, make sure you are running the version that Jeremy said he was, if that matches you might go look at settings in the BIOS that are about management. I thought you told us that when you had a back to back connection that it worked, no?? Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0808111340o7b506804u9e4c95f1af22b95c>