From owner-freebsd-questions@FreeBSD.ORG Sun Nov 6 20:28:41 2005 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 A0AC016A41F for ; Sun, 6 Nov 2005 20:28:41 +0000 (GMT) (envelope-from matt@kbc.net.au) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08E5D43D49 for ; Sun, 6 Nov 2005 20:28:40 +0000 (GMT) (envelope-from matt@kbc.net.au) Received: from [10.10.10.210] (ppp211-161.lns1.adl2.internode.on.net [203.122.211.161]) by smtp1.adl2.internode.on.net (8.12.9/8.12.6) with ESMTP id jA6KSc7X077639 for ; Mon, 7 Nov 2005 06:58:39 +1030 (CST) (envelope-from matt@kbc.net.au) Message-ID: <436E6776.8030507@kbc.net.au> Date: Mon, 07 Nov 2005 06:58:38 +1030 From: Matthew Smith User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <436DCB19.2090005@kbc.net.au> <20051106102456.GA26939@slackbox.xs4all.nl> In-Reply-To: <20051106102456.GA26939@slackbox.xs4all.nl> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: NFS Installation Issues 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: Sun, 06 Nov 2005 20:28:41 -0000 >>My problem is that when I select the installation source, Ethernet is >>not amongst the options (just SLIP, PPP and something else weird). > > That "something weird" could well be the ethernet card. unlike Linux, > the ethernet devices are not all named "ethX', but are named after the > driver. So it could be e.g. sk0, xl0, dc0, de0, fxp0, vr0 etc. > >>I assume that there's a kernel module not loaded, so after looking >>further through the documentation, I found that I should be able to put >>a line in /boot/defaults/loader.conf. Since the installation so far was >>actually bootable (that's one up on Linux!), I did this. All this did >>for me was to generate a warning that the module was already loaded. > > Then try to use the "something weird" as the ethernet device. Thanks for that Roland - I've had another look, but the "something weird" is PLIP, which I believe to be some parallel port communication system. So, my real question remains: how does one get a network card recognised? One piece of documentation refers to kernel configuration as part of the installation process - I don't know if that's for an older version, because this step certainly doesn't show up on mine. Cheers M -- Matthew Smith Kadina Business Consultancy, South Australia Work: Personal: