From owner-freebsd-current Mon Sep 21 19:53:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24991 for freebsd-current-outgoing; Mon, 21 Sep 1998 19:53:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24829 for ; Mon, 21 Sep 1998 19:52:09 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.9.1/kong/0.01) with SMTP id GAA04519; Tue, 22 Sep 1998 06:50:51 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Tue, 22 Sep 1998 06:50:50 +0400 (MSD) From: Hostas Red To: Bill Paul cc: current@FreeBSD.ORG Subject: xl driver problems In-Reply-To: <199809200152.VAA20479@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Sat, 19 Sep 1998, Bill Paul wrote: >> Yes, it always says that. And it always plugged into network. > Something tells me your cabling should be checked. My cabling is OK, it's up for 1 year now, and no problems was here before. Not under freebsd vx driver, not under windows. > > ifconfig_xl0="inet 195.19.252.147 netmask 255.255.255.0 media 10baseT/UTP mediaopt half-duplex" > > Do it like that and use ifconfig to force the card to 10baseT/UTP like I > said to do before. Then tell me if it still gives you trouble. I did that. And for past 24 hours 'watchdog timeout' happened 3 times: xl0: watchdog timeout xl0: no carrier - transceiver cable problem? What sort of info you need now, if any? Adios, /KONG PS: I definetly have NO cable problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message