Very Computer

I installed a 486DX2-66 CPU on my machine. The only jumper-setting that
works
is CPU Clock 33.3 MHz, CPU Clock Select ( 1X or 2X) 1X and for the VESA Bus
Connector Jumper CPU Speed Select either "Greater than 33 MHz" or "Less than
or equal to 33 MHz" ( both settings work).
When I tried to compile the kernel, a message ("CPU Clock skew") appeared. I
checked the CPU and found out that it got too hot. That was why the kernel
couldn't be compiled, I think. But how could the CPU get so hot when it
wasn't used with the highest frequency possible ? ( it wasn't cooled, but I
had removed this CPU from a PC where it was run with 66 MHz and there had
also been no cooling on it )
I tried other jumper settings: CPU Clock 66 MHz, 1X, "Greater than 33 MHz"
nothing worked. Then I tried CPU Clock 33.3 MHz, 2X, "Less than or equal to
33 MHz" ...
Might the board be defect, how can I figure that out with linux ?

I would be glad to get some advice,

Beni

: checked the CPU and found out that it got too hot.

It is normal that processors get hot. Why Do you think it is too hot?
Did you compare it to the temperature it had on the other board?

Stef
--
WebMaster D-WERK
President SOS-ETH
ETH Zurich

It also has a hardware problem that makes gcc receive fatal Signal-11 while
compiling the kernel. I had to desactivate the external cache from the BIOS.
(please note that this problem was not significant under dos/windows) (ie.
Windows was sometimes crashing - but I thought it was a "normal ms issue")

--
  Guillaume Cottenceau, 4eme annee informatique, I.N.S.A Rennes.

Quote:> When I tried to compile the kernel, a message ("CPU Clock skew")
> appeared. I

This clock difference will lead make(1) to believe that a file needs
rebuilding when it really doesn't (or vice versa).  Therefore, an
error message is issued.

Fix your problem with xntpd or rdate.

Quote:> checked the CPU and found out that it got too hot. That was why the kernel
> couldn't be compiled, I think. But how could the CPU get so hot when it
> wasn't used with the highest frequency possible ? ( it wasn't cooled, but I
> had removed this CPU from a PC where it was run with 66 MHz and there had
> also been no cooling on it )
> I tried other jumper settings: CPU Clock 66 MHz, 1X, "Greater than 33 MHz"
> nothing worked. Then I tried CPU Clock 33.3 MHz, 2X, "Less than or equal to
> 33 MHz" ...
> Might the board be defect, how can I figure that out with linux ?

--