From owner-freebsd-questions@FreeBSD.ORG Tue Aug 22 15:47:46 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 A508D16A4DA for ; Tue, 22 Aug 2006 15:47:46 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C4E43DA4 for ; Tue, 22 Aug 2006 15:47:31 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.137] (helo=anti-virus01-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1GFYTR-0007ug-M5; Tue, 22 Aug 2006 16:47:29 +0100 Received: from [82.41.35.166] (helo=[192.168.0.2]) by asmtp-out1.blueyonder.co.uk with esmtp (Exim 4.52) id 1GFYTR-0001V2-15; Tue, 22 Aug 2006 16:47:29 +0100 Message-ID: <44EB2710.9050105@dial.pipex.com> Date: Tue, 22 Aug 2006 16:47:28 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: Vizion References: <20060822134833.GQUI15709.dukecmmtao03.coxmail.com@dukecmmtao03> In-Reply-To: <20060822134833.GQUI15709.dukecmmtao03.coxmail.com@dukecmmtao03> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: devices 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: Tue, 22 Aug 2006 15:47:46 -0000 Vizion wrote: >As an experiment I disconnected ad0 and then rebooted from the iso image to see what would be reported. >The installation menu reported >No disks found! > > > >Does anyone have a clue as to what might be going on here and how I might be able to deal with it? > > It would appear that your disk controller is not supported by the version of FreeBSD you are trying to run. Have you checked it against the hardware compatibility list? You can find the controller by looking through /var/run/dmesg.boot - with ad0 reconnected of course :-) You could try a -STABLE or -CURRENT CD to see if support has appeared more recently than your release. I have previously reported an inability to get my amd Freebsd > 6.1 system to recognize a drive and am wondering if it is > because the relevant device node is not in /dev. having said > that I am unsure of what I need to be looking for or how to create it. Device nodes are created automatically when devices are recognised. If the device isn't recognised there is no point trying to manually create device nodes - it won't help even if you created them correctly. AFAIK, the only things worth creating in /dev these days are symlimks, which can be done automatically using a devfs.conf rule like link acd0 cdrom The days of MAKEDEV are over as its manpage testifies :-) --Alex