public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Moore <timothymoore@bigfoot.com>
To: Cheryl Homiak <chomiak@chartermi.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via82cxx chipset problem
Date: Tue, 04 Dec 2001 09:30:56 -0800	[thread overview]
Message-ID: <3C0D0850.1F156158@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0112030943110.223-100000@maranatha.chartermi.net>

Cheryl Homiak wrote:
> 
> I tried this question on another list and was told not to try to change my
> mhz speed because I would corrupt my hard drive possibly. But does this
> mean I am actually running at only 33mhz.? This doesn't seem like a viable
> way to run my computer and I am having problems with installing new memory
> that may be related to this. My original message is below; any help would
> be appreciated.
> Thanks.

Most modern motherboards use a 1/2, 1/3 or 1/4 divider on the memory bus
(set in BIOS) to get PCI values.  idebus= is used for anything other
than 33MHz:

Mem	PCI	divider	idebus=
66	33	1/2	default
75	37.5	1/2	38
85	42.5	1/2	43
100	33	1/3	default
133	33	1/4	default

For example, setting the bus at 75MHz would mean 'idebus=38' on the boot
command line or in lilo to prevent timing problems which could lead to
disk data corruption.  Most PCI bus related data corruption occured when
driving the bus more than 15% over spec.

rgds,
tim.
--

  parent reply	other threads:[~2001-12-04 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 15:50 Via82cxx chipset problem Cheryl Homiak
2001-12-04  8:51 ` Lionel Bouton
2001-12-04 17:30 ` Tim Moore [this message]
2001-12-04 21:45 ` Daniel R. Warner

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=3C0D0850.1F156158@bigfoot.com \
    --to=timothymoore@bigfoot.com \
    --cc=chomiak@chartermi.net \
    --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