public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lists@sapience.com
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: aic7xxx and newer kernels
Date: Tue, 10 Apr 2001 08:33:40 -0400	[thread overview]
Message-ID: <20010410083340.A16601@sapience.com> (raw)
In-Reply-To: <20010408001132.A28840@sapience.com> <200104092119.f39LJts17813@aslan.scsiguy.com>
In-Reply-To: <200104092119.f39LJts17813@aslan.scsiguy.com>; from gibbs@scsiguy.com on Mon, Apr 09, 2001 at 03:19:55PM -0600


Justin:

Ya think very buggy? I checked seagate web page and 
unfortunately was unable to find any firmware updates
for the barracuda drives.

Curious tho that this has worked flawlessly for well over a 
year with all prior version of linux and win2000 as well.  
Also a few other folks seem to have similar problems with 
newer kernels. 

Do the newer drivers put a bigger demand on the drives that 
might start to uncover the problems previously not seen? 

I did find newer firmware for the adaptec 2940u2w card 
tho so perhaps I should upgrade that?

I will try turning off write cache - kernel config option right?

Will report back.

Thanks for your help - it sure would be nice to be able to
run with the newer kernels again!

Regards,


Gene/

On Mon, Apr 09, 2001 at 03:19:55PM -0600, Justin T. Gibbs wrote:
> >Apr  7 19:56:13 snap kernel:   Vendor: SEAGATE   Model: ST318275LW        Rev:
> > 0001
> 
> I seem to recall this being a very buggy firmware version.  You should
> check with Seagate to see if they have something new.  If this is the
> firmware I'm thinking of, the driver should perform correctly if you
> disable write caching.  You can do this via the SCSI-Select menu for
> the controller.
> 
> --
> Justin
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-04-10 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010407195031.B25801@sapience.com>
     [not found] ` <200104080139.f381dZs92143@aslan.scsiguy.com>
2001-04-08  4:11   ` aic7xxx 6.1.10 and 2.4.4-pre1 lists
2001-04-08  4:42     ` lists
2001-04-09 21:19     ` Justin T. Gibbs
2001-04-10 12:33       ` lists [this message]
2001-04-10 14:00         ` aic7xxx and newer kernels Justin T. Gibbs
2001-04-10 21:37           ` lists

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=20010410083340.A16601@sapience.com \
    --to=lists@sapience.com \
    --cc=gibbs@scsiguy.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