From owner-freebsd-current Sat Feb 17 12:17:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.de [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id D8C5837B401 for ; Sat, 17 Feb 2001 12:17:14 -0800 (PST) Received: (qmail 19845 invoked by uid 0); 17 Feb 2001 20:16:54 -0000 Received: from p3ee21647.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.71) by mail.gmx.net (mp006-rz3) with SMTP; 17 Feb 2001 20:16:54 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id RAA23244 for current@freebsd.org; Sat, 17 Feb 2001 17:06:45 +0100 Date: Sat, 17 Feb 2001 17:06:45 +0100 From: Gerhard Sittig To: current@freebsd.org Subject: Re: linksys Etherfast.. broken? Message-ID: <20010217170645.C20830@speedy.gsinet> Mail-Followup-To: current@freebsd.org References: <3A89C231.D03793D4@westmarsh.com> <20010214211548.B15618@speedy.gsinet> <20010216211610.B20830@speedy.gsinet> <200102170700.f1H70rW84857@harmony.village.org> <3A8E3CF0.7DEF9B5F@elischer.org> <3A896E33.8AC84353@elischer.org> <3A89C231.D03793D4@westmarsh.com> <20010214211548.B15618@speedy.gsinet> <20010216211610.B20830@speedy.gsinet> <3A8E0D9C.261A0259@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A8E0D9C.261A0259@elischer.org>; from julian@elischer.org on Fri, Feb 16, 2001 at 09:35:24PM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 16, 2001 at 21:35 -0800, Julian Elischer wrote: > > Gerhard Sittig wrote: > > > > Now that I had success with the fa_select tool, I filed a PR > > with a patch: misc/25147. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=25147 > > thanks for this.. but it didn't seem to help > > It looks to me like the interrupt vector is not being > registered.. I'll try figut out what I've screwed up in the > config. On Sat, Feb 17, 2001 at 00:57 -0800, Julian Elischer wrote: > > the thing that pisses me of is that this card DID WORK! > I tried the fa_select program.. it didn't help. Sorry, but the method described in the PR assumes that fa_select _is_ the tool that makes the cards work. What the PR achieves is that the card is useful right after getting plugged in -- without manual intervention. If only I had known earlier about the fa_select tool (didn't find it in the archives when I searched for my card back in November/December, it seems there are too many ways of spelling model names plus there are sooo many models basically being the same -- I never considered "Netgear" to be of concern for me ...)! But I still see the PR method as a hack just to get network access to a machine with failed media negotiation. Especially forcing speed as well as duplex mode is what I don't like about the current situation (you all know the regular threads about "it doesn't work" with the usual answers "then don't hardware it"). Your "fa_select doesn't help" and Warner's message suggest that your situation is different from mine and that you have some kind of resource allocation problem or a conflicting assignment. Sorry ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message