mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Etienne Lorrain" <etienne_lorrain@yahoo.fr>
To: linux-kernel@vger.kernel.org
Cc: vasja@nuedi.com
Subject: Re: HPT372 on KR7A-133R (ATA133) on production server
Date: Thu, 18 Apr 2002 17:59:43 +0200 (CEST)	[thread overview]
Message-ID: <20020418155943.93909.qmail@web11802.mail.yahoo.com> (raw)

  I have this exact motherboard, with CRUCIAL 256MB 184DIMM PC2100 NP CL2.5
 memory.
 You first have to patch your kernel like Andy Jeffries said to activate
 the RAID controller. Most of the distribution still did not do it,
 you probably have to compile your own kernel.

 For a long time, I have only been able to run it 100% CPU for one hour,
 no disk access, if I set the memory clock to 100/200 MHZ.

 I am currently experimenting running at 133/266 MHz with the two
 parameters "DDR DQS Input Delay" and "DDR DQS Output Delay" changed
 to manual and increased by 2.
 Their autodetection does not seem to work, I am not sure.
 It seems stable - no error noticed for the last few weeks.
 Note that 100/200 to 133/266 did not seem to increase the CPU speed
 a lot, my usual task takes 39 minutes 100% CPU in 133/266 and
 40 min in 100/200 mode.
 I am not on a production server, so your millage may vary.

  Just my €0.02,
  Etienne.

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

             reply	other threads:[~2002-04-18 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 15:59 Etienne Lorrain [this message]
2002-04-18 16:10 ` Vasja J Zupan
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18 14:16 Vasja J Zupan
2002-04-18 15:12 ` Andy Jeffries
2002-04-18 15:37   ` Vasja J Zupan
2002-04-19 10:22   ` Vincent Bernat
2002-04-22 16:15 ` Nicolae P. Costescu

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=20020418155943.93909.qmail@web11802.mail.yahoo.com \
    --to=etienne_lorrain@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vasja@nuedi.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 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®