Date: Thu, 21 Jul 2011 15:56:05 -0400 From: Jerry <jerry@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: em0 NIC slow on 8.2-p1 amd64? Message-ID: <20110721155605.12a4ecb5@scorpio> In-Reply-To: <4e285427.cc43d80a.4e87.5777@mx.google.com> References: <4e285427.cc43d80a.4e87.5777@mx.google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110721155605.12a4ecb5>