From: egger@suse.de
To: chromi@cyberspace.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Only 10 MB/sec with via 82c686b chipset?
Date: Wed, 21 Mar 2001 18:34:40 +0100 (CET) [thread overview]
Message-ID: <20010321182613.85AF354D6@Nicole.muc.suse.de> (raw)
In-Reply-To: <l03130301b6de66229e10@[192.168.239.101]>
On 21 Mar, Jonathan Morton wrote:
> The "blue and white" PowerMac G3 and certain early PowerMac G4s used a
> 66MHz PCI card for graphics in lieu of proper AGP. 66MHz PCI is used
> in certain high-end workstations, as well, but it's not normally found
> on consumer-level devices.
> Look at 'lspci -vvv' output for the "66MHz" flag on the devices listed
> there - all the ones in my Duron system leave it unset, except for my
> (very recent and pretty nippy) SCSI controller and (AGP) video card.
Well, I wasn't talking about 66Mhz nor about 64bit cards but rather
normal consumer cards which are specified for 33Mhz.
> That said, *most* PCI devices don't like being overclocked, and it's
> not well known that pushing the system bus also pushes the PCI and ISA
> buses in the same manner. A friend of mine had *severe* locking
> problems with his system when he inserted his cheap SCSI adapter into
> his overclocked machine, even though the other cards handled it OK
> (relatively speaking - I'm not convinced). I don't know how far he'd
> overclocked it, but 37MHz kinda rings true.
Trying to enhance a systems performance by overclocking the bus is
about the most stupid thing one can do as one ANY of the connected
devices memory/CPU/chipset/PCI devices/AGP cards (just to name a
few) have a high probability of failing and all those probabilites
factor up which basically means that the system is in a unpredictable
state which is never acceptable for any serious kind of system.
Better leave the overclocking of busses to kids who are bored
by their live.
--
Servus,
Daniel
prev parent reply other threads:[~2001-03-21 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 3:48 SodaPop
2001-03-21 13:48 ` egger
2001-03-22 2:14 ` TimO
2001-03-23 2:38 ` Only 10 MB/sec with via 82c686b - FIXED SodaPop
2001-03-23 9:48 ` Alan Cox
2001-03-23 16:21 ` SodaPop
2001-03-23 17:00 ` [PATCH] Prevent OOM from killing init SodaPop
2001-03-23 18:42 ` Martin Dalecki
2001-03-23 20:25 ` SodaPop
2001-03-23 20:33 ` Martin Dalecki
2001-03-23 19:19 ` Jonathan Morton
2001-03-23 2:59 ` Only 10 MB/sec with via 82c686b - FIXED SodaPop
2001-03-21 14:18 ` Only 10 MB/sec with via 82c686b chipset? Jonathan Morton
2001-03-21 17:34 ` egger [this message]
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=20010321182613.85AF354D6@Nicole.muc.suse.de \
--to=egger@suse.de \
--cc=chromi@cyberspace.org \
--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®