The solution has been found! The mainboard with the AMD-K6-2
had got into an undocumented multiplier which meant slightly
overclocking the processor. When keeping the 66 MHz clock setting
and producing 333 MHz processor speed instead of 400 MHz, and
where the processor was marked for 350, I ran mem
Andy Hayward wrote:
> On 09/12/2007, Mats Erik Andersson <[EMAIL PROTECTED]> wrote:
>> First, I have OpenBSD 4.2 running on this machine using
>> AMD-K6-2/350 on an AT-mainboard with VIA chipset VT82C598
>> and VT82C586B. (Well, both AT and ATX in fact.) I have not
>> detected any trouble until I p
Greetings :)
Have you considered running a passes with memtest86? I have the feeling one of
those RAM modules is defective, I still own a few K6-2 systems and they work
perfectly. ;)
-Nix fan.
On 09/12/2007, Mats Erik Andersson <[EMAIL PROTECTED]> wrote:
> First, I have OpenBSD 4.2 running on this machine using
> AMD-K6-2/350 on an AT-mainboard with VIA chipset VT82C598
> and VT82C586B. (Well, both AT and ATX in fact.) I have not
> detected any trouble until I patched libssl according to
Hello all,
I am trying to untangle a strange segmentation fault
created by gcc using AMD-K6-2, but not with Pentium-II.
In particular, any hints on particular information bits
needed to pinpoint the error will be appreciated.
First, I have OpenBSD 4.2 running on this machine using
AMD-K6-2/350 on
5 matches
Mail list logo
