From owner-freebsd-questions@FreeBSD.ORG Thu Jan 26 14:58:45 2012 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 481E6106566B for ; Thu, 26 Jan 2012 14:58:45 +0000 (UTC) (envelope-from jasper.valentijn@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 02FDA8FC0C for ; Thu, 26 Jan 2012 14:58:44 +0000 (UTC) Received: by yhfs35 with SMTP id s35so282586yhf.13 for ; Thu, 26 Jan 2012 06:58:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=kX2mVrj8VwyXNZZrt43/7K5S15kUCSE//6WB13oiUnw=; b=mTB2ttClAWHodoCvzG2Rot7Hhsxfjk1FMY7wEx04L6Aolae6RUmBcfTbRnJJaRjvKn wxjlsk82bI7RExRFNZUwyiHgjMNhCci+5/2cbgonKcw6Fg7tqKesOWdznB1qqEjVssqD dvyRlHjd94RKAfksyI1Gx9FtUh8AIyR3Cxd6Q= MIME-Version: 1.0 Received: by 10.236.197.103 with SMTP id s67mr3870554yhn.5.1327589924439; Thu, 26 Jan 2012 06:58:44 -0800 (PST) Received: by 10.236.116.9 with HTTP; Thu, 26 Jan 2012 06:58:44 -0800 (PST) In-Reply-To: References: Date: Thu, 26 Jan 2012 15:58:44 +0100 Message-ID: From: Jasper Valentijn To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: FreeBSD 9.0 ICH8M trouble, no HDD found, unable to install. 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: Thu, 26 Jan 2012 14:58:45 -0000 Mike wrote: > I do not have this hardware, so these are just a couple of wild guessses > from the blue on my part. =A0I am also looking only at 64 bit platforms h= ere, > so if there is any signifigant difference with 32 bit I can't look/see. Just to be on the safe side I've also tried the 9.0 amd64 image. Same results though. > First, you might try using the "2" option on the boot menu and then 'load= acpi_sony' followed by 'boot'. No change here, on both i386 and amd64. > You may try disabling AHCI by switching to Legacy IDE mode and see what > changes. If it works when you do this it confirms this to be where the=A0= > problem lies. > Also ensure you are not using any BIOS config for AHCI+RAID. Sony has completely stripped the bios, no options to set here. > You may be able to play around a little using the loader (press=A0"2") to= set and unset various variables. > For example, hint.ahci.X.msi=3D0=A0would turn off MSI support. No luck with this either. Have tried your suggestion and some others 'hint.ata.0.*'. > As far as specific settings for controlling=A0ATA_CAM and/or other AHCI s= upport I'm fuzzy on this. > Perhaps if you reach=A0this point someone more knowlegable can chime in. Same here. > As far as what I can tell from the PR you mentioned, if you saw the exact= =A0same behavior after > having installed FBSD 8.1 and then subsquently trying to=A0upgrade to 8.2= it would nail it to matching > the PR. I have tried the 8.1 i386 memstick image and it does see the drive. I have tried the 8.2 i386 memstick image and it does not see the drive. I have tried the 9.0 i386 memstick image and it does not see the drive. I have tried the 9.0 amd64 memstick image and it does not see the drive. Didn't do an install of 8.1 and upgrade to 8.2 though. If needed I could try that, but I'd prefer to do a clean 9.0 install. > Hope this helps any, as it's just basically just a couple of wild guesses= to=A0maybe get you started. Well, still no FBSD 9.0 on the box but it kept me busy. Thanks anyways! Jasper --=20 =93We spend the first twelve months of our children's lives teaching them to walk and talk and the next twelve telling them to sit down and shut up.=94