From: Michael Thonke <iogl64nx@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: NCQ support NVidia NForce4 (CK804) SATAII
Date: Thu, 11 Aug 2005 20:55:26 +0200 [thread overview]
Message-ID: <42FB9F1E.9060302@gmail.com> (raw)
In-Reply-To: <42FB99D7.6030403@pobox.com>
Jeff Garzik schrieb:
> Michael Thonke wrote:
>
>> Jeff Garzik schrieb:
>>
>>> Please enable ATA_DEBUG and ATA_VERBOSE_DEBUG, and send me the output.
>>
>>
>>
>> I tried that Jeff, but the base problem is on the low-level..
>
>
>
> There may be a BIOS problem, but there is no problem with the
> controller using SATA II drives.
>
> Can you boot with another drive, and then send the output requested
> above?
Sorry, but I can't provide them, because I changed the VIA chipset based
mainboard against a NForce4 Ultra chipset mainboard.
But on heise.de they also pointed out that it's VIA's bug. Not the
harddrives one, they have some but this not apply on VIA. Samsung act
and updated the firmware of their drives for compatibility reasons.
And the work-around is to jumper the hdd as SATA I hdd. The problem was,
that my system to this time was not bootable with my Samsungs Hd160JJ
and VIA VT8237. Nos they fix it with a new Chipset the VT8327R...where
we don't need a work-around.
<http://www.via.com.tw/en/products/chipsets/southbridge/vt8237/>
>
> Jeff
>
Michael
--
Michael Thonke
IT-Systemintegrator /
System- and Softwareanalyist
next prev parent reply other threads:[~2005-08-11 18:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 20:53 NCQ support NVidia NForce4 (CK804) SATAII Allen Martin
2005-08-10 21:31 ` Lennart Sorensen
2005-08-11 7:09 ` Gábor Lénárt
2005-08-11 13:05 ` Lee Revell
2005-08-11 15:17 ` Michael Thonke
2005-08-11 15:22 ` Lee Revell
2005-08-11 15:43 ` Michael Thonke
2005-08-11 16:18 ` Roger Heflin
2005-08-11 16:32 ` Michael Thonke
2005-08-12 19:02 ` Jan Engelhardt
2005-08-11 15:39 ` Diego Calleja
2005-08-12 6:17 ` Gábor Lénárt
2005-08-11 17:20 ` Jeff Garzik
2005-08-11 17:27 ` Lennart Sorensen
2005-08-11 17:44 ` Michael Thonke
2005-08-11 17:48 ` Lennart Sorensen
2005-08-11 19:29 ` Heikki Orsila
2005-08-11 17:38 ` Michael Thonke
2005-08-11 17:46 ` Jeff Garzik
2005-08-11 17:57 ` Michael Thonke
2005-08-11 18:32 ` Jeff Garzik
2005-08-11 18:55 ` Michael Thonke [this message]
2005-08-11 18:04 ` Lennart Sorensen
2005-08-11 18:17 ` Michael Thonke
2005-08-12 20:10 ` Andre Tomt
2005-08-11 15:09 ` Michael Thonke
2005-08-15 6:01 ` Christopher Chan
[not found] <fa.psg95ip.1emqnop@ifi.uio.no>
2005-08-14 13:29 ` Willem Riede
2005-08-14 15:18 ` Lion Vollnhals
2005-08-15 13:42 ` Stephen Frost
2005-08-18 14:23 ` Chris Wedgwood
[not found] <DBFABB80F7FD3143A911F9E6CFD477B004FAE3E7@hqemmail02.nvidia.com.suse.lists.linux.kernel>
[not found] ` <20050811070943.GB8025@vega.lgb.hu.suse.lists.linux.kernel>
[not found] ` <1123765523.32375.10.camel@mindpipe.suse.lists.linux.kernel>
[not found] ` <42FB6C27.1010408@gmail.com.suse.lists.linux.kernel>
[not found] ` <42FB88F8.7040807@pobox.com.suse.lists.linux.kernel>
2005-08-11 18:44 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-08-10 18:59 Allen Martin
2005-08-10 18:11 Michael Thonke
2005-08-10 18:18 ` Jeff Garzik
2005-08-10 18:28 ` Michael Thonke
2005-08-10 18:52 ` Michael Thonke
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=42FB9F1E.9060302@gmail.com \
--to=iogl64nx@gmail.com \
--cc=jgarzik@pobox.com \
--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