-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Vogel wrote:
| I have reproduced the problem, you are correct. Thank you for
| persisting thru my doubts :)
Always persisting to help improving FreeBSD. Another odd thing I noticed
today:
When dual-booting Windows on the same machine and doin
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
resu
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?
--
Markus
___
freebsd-stable@freebsd.org mailing
Mike Tancsa schrieb:
If you manually type,
dhclient em0
No, even if I type ifconfig em0 down && ifconfig em0 up it won´t work.
The interface just gets no link until I reload the driver with a cable
plugged.
--
Markus
___
freebsd-stable@freebsd.org m
Jack Vogel schrieb:
"me too" 's are of little help. Please elaborate on your "exact same", since
each person's perception will be slightly different.
Hi Jack,
maybe read it like: Thinkpad X60 1706GMG affected too, so the problem is
not specific to Martins machine.
I can write the same s
Hi,
I just stumbled upon this thread. I experience the exact same behaviour
as Martin on my Thinkpad X60:
Thinkpad X60 Model: 1706GMG
BIOS-Version 2.15 (7BETD4WW)
FreeBSD 7.0 STABLE amd64 (from about two weeks ago) - same situtation on
7.0-RELEASE i386
--
Markus
___
