Raffaele BELARDI wrote:
On 11/16/2011 08:34 AM, Dale wrote:
I agree tho that checking those BIOS setting is a good start.  If that fails, 
boot a CD or something, chroot in, do a emerge -e system.  Maybe make some 
corrections to the kernel then try booting.  Oh, I'd rebuild the input drivers 
to, mouse and keyboard.  Check the USE flags too.  I'm not sure what all 
options they have.

Boot from CD also was failing with a lock so I think it was a mobo/CPU
incompatibility issue. Nevertheless I'd like to understand the points
you and Michael are making.

The Award BIOS has almost no CPU-related options.
There is no way I can control cache size from BIOS.
Since the memory controller is integrated in the Athlon64 I'd think DRAM
settings page could be affected by a CPU swap but I have it all set to
'auto' so I suppose that the BIOS should fix them after the swap.
USB is implemented on southbridge, not on CPU.

I found no parameter in the kernel config that could be affected by the
CPU swap except for SMP setting, but a misconfiguration there should not
cause a hang, just a core not being used.

Which drivers should be affected by a CPU swap? All the ones I can think
of are motherboard-related, not CPU-related.

Thanks for the hint on gcc, I'll check the differences on the two
systems once I have them back up and working.


You could be right that it is a mobo CPU issue. When you are grasping at straws, just grab all you can. Since you got it to work then I wouldn't think it was software, a failing hardware such as a bad CPU or a bad kernel.

Generally if it works on a CD, then it is software. If it also fails from a CD, then it should be hardware. Sounds like yours is a hardware issue but just a compatibility problem, not failure.

Maybe check if there is a BIOS update available?  Might be worth a shot.

Dale

:-)  :-)

--
I am only responsible for what I said ... Not for what you understood or how 
you interpreted my words!


Reply via email to