public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] swapping processor problem
Date: Wed, 16 Nov 2011 02:23:24 -0600	[thread overview]
Message-ID: <4EC372FC.3040608@gmail.com> (raw)
In-Reply-To: <4EC36F66.30204@st.com>

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	other threads:[~2011-11-16  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  7:33 [gentoo-user] swapping processor problem Raffaele BELARDI
2011-11-16  6:59 ` [gentoo-user] " Raffaele BELARDI
2011-11-16  7:11 ` [gentoo-user] " Michael Mol
2011-11-16  7:26   ` Raffaele BELARDI
2011-11-16  7:34   ` Dale
2011-11-16  8:08     ` Raffaele BELARDI
2011-11-16  8:23       ` Dale [this message]
2011-11-16  8:33         ` Raffaele BELARDI
2011-11-16  8:55           ` Dale
2011-11-16  9:31             ` James Broadhead
2011-11-16  9:51               ` Dale

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=4EC372FC.3040608@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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