Archived from groups: alt.comp.periphs.mainboard.asus (
More info?)
Qoth The Raven "Paul"<nospam@needed.com> in
nospam-0403052019500001@192.168.1.177
> In article <38s0caF5rrmveU1@individual.net>, "Highlandish"
> <ckreskay_CURSEING@dodo.com.au> wrote:
>
>> Qoth The Raven "Paul"<nospam@needed.com> in
>> nospam-0403050648090001@192.168.1.177
>>> In article <TdQVd.41183$kz6.778640@news20.bellglobal.com>, "RonK"
>>> <I'mhere@home.com> wrote:
>>>
>>>> Hey Paul, What is AGP/PCI lock and what does it do ?
>>>> Thanks
>>>> Ron
>>>
>>> An AGP/PCI lock keeps the clocks at 66.66/33.33 MHz, while
>>> you are overclocking. On previous generations of boards lacking
>>> this feature, as you raised the FSB frequency, the AGP and
>>> PCI would go up also. Once PCI, which is normally 33MHz, goes
>>> above about 37.5MHz, you could corrupt an IDE disk drive, as
>>> they did the timing on the drive interface with the PCI clock.
>>> (Not all boards did that, just the stupid ones
🙂 And if it
>>> wasn't the IDE interface, then at perhaps 40MHz, the rest of
>>> the PCI bus would break.)
>>>
>>> To make a working AGP/PCI lock requires a couple of things.
>>> It needs the chipset to be designed with asynchronous clocking.
>>> That means normally one clock signal would enter a certain
>>> part of the chip, and for a lock, you need a separate clock for
>>> two parts of the circuit. Special precautions must be made
>>> to pass data between the two domains. (I suspect these requirements
>>> weren't met properly on the chipset of the A8V rev one, and
>>> Asus had to disable the lock on the rev one, to avoid problems
>>> with the chipset. It was fixed on rev two. If you are not an
>>> overclocker, the lock is a "don't care" feature you will never
>>> use.)
>>>
>>> The second requirement, is a flexible clockgen chip, that can
>>> hold the AGP/PCI clock at a constant frequency, while changing
>>> the FSB.
>>>
>>> Even with all this fancy mumbo-jumbo, the new boards do have
>>> problems with the SATA interface. It seems mobo designers
>>> learn the same lessons over and over again, as there are some
>>> SATA interfaces on motherboards that malfunction when you
>>> overclock past a certain point. That is why it pays to read
>>> the reviews for your motherboard on Anandtech, as they sometimes
>>> mention which interfaces can suffer from corruption.
>>> Seasoned overclockers pick their disk drive interface with
>>> great care, due to the potential to lose the contents of the
>>> disk drive while experimenting.
>>>
>>> HTH,
>>> Paul
>>
>> I'm about to manually OC my rev 1 with a 939 3000+ to a 3800+. is
>> this going to effect my ide/sata bus?
>
> That is going from 1800MHz to 2400MHz. A 33% overclock.
>
> I'd take a look through this thread. Early in the thread,
> some people are using a modded BIOS, and it shows an item
> for the lock. They seem to be able to run high clocks on
> the FSB (but they are also careful as to how they connect
> a hard disk). This thread is too long for me to read the
> whole thing.
>
>
http://www.abxzone.com/forums/showthread.php?t=74370
>
> I think you really need to find an overclocking summary
> thread. This link was posted in this group a few days
> ago:
>
>
http://www.ocforums.com/showthread.php?t=332591
>
> The K8V is a board that doesn't have a working lock, and
> it hits a "wall" at 237MHz. If the A8V Rev1 is going to go
> farther than that, maybe the modded BIOS will help. So far
> I haven't read a thread, where someone tries to overclock
> a Rev.1 in its "out of the box" state. Sounds like plenty
> of experiments to come...
>
> HTH,
> Paul
thanks, I read the latter mentioned link to oc the a8v, but the first link
was great, lots of info there too. little question, I currently have the
1009 bios, is that pci locked? will it hurt to go back to the modded 1005.21
bios?
--
Multitasking: Reading in the bathroom !
Take out the _CURSEING to reply to me
Facebook
Twitter
Instagram