Date: Wed, 29 Sep 1999 17:45:46 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: Bill Paul <wpaul@skynet.ctr.columbia.edu> Cc: current@freebsd.org Subject: Re: Is the wb driver broken? Message-ID: <XFMail.990929174546.jdp@polstra.com> In-Reply-To: <199909300040.UAA03387@skynet.ctr.columbia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990929174546.jdp>