Date: Fri, 18 Apr 1997 14:23:06 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: adrian@virginia.edu Cc: hackers@freebsd.org Subject: Re: DEC 21140-Ax problems resolved? Message-ID: <199704182123.OAA02842@phaeton.artisoft.com> In-Reply-To: <Pine.SUN.3.90.970418112013.19732L-100000@stretch.cs.Virginia.edu> from "Adrian T. Filipi-Martin" at Apr 18, 97 11:23:57 am
next in thread | previous in thread | raw e-mail | index | archive | help
> [ N.B. This ia an augmneted repost that drew ] > [ little response from freebsd-questions. ] > > I searched the mail archives and find no mention of the problem > with this chipset after mid-March. Has the problem with the de0 driver > been resolved? > > I get the same problems I found in many of the posts. The link > light is on for out 10Base-T hub, then it goes off after the kernel probes > and switches the device into 100Base-T mode. > > I have tried using the NetBSD driver as well as the -currrent > one. In both cases the kernel won't compile. In the -current case, I > think I may have missed a crucial file. The NetBSD may just be to far > out of synch. >From what I recollect, this isn't a driver problem, it's a link flag problem. Use 'man ifconfig' and modify your /etc/sysconfig appropriately to get the other link. Also from what I recollect, there are three modes: "autosense", "specific link", and "CMOS default setting". I believe the driver selects the third. If that fails, the NetBSD driver was recently announced as ported on the -current list (which is probably a better place to look, especially if the 'x' in your '-Ax' is recent, since your card may have overflow problems which need to be worked around in software). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704182123.OAA02842>