From owner-freebsd-hardware@FreeBSD.ORG Thu May 1 09:39:56 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C1D21065672; Thu, 1 May 2008 09:39:56 +0000 (UTC) (envelope-from geo@pulsar.bg) Received: from pulsar.bg (pulsar.bg [213.130.70.6]) by mx1.freebsd.org (Postfix) with ESMTP id C210F8FC15; Thu, 1 May 2008 09:39:55 +0000 (UTC) (envelope-from geo@pulsar.bg) Received: from [212.72.201.62] (helo=GEOPC) by pulsar.bg with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JrV1o-0004Ry-Aa; Thu, 01 May 2008 12:24:36 +0300 Date: Thu, 1 May 2008 12:24:36 +0300 From: Georgi Iovchev X-Mailer: The Bat! (v3.0.1.33) Professional Organization: Pulsar Ltd X-Priority: 3 (Normal) Message-ID: <422521026.20080501122436@pulsar.bg> To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: geo@pulsar.bg Subject: is there driver for (Bearlake) HECI Controller for releng_7 (or 7_0_0) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Georgi Iovchev List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 09:39:56 -0000 Hello lists Intel G33 motherboard (Intel DG33FB) with FreeBSD 7 AMD64 (7.0-RELEASE-p1) one thing is missing: [root@asterisk ~]# pciconf -lv | grep -A3 none none0@pci0:0:3:0: class=0x078000 card=0x50448086 chip=0x29c48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '(Bearlake) HECI Controller' class = simple comms Actually I dont know if I really need this (machine will be used for asterisk voip solution), but for completeness is there a driver for this piece of hardware? 10x in advance From owner-freebsd-hardware@FreeBSD.ORG Thu May 1 18:02:37 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE27D1065681 for ; Thu, 1 May 2008 18:02:37 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 6ECF68FC24 for ; Thu, 1 May 2008 18:02:37 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so528757nfh.33 for ; Thu, 01 May 2008 11:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=2S8SqwORcn94oCxtEL+IzwfVOXjmb0yQaZ/kkU8zFcQ=; b=JPfJjbU2MZR+c6E2S7jK8+AUqOl2lqo73GN3OjWorUAOwZ+O/OwNo9V/M9lRPXfHkAM+F2HLeY3p8uDI8K8JUQUfpvxQNE0NfXIB3NVphCK/aQgjRlf6CUAHiWNkzAERgVdipzCjrc4BhO4arAg9R5T9fAHuprtJ3ZqGlZCPw08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=dOqolBScoHdm/bTwq0SmdWpLZfQQE53aMdBE0BxAbuoLpw+cz05cRtLBSqkTRVyOnaFRzWOVAwswntNiiI4BOWbpZGKp6BR9Xnz2pkvirvCIT/T6zJJ9ajOLbSOllTeygO4HJONqmvPfpvAtjx2xqll7sttFo/BdLFEnpYYi6RU= Received: by 10.78.107.1 with SMTP id f1mr696913huc.85.1209663293838; Thu, 01 May 2008 10:34:53 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Thu, 1 May 2008 10:34:53 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 13:34:53 -0400 From: "Shaun Sabo" To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 18:02:37 -0000 Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop machine and im having a lot of trouble with this. First I could not use USB keyboards with the installer program (which is fine, i dont mind switching to PS2). then once i got into the sysinstaller it does not detect my Hard Disks. i also tried installing an old 6.2 cd that i had sitting around and remaking world and kernel but when i installed the kernel and restarted to go into single user mode the system could not mount the root filesystem. the motherboard im using is a nvidia nforce4 with Serial ATA hard disks. Does anyone know how to get FreeBSD 7.0 to recognize my hard drives? From owner-freebsd-hardware@FreeBSD.ORG Thu May 1 18:23:26 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0466C106564A for ; Thu, 1 May 2008 18:23:26 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id E4B0E8FC0C for ; Thu, 1 May 2008 18:23:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id B1FDC1CC033; Thu, 1 May 2008 11:23:25 -0700 (PDT) Date: Thu, 1 May 2008 11:23:25 -0700 From: Jeremy Chadwick To: Shaun Sabo Message-ID: <20080501182325.GA62281@eos.sc1.parodius.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 18:23:26 -0000 On Thu, May 01, 2008 at 01:34:53PM -0400, Shaun Sabo wrote: > Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop machine and im > having a lot of trouble with this. First I could not use USB keyboards with > the installer program (which is fine, i dont mind switching to PS2). then > once i got into the sysinstaller it does not detect my Hard Disks. i also > tried installing an old 6.2 cd that i had sitting around and remaking world > and kernel but when i installed the kernel and restarted to go into single > user mode the system could not mount the root filesystem. the motherboard im > using is a nvidia nforce4 with Serial ATA hard disks. Does anyone know how > to get FreeBSD 7.0 to recognize my hard drives? Re: USB keyboard: USB support on FreeBSD is spotty. That said, I've never run into problems getting FreeBSD to detect and use a USB keyboard (other USB devices are a different story). You'd need to provide some dmesg(8) output to verify, but I know that's going to be difficult until you can get FreeBSD installed. Re: SATA disks: I can assure you that FreeBSD works fine with SATA disks connected to an nForce 4 chipset, because I've used them myself with no issue. Chances are there's a BIOS setting that's causing mayhem, or you may be using a RAID array of some sort (since the XPS700 is one of those "gamer lozlozlz" systems). The manual for this system is here: http://support.dell.com/support/edocs/systems/xps700/ Screenshots of the BIOS are here: http://www.bit-tech.net/hardware/2006/09/04/Dell_XPS_700_review/5 Are you using RAID at all on this system? If so, chances are that's why it doesn't see your array. Finally, if available, I'd try a BIOS update. Googling for results shows that system has quite a large number of issues with its BIOSes, and Dell has been fairly good about providing updates to fix problems. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Thu May 1 19:04:31 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B8361065678 for ; Thu, 1 May 2008 19:04:31 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 7B24D8FC0A for ; Thu, 1 May 2008 19:04:30 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so544233nfh.33 for ; Thu, 01 May 2008 12:04:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=RB4ib+2H1q4BRy1uaSUVm01yz1Fv0GSU3WM55aKYHa4=; b=b1PVHsjONLw2qsE9gSrSkOy0PtB3h1lGoBee+EAIeOv7JKOsNZoxhQe1w+Ov+w2RqvUEle1PklOiGGaI9G6UGQXDGut2dzJewJsydvcNiOoWlSHNRXwKWupaDClfPUYBLaMrzbX3N53OWzqOkcbCzn6cmpnKODK9LzR5nDNCDfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=L/OeuCBnhlxenwTZDIwc+rFYBD0wUBHNIAcIFWoIWo0vF6Ga0tFlo5FTuEI3CPOUkgk1aO78qYxzsVFFzWhTsdDogVB3RuKuFdlASwXiu3vfc6/N/Gcuu1rkr8ODcFDTM2LX7JvUvwtcix0SWBXCZfHouLFSGs4+PKorpSWL0Xg= Received: by 10.78.205.16 with SMTP id c16mr702083hug.109.1209668668973; Thu, 01 May 2008 12:04:28 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Thu, 1 May 2008 12:04:28 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 15:04:28 -0400 From: "Shaun Sabo" To: "Jeremy Chadwick" In-Reply-To: <20080501182325.GA62281@eos.sc1.parodius.com> MIME-Version: 1.0 References: <20080501182325.GA62281@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 19:04:31 -0000 I checked to make sure that the hard disks are not in raid configuration and there are not. i also checked and my bios are at the latest version available (A11). also this is an XPS 600 not 700 and i have the correct users manual in paper and digital formats. how would you like the dmesg to be presented? i dont think i have any way to writing it to a thumb drive or such devices from the installer. should i just take digital pictures? On Thu, May 1, 2008 at 2:23 PM, Jeremy Chadwick wrote: > On Thu, May 01, 2008 at 01:34:53PM -0400, Shaun Sabo wrote: > > Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop machine and > im > > having a lot of trouble with this. First I could not use USB keyboards > with > > the installer program (which is fine, i dont mind switching to PS2). > then > > once i got into the sysinstaller it does not detect my Hard Disks. i > also > > tried installing an old 6.2 cd that i had sitting around and remaking > world > > and kernel but when i installed the kernel and restarted to go into > single > > user mode the system could not mount the root filesystem. the > motherboard im > > using is a nvidia nforce4 with Serial ATA hard disks. Does anyone know > how > > to get FreeBSD 7.0 to recognize my hard drives? > > Re: USB keyboard: USB support on FreeBSD is spotty. That said, I've > never run into problems getting FreeBSD to detect and use a USB keyboard > (other USB devices are a different story). You'd need to provide some > dmesg(8) output to verify, but I know that's going to be difficult until > you can get FreeBSD installed. > > Re: SATA disks: I can assure you that FreeBSD works fine with SATA disks > connected to an nForce 4 chipset, because I've used them myself with no > issue. Chances are there's a BIOS setting that's causing mayhem, or > you may be using a RAID array of some sort (since the XPS700 is one of > those "gamer lozlozlz" systems). > > The manual for this system is here: > > http://support.dell.com/support/edocs/systems/xps700/ > > Screenshots of the BIOS are here: > > http://www.bit-tech.net/hardware/2006/09/04/Dell_XPS_700_review/5 > > Are you using RAID at all on this system? If so, chances are that's why > it doesn't see your array. > > Finally, if available, I'd try a BIOS update. Googling for results > shows that system has quite a large number of issues with its BIOSes, > and Dell has been fairly good about providing updates to fix problems. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-hardware@FreeBSD.ORG Thu May 1 20:41:58 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 770831065676 for ; Thu, 1 May 2008 20:41:58 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 619C48FC1A for ; Thu, 1 May 2008 20:41:58 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id EDA591CC038; Thu, 1 May 2008 13:41:57 -0700 (PDT) Date: Thu, 1 May 2008 13:41:57 -0700 From: Jeremy Chadwick To: Shaun Sabo Message-ID: <20080501204157.GA67015@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 20:41:58 -0000 On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote: > I checked to make sure that the hard disks are not in raid configuration and > there are not. i also checked and my bios are at the latest version > available (A11). also this is an XPS 600 not 700 and i have the correct > users manual in paper and digital formats. how would you like the dmesg to > be presented? i dont think i have any way to writing it to a thumb drive or > such devices from the installer. should i just take digital pictures? Digital pictures would be fine, unless you want to try the serial console route (chances are you don't have this sort of environment set up, so it's probably more effective to take photos). One thing: does Linux detect your disks on this system? I'd recommend downloading one of the recent RELENG_7 snapshot CDs, specifically the "livefs" one, and boot it. dmesg doesn't come with the standard installation disc (disc1), hence why I'm recommending livefs. The snapshots are available here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 You probably want one of these two: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-amd64-livefs.iso ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso dmesg should show some ATA stuff at the end, assuming you're familiar with FreeBSD's kernel output. Something like this, assuming the physical disks are detected: ad4: 190782MB at ata2-master SATA150 ad6: 476940MB at ata3-master SATA300 ad8: 476940MB at ata4-master SATA300 ad10: 476940MB at ata5-master SATA300 You'll need to work backwards to figure out what is connected to what, e.g.: $ dmesg | grep ata2 ata2: on atapci1 ata2: [ITHREAD] ad4: 190782MB at ata2-master SATA150 $ dmesg | grep atapci1 atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 Otherwise, if none of this works, you'll need to somehow provide the full output of "pciconf -lv", which will be many screen fulls of data. You'll probably have to pipe it through "more", take a shot, hit spacebar, take another shot, etc... Please post URLs to the photos, rather than attaching them. The mailing list software does not take kindly to large attachments. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 02:18:51 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3748B106566C for ; Fri, 2 May 2008 02:18:51 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by mx1.freebsd.org (Postfix) with ESMTP id A9EEE8FC13 for ; Fri, 2 May 2008 02:18:50 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1094098fkk.11 for ; Thu, 01 May 2008 19:18:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=htGYeT9pwmMtkD0tSrmzCFO/SQ1L9Vh2PZcLBz6tb4Y=; b=WznNvDdsSdCjM1blM3YM3UBHFunXsLluUoRrQA+xJ5qDVCbu7g6Inv4XerK7fh/tzMdcy48rd7w4504zkQIHIJQoq0pksBTRsaVBsSmL3FFrwoOmU3rGZ44W/hheuYhl10YjvMU/y3WqgPxRK6E1yuUrVOmPgfGs3eWr0MhS1MI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Qsq2+duj9I9Nz0xlyh4wi+cdqF7wYL33wfRL0BKWhw4AenJjRN3sBA73yDadlkt4trG1dOdU7DQvGgcbLkh4PiKZBYIPsTeYEG1kzH71SDXF8SPvejzJqvVD7CR0uQsWIChoV0UPADrkrstRdPo8R9nnXSOdmigKRu6av2IlY7s= Received: by 10.78.198.14 with SMTP id v14mr779700huf.115.1209694729431; Thu, 01 May 2008 19:18:49 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Thu, 1 May 2008 19:18:49 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 22:18:49 -0400 From: "Shaun Sabo" To: "Jeremy Chadwick" In-Reply-To: <20080501204157.GA67015@eos.sc1.parodius.com> MIME-Version: 1.0 References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 02:18:51 -0000 since it is not 7-stable im interested in shouldnt i use the 7.0-RELEASE livefs? On Thu, May 1, 2008 at 4:41 PM, Jeremy Chadwick wrote: > On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote: > > I checked to make sure that the hard disks are not in raid configuration > and > > there are not. i also checked and my bios are at the latest version > > available (A11). also this is an XPS 600 not 700 and i have the correct > > users manual in paper and digital formats. how would you like the dmesg > to > > be presented? i dont think i have any way to writing it to a thumb drive > or > > such devices from the installer. should i just take digital pictures? > > Digital pictures would be fine, unless you want to try the serial > console route (chances are you don't have this sort of environment set > up, so it's probably more effective to take photos). > > One thing: does Linux detect your disks on this system? > > I'd recommend downloading one of the recent RELENG_7 snapshot CDs, > specifically the "livefs" one, and boot it. dmesg doesn't come with the > standard installation disc (disc1), hence why I'm recommending livefs. > The snapshots are available here: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 > > You probably want one of these two: > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-amd64-livefs.iso > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso > > dmesg should show some ATA stuff at the end, assuming you're familiar > with FreeBSD's kernel output. Something like this, assuming the > physical disks are detected: > > ad4: 190782MB at ata2-master SATA150 > ad6: 476940MB at ata3-master SATA300 > ad8: 476940MB at ata4-master SATA300 > ad10: 476940MB at ata5-master SATA300 > > You'll need to work backwards to figure out what is connected to what, > e.g.: > > $ dmesg | grep ata2 > ata2: on atapci1 > ata2: [ITHREAD] > ad4: 190782MB at ata2-master SATA150 > > $ dmesg | grep atapci1 > atapci1: port > 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem > 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 > atapci1: [ITHREAD] > atapci1: AHCI Version 01.10 controller with 4 ports detected > ata2: on atapci1 > ata3: on atapci1 > ata4: on atapci1 > ata5: on atapci1 > > Otherwise, if none of this works, you'll need to somehow provide the > full output of "pciconf -lv", which will be many screen fulls of data. > You'll probably have to pipe it through "more", take a shot, hit > spacebar, take another shot, etc... > > Please post URLs to the photos, rather than attaching them. The mailing > list software does not take kindly to large attachments. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 02:46:55 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBF931065675 for ; Fri, 2 May 2008 02:46:55 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 46D7A8FC14 for ; Fri, 2 May 2008 02:46:54 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id 13so1928102fge.35 for ; Thu, 01 May 2008 19:46:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=/UjImd8ZXaN+tKz32vjP8TNXyE9N913oieK+ZP9X0YQ=; b=Qh+wnXfVAe8EGTKrX091nNLlkpIJLcAuKxljUZzn1pBUKzrSoxzpiYlKzh7wD5/Kxyfex06NbjfwLAiSzSYljorvfrKXfLiF4BiXzVBVMvAvL+3sOzUDYtVs4sFSmDWeh4WmQqSewfNmMq1sU6E6hTvtH2h4mZ+d2lk+dbnLb+Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=xpTnhrhleBu4IQNYujCWJMZOm/vpamoF0MP6tDzFL8FarwZu8wUJpRmXHnSn4BzeHSXnKsABnkAoxuIdXvsB/JQJBV4skbirfwSBZ+HcNjemYwBJelnNAEqOc47XYdmmdSdw/MULkX4fk6RrMpFj8uFKXJsrQy70EGents5PAVs= Received: by 10.78.124.7 with SMTP id w7mr808837huc.60.1209696413725; Thu, 01 May 2008 19:46:53 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Thu, 1 May 2008 19:46:53 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 22:46:53 -0400 From: "Shaun Sabo" To: "Jeremy Chadwick" In-Reply-To: MIME-Version: 1.0 References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 02:46:56 -0000 i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went into fixit then to CD/DVD livefs it would ask me for the livefs cd (which i had in the drive and which i booted from) it looks like i cant even mount the image of the livefs disk from the cd-rom drive. also iv noticed that when i reboot after booting into the sysinstaller the bios gets about 2/3 of the way booted and stops and i have to hold the power and reboot to get back into opensuse/vista. On Thu, May 1, 2008 at 10:18 PM, Shaun Sabo wrote: > since it is not 7-stable im interested in shouldnt i use the 7.0-RELEASE > livefs? > > > On Thu, May 1, 2008 at 4:41 PM, Jeremy Chadwick > wrote: > > > On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote: > > > I checked to make sure that the hard disks are not in raid > > configuration and > > > there are not. i also checked and my bios are at the latest version > > > available (A11). also this is an XPS 600 not 700 and i have the > > correct > > > users manual in paper and digital formats. how would you like the > > dmesg to > > > be presented? i dont think i have any way to writing it to a thumb > > drive or > > > such devices from the installer. should i just take digital pictures? > > > > Digital pictures would be fine, unless you want to try the serial > > console route (chances are you don't have this sort of environment set > > up, so it's probably more effective to take photos). > > > > One thing: does Linux detect your disks on this system? > > > > I'd recommend downloading one of the recent RELENG_7 snapshot CDs, > > specifically the "livefs" one, and boot it. dmesg doesn't come with the > > standard installation disc (disc1), hence why I'm recommending livefs. > > The snapshots are available here: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 > > > > You probably want one of these two: > > > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-amd64-livefs.iso > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso > > > > dmesg should show some ATA stuff at the end, assuming you're familiar > > with FreeBSD's kernel output. Something like this, assuming the > > physical disks are detected: > > > > ad4: 190782MB at ata2-master SATA150 > > ad6: 476940MB at ata3-master SATA300 > > ad8: 476940MB at ata4-master SATA300 > > ad10: 476940MB at ata5-master SATA300 > > > > You'll need to work backwards to figure out what is connected to what, > > e.g.: > > > > $ dmesg | grep ata2 > > ata2: on atapci1 > > ata2: [ITHREAD] > > ad4: 190782MB at ata2-master SATA150 > > > > $ dmesg | grep atapci1 > > atapci1: port > > 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem > > 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 > > atapci1: [ITHREAD] > > atapci1: AHCI Version 01.10 controller with 4 ports detected > > ata2: on atapci1 > > ata3: on atapci1 > > ata4: on atapci1 > > ata5: on atapci1 > > > > Otherwise, if none of this works, you'll need to somehow provide the > > full output of "pciconf -lv", which will be many screen fulls of data. > > You'll probably have to pipe it through "more", take a shot, hit > > spacebar, take another shot, etc... > > > > Please post URLs to the photos, rather than attaching them. The mailing > > list software does not take kindly to large attachments. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 02:56:58 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 208D6106566B for ; Fri, 2 May 2008 02:56:58 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0DAB08FC1B for ; Fri, 2 May 2008 02:56:57 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id D49751CC05B; Thu, 1 May 2008 19:56:57 -0700 (PDT) Date: Thu, 1 May 2008 19:56:57 -0700 From: Jeremy Chadwick To: Shaun Sabo Message-ID: <20080502025657.GA82058@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 02:56:58 -0000 On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote: > i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went into > fixit then to CD/DVD livefs it would ask me for the livefs cd (which i had > in the drive and which i booted from) it looks like i cant even mount the > image of the livefs disk from the cd-rom drive. I'd recommend you burn one of the snapshot livefs images to a CD and boot it. This is what I was implying the first time around. It should give you a live FreeBSD system with common utilities. > also iv noticed that when i > reboot after booting into the sysinstaller the bios gets about 2/3 of the > way booted and stops and i have to hold the power and reboot to get back > into opensuse/vista. I don't understand what this means. "When I reboot after booting into the sysinstaller". Are you talking about FreeBSD sysinstall? Otherwise, any situation where the BIOS does not boot your hard disks sounds more like a BIOS or system problem and definitely has nothing to do with FreeBSD. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 03:03:18 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B905E1065673 for ; Fri, 2 May 2008 03:03:18 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 3C83D8FC0A for ; Fri, 2 May 2008 03:03:17 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id 13so1938208fge.35 for ; Thu, 01 May 2008 20:03:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=bYKHsulgQVx13PqT2E9Gk6RGZpSbkAYvvJeW7WBLv0c=; b=T67+F8WcnnA6AZgxSSTKOItcZyEuKOHH13fojqy45bkXUW1M7O2XhXHYMCTK4LqH4BOHRc0fpFr4vMxZ6jOf8CbKjMZp2Z4MudaTGKBQPPs/bPl5L88EBD4DoNpF7Pg8oQdiAkeNaMlZwvSOCbmazAIsLYsSl2gaJIqIIlrxehs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pLf73DpM+F1PYZxxgMbPQCGLw9LOLLqyEQ3R4jRquaKxSiA4WGMWTV93ElJfGmEIU3imCIBGNNPcUpcEkACUDAWZMOjOtIUOglwSkL9K06CBlou8jpLvFcBfFgUMwMvH31rin14od7fn6LFRIhQ0ffMaJ9Ryo4vtScF4o1G9vHo= Received: by 10.78.173.20 with SMTP id v20mr788957hue.100.1209697395212; Thu, 01 May 2008 20:03:15 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Thu, 1 May 2008 20:03:15 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 23:03:15 -0400 From: "Shaun Sabo" To: "Jeremy Chadwick" In-Reply-To: <20080502025657.GA82058@eos.sc1.parodius.com> MIME-Version: 1.0 References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 03:03:18 -0000 but then why does it not complain in freebsd 6.2, linux, or windows but it does in 7.0? and why i mean by the freebsd sysinstaller is the screen you get when you boot a freebsd disk or when you type sysinstall at a command line in a bsd system. i had the problem where it would only boot 2/3 of the way into the bios once before when i used debian, it was because debian was still on the 2.4 linux kernel and didnt support my mobo yet so it tried to detect it and you had to completely power off the system to get it to boot again, which seems like what is happening here. im going to try re-flashing the bios just to make sure that nothing is wrong with them. And also i tried both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount the livefs image. On Thu, May 1, 2008 at 10:56 PM, Jeremy Chadwick wrote: > On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote: > > i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went > into > > fixit then to CD/DVD livefs it would ask me for the livefs cd (which i > had > > in the drive and which i booted from) it looks like i cant even mount > the > > image of the livefs disk from the cd-rom drive. > > I'd recommend you burn one of the snapshot livefs images to a CD and > boot it. This is what I was implying the first time around. It should > give you a live FreeBSD system with common utilities. > > > also iv noticed that when i > > reboot after booting into the sysinstaller the bios gets about 2/3 of > the > > way booted and stops and i have to hold the power and reboot to get back > > into opensuse/vista. > > I don't understand what this means. "When I reboot after booting into > the sysinstaller". Are you talking about FreeBSD sysinstall? > > Otherwise, any situation where the BIOS does not boot your hard disks > sounds more like a BIOS or system problem and definitely has nothing to > do with FreeBSD. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 03:17:15 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 870EA1065676 for ; Fri, 2 May 2008 03:17:15 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by mx1.freebsd.org (Postfix) with ESMTP id DB5BB8FC17 for ; Fri, 2 May 2008 03:17:14 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1105412fkk.11 for ; Thu, 01 May 2008 20:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=T1OcNSsKI8iMBfWMGT7PSDXh0FyWtue6TVDEX+fgVJA=; b=ORnCT8NnogPHORr+/bokwXfHjHQ6/fBshZQGPrVINr5+k7G66LrsEXX+c46CGKyRTojRfuW6EVocmoBcOqO0FgX9weecxIzlTyCPe+ALEyEfeKFiHIzl2enC7r/GhPtWk9sER9QKPCjoENsVLZY1/hTtvBW0sgRD4kNc+To7qd4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=aGYxhcGhQ5Twt4UbUNkuMO+vkhJ2duEtkcf4/Z4VIgVEp86WqoeCz0imhaTOEyzbdtso7+JSpWZnHiS/xLYwwi6deRyZJZkuHAViMP5nQGNo0hZWO7vo8FWPKlsSlCUh4pIVCm8eEp7QzFvqTeozoeYtIFPofZ/eCfRtToU1GvA= Received: by 10.78.100.1 with SMTP id x1mr831631hub.16.1209698233511; Thu, 01 May 2008 20:17:13 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Thu, 1 May 2008 20:17:13 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 23:17:13 -0400 From: "Shaun Sabo" To: "Jeremy Chadwick" In-Reply-To: MIME-Version: 1.0 References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 03:17:15 -0000 re-flashed bios with latest version from dell's website. it was the same version but i re-flashed anyways and im still seeing the same behavior where i cant mount any disks to install or use the livefs. On Thu, May 1, 2008 at 11:03 PM, Shaun Sabo wrote: > but then why does it not complain in freebsd 6.2, linux, or windows but it > does in 7.0? and why i mean by the freebsd sysinstaller is the screen you > get when you boot a freebsd disk or when you type sysinstall at a command > line in a bsd system. i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was > still on the 2.4 linux kernel and didnt support my mobo yet so it tried to > detect it and you had to completely power off the system to get it to boot > again, which seems like what is happening here. im going to try re-flashing > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. > > On Thu, May 1, 2008 at 10:56 PM, Jeremy Chadwick > wrote: > > > On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote: > > > i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went > > into > > > fixit then to CD/DVD livefs it would ask me for the livefs cd (which i > > had > > > in the drive and which i booted from) it looks like i cant even mount > > the > > > image of the livefs disk from the cd-rom drive. > > > > I'd recommend you burn one of the snapshot livefs images to a CD and > > boot it. This is what I was implying the first time around. It should > > give you a live FreeBSD system with common utilities. > > > > > also iv noticed that when i > > > reboot after booting into the sysinstaller the bios gets about 2/3 of > > the > > > way booted and stops and i have to hold the power and reboot to get > > back > > > into opensuse/vista. > > > > I don't understand what this means. "When I reboot after booting into > > the sysinstaller". Are you talking about FreeBSD sysinstall? > > > > Otherwise, any situation where the BIOS does not boot your hard disks > > sounds more like a BIOS or system problem and definitely has nothing to > > do with FreeBSD. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 03:25:26 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0699E1065678 for ; Fri, 2 May 2008 03:25:26 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id E6AFF8FC0A for ; Fri, 2 May 2008 03:25:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id ADDFA1CC038; Thu, 1 May 2008 20:25:25 -0700 (PDT) Date: Thu, 1 May 2008 20:25:25 -0700 From: Jeremy Chadwick To: Shaun Sabo Message-ID: <20080502032525.GA83155@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 03:25:26 -0000 On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > but then why does it not complain in freebsd 6.2, linux, or windows but it > does in 7.0? FreeBSD 6.2 is very different than 7.0. :-) And you later state that Linux had the same problem as FreeBSD. And chances are, Dell has tested their system thoroughly on Windows, not Linux or FreeBSD, so device support under Windows is going to be quite solid. > and why i mean by the freebsd sysinstaller is the screen you > get when you boot a freebsd disk or when you type sysinstall at a command > line in a bsd system. I don't see what this has to do with your machine stalling 2/3rds of the way through its boot-up process. The only thing I can think of is that some kind of ATA request is causing the nF4 to lock up, and the BIOS isn't properly resetting it upon a soft reboot. > i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was > still on the 2.4 linux kernel and didnt support my mobo yet so it tried to > detect it and you had to completely power off the system to get it to boot > again, which seems like what is happening here. Okay, so this is useful knowledge. It means that Linux has also exhibited the same behaviour as FreeBSD, at least in the past, which means there may be some incompatibility with the devices on the motherboard. It would be useful to know what the Linux folks did to work around the problem. Since I know the nForce 4 works on FreeBSD, the only thing I can think of which might be causing chaos is ACPI, and there are many board manufacturers who release incorrect ACPI tables within in their BIOS. If you try booting either 7.0-RELEASE or 7.0-STABLE with ACPI disabled (it's one of the bootup menu items), does it help? > im going to try re-flashing > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. You're burning the livefs ISO image to a CD and booting it, correct? What is the exact error you get from FreeBSD when trying to boot the livefs CD? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Fri May 2 19:11:32 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79E531065678 for ; Fri, 2 May 2008 19:11:32 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id E2E9D8FC24 for ; Fri, 2 May 2008 19:11:31 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 21458 invoked by uid 2001); 2 May 2008 18:44:49 -0000 Date: Fri, 2 May 2008 13:44:49 -0500 From: "Rick C. Petty" To: Shaun Sabo Message-ID: <20080502184449.GA21226@keira.kiwi-computer.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 19:11:32 -0000 On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > line in a bsd system. i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was What do you mean by 2/3 of the way into the BIOS? Are you saying it only completes 2/3 of the POST? If so, it's not even getting to the point where it boots the CD. Or are you talking about 2/3 of the way through the kernel probes? If so, that's a problem I've seen a lot with Dells. In fact on a newly-purchased Dell 755, I couldn't get halfway through the POST about 75% of the time. Clearing the CMOS/RTC helped, and still about half of the time I boot into the FreeBSD kernel (7-STABLE) it would hang for no reason. Hitting the power button triggered an ACPI event to properly shutdown and restart, but it's damn annoying. > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. What do you mean by mointing the livefs image? Are you booting a different CD? It was recommended that you burn the livefs CD and then boot *it*. That should also take care of the mounting. -- Rick C. Petty From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 02:09:22 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4E3B1065671 for ; Sat, 3 May 2008 02:09:22 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 5DC9A8FC15 for ; Sat, 3 May 2008 02:09:22 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id 13so3226109fge.35 for ; Fri, 02 May 2008 19:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=m2HhvRDo2O6CiHkMwgEXqZNpjD0a9G/T5ZD6/Iae6vU=; b=XF+znxLiiOVJKtJhk3bp6WK2NI73+bPcJ3RYm43IEapyXQGiNkV/eCqPI7AG3mh55MTyGigbUbIkZEOD0mTO8XjxtuTOanMpVuwTwgc/WvRPNpZ6MNHiFqpvGd5+OiYzSh2ArLqsycbYp8UXfcvG9jqG6jNZo7KMHQIQ8j2GSUI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LshqvZQmsfSXZtrhdZst31QWFVzsCheM9h/bMEMyjGNu301f4mamnBs//MnWxuSucqqVSNcO0Q+QVYF0UNAt0/8MyMdOESTb5SULefUrNgC6tMdvdRECxp1J4EsQngORpq9kIAkYik95VxDu9O9VjsC7+hRIKUmzmIGYOiHT8Ww= Received: by 10.78.204.7 with SMTP id b7mr1064618hug.27.1209780561044; Fri, 02 May 2008 19:09:21 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Fri, 2 May 2008 19:09:20 -0700 (PDT) Message-ID: Date: Fri, 2 May 2008 22:09:20 -0400 From: "Shaun Sabo" To: rick-freebsd@kiwi-computer.com In-Reply-To: <20080502184449.GA21226@keira.kiwi-computer.com> MIME-Version: 1.0 References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 02:09:23 -0000 What happens with the bios is i start with the machine off. turn it on. boot into any freebsd 7 based disk. ill exit the disk and tell it to reboot the system. the system shuts down and it goes to turn on again. when you turn on a dell computer a progress bar will fill and then it will go to the boot loader/active partition, i believe that it initializes the bios settings. what happens after i reboot out of the freebsd 7 based disks is the progress bar hangs at about 2/3 full. i can boot into a cd or operating system fine if i turn the machine completely off but something isnt re-settting when i reboot out of freebsd. this used to happen when i tried using debian linux because debian was still on the 2.4 kernel which did not have support for my motherboard so i couldnt even boot the debian installer cd. i also tried booting the freebsd installer disks without apic but the same problem occurs so i dont think its hanging because of the power managment. as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs cds. when i boot them up it gets to the sysinstall program like all of the other disks do. to use the livefs functions you have to go into fixit and then choose the CD/DVD option. what this does is it mounts the filesystem kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) and use the system as a recovery disk or for dmesg and such. the error i get is "could not mount the livefs cd. try again?" for some reason i cannot mount any sort of media in freebsd 7 systems. the computer handles the booting of the cd's fine but freebsd cannot for some reason handle the mounting of disks. the next step im going to take is installing 6.2 and remaking the world but adding device aptic to the kernel. On Fri, May 2, 2008 at 2:44 PM, Rick C. Petty < rick-freebsd@kiwi-computer.com> wrote: > On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > > line in a bsd system. i had the problem where it would only boot 2/3 of > the > > way into the bios once before when i used debian, it was because debian > was > > What do you mean by 2/3 of the way into the BIOS? Are you saying it only > completes 2/3 of the POST? If so, it's not even getting to the point > where > it boots the CD. Or are you talking about 2/3 of the way through the > kernel probes? If so, that's a problem I've seen a lot with Dells. In > fact on a newly-purchased Dell 755, I couldn't get halfway through the > POST > about 75% of the time. Clearing the CMOS/RTC helped, and still about half > of the time I boot into the FreeBSD kernel (7-STABLE) it would hang for no > reason. Hitting the power button triggered an ACPI event to properly > shutdown and restart, but it's damn annoying. > > > the bios just to make sure that nothing is wrong with them. And also i > tried > > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot > mount > > the livefs image. > > What do you mean by mointing the livefs image? Are you booting a > different > CD? It was recommended that you burn the livefs CD and then boot *it*. > That should also take care of the mounting. > > -- Rick C. Petty > From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 02:42:41 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 353721065672 for ; Sat, 3 May 2008 02:42:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1752E8FC15 for ; Sat, 3 May 2008 02:42:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id F041B1CC038; Fri, 2 May 2008 19:42:40 -0700 (PDT) Date: Fri, 2 May 2008 19:42:40 -0700 From: Jeremy Chadwick To: Shaun Sabo Message-ID: <20080503024240.GA28006@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: rick-freebsd@kiwi-computer.com, freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 02:42:41 -0000 On Fri, May 02, 2008 at 10:09:20PM -0400, Shaun Sabo wrote: > What happens with the bios is i start with the machine off. turn it on. boot > into any freebsd 7 based disk. ill exit the disk and tell it to reboot the > system. the system shuts down and it goes to turn on again. when you turn on > a dell computer a progress bar will fill and then it will go to the boot > loader/active partition, i believe that it initializes the bios settings. > what happens after i reboot out of the freebsd 7 based disks is the progress > bar hangs at about 2/3 full. i can boot into a cd or operating system fine > if i turn the machine completely off but something isnt re-settting when i > reboot out of freebsd. this used to happen when i tried using debian linux > because debian was still on the 2.4 kernel which did not have support for my > motherboard so i couldnt even boot the debian installer cd. i also tried > booting the freebsd installer disks without apic but the same problem occurs > so i dont think its hanging because of the power managment. APIC != ACPI. If you disabled the APIC, you'd be changing the method of interrupt routing used by FreeBSD, which won't affect power management. Additionally, you need to understand that ACPI isn't used for just power management. It's used to define system parameters via a series of tables which are stored in the BIOS. There are a lot of motherboard manufacturers who have improper ACPI tables stored in their BIOS (read: BIOS bugs), and by disabling ACPI, one can sometimes work around odd problems with devices not working correctly, or odd system hangs. Finally, the behaviour you're experiencing with your machine (re: the progress bar stalling 2/3rds of the way through) sounds almost as if the hard disks aren't spinning up quick enough after a soft reset from within FreeBSD or Linux 2.4. If there's a BIOS option to "delay hard disk startup", I would recommend setting that to 1-2 seconds and see what happens. Otherwise, this really sounds like a BIOS bug, and much less like a FreeBSD or Linux bug. I realise it may not happen with Linux 2.6, but possibly their reboot method changed. FreeBSD has a couple sysctls you can change which adjust the reboot method used. One disabled ACPI during the reboot phase, which can sometimes cause the system to hang/lock before the reboot is complete. Another uses ACPI itself to do the rebooting, vs. (I believe) an older system reboot method. These are the sysctls and their default values: hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 > as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs > cds. when i boot them up it gets to the sysinstall program like all of the > other disks do. to use the livefs functions you have to go into fixit and > then choose the CD/DVD option. what this does is it mounts the filesystem > kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) and > use the system as a recovery disk or for dmesg and such. the error i get is > "could not mount the livefs cd. try again?" Okay, you're confusing two things. livefs != fixit. What it sounds to me like you're doing is booting a CD of "disc1" and then going into the Fixit menu. If you do this then insert a livefs CD, it's not going to work. When you boot a CD burnt with "livefs", the FreeBSD kernel will start, and you'll be immediately dropped into a shell with a whole ton of available utilities. It's basically a working FreeBSD system on a CD, which is why it's called livefs. > for some reason i cannot mount any sort of media in freebsd 7 systems. > the computer handles the booting of the cd's fine but freebsd cannot > for some reason handle the mounting of disks. the next step im going > to take is installing 6.2 and remaking the world but adding device > aptic to the kernel. I think you mean "device apic" to the kernel? Please see the first paragraph above; I think you're misunderstanding ACPI vs. APIC. You should follow the standard devices listed in the GENERIC configuration. This includes support for APICs, as well as SMP. Look at /sys/i386/conf/GENERIC, or /sys/amd64/conf/GENERIC (depending on if you went i386 or amd64). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 03:33:11 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92085106566B for ; Sat, 3 May 2008 03:33:11 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 0CCA48FC13 for ; Sat, 3 May 2008 03:33:10 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m433X9L74258; Fri, 2 May 2008 20:33:09 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id DAA29798; Sat, 3 May 2008 03:31:35 GMT Message-Id: <200805030331.DAA29798@sopwith.solgatos.com> To: Jeremy Chadwick In-reply-to: Your message of "Fri, 02 May 2008 19:42:40 PDT." <20080503024240.GA28006@eos.sc1.parodius.com> Date: Fri, 02 May 2008 20:31:35 +0100 From: Dieter Cc: Shaun Sabo , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 03:33:11 -0000 > Finally, the behaviour you're experiencing with your machine (re: the > progress bar stalling 2/3rds of the way through) sounds almost as if the > hard disks aren't spinning up quick enough after a soft reset from > within FreeBSD or Linux 2.4. The disks should have spun up long before a reset gets issued. > > for some reason i cannot mount any sort of media in freebsd 7 systems. > > the computer handles the booting of the cd's fine but freebsd cannot > > for some reason handle the mounting of disks. It is the firmware (and maybe a bootstrap) that boots a CD. Once control is handed over to the FreeBSD kernel, then the kernel has to be able to talk to the disks. It is the FreeBSD 7 kernel that is having the problem. > > the next step im going > > to take is installing 6.2 and remaking the world but adding device > > aptic to the kernel. > > I think you mean "device apic" to the kernel? No, it is "device aptic". It was in 6 but removed from 7. I had to add aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 03:53:07 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60C4B1065670 for ; Sat, 3 May 2008 03:53:07 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id AA9EC8FC18 for ; Sat, 3 May 2008 03:53:06 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id 13so3314792fge.35 for ; Fri, 02 May 2008 20:53:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=hX2dDBX+8pUZNjhsEhC0O5jpQ9puxK7IJmppCBty3C8=; b=gBEBgjKTdyVW79f1mLC5mICjhULfgQzcQ6Mo8sDEqh1IAqvu6RD79D2OncJIBENT7vF1OQ3E2PxTcJzDFBuMTjYtNfsWGA7paPvb/tqW5dqWQTVamfVsKYfq0GQnjgT1+gaWlV6LQlzmT3xL0/oMptADDpFqSRs/Sl/KUWxaRV0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=O2HmytcmPIChH21P5Bo5kO08zdJswdYpRkMuolkhgSesbZT022gWXv/JQ/2KlxIYDVJ/FKHavxXuNtd4u1mmlIFdWBOhe4sjBS1mD8l7rlf3e16VtFmSNXoM1U4kzZNNidF7DnZWopbYkXx8vSBdbGkfOpEeVtcqBHobgTHtvR0= Received: by 10.78.182.17 with SMTP id e17mr1061194huf.57.1209786784611; Fri, 02 May 2008 20:53:04 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Fri, 2 May 2008 20:53:04 -0700 (PDT) Message-ID: Date: Fri, 2 May 2008 23:53:04 -0400 From: "Shaun Sabo" To: "Jeremy Chadwick" In-Reply-To: <20080503024240.GA28006@eos.sc1.parodius.com> MIME-Version: 1.0 References: <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> <20080503024240.GA28006@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: rick-freebsd@kiwi-computer.com, freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 03:53:07 -0000 the livefs cds do not drop you into a shell. they drop you into the same screen you see when you insert an installation cd. try it on qemu or another virtualization program or even boot one up if you have a spare cd rom. in order to access the livefs shell you need to navigate to the fixit menu and then go to the livefs CD/DVD option. as for the apic vc acpi that was a typo due to exhaustion, sorry bout that. On Fri, May 2, 2008 at 10:42 PM, Jeremy Chadwick wrote: > On Fri, May 02, 2008 at 10:09:20PM -0400, Shaun Sabo wrote: > > What happens with the bios is i start with the machine off. turn it on. > boot > > into any freebsd 7 based disk. ill exit the disk and tell it to reboot > the > > system. the system shuts down and it goes to turn on again. when you > turn on > > a dell computer a progress bar will fill and then it will go to the boot > > loader/active partition, i believe that it initializes the bios > settings. > > what happens after i reboot out of the freebsd 7 based disks is the > progress > > bar hangs at about 2/3 full. i can boot into a cd or operating system > fine > > if i turn the machine completely off but something isnt re-settting when > i > > reboot out of freebsd. this used to happen when i tried using debian > linux > > because debian was still on the 2.4 kernel which did not have support > for my > > motherboard so i couldnt even boot the debian installer cd. i also tried > > booting the freebsd installer disks without apic but the same problem > occurs > > so i dont think its hanging because of the power managment. > > APIC != ACPI. If you disabled the APIC, you'd be changing the method of > interrupt routing used by FreeBSD, which won't affect power management. > Additionally, you need to understand that ACPI isn't used for just power > management. It's used to define system parameters via a series of > tables which are stored in the BIOS. There are a lot of motherboard > manufacturers who have improper ACPI tables stored in their BIOS (read: > BIOS bugs), and by disabling ACPI, one can sometimes work around odd > problems with devices not working correctly, or odd system hangs. > > Finally, the behaviour you're experiencing with your machine (re: the > progress bar stalling 2/3rds of the way through) sounds almost as if the > hard disks aren't spinning up quick enough after a soft reset from > within FreeBSD or Linux 2.4. If there's a BIOS option to "delay hard > disk startup", I would recommend setting that to 1-2 seconds and see > what happens. Otherwise, this really sounds like a BIOS bug, and much > less like a FreeBSD or Linux bug. I realise it may not happen with > Linux 2.6, but possibly their reboot method changed. > > FreeBSD has a couple sysctls you can change which adjust the reboot > method used. One disabled ACPI during the reboot phase, which can > sometimes cause the system to hang/lock before the reboot is complete. > Another uses ACPI itself to do the rebooting, vs. (I believe) an older > system reboot method. These are the sysctls and their default values: > > hw.acpi.disable_on_reboot: 0 > hw.acpi.handle_reboot: 0 > > > as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs > > cds. when i boot them up it gets to the sysinstall program like all of > the > > other disks do. to use the livefs functions you have to go into fixit > and > > then choose the CD/DVD option. what this does is it mounts the > filesystem > > kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) > and > > use the system as a recovery disk or for dmesg and such. the error i get > is > > "could not mount the livefs cd. try again?" > > Okay, you're confusing two things. livefs != fixit. What it sounds to > me like you're doing is booting a CD of "disc1" and then going into the > Fixit menu. If you do this then insert a livefs CD, it's not going to > work. > > When you boot a CD burnt with "livefs", the FreeBSD kernel will start, > and you'll be immediately dropped into a shell with a whole ton of > available utilities. It's basically a working FreeBSD system on a CD, > which is why it's called livefs. > > > for some reason i cannot mount any sort of media in freebsd 7 systems. > > the computer handles the booting of the cd's fine but freebsd cannot > > for some reason handle the mounting of disks. the next step im going > > to take is installing 6.2 and remaking the world but adding device > > aptic to the kernel. > > I think you mean "device apic" to the kernel? Please see the first > paragraph above; I think you're misunderstanding ACPI vs. APIC. > > You should follow the standard devices listed in the GENERIC > configuration. This includes support for APICs, as well as SMP. Look > at /sys/i386/conf/GENERIC, or /sys/amd64/conf/GENERIC (depending on if > you went i386 or amd64). > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 04:02:08 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F8AE106566C for ; Sat, 3 May 2008 04:02:08 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id C4D048FC19 for ; Sat, 3 May 2008 04:02:07 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 26675 invoked by uid 2001); 3 May 2008 04:02:07 -0000 Date: Fri, 2 May 2008 23:02:06 -0500 From: "Rick C. Petty" To: Shaun Sabo Message-ID: <20080503040206.GA26564@keira.kiwi-computer.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 04:02:08 -0000 On Fri, May 02, 2008 at 10:09:20PM -0400, Shaun Sabo wrote: > What happens with the bios is i start with the machine off. turn it on. boot > into any freebsd 7 based disk. ill exit the disk and tell it to reboot the > system. the system shuts down and it goes to turn on again. when you turn on > a dell computer a progress bar will fill and then it will go to the boot > loader/active partition, i believe that it initializes the bios settings. > what happens after i reboot out of the freebsd 7 based disks is the progress > bar hangs at about 2/3 full. i can boot into a cd or operating system fine > if i turn the machine completely off but something isnt re-settting when i > reboot out of freebsd. this used to happen when i tried using debian linux This sounds like a BIOS bug. FreeBSD has no control over what happens while the BIOS is doing a cold restart, until the initial boot record is read and then executed. AFAIR, there are two ways FreeBSD initiates a warm restart.. via a BIOS call or using ACPI. In either case, the hardware and the firmware controlling said hardware (which we call the BIOS) is responsible for ensuring everything gets initialized correctly. There's not much that FreeBSD can do, although you could try with and without ACPI and see if one works better than another. This situation reinforces my belief that Dell has problems with their BIOS firmware. I've yet to see a Dell behave as well as any system I've built myself. > as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs > cds. when i boot them up it gets to the sysinstall program like all of the > other disks do. Then I don't believe you are using the livecd. If you're hitting sysinstall, you must be using the bootonly, disc1, or fixit CDs. > to use the livefs functions you have to go into fixit and > then choose the CD/DVD option. what this does is it mounts the filesystem > kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) and > use the system as a recovery disk or for dmesg and such. the error i get is > "could not mount the livefs cd. try again?" Then that rules out fixit CD. I thought even the bootonly & disk1 images had a minimal (i.e. useless) image and that this step is always successful. > for some reason i cannot mount any sort of media in freebsd 7 systems. I assume you mean from a freebsd 7.0-RELEASE CD image? Otherwise that's a pretty bold statement. If true, then this may be a driver issue that I've never heard of. > the computer handles the booting of > the cd's fine but freebsd cannot for some reason handle the mounting of > disks. What is the name of the image you downloaded, perhaps the full URL you grabbed it from? It was suggested that you try a post-7.0 livecd. I've had very good luck with these, both using and creating them. > the next step im going to take is installing 6.2 and remaking the > world but adding device aptic to the kernel. What is this "aptic" device? I can't seem to find it on any 6.x or 7.x system. Perhaps it is a typo? Please explain. -- Rick C. Petty From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 04:09:31 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2CEB1065674 for ; Sat, 3 May 2008 04:09:31 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 4F04F8FC12 for ; Sat, 3 May 2008 04:09:31 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 26754 invoked by uid 2001); 3 May 2008 04:09:30 -0000 Date: Fri, 2 May 2008 23:09:30 -0500 From: "Rick C. Petty" To: Shaun Sabo Message-ID: <20080503040930.GB26564@keira.kiwi-computer.com> References: <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> <20080503024240.GA28006@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 04:09:31 -0000 On Fri, May 02, 2008 at 11:53:04PM -0400, Shaun Sabo wrote: > the livefs cds do not drop you into a shell. they drop you into the same > screen you see when you insert an installation cd. try it on qemu or another > virtualization program or even boot one up if you have a spare cd rom. in > order to access the livefs shell you need to navigate to the fixit menu and > then go to the livefs CD/DVD option. Please explain where you obtained said "livefs" CD. Every livefs CD I've tried (in qemu) has dropped me to a shell. Every "fixit" CD I've tried brings me to sysinstall and from there I drop to the shell after navigating the menus. > as for the apic vc acpi that was a typo > due to exhaustion, sorry bout that. Sure, but which one do you mean? I assume you mean booting with or without ACPI, which is an option in the boot loader. > > > motherboard so i couldnt even boot the debian installer cd. i also tried > > > booting the freebsd installer disks without apic but the same problem > > occurs > > > so i dont think its hanging because of the power managment. ACPI isn't just power management-- it's advanced _configuration_ and power interface. My understanding is that if present, FreeBSD talks to the ACPI on the BIOS to allocate IRQs and other resources. There have been bugs in the past when dealing with ACPI which caused the FreeBSD devs to include a boot option to disable it. If your system breaks w/o ACPI, then there's certainly a BIOS firmware problem. Have you tried the following test? Cold boot (from power off) to FreeBSD CD, disable ACPI from the menu, boot the kernel, then do a warm reboot and see if the problem exists. My sense is that if your first attempt from a cold start has ACPI enabled, the problem will persist for every subsequent warm reboot. -- Rick C. Petty From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 04:25:41 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CE3E1065671 for ; Sat, 3 May 2008 04:25:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id F18FD8FC16 for ; Sat, 3 May 2008 04:25:40 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id D80861CC038; Fri, 2 May 2008 21:25:40 -0700 (PDT) Date: Fri, 2 May 2008 21:25:40 -0700 From: Jeremy Chadwick To: Dieter Message-ID: <20080503042540.GA32245@eos.sc1.parodius.com> References: <20080503024240.GA28006@eos.sc1.parodius.com> <200805030331.DAA29798@sopwith.solgatos.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200805030331.DAA29798@sopwith.solgatos.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Shaun Sabo , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 04:25:41 -0000 On Fri, May 02, 2008 at 08:31:35PM +0100, Dieter wrote: > > Finally, the behaviour you're experiencing with your machine (re: the > > progress bar stalling 2/3rds of the way through) sounds almost as if the > > hard disks aren't spinning up quick enough after a soft reset from > > within FreeBSD or Linux 2.4. > > The disks should have spun up long before a reset gets issued. Not necessarily. It ultimately depends on what the system is engineered to do during a soft reboot. The disks themselves may be powering down briefly, may take a long time to initialise, or maybe there's a bug in the drive firmware. My personal guess is that it's a BIOS bug. > > > for some reason i cannot mount any sort of media in freebsd 7 systems. > > > the computer handles the booting of the cd's fine but freebsd cannot > > > for some reason handle the mounting of disks. > > It is the firmware (and maybe a bootstrap) that boots a CD. > Once control is handed over to the FreeBSD kernel, then the > kernel has to be able to talk to the disks. It is the FreeBSD 7 > kernel that is having the problem. Again, not necessarily. I think I've provided enough evidence of where BIOS settings can affect FreeBSD's behaviour when it comes to disk controllers. My RAID question was one such example. > > > the next step im going > > > to take is installing 6.2 and remaking the world but adding device > > > aptic to the kernel. > > > > I think you mean "device apic" to the kernel? > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" /usr/src on our RELENG_6 box and found absolutely no trace of said device. You are thinking of "apic". -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 06:04:45 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8233E1065671; Sat, 3 May 2008 06:04:45 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 027D98FC14; Sat, 3 May 2008 06:04:44 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m4364hp74279; Fri, 2 May 2008 23:04:43 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id GAA23115; Sat, 3 May 2008 06:03:16 GMT Message-Id: <200805030603.GAA23115@sopwith.solgatos.com> To: Jeremy Chadwick In-reply-to: Your message of "Fri, 02 May 2008 21:25:40 PDT." <20080503042540.GA32245@eos.sc1.parodius.com> Date: Fri, 02 May 2008 23:03:16 +0100 From: Dieter Cc: Shaun Sabo , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 06:04:45 -0000 > > > > the next step im going > > > > to take is installing 6.2 and remaking the world but adding device > > > > aptic to the kernel. > > > > > > I think you mean "device apic" to the kernel? > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > /usr/src on our RELENG_6 box and found absolutely no trace of said > device. You are thinking of "apic". Typo. Should be "device atpic". From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 14:46:14 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 011081065671 for ; Sat, 3 May 2008 14:46:14 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id 743A88FC17 for ; Sat, 3 May 2008 14:46:12 +0000 (UTC) (envelope-from shaun.bsd@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so16155fkk.11 for ; Sat, 03 May 2008 07:46:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=Q8UU5N37ZOwXr2364mzYB/zvRH3dIPj+nIvpxnkIGsQ=; b=VgB8S59IvodFT4fQQXEqVwvphYSNMLa4kFUPuXXFs+7W4iTJvMRmaxWQVZE8olp7DxeB+TZalpdaMHcX2gjgbCwNyON+7PqEjL58yb/LC2B9kgglz8zBcKPsNSk6xEuD7uDlm+ZElDA2tqM66LrHDjW/krWbayar5PECZ3T59v8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KLP3EBuKsJcxj/xiDABaUIYDpX77WmqoZn5VmcdD2wOn9or8jL/pLo1AHdlET9KYko+W2BBF141heudQas7pJekuIEbmoT9Rm35fQVJE04TiM+a5z77OLadLn7eehSRxbLy0/2MqS6Gr52Kjjt+RtHLQ3DEENtUbedNtz2O+9Rw= Received: by 10.78.81.2 with SMTP id e2mr1179043hub.13.1209825971276; Sat, 03 May 2008 07:46:11 -0700 (PDT) Received: by 10.78.180.19 with HTTP; Sat, 3 May 2008 07:46:11 -0700 (PDT) Message-ID: Date: Sat, 3 May 2008 10:46:11 -0400 From: "Shaun Sabo" To: rick-freebsd@kiwi-computer.com In-Reply-To: <20080503040930.GB26564@keira.kiwi-computer.com> MIME-Version: 1.0 References: <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> <20080503024240.GA28006@eos.sc1.parodius.com> <20080503040930.GB26564@keira.kiwi-computer.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 14:46:14 -0000 the livefs cd links are 7.0-RELEASE ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.0/7.0-RELEASE-i386-livefs.iso 7-STABLE ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso i tried these in vmware and on another computer and neither one drops me into a shell. they both put me in the sysinstall program and i have to activate the livefs from the fixit menu then go to virtual terminal 4 (alt+f4). problem is i cant get the livefs shell to start on my system. works fine in vmware, qemu, and my sisters computer so i know there isnt something wrong with the cds. Im really not too concerned about the bios bug. i just figured it might be a side effect of freebsd not being able access the disks. just out of curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic device supposed to do? as for not being able to mount any media from any freebsd 7.0 system. this includes when i rebuilt the kernel and world from 6.2 to 7.0 with the generic kernel. when i tried booting it was not able to find the root partition. the install and livefs cds can also not find the hard disks nor can you use the livefs utilities as stated above. On Sat, May 3, 2008 at 12:09 AM, Rick C. Petty < rick-freebsd@kiwi-computer.com> wrote: > On Fri, May 02, 2008 at 11:53:04PM -0400, Shaun Sabo wrote: > > the livefs cds do not drop you into a shell. they drop you into the same > > screen you see when you insert an installation cd. try it on qemu or > another > > virtualization program or even boot one up if you have a spare cd rom. > in > > order to access the livefs shell you need to navigate to the fixit menu > and > > then go to the livefs CD/DVD option. > > Please explain where you obtained said "livefs" CD. Every livefs CD I've > tried (in qemu) has dropped me to a shell. Every "fixit" CD I've tried > brings me to sysinstall and from there I drop to the shell after > navigating > the menus. > > > as for the apic vc acpi that was a typo > > due to exhaustion, sorry bout that. > > Sure, but which one do you mean? I assume you mean booting with or > without > ACPI, which is an option in the boot loader. > > > > > motherboard so i couldnt even boot the debian installer cd. i also > tried > > > > booting the freebsd installer disks without apic but the same > problem > > > occurs > > > > so i dont think its hanging because of the power managment. > > ACPI isn't just power management-- it's advanced _configuration_ and power > interface. My understanding is that if present, FreeBSD talks to the ACPI > on the BIOS to allocate IRQs and other resources. There have been bugs in > the past when dealing with ACPI which caused the FreeBSD devs to include a > boot option to disable it. If your system breaks w/o ACPI, then there's > certainly a BIOS firmware problem. > > Have you tried the following test? Cold boot (from power off) to FreeBSD > CD, disable ACPI from the menu, boot the kernel, then do a warm reboot and > see if the problem exists. My sense is that if your first attempt from a > cold start has ACPI enabled, the problem will persist for every subsequent > warm reboot. > > -- Rick C. Petty > From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 16:05:17 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1A5D1065670 for ; Sat, 3 May 2008 16:05:17 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 608C18FC18 for ; Sat, 3 May 2008 16:05:17 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m43G5Bv77252; Sat, 3 May 2008 09:05:11 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id QAA03668; Sat, 3 May 2008 16:03:45 GMT Message-Id: <200805031603.QAA03668@sopwith.solgatos.com> To: "Shaun Sabo" In-reply-to: Your message of "Sat, 03 May 2008 10:46:11 EDT." Date: Sat, 03 May 2008 09:03:45 +0100 From: Dieter Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 16:05:18 -0000 > Im really not too concerned about the bios bug. i just figured it might be a > side effect of freebsd not being able access the disks. just out of > curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic > device supposed to do? My understanding is that atpic is the old way of mapping interrupts, and apic is the new way. If apic doesn't work for whatever reason, you need atpic. I was was getting lots of errors like Could not allocate irq attach returned 6 no driver attached Can't map interrupt -> can't attach driver -> can't talk to disks -> can't mount root From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 17:34:08 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE6B7106567F for ; Sat, 3 May 2008 17:34:08 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id A23098FC0C for ; Sat, 3 May 2008 17:34:08 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 91D6E1CC05B; Sat, 3 May 2008 10:34:08 -0700 (PDT) Date: Sat, 3 May 2008 10:34:08 -0700 From: Jeremy Chadwick To: Dieter Message-ID: <20080503173408.GA58602@eos.sc1.parodius.com> References: <20080503042540.GA32245@eos.sc1.parodius.com> <200805030603.GAA23115@sopwith.solgatos.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200805030603.GAA23115@sopwith.solgatos.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Shaun Sabo , freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 17:34:08 -0000 On Fri, May 02, 2008 at 11:03:16PM +0100, Dieter wrote: > > > > > the next step im going > > > > > to take is installing 6.2 and remaking the world but adding device > > > > > aptic to the kernel. > > > > > > > > I think you mean "device apic" to the kernel? > > > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. > > > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > > /usr/src on our RELENG_6 box and found absolutely no trace of said > > device. You are thinking of "apic". > > Typo. Should be "device atpic". Ah yes. That would be the classic AT-style PIC used for interrupt handling. That makes much more sense. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |