From owner-freebsd-questions@FreeBSD.ORG Fri Aug 25 20:55:20 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0120B16A4DD for ; Fri, 25 Aug 2006 20:55:19 +0000 (UTC) (envelope-from karlj000@unbc.ca) Received: from pg-cts-imap-03.unbc.ca (pg-cts-imap-03.unbc.ca [142.207.144.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7649343D46 for ; Fri, 25 Aug 2006 20:55:19 +0000 (GMT) (envelope-from karlj000@unbc.ca) Received: from webmail2.unbc.ca (webmail.unbc.ca [142.207.144.59]) by pg-cts-imap-03.unbc.ca (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id k7PKtGH5015651 for ; Fri, 25 Aug 2006 13:55:18 -0700 Received: by webmail2.unbc.ca (Postfix, from userid 30) id E586A1DAE; Fri, 25 Aug 2006 13:55:16 -0700 (PDT) Message-ID: <16209.204.50.77.42.1156539316.squirrel@webmail.unbc.ca> In-Reply-To: <9AD1321C-3D18-404E-809C-91174EC9F7B9@unbc.ca> References: <95AEF7C1-337B-4686-AF5C-3A41D0EB7C9C@unbc.ca> <17646.30432.803446.748621@jerusalem.litteratus.org> <17646.34774.109468.614268@jerusalem.litteratus.org> <9AD1321C-3D18-404E-809C-91174EC9F7B9@unbc.ca> Date: Fri, 25 Aug 2006 13:55:16 -0700 (PDT) From: "Jeremy Karlson" To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: NGE Network Driver Problem. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Aug 2006 20:55:20 -0000 > On 24-Aug-06, at 22:17, Robert Huff wrote: >> Probably. The chip name means a Realtek 8169, and that >> takes the re() driver. > Unfortunately, this didn't work out for me. I tried a bit of other > fiddling as well and didn't get any change in behaviour. I'll just > take the card back and maybe try a D-Link one with a > different chipset. After doing some digging, I've found that there was a patch applied to RELENG_6, modifying the sk driver to ignore my revision of card, and instructing the re driver to attach. This is probably why it works for Robert and not for me; he's probably running 6 , while I'm still on 5 STABLE. Applying the patch to these drivers myself is not a problem, but I'm just wondering if this can / will / will ever be pushed into the RELENG_5 branch. Does anyone know, or at the very least, who I should be talking to? Thanks. -- Jeremy