Date: Fri, 08 Dec 2000 07:35:05 -0600 From: Jeremy Vandenhouten <jeremy.vandenhouten@marquette.edu> To: Mike Galvez <mrg8n@mail.virginia.edu>, questions@freebsd.org Subject: Re: dc0: failed to force tx and rx to idle state... dang Message-ID: <2e1e0e2db0f5.2db0f52e1e0e@marquette.edu>
next in thread | raw e-mail | index | archive | help
If I remember correctly after reading through the hardware section. The Netgear FA310TX is supported by the Tulip driver. ----- Original Message ----- From: Mike Galvez <mrg8n@mail.virginia.edu> Date: Thursday, December 7, 2000 5:32 pm Subject: Re: dc0: failed to force tx and rx to idle state... dang > Thanks for replying, > > Was this problem with FreeBSD? > > I'm not aware of any Bay Networks / Netgear software for FreeBSD. > Part of the > problem I believe is that I am in an older building with mixed > topology. My area > of the building is not yet re-wired so my 10/100 card plugs into a > hub via UTP and > then travels over 10base-2 until it reaches the nearest switch. I > read the man > page on ifconfig which mentions "media type" and "media opt" > parameters; however, > I'm not sure if this card supports any additional parameters. I > looked on Netgears > site and didn't find anything useful. > > I would be grateful if you or anyone else knows of additional > parameters regarding > the FA310TX. > > Thanks again > > Mike > > > On Thu, Dec 07, 2000 at 03:28:43PM -0500, Courtney Thomas wrote: > > I had the same problem > vendor's software and selecting > suitably functional parameters, and as I > > recall I turned off tx/rx. > > > > Goodluck, > > Courtney > > > > > > > > > > > > > > Mike Galvez wrote: > > > > > > I hope someone has some wisdom to share (other than not using > cheap NICs). I have > > > a Netgear FA 310tx installed on my 4.0 FreeBSD box. It has > worked fine for the > > > last couple of months but occasionally I get the following > message:> > > > > dc0: failed to force tx and rx to idle state > > > > > > This message will appear on the console every now and then but > yesterday and > > > today, I get this message and the NIC just quits, or seems to. > ifconfig dc0 shows > > > it to be up and you can ping it from the console but its not > sending packets over > > > the lan. > > > > > > Until I can get a better NIC, is there a way to restart/reset > this hardware > > > without having to take the server down? > > > > > > Thanks > > > > > > -- > > > > > > Michael Galvez > > > Computer Systems Sr. Engineer Office: 804-982-2975 > > > Financial Analysis E-Mail: mrg8n@virginia.edu > > > University of Virginia Messenger Mail: Carruthers Hall > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > -- > > Michael Galvez > Computer Systems Sr. Engineer Office: 804-982-2975 > Financial Analysis E-Mail: mrg8n@virginia.edu > University of Virginia Messenger Mail: Carruthers Hall > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2e1e0e2db0f5.2db0f52e1e0e>