Date: Sun, 25 Mar 2001 15:57:05 -0500 From: Andrew J Caines <A.J.Caines@altavista.net> To: freebsd-stable@FreeBSD.ORG Subject: Re: Problem with 4.2-STABLE and dc0 Message-ID: <20010325155705.C474@hal9000.bsdonline.org> In-Reply-To: <200103181429.f2IETWu05880@dungeon.home>; from mckay@thehub.com.au on Mon, Mar 19, 2001 at 12:29:32AM %2B1000 References: <002401c0b53d$cdbcf840$0100a8c0@cascade> <20010323222913.17220.cpmta@c000.sfo.cp.net> <16DC0F334516F5478EC60CADEDB6A68410D9C6@moe.wojo.net> <5.0.2.1.0.20010312122304.02ad89a8@pop.schulte.org> <200103181429.f2IETWu05880@dungeon.home>
next in thread | previous in thread | raw e-mail | index | archive | help
As a user of a Netgear FA-410TXC which uses the dc driver, I've been waiting to see a confirmation that the existing problem as reported by various people has been fixed, but with the release almost here I've still not anything positive. Stephen McKay provided a patch to address a problem with dc, but according to Perry Glen, this didn't stop his system booting without a working interface. Does anyone have an update to the dc "failed to force tx and rx to idle state" problem which stops systems booting with a working interface? Conversely is anyone running recent code with dc working perfectly. How about specifically with a Netgear FA-410TXC or Linksys FA-310TX? I'm happy to help testing, but don't have a lot of time to offer. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | 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?20010325155705.C474>