From owner-freebsd-current@FreeBSD.ORG Tue Nov 6 10:17:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 850E516A469 for ; Tue, 6 Nov 2007 10:17:23 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.freebsd.org (Postfix) with ESMTP id 2744B13C494 for ; Tue, 6 Nov 2007 10:17:22 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so1767728wxd for ; Tue, 06 Nov 2007 02:17:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=EWjYksXDfQPreFE2Lq3UwXT7mWO5bfw2LPXjQX4Dejk=; b=qOLbKmOjJbf4VJBCKTabP4ckmKytLfqBvIZyLifwIEYl55k3YUoaJCweq4xLs7Lb32xt/vA8h0DzCwRyV32U/u+1nKkoHWs2RrOQyOIA9+USZskSOoyngke98vC3hLVqD/5ZsCG9zzBY2d9u2wpJZXl9yDZH2yHTH35eu0uQJWk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NweCHVVb6jmaIDEdJqmsfTlXxTf2G5Q+rXQweezlP7LVLJLXlNQw86H6c0jnW1YkkaZow6od3KQ99s3rtvtBxszs0NS787zhCoT+PVwqUbiOzwDx6C1ukzCSLnKXLzmdb2sdmZjJmykh1TAcSG59TTDF4OfM0/BjsswbRFM1qzE= Received: by 10.90.89.5 with SMTP id m5mr4125590agb.1194344231344; Tue, 06 Nov 2007 02:17:11 -0800 (PST) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id v26sm10828762ele.2007.11.06.02.17.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 06 Nov 2007 02:17:08 -0800 (PST) Message-ID: <47303F22.7080809@gmail.com> Date: Tue, 06 Nov 2007 05:17:06 -0500 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: Jeremy Chadwick References: <472F5D9A.9050900@delphij.net> <472FCC15.9040903@gmail.com> <472FD0FB.9090608@delphij.net> <472FD23E.1060001@delphij.net> <47301CF6.8030808@delphij.net> <47301E91.7070303@gmail.com> <47301F40.8070605@delphij.net> <47302667.8030900@gmail.com> <20071106091409.GB83703@eos.sc1.parodius.com> <473035D4.3030200@gmail.com> <20071106095720.GA84549@eos.sc1.parodius.com> In-Reply-To: <20071106095720.GA84549@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, d@delphij.net, Justin Hibbits Subject: Re: [ANNOUNCEMENT] Wiki for discussing P35/IHC9(R)/SATA issues set up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2007 10:17:23 -0000 Jeremy Chadwick wrote: > On Tue, Nov 06, 2007 at 04:37:24AM -0500, Aryeh M. Friedman wrote: > >> yes btw due to god knows what reason the patch renumbered ad8 to ad6 >> > > That can be discussed in the future. ATA device numbering (that is to > say, the X of an "adX" device) has always been a little odd in my > experiences. Turning on or off a ATA interface (PATA or SATA) seems to > adjust the numbering, regardless of ATA_STATIC_ID or not. It's likely > that I do not understand what the kernel option does. > > >>> 1) Have you verified that the SATA150-limiting jumper on your Seagate >>> drive has been removed? SATA300 drives from Seagate come from the >>> factory with that jumper connected, limiting the drive to SATA150. >>> >>> >> I will check but: >> >> 1. I was unaware of this "feature" >> 2. I didn't see any jumpers when I installed it >> > > The jumper is very tiny, usually gray, and on the back of the drive next > to the SATA interface port. It's documented both on the drive itself, > and in the product manual for the Barracuda 7200.10 -- see Section 3.2: > > http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.10/100402371h.pdf > > The default (SATA150) is chosen because of known issues with SATA300 on > older nForce chipsets. Seagate chose to limit the drives to SATA150 via > a jumper, so that they would work on all machines, regardless of buggy > or incompatible chipsets. > See reply to Xi Lin but odd it was right where the manual said it was but when I built the machine I remember not seeing it and/or any mention of it in the manual (I was using the online manual so might be slightly diff then the shipped one) > >>> 2) Do you happen to be using a PATA-to-SATA adapter on the DVD drive? >>> >>> >> It is native SATA (300) >> >>> 3) If No to #2, are you sure that the ICH9 does SATA300 with ATAPI >>> devices? Does the mainboard BIOS even support it for ATAPI? >>> >> Mobo has ATAPI I am not sure about the IHC issue though... will look it >> up and get back to you. >> > > My motherboard also has SATA ATAPI support -- but my DVD drives are > SATA150. I have never seen a SATA300 ATAPI drive. Now, that said -- I > *have* seen Fujitsu hard disks which claimed to be SATA300 capable but > weren't. It turned out to be false advertising; the SATA chip they used > on their drives did not support SATA300, yet their product manual and > ads said it did. > > This may be the case with your DVD drive as well. I would not put it > past a manufacturer to put incorrect information in their product specs. > OEM so no freaking idea > Also, you do realise that having a SATA150 drive on your SATA bus does > not mean that the entire bus runs at 150MB/sec, correct? It's not like > SCSI. So there should be no performance hit having a single SATA150 > drive on SATA controller also filled with SATA300 devices. > My mobo uses seperate controllers for each SATA slot (I know you can chain them but I am using one per controler): Note ata2 is PATA all the rest are SATA ATA channel 2: Master: ad4 ATA/ATAPI revision 7 Slave: ad5 ATA/ATAPI revision 7 ATA channel 3: Master: ad6 Serial ATA II Slave: no device present ATA channel 4: Master: acd0 Serial ATA v1.0 Slave: no device present ATA channel 5: Master: no device present Slave: no device present ATA channel 6: Master: no device present Slave: no device present > In the future, take proper time to thoroughly read about the hardware > you purchase, or at a bare minimum, read the labels manufacturers put on > their products. :-) > There was no label and as I said above I don't remember seeing any thing in the manual. > However: your PATA ports becoming unusable/disabled when you enable SATA > in the BIOS could be either a BIOS bug (or "feature") or a FreeBSD bug. > I would not put it past Gigabyte to have a BIOS bug (they are very > well-known for having such, but are also pretty good about fixing > such problems). Have you tried a BIOS upgrade on your P35 since you > got it, or looked at the BIOS changelog? > It appears to be a FreeBSD issue because: 1. After Xi Lin's patch they are seen 2. The boot manager and cmos boot order see and can boot from them > I do not have an ICH9 board to help confirm or deny -- I can purchase > one if needed, and/or send it to Xin Li free of cost. > >From what other people are saying I think it needs to be the p35/ihc9(r) combo specifically. -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com