From owner-freebsd-current  Wed Sep 29 17:46: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 7228115285
	for <current@freebsd.org>; Wed, 29 Sep 1999 17:45:48 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA18576;
	Wed, 29 Sep 1999 17:45:47 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id RAA23734;
	Wed, 29 Sep 1999 17:45:46 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929174546.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199909300040.UAA03387@skynet.ctr.columbia.edu>
Date: Wed, 29 Sep 1999 17:45:46 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Paul wrote:
> 
> I converted the wb driver to miibus ages ago. Your description makes
> it sound like the problem just magically appeared yesterday. That's
> a no-no, m'kay?

Thanks for the quick reply.  I didn't mean to imply anything.  I
have one machine with a Winbond running current a week old, and
never saw the problem there.  I also notice that there have been
commits to a lot of the network interfaces recently, including wb.
In any case, I'm a bit stressed out over having broken cvsup-master,
so please forgive me if I clumsily gave offense.

>> cvsup-master# ifconfig wb0 inet 204.216.27.25  netmask 255.255.255.240 
>>  media 100baseTX mediaopt half-duplex
>> ifconfig: SIOCSIFMEDIA: Device not configured
> 
> You don't need to explicitly specify mediaopt half-duplex anymore.
> Specifying media 100baseTX without mediaopt full-duplex implies
> half-duplex. Leave off the mediaopt half-duplex part and it will work.

OK, I did that and it made the SIOCSIFMEDIA message go away.  But
now it's not showing carrier:

Doing initial network setup: hostname domain.
wb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 204.216.27.25 netmask 0xfffffff0 broadcast 204.216.27.31
        ether 00:00:e8:18:5b:1d 
        media: 100baseTX status: no carrier
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none

Any other ideas?

Thanks,
John


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message