On Wed, Sep 09, 2009 at 07:07:01PM +0200, Thierry Thomas wrote:
> Le Mer 9 sep 09 ? 17:52:57 +0200, Brooks Davis
> ?crivait?:
>
> > I'd rather not mention the "link state changed" message since I'd love
> > to see it go away. How's this?
>
> Seems good, go!
Thanks. I've committed it.
Brook
Le Mer 9 sep 09 à 17:52:57 +0200, Brooks Davis
écrivait :
> I'd rather not mention the "link state changed" message since I'd love
> to see it go away. How's this?
Seems good, go!
--
Th. Thomas.
___
freebsd-stable@freebsd.org mailing list
http://li
On Sat, Sep 05, 2009 at 01:06:35PM +0200, Thierry Thomas wrote:
> Le Ven 4 sep 09 ? 23:57:47 +0200, Brooks Davis
> ?crivait?:
>
> > This is a know issue with some devices supported by ed(4). You can work
> > around it by changing DHCP to SYNCDHCP which will cause dhclient to
> > alwasy start
Le Ven 4 sep 09 à 23:57:47 +0200, Brooks Davis
écrivait :
> This is a know issue with some devices supported by ed(4). You can work
> around it by changing DHCP to SYNCDHCP which will cause dhclient to
> alwasy start immediatly on that interface instead of waiting for a link
> state change th
On Fri, Sep 04, 2009 at 02:41:48PM -0700, Pyun YongHyeon wrote:
> On Fri, Sep 04, 2009 at 07:38:11PM +0200, Thierry Thomas wrote:
> > Hello,
> >
> > I have a machine with the following ethernet PCI card:
> >
> > ed0: port 0xdc00-0xdc1f irq 16 at device 0.0 on pci2
> > ed0: WARNING: using obsolet
Hello,
Le Ven 4 sep 09 à 23:41:48 +0200, Pyun YongHyeon
écrivait :
> I guess it's related with link state handling. Can you see
> "ed0: link state changed to UP" in dmesg output? Quick reading code
> reveals only some variants(pccard) support mii(4) but others looks
> dumb on link state handli
On Fri, Sep 04, 2009 at 07:38:11PM +0200, Thierry Thomas wrote:
> Hello,
>
> I have a machine with the following ethernet PCI card:
>
> ed0: port 0xdc00-0xdc1f irq 16 at device 0.0 on pci2
> ed0: WARNING: using obsoleted if_watchdog interface
> ed0: Ethernet address: 00:50:bf:27:ba:24
> ed0: [IT
