From owner-freebsd-hackers Tue Sep 14 12:20:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 063E814FFD for ; Tue, 14 Sep 1999 12:20:36 -0700 (PDT) (envelope-from rene@canyon.demon.nl) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11Qy83-00018N-00; Tue, 14 Sep 1999 19:20:35 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id UAA00578; Thu, 14 Sep 2000 20:10:54 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <200009141810.UAA00578@canyon.demon.nl> Subject: Re: de0 strangenesses In-Reply-To: <199909130856.KAA33966@gil.physik.rwth-aachen.de> from Christoph Kukulies at "Sep 13, 1999 10:56:09 am" To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Thu, 14 Sep 2000 20:10:54 +0200 (CEST) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think i've got a similar problem. This involves a DE500 (de0 driver) ethernet card and a 100 Mbit UTP. The problem was that somehow the driver didn't detect the 100Mbit and always switched to 10Mbit. The workaround that I use is a simple script "/etc/start_if.de0" with the following contents: # workaround 10/100Mbit start problem ifconfig de0 192.168.1.2 media 100baseTX ifconfig de0 down sleep 2 ifconfig de0 up Since I started using this script the machine always started with the 100baseTX interface active. Rene > On a 3.0-current of October 1998 I'm having often trouble with de0. > The machine often reboots over night (when either the locate db is built or > some other big job - like mirror - is running). Anyway, after the reboot, > often de0 is dead. > > This happend today again. When I came into the office I could not > ping said machine. I sat at the console, logged in. The machine was > perfectly alive, only the de0 interface didn't work at the BNC network. > > I did a ifconfig de0 down and exactly with doing that I got a kernel message > from the driver: de0 BNC interface enabled (or something like that). > Doing an ifconfig de0 up right after that the interface continued working > at the BNC port. > > Can the driver writer(s) comment whether there have been changes to the driver > WRT that behaviour so I can expect that with either 3.2 or -current > the problem would be gone? -- Rene de Vries http://www.tcja.nl/~rene; mailto:rene@tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message