Date: Fri, 22 Aug 2014 12:00:47 -0700 From: leeoliveshackelford@surewest.net To: freebsd-questions@freebsd.org Subject: how to install wireless n.i.c. on FreeBSD 9.1 Message-ID: <c0493cf1a6cb62e193163d781348b8ad@surewest.net>
next in thread | raw e-mail | index | archive | help
Good morning, dear FreeBSD enthusiasts. I am attempting to install a wireless network interface circuit on a computer running FreeBSD 9.1. I have read the very thorough instructions written by Messrs. Marc Fonvielle and Murray Stokely in the currently posted Chapter 30 of the FreeBSD Handbook. I did not find in that chapter a specification of the version or versions of FreeBSD to which it applied. The circuit board is manufactured by T-LInk, and uses an Atheros integrated circuit I have followed as closely as possible those instuctions, to no avail. The printed circuit board is located at slot 4. About it, dmesg.boot reads only the following: pci40: <network> at device 0.0 (no driver attached). My interpretation of this message is that the operating system sees that there is a circuit board in slot 4, and that it has something to do with networking, and otherwise knows nothing about it. I have checked the /dev directory, and find listed in it none of the driver files mentioned in Chapter 30. I had expected to receive error messages for lines in the configuration files calling for driver files that could not be located, but the only error message generated was "SYNCDHCP not found." This line does not occur in dmesg.boot, but in response to the command (I forgot which command). How do I obtain and install the missing driver files? Why does the fact that they are missing not generate error notices? Any and all comments are appreciated. If these questions have already been answered many times before, please do not flame me. Just let me know where I should have looked for the answers. Thank you. Lee From owner-freebsd-questions@FreeBSD.ORG Fri Aug 22 19:21:12 2014 Return-Path: <owner-freebsd-questions@FreeBSD.ORG> Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B117796 for <freebsd-questions@freebsd.org>; Fri, 22 Aug 2014 19:21:12 +0000 (UTC) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96E3639E3 for <freebsd-questions@freebsd.org>; Fri, 22 Aug 2014 19:21:11 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id x48so10981719wes.5 for <freebsd-questions@freebsd.org>; Fri, 22 Aug 2014 12:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=8jyWssbU+tDeXqnQadnZRLVTDrNyo60J0Lu4fKJ0Mi8=; b=VEHxtV7pPK0HTwJCVOar6n0h2e/KgtlZYm6vc4+Gy3uaVFuKSKKHc3hh5RMEfg5DJQ 3pGiM2Hcj+kHtWDn0bbo9DMIyZZyUo7RdA39n9AkJ+bnuin9oaKv6z5x7OJ4KrgbQoAf Vl+VU/tKh3+cZ2DCghiUQuNbjFy/56X6oOxJUnMZW9T6tA9kR2eCSFqIX9DjroBoO5kD EXhjGpuHMQDyyT7fAhv0ztO6QhXKsE13ndETfLyElAXf/21bDjl0eALliSDO+LuvYXmg +FGaI6B1EjuWB3+FyKUcwoygFKNp9xxG9U/t0QTZ+0FgUnkwPGRMKPUC3UQrEdw3I44I 5Waw== X-Received: by 10.194.19.200 with SMTP id h8mr6929896wje.40.1408735269688; Fri, 22 Aug 2014 12:21:09 -0700 (PDT) Received: from gumby.homeunix.com (5ec2dc90.skybroadband.com. [94.194.220.144]) by mx.google.com with ESMTPSA id jx10sm77325286wjc.7.2014.08.22.12.21.08 for <freebsd-questions@freebsd.org> (version=SSLv3 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Aug 2014 12:21:09 -0700 (PDT) Date: Fri, 22 Aug 2014 20:21:08 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: solid state drives? Message-ID: <20140822202108.2690f55d@gumby.homeunix.com> In-Reply-To: <alpine.LRH.2.11.1408221239310.9489@nber2.nber.org> References: <53F22E89.3050005@rcn.com> <53F2399D.5050609@hiwaay.net> <20140822170112.69830ad9@gumby.homeunix.com> <alpine.LRH.2.11.1408221239310.9489@nber2.nber.org> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 22 Aug 2014 19:21:12 -0000 On Fri, 22 Aug 2014 12:41:57 -0400 (EDT) Daniel Feenberg wrote: > > A typical modern 120GB MLC SSD will have a specified write > > endurance of around 8TB which is equivalent to 1GB a day for 22 > > years. They should be fine for most things where there's nothing > > doing heavy duty writing. > > I sort of understand that - but does the SSD have the ability to move > unchanged data around to even out the wear? It's called static wear-levelling. I think it's the norm on enterprise grade SSDs, but it's rarely mentioned in the specs of domestic grade drives. > That is, if I fill the > drive with 100GB of never changing files, and then write lots of > frequently changing files to the last 20GB, does this put all the > wear on a small portion of the drive, while most of the drive suffers > no wear at all? Without static wear-levelling it's advisable to leave a sizeable fraction of the drive unused. With trim support that can be inside the filesystem, without it the partitioning should not fill the whole drive. OS files tend to get deleted several times a year during updates, so they aren't so much of a problem, if you have trim support. BTW GELI doesn't support trim, so you have to have some free space outside an encrypted partition.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c0493cf1a6cb62e193163d781348b8ad>