From owner-freebsd-questions@FreeBSD.ORG Thu Jul 21 19:56:09 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50824106564A for ; Thu, 21 Jul 2011 19:56:09 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id F33468FC14 for ; Thu, 21 Jul 2011 19:56:08 +0000 (UTC) Received: by qyk38 with SMTP id 38so1117351qyk.13 for ; Thu, 21 Jul 2011 12:56:08 -0700 (PDT) Received: by 10.224.206.72 with SMTP id ft8mr556166qab.206.1311278168181; Thu, 21 Jul 2011 12:56:08 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id s14sm1076186qct.18.2011.07.21.12.56.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jul 2011 12:56:07 -0700 (PDT) Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RKm7n5kBKz2CG4m for ; Thu, 21 Jul 2011 15:56:05 -0400 (EDT) Date: Thu, 21 Jul 2011 15:56:05 -0400 From: Jerry To: FreeBSD Message-ID: <20110721155605.12a4ecb5@scorpio> In-Reply-To: <4e285427.cc43d80a.4e87.5777@mx.google.com> References: <4e285427.cc43d80a.4e87.5777@mx.google.com> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: em0 NIC slow on 8.2-p1 amd64? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2011 19:56:09 -0000 On Thu, 21 Jul 2011 16:31:25 +0000 Peter Harrison articulated: > Sorry for top posting. My 'phone makes it awkward. > > I use ndis for the wifi connection in my netbook. Was trivial to > convert the Windows driver, and it works without issue. > > Anyone know whether it could do 'N' class devices, to address Jerry's > longstanding (and vocal, and justified) complaint - so that we can > have an argument about why I'd rather configure my wireless manually > in a text file and not have it done automagically by the OS and not > be side-tracked by the non-availability of drivers? Problem one was that NDIS was not working on 64 bit systems. I believe that has been addressed; however I cannot confirm it. The last time I tired was approximately three months ago. It would not work on the system, ie, the system would not use the driver. I even tried a piece of shit USB device (N protocol) on another one of my FreeBSD machines, and that failed also. The last of my FreeBSD laptops is now gone; they are all Win7 machines. I still have two towers, one with wireless USB that fails on FreeBSD. Now, I have absolutely no problem with you manually creating a file(s), etc to get a connection created. On the other hand, my 10 year old niece was visiting a few weeks ago. Like all kids, she had her laptop with her. Upon turning it on, it discovered my wireless network. All I had to do was give her the password, and she was on. Of course we are not talking about network discovery and but rather the act of getting a wireless card working in the first place. To a degree, they are connected though. Computers should make life easier, not more complicated. Manually having to discover what form of encryption is being used on a network when it can be done automatically, etcetera, just does not suit my definition of easier. I would much rather be playing a round of golf while you are debugging a wireless connection. So if you are looking for an argument as to why you should not be manually forced to configure a simple device that can and is automatically handled by other OSs, you will not get an argument from me. That is unless you think that I should also be forced to do the same. The "Marquis de Sade" isn't my hero and I am definitely not into "sadism". -- Jerry ✌ jerry+fbsd@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the "Reply-To" header. http://www.catb.org/~esr/faqs/smart-questions.html