Date: Wed, 23 Oct 2002 22:40:12 +0100 From: ian j hart <ianjhart@ntlworld.com> To: Mike Tancsa <mike@sentex.net> Cc: Semen Ustimenko <semenu@FreeBSD.ORG>, stable@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/mii acphy.c Message-ID: <3DB7173C.35A6EFA0@ntlworld.com> References: <5.1.1.6.0.20021023112517.05e18a38@marble.sentex.ca> <5.1.1.6.0.20021023170004.05d0e3d8@marble.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
[Top post fixed]
> At 09:39 PM 23/10/2002 +0100, ian j hart wrote:
> >Mike Tancsa wrote:
> > >
> > > Hi,
> > > I noticed that on 2 boxes which were 4.7RC-1 going to stable as of this
> > > morning, do not work with DHCP assigned addresses.
> > >
> > > The nic is
> > >
> > > rl0: <RealTek 8139 10/100BaseTX> port 0xdc00-0xdcff mem
> > > 0xe1c10000-0xe1c100ff irq 12 at device 9.0 on pci0
> > > rl0: Ethernet address: 00:50:fc:56:8a:7c
> > > miibus0: <MII bus> on rl0
> > > rlphy0: <RealTek internal media interface> on miibus0
> > > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > >
> > > (i.e. /etc/rc.conf has ifconfig_rl0="DHCP")
> > >
> > > I doubled checked to make sure /etc was properly updated and it seems to be
> > > the case.
> > >
> > > I know with the realteks I have used, until an IP address is given to them
> > > to "up" the interface, they see the link as being down. Not even sure if
> > > the commit below has anything to do with it but thought I would start here
> > > as it seems to be possibly related.
> > >
> > > Can anyone confirm that DHCP assigned addresses are working for you on
> > > STABLE as of today or yesterday ?
> > >
> > > ---Mike
> > >
> > > At 02:20 PM 21/10/2002 -0700, Semen Ustimenko wrote:
> > > >semenu 2002/10/21 14:20:19 PDT
> > > >
> > > > Modified files: (Branch: RELENG_4)
> > > > sys/dev/mii acphy.c
> > > > Log:
> > > > MFC v1.8: MII_TICK needs not restart autonegotiation, the chip behaves
> > > > pretty well by itself. Slightly rearrange the code to make diff to
> > > > -current smaller.
> > > >
> > > > Revision Changes Path
> > > > 1.2.2.2 +20 -46 src/sys/dev/mii/acphy.c
> > > >
> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > >with "unsubscribe cvs-all" in the body of the message
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-stable" in the body of the message
> >
> >Works for me(TM).
> >
> >%ifconfig
> >rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > inet6 fe80::200:b4ff:fe91:c482%rl0 prefixlen 64 scopeid 0x1
> > inet 192.168.0.3 netmask 0xffff0000 broadcast 192.168.255.255
> > ether 00:00:b4:91:c4:82
> > media: Ethernet autoselect (100baseTX <full-duplex>)
> > status: active
> >
> >Is this the same problem as "rl media detect failure during boot"?
> >
[from top]
Mike Tancsa wrote:
>
> Actually, on my other box I just test it works fine. The only difference is
> that its an onboard realtek as opposed to an external version. I will try
> and see if it "follows" the card so to speak tomorrow as it works fine on
> my fxp card.
>
> ---Mike
My problem is certainly brand dependent. The above card is okay.
The following card (static IP) has the media detect failure (during
boot).
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.0.2 netmask 0xffff0000 broadcast 192.168.255.255
inet6 fe80::24f:4eff:fe04:be58%rl0 prefixlen 64 scopeid 0x1
ether 00:4f:4e:04:be:58
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
--
ian j hart
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB7173C.35A6EFA0>