Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Daniel Brahneborg <daniel.com@wtnord.net>
To: "J. Ryan Earl" <heretic@clanhk.org>
Cc: Daniel Brahneborg <daniel.com@wtnord.net>, linux-ide@vger.kernel.org
Subject: Re: siimage and two nics
Date: Sat, 27 Dec 2003 08:30:50 +0100	[thread overview]
Message-ID: <20031227083050.A8631@nettis.grimsta> (raw)
In-Reply-To: <3FEBCA3C.5000803@clanhk.org>; from heretic@clanhk.org on Fri, Dec 26, 2003 at 05:42:20AM +0000

On Fri, Dec 26, 2003 at 05:42:20AM +0000, J. Ryan Earl wrote:
> Daniel Brahneborg wrote:
> 
> >I guess I could, I just needed something to install to.
> >It's a file server, so it's the SATA disks that will take
> >the biggest hit.
>
> You should put your busiest disks on the southbridge (via_sata).

I'll keep that in mind, thanks.

> >I wouldn't mind using something else, but then I must first
> >understand how to get it to stop messing with my PATA hda.
> >Would that driver make the SATA disk suddenly appear as IDE
> >disks instead of SCSI?
>
> I don't understand why that matters.

It doesn't matter if they are IDE or SCSI, as long as they work.

What matters is that I still want to be able to access the small
IDE drive I have on the PATA connector.

> >Checking... oh, it's 1.06 in Linus 2.4.23 kernel.  The diff
> >doesn't seem to be very much, just a check for 3114 and a fix
> >for Seagate drives.
>
> Have you considered 2.6?

I tested it for a while, but had some problems with it.  I'll
try it again and see if it makes any difference.

> >SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> > sda: sda1 sda2
> >SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
> > sdb: sdb1 sdb2
> >SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
> > sdc: sdc1 sdc2
> >SCSI device sdd: 312581808 512-byte hdwr sectors (160042 MB)
> > sdd: sdd1 sdd2
> 
> OK.  So you have a 4 160GB SATA drives that show up as sda-sdd using 
> libata.

Exactly.  Or rather, 4 152GB drives, since Samsung seems to think
that K = 1000. *sigh*

> That's cool.  I had problems with the sata_sil driver though, 
> it wasn't stable for me.  I'd suggest using the IDE driver until it's 
> been worked on more.

How do I find out what happens with the PATA disk when I load the
siimage module?

> It's alpha right now, but the IDE driver is 
> production ready by my testing anyway.  You just have to modify your 
> raidtab to account for the new device location (hda/hdc or hde/hdg) of 
> using the IDE driver.

That's no problem.

Btw, what speed should I be able to get with the siimage module?

/Basic


  reply	other threads:[~2003-12-27  7:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26  7:54 siimage and drive order problem Daniel Brahneborg
2003-12-26 13:14 ` Ryan Earl
2003-12-26 18:57   ` siimage and two nics (was: drive order problem) Daniel Brahneborg
2003-12-26  3:48     ` siimage and two nics J. Ryan Earl
2003-12-26 22:28       ` Daniel Brahneborg
2003-12-26  5:42         ` J. Ryan Earl
2003-12-27  7:30           ` Daniel Brahneborg [this message]
2003-12-27  0:24             ` J. Ryan Earl
2003-12-27 22:40               ` Daniel Brahneborg
2003-12-28 14:49               ` Daniel Brahneborg

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=20031227083050.A8631@nettis.grimsta \
    --to=daniel.com@wtnord.net \
    --cc=heretic@clanhk.org \
    --cc=linux-ide@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