From: Robert Hancock <hancockr@shaw.ca>
To: koan <koan00@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6.20.15] CK804 / sata_nv: Reported link speed not as expected.
Date: Thu, 12 Jul 2007 23:18:35 -0600 [thread overview]
Message-ID: <46970B2B.1040907@shaw.ca> (raw)
In-Reply-To: <fa.TEHWvKEhf5s38aD0n11fk9CU28k@ifi.uio.no>
koan wrote:
> Hello, I am not on list so please CC me with any responses.
>
> I recently switched to an nforce4 board and have been looking over my
> dmesg output for any oddities. This is a Slackware 12.0 machine with a
> custom 2.6.20.15 kernel.
>
> As far as I know, the motherboard is an Nforce4 based (non-ultra/sli,
> etc) board. The exact model is Foxconn (Winfast) NF4K8AB-RS (
> http://www.foxconnchannel.com/EN-US/Product/motherboard_detail.aspx?ID=en-gb0000027
>
> ). It has the latest BIOS available applied.
>
> The product documentation states the board only supports 4x SATA150
> connectors and that seems to match the information on this page (
> http://www.nvidia.com/page/nforce4_family.html ). Three of the disks
> are Seagate drives and have the SATA150 clip jumper set. However when
> I boot, the kernel output seems to show 2 of the 4 ports operating at
> 3 Gbps. Is this a known issue and/or something I can safely ignore?
I don't think the NVIDIA page is correct. AFAIK all nForce4 chipsets
support SATA 3Gbps transfer speeds.
The kernel doesn't have any control over the default speed chosen by the
controller in any case (though it can force it down to a lower speed).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-07-13 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.TEHWvKEhf5s38aD0n11fk9CU28k@ifi.uio.no>
2007-07-13 5:18 ` Robert Hancock [this message]
2007-07-12 15:20 [2.6.20.15] CK804 / sata_nv: Reported link speed not as expected koan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46970B2B.1040907@shaw.ca \
--to=hancockr@shaw.ca \
--cc=koan00@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).