From: Stephan van Hienen <kernel@ddx.a2000.nu>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)
Date: Sat, 5 Apr 2003 23:27:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.53.0304052324360.16674@ddx.a2000.nu> (raw)
In-Reply-To: <Pine.LNX.4.44.0304051622180.31153-100000@coffee.psychology.mcmaster.ca>
On Sat, 5 Apr 2003, Mark Hahn wrote:
> > > > I don't think it is doing U100 :
> > >
> > > why? 25 MB/s is exactly what you should expect from a disk
> > > which has around 15 GB/platter density. the transfer mode
> > > doesn't matter, as long as it's 10-20% faster than the transfer
> > > rate of the disk's outer tracks.
> >
> > because it is the same disk (WD1800BB (180GB)) only difference is the
> > controller...
>
> is the 80-pin cable validly configured and properly detected?
> or did you cover this already?
all disks and cables are the same
(i have 15 of these disks in this server)
only difference are the controllers
and since the kernel is giving me incorrect info at boottime
(ICH3 (instead of what is really there (ICH4))
i really think this is an kernel problem
next parent reply other threads:[~2003-04-05 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0304051622180.31153-100000@coffee.psychology.mcmaster.ca>
2003-04-05 21:27 ` Stephan van Hienen [this message]
2003-04-05 21:39 ` Andre Hedrick
2003-04-05 22:24 ` Stephan van Hienen
2003-04-06 7:33 ` Andre Hedrick
2003-04-06 10:20 ` Stephan van Hienen
[not found] <Pine.LNX.4.44.0304051431220.31153-100000@coffee.psychology.mcmaster.ca>
2003-04-05 21:17 ` Stephan van Hienen
2003-04-05 9:53 kernel
2003-04-05 16:39 ` Alan Cox
2003-04-05 19:05 ` Stephan van Hienen
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=Pine.LNX.4.53.0304052324360.16674@ddx.a2000.nu \
--to=kernel@ddx.a2000.nu \
--cc=hahn@physics.mcmaster.ca \
--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
all inboxes | Powered by JetHome®