All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Strauss <me@heyjay.com>
To: Mike Hardy <mhardy@h3c.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 1 install revealed poor HD performance (I think)
Date: Thu, 19 May 2005 20:43:43 -0500	[thread overview]
Message-ID: <428D40CF.5040808@heyjay.com> (raw)
In-Reply-To: <428CFA71.6040202@h3c.com>

Mike Hardy wrote:
> 
> Jay Strauss wrote:
> 
> 
>>Thanks for the reply Mike.  After some Googling and looking at my kernel
>>config file,  it seems that SIS support is a module, like so:
>>
>>CONFIG_BLK_DEV_SIS5513=m
>>
>>I found this link but can't find any of the files that it references
>>
>>http://kerneltrap.org/comment/reply/4925/129324
> 
> 
> That message looks like the trick - the module doesn't have the right
> PCI id for some reason, assuming you have the same chip
> 
> You may not have the kernel source, if you can't find the file with
> locate. You'll need to fetch the kernel source first, then build a
> custom kernel with that line changed.
> 
> This issue came up with my laptop when I first got it - a Dell Latitude
> D800, it has an intel 5705M chipset that was supportable but had a new
> PCI id and so didn't work. The custom kernel was a bit of a pain, but it
> did work, and the patch made its way upstream really quickly. You can
> help that along by posting it to linux-kernel even, most likely
> (assuming it works)
> 
> If not, I will say that this is probably something that should be on
> linux-ide at this point, as it really has nothing to do with raid
> specifically other than this being a decent place to find folks trying
> to help. The linux-ide folks will be closer to the code you're working
> with so might be more capable
> 
> -Mike

Thanks everyone for contributing.  I very much appreciate the help. 
I'll bring this over to the linux-ide as Mike suggests

Again thanks
Jay


  reply	other threads:[~2005-05-20  1:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 15:11 Raid 1 install revealed poor HD performance (I think) Jay Strauss
2005-05-17 15:50 ` Gordon Henderson
2005-05-17 16:17   ` Jay Strauss
2005-05-17 16:23     ` Gordon Henderson
2005-05-17 16:52       ` Mike Hardy
2005-05-17 20:51         ` Jay Strauss
2005-05-17 20:54           ` Mike Hardy
2005-05-17 22:16             ` Tobias Hofmann
2005-05-17 23:00               ` Jay Strauss
2005-05-18  3:28               ` Jay Strauss
2005-05-17 22:45           ` Peter T. Breuer
2005-05-17 23:42 ` Henrik Holst
2005-05-18  3:30   ` Jay Strauss
2005-05-17 23:44 ` Henrik Holst
2005-05-19 15:32   ` Jay Strauss
2005-05-19 16:14     ` Mike Hardy
2005-05-19 18:40       ` Jay Strauss
2005-05-19 20:43         ` Mike Hardy
2005-05-20  1:43           ` Jay Strauss [this message]
     [not found] <Pine.LNX.4.44.0505180206580.1777-100000@coffee.psychology.mcmaster.ca>
2005-05-18 15:08 ` Mike Hardy

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=428D40CF.5040808@heyjay.com \
    --to=me@heyjay.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mhardy@h3c.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.