linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Furness <paul.furness@vil.ite.mee.com>
To: Jamie Harris <jamie@jharris.homeip.net>
Cc: linux-admin@vger.kernel.org
Subject: Re: IDE tuning - How?
Date: 08 Apr 2003 10:10:55 +0100	[thread overview]
Message-ID: <1049793055.4726.12.camel@zebra.vil.ite.mee.com> (raw)
In-Reply-To: <61933.164.11.204.246.1049456363.squirrel@jharris.homeip.net>

Yeah, the controller does do 133. I tried idebus=133 but it isn't
recognised by the ide code as a valid option.

However, hdparm _might_ do what I wanted, I just didn't realise it; I
added "hdparm -X70 /dev/hda" to my startup script and it _appears_ to
have made things go faster. On the other hand, an hdparm -t still shows
the same transfer rates as before. 




On Fri, 2003-04-04 at 12:39, Jamie Harris wrote:
> Don't you just want to do the idebus=133 append agagin or am I missing
> something?  You IDE controller is capable of 133 yeah?  Not just 100?
> 
> cheers
> 
> Jamie...
> 
> > Hi.
> >
> > Can anyone tell me how to tell the linux kernel that my IDE hard disk
> > and interface are ATA133 not ATA100?
> >
> > I first noticed a problem after installing Debian on my development
> > system. The install took ages, but after the install the whole system
> > was very jerky and slow (this was on a P4 1.9G with lots of memory, so I
> > figured it wasn't CPU problems. Top confirmed this). Further
> > investigation showed that it was only slow when accessing the hard disk.
> > hdparm -t /dev/hda told me that it was going at between 3 and 4 M/s
> > which is scarily slow.
> >
> > I looked carefully through the boot messages, and came across "assuming
> > IDE bus speed 33MHz. override with idebus=xx" (Sorry, the wording might
> > be a little different but the message was essentially that). I therefore
> > added "idebus=66" to my kernel boot up line in grub.conf, and sure
> > enough it booted and told me "assuming IDE bus speed 66MHz." According
> > to hdparm, it is now giving me around 40MB/s, which is a definite
> > improvement.
> >
> > So far so good. But then I noticed that is detects the hard disk as
> > ATA100. I know it's a 133, as I only bought it recently and I know what
> > model I bought (Diamond max +9 120GB ATA133). I am assuming (possibly
> > naively) that if the IDE module in the kernel is only using 100, I'm
> > only getting about 66% of the performance I should. ( I know, nothing's
> > ever linear...)
> >
> > I tried adding "ide0=ata133" to the kernel params, but it makes no
> > difference. The IDE code documentation doesn't seem to help beyond
> > telling me to do what I have already tried.
> >
> > Am I missing something obvious?
> >
> >
> > Paul.
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2003-04-08  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04  9:33 IDE tuning - How? Paul Furness
2003-04-04 11:39 ` Jamie Harris
2003-04-08  9:10   ` Paul Furness [this message]
2003-04-09 15:34   ` Christian Reis

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=1049793055.4726.12.camel@zebra.vil.ite.mee.com \
    --to=paul.furness@vil.ite.mee.com \
    --cc=jamie@jharris.homeip.net \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).