Date: Wed, 13 Aug 2008 12:04:59 +0200 From: Markus Vervier <markus@vervier.info> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: em(4) on FreeBSD is sometimes annoying Message-ID: <48A2B1CB.7060303@vervier.info> In-Reply-To: <2a41acea0808111340o7b506804u9e4c95f1af22b95c@mail.gmail.com> 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> <2a41acea0808111340o7b506804u9e4c95f1af22b95c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote: > > 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'm now running the latest BIOS for my X60 version 2.22 with the same results. Jeremy runs version 1.15 but on a T60. > I thought you told us that when you had a back to back connection that it > worked, no?? Sorry, it does not work when having a b2b connection, never said that. But I noticed another thing: It is important that the device was up without a cable connected: 1. power off completely 2. boot freebsd without a cable connected 3. in a rootshell do ifconfig em0 up 4. connect the cable 5. no link -- Markus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48A2B1CB.7060303>