From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] swapping processor problem
Date: Wed, 16 Nov 2011 02:11:53 -0500 [thread overview]
Message-ID: <CA+czFiB7QqBt1mh7N-xQqH-W3HCjCY0CtT_ip2Jgy09xGoCn4A@mail.gmail.com> (raw)
In-Reply-To: <4EC215DE.50202@st.com>
On Tue, Nov 15, 2011 at 2:33 AM, Raffaele BELARDI
<raffaele.belardi@st.com> wrote:
> I have two gentoo boxes, X has an ASUS M2NPV-VM with AMD64 3500+ CPU, Y
> has a AMD64 X2 5600+ CPU. Since I need more juice on X I thought I could
> swap CPUs.
>
> After updating X's BIOS the system with the 'new' CPU boots up to the
> MythTv screen with no error but does not respond to the USB keyboard nor
> to the remote control keypresses. More precisely:
>
> - keyboard is fine at grub boot, I can select up and down or edit the
> entries
> - keyboard is no longer responsive at the init scripts start (when you
> can press 'I' to select services)
>
> My first thought was that X (and Y) WERE compiled with '-march=native'
> GCC flag and maybe the 5600+ does not execute properly the 3500+ code.
> But a quick search on wikipedia shows that 5600+ has a superset of the
> 3500+ so I should have problems putting the 3500+ in the Y box, not
> vice-versa.
>
> Any suggestions?
Play with your BIOS settings. Look for things like legacy USB support.
Also, double-check that all the relevant USB drivers (UHCI, EHCI,
XHCI, HID, etc) are either built-into the kernel, or are loaded as
modules. Consider rebuilding your kernel.
Just because one processor has a superset of the instructions of the
other doesn't mean there may not be other compatibilities. Some time
back, a thread on here discussed how to find out what -march=native
becomes, in terms of -march and a bunch of other parameters. I've
noticed parameters like cache line sizes and cache sizes, among a
couple others. I imagine a bungling of, e.g., cache line sizes could
break code that has heavy dependency on data locality and/or memory
models; it might have broken your USB drivers, for example.
But, really, I think BIOS settings and driver presence are the more
likely culprit.
--
:wq
next prev parent reply other threads:[~2011-11-16 7:13 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 ` Michael Mol [this message]
2011-11-16 7:26 ` [gentoo-user] " Raffaele BELARDI
2011-11-16 7:34 ` Dale
2011-11-16 8:08 ` Raffaele BELARDI
2011-11-16 8:23 ` Dale
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=CA+czFiB7QqBt1mh7N-xQqH-W3HCjCY0CtT_ip2Jgy09xGoCn4A@mail.gmail.com \
--to=mikemol@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