From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CPU upgrade and LVM questions.
Date: Thu, 6 Dec 2018 15:55:00 -0600 [thread overview]
Message-ID: <00229f0e-cce0-947c-407c-ea76a8914d97@gmail.com> (raw)
In-Reply-To: <ANHXW2EY.Z22KHV7W.AG334LLL@6TREYRFX.BSGMKNTL.ZZR2UY5T>
Jack wrote:
> On 2018.12.06 15:58, Dale wrote:
> [snip...]
>> My concern is this tho. I have my old CPU still installed and
>> everything is compiled based on that. So, I'm stable with the old
>> CPU. However, when I shutdown, take out the old CPU and install the
>> new one, I'm concerned it may not boot at all because of the change
>> or may boot but be very unstable. I recall years ago being able to
>> set up the flags in such a way that it can run on virtually any CPU
>> but it's been a long time ago and I don't know if it is needed or
>> not. My hope was, someone did a very similar upgrade and can say for
>> sure if it works or if I need to do things before changing the CPUs
>> to make sure I can boot and be stable. If I can just get a stable
>> console, I can do a emerge -e world and get the OS inline with the
>> CPU. I'm just concerned whether I will have that or not.
>>
> [snip...]
>>
>> I just don't want to swap CPUs only to find out I've got to swap back
>> because my system won't boot at all. Heck, it may even fail to load
>> the kernel itself for all I know.
> I once made the mistake of getting a whole new (used...) PC and just
> moved the HDD from the old one to the new, without thinking about any
> of this. Of course it wouldn't boot at all, because I was switching
> from an AMD to an Intel CPU and had set all flags accordingly in the
> old box. In your case, as long as you include any flags necessary for
> the new CPU, and remove any flags for features the new CPU does not
> have, you should be good. (I know that sounds simple, but does ignore
> how you find that info.) Given your two CPUs are relatively close
> (unless I misread something) there should be little if anything
> critical to change.
>
> However, if you have a live DVD, (or on USB stick) that will always
> boot, and you can then do a chroot and reset flags and start
> recompiling whatever might fail. I actually think the kernel IS the
> likely failure if any, but once that boots, you should be good to
> recompile whatever fails. (Yes, toolchain stuff might be an issue,
> but again, just boot back to the live DVD.) You may need to reboot a
> few times, but you won't need to swap the old CPU back in.
>
> Jack
>
I've tried that too. Heck, sometimes that doesn't work even with
windoze. My concerns are sort of along those lines tho. I don't have
and can't find the current flags for the new CPU so I don't know what to
do flag wise. I'm not sure that there is even a common setting but
suspect there is. If I can get the kernel to boot and login at a
console, even with no X, I can rebuild from there, provided everything
works toolchain wise.
I guess this is a good time to make sure my sysrescue and other tools
work. That slipped my mind completely. Thanks for the reminder. Hmmm,
I need to check on the current mount and chroot process for this too.
Thanks.
Dale
:-) :-)
next prev parent reply other threads:[~2018-12-06 21:55 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:27 [gentoo-user] CPU upgrade and LVM questions Dale
2018-12-06 10:03 ` Neil Bothwick
2018-12-06 15:17 ` Dale
2018-12-06 16:51 ` J. Roeleveld
2018-12-06 18:36 ` Corbin Bird
2018-12-06 20:58 ` Dale
2018-12-06 21:24 ` Jack
2018-12-06 21:55 ` Dale [this message]
2018-12-07 1:06 ` Corbin Bird
2018-12-07 1:17 ` Dale
2018-12-07 5:10 ` Dale
2018-12-07 6:22 ` [gentoo-user] " Nikos Chantziaras
2018-12-07 7:30 ` Dale
2018-12-07 10:49 ` Alec Ten Harmsel
2018-12-07 23:47 ` Nikos Chantziaras
2018-12-07 23:59 ` Dale
2018-12-09 18:23 ` Taiidan
2018-12-09 18:57 ` J. Roeleveld
2018-12-09 22:41 ` Dale
2018-12-10 21:33 ` Taiidan
2018-12-10 22:14 ` Neil Bothwick
2018-12-10 22:54 ` Dale
2018-12-11 2:00 ` Taiidan
2018-12-11 8:49 ` Neil Bothwick
2018-12-11 9:23 ` Mick
2018-12-11 10:48 ` Dale
2018-12-11 15:14 ` J. Roeleveld
2018-12-11 22:46 ` Adam Carter
2018-12-11 23:56 ` Dale
2018-12-12 2:15 ` Adam Carter
2018-12-11 10:20 ` Alan Mackenzie
2018-12-11 15:03 ` J. Roeleveld
2018-12-07 8:47 ` [gentoo-user] " Neil Bothwick
2018-12-07 8:58 ` Dale
2018-12-06 21:02 ` [gentoo-user] " Nikos Chantziaras
2018-12-06 21:45 ` Dale
2018-12-06 22:22 ` Nikos Chantziaras
2018-12-06 23:23 ` Dale
2018-12-06 23:40 ` Nikos Chantziaras
2018-12-07 0:19 ` Dale
2018-12-07 10:01 ` Peter Humphrey
2018-12-07 12:41 ` Dale
2018-12-07 16:51 ` Peter Humphrey
2018-12-08 1:01 ` Dale
2018-12-08 2:51 ` Nikos Chantziaras
2018-12-08 4:39 ` Dale
2018-12-08 5:33 ` David Haller
2018-12-08 5:45 ` Dale
2018-12-08 6:00 ` Nikos Chantziaras
2018-12-08 6:28 ` David Haller
2018-12-08 4:23 ` David Haller
2018-12-08 5:35 ` Dale
2018-12-08 6:06 ` David Haller
2018-12-08 5:38 ` David Haller
2018-12-08 9:40 ` Peter Humphrey
2018-12-08 9:50 ` Peter Humphrey
2018-12-06 21:03 ` [gentoo-user] " Grant Taylor
2018-12-09 22:45 ` Dale
2018-12-10 1:35 ` Grant Taylor
2018-12-10 2:38 ` Dale
2018-12-10 3:37 ` Grant Taylor
2018-12-10 9:27 ` Neil Bothwick
2018-12-10 16:00 ` Dale
2018-12-08 17:49 ` Alexander Puchmayr
2018-12-08 18:23 ` Dale
2018-12-08 19:09 ` J. Roeleveld
2018-12-08 20:48 ` Dale
2018-12-11 10:41 ` Dale
2018-12-22 23:58 ` 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=00229f0e-cce0-947c-407c-ea76a8914d97@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