public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: manu <hislen@mindspring.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SiI2112 + Seagate + nFroce2: no DMA!
Date: Wed, 01 Jan 2003 09:06:43 -0800	[thread overview]
Message-ID: <3E132023.10206@mindspring.com> (raw)
In-Reply-To: <20040120085800.GB31330@carfax.org.uk>

Wonderful, so there is hope!

Yep my date was wrong because I was just coming back from flashing the 
BIOS with a new version and clearing CMOS, which did not change a darn 
thing and pushed me to send this mail :-)

RedHat seems to be releasing relatively old kernel so (what I have is 
the latest from them), must say I never paid attention to it, now I will.

Thanks so much,

Emmanuel.

Hugo Mills wrote:

>On Tue, Dec 31, 2002 at 09:55:59PM -0800, manu wrote:
>
>   Incidentally, did you know that the date on your computer is very,
>very wrong?
>
>  
>
>>I'm about to give up on my SATA drive as I can't get it to work properly.
>>So I thought I may try asking the experts before falling back to PATA.
>>
>>I have seen many mails reporting the same issue, some of them 6-month old:
>>
>>- SATA drive comes up in pio mode, not in dma
>>- trying to turn on dma with hdparm is a nightmare: I/O errors, crash 
>>with data corruption... I tried both:
>>
>> hddarm -d1 /dev/hde
>>
>>and:
>>
>> hdparm -u1 -c3 -d1 -X66 /dev/hde
>>
>>crash in both cases :-((
>>
>>
>>Here's my equipment:
>>
>>
>>ABIT AN7 motherboard (nForce2 chipset, SiI3112 SATA controller)
>>AMD Athlon XP 2600+ (+ 512 DDR / 400 MHz)
>>SATA HD Seagate Barracuda 160 Gb
>>
>>The SATA HD is my only drive. The only thing connected to my IDE 
>>controllers is a DVD/CD combo.
>>
>>Running Linux Redhat 9.0
>>kernel 2.4.20-28.9
>>    
>>
>  ^^^^^^^^^^^^^^^^^^
>   This is your problem. There have been a number of bug-fixes to the
>SiI drivers since 2.4.20. Try it again with a newer kernel -- such as
>2.4.24.
>
>  
>
>>I've been googling for days now and could not come accross a solution, 
>>on the contrary I came under the impression that the combination of 
>>SiI3112 +and Seagate was doomed.
>>    
>>
>
>   Not so. I have a SiI3112 controller and a 120GiB Seagate drive, and
>they work very well together. I'm using 2.6.1, although 2.4.23 also
>worked well for me.
>
>[snip]
>  
>
>>Isn't there a solution??
>>
>>I am willing to try patches of experimental code. At this point I am 
>>looking at reinstalling everything on a PATA drive anyway, so  I have 
>>nothing to loose.
>>    
>>
>
>   Try using 2.4.24 or 2.6.1.
>
>   Hugo.
>
>  
>



  reply	other threads:[~2004-01-20 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01  5:55 SiI2112 + Seagate + nFroce2: no DMA! manu
2004-01-20  8:58 ` Hugo Mills
2003-01-01 17:06   ` manu [this message]
2004-01-24  9:27   ` Emmanuel Hislen

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=3E132023.10206@mindspring.com \
    --to=hislen@mindspring.com \
    --cc=hugo-lkml@carfax.org.uk \
    --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