| 1 |
Jack wrote: |
| 2 |
> On 2018.12.06 15:58, Dale wrote: |
| 3 |
> [snip...] |
| 4 |
>> My concern is this tho. I have my old CPU still installed and |
| 5 |
>> everything is compiled based on that. So, I'm stable with the old |
| 6 |
>> CPU. However, when I shutdown, take out the old CPU and install the |
| 7 |
>> new one, I'm concerned it may not boot at all because of the change |
| 8 |
>> or may boot but be very unstable. I recall years ago being able to |
| 9 |
>> set up the flags in such a way that it can run on virtually any CPU |
| 10 |
>> but it's been a long time ago and I don't know if it is needed or |
| 11 |
>> not. My hope was, someone did a very similar upgrade and can say for |
| 12 |
>> sure if it works or if I need to do things before changing the CPUs |
| 13 |
>> to make sure I can boot and be stable. If I can just get a stable |
| 14 |
>> console, I can do a emerge -e world and get the OS inline with the |
| 15 |
>> CPU. I'm just concerned whether I will have that or not. |
| 16 |
>> |
| 17 |
> [snip...] |
| 18 |
>> |
| 19 |
>> I just don't want to swap CPUs only to find out I've got to swap back |
| 20 |
>> because my system won't boot at all. Heck, it may even fail to load |
| 21 |
>> the kernel itself for all I know. |
| 22 |
> I once made the mistake of getting a whole new (used...) PC and just |
| 23 |
> moved the HDD from the old one to the new, without thinking about any |
| 24 |
> of this. Of course it wouldn't boot at all, because I was switching |
| 25 |
> from an AMD to an Intel CPU and had set all flags accordingly in the |
| 26 |
> old box. In your case, as long as you include any flags necessary for |
| 27 |
> the new CPU, and remove any flags for features the new CPU does not |
| 28 |
> have, you should be good. (I know that sounds simple, but does ignore |
| 29 |
> how you find that info.) Given your two CPUs are relatively close |
| 30 |
> (unless I misread something) there should be little if anything |
| 31 |
> critical to change. |
| 32 |
> |
| 33 |
> However, if you have a live DVD, (or on USB stick) that will always |
| 34 |
> boot, and you can then do a chroot and reset flags and start |
| 35 |
> recompiling whatever might fail. I actually think the kernel IS the |
| 36 |
> likely failure if any, but once that boots, you should be good to |
| 37 |
> recompile whatever fails. (Yes, toolchain stuff might be an issue, |
| 38 |
> but again, just boot back to the live DVD.) You may need to reboot a |
| 39 |
> few times, but you won't need to swap the old CPU back in. |
| 40 |
> |
| 41 |
> Jack |
| 42 |
> |
| 43 |
|
| 44 |
I've tried that too. Heck, sometimes that doesn't work even with |
| 45 |
windoze. My concerns are sort of along those lines tho. I don't have |
| 46 |
and can't find the current flags for the new CPU so I don't know what to |
| 47 |
do flag wise. I'm not sure that there is even a common setting but |
| 48 |
suspect there is. If I can get the kernel to boot and login at a |
| 49 |
console, even with no X, I can rebuild from there, provided everything |
| 50 |
works toolchain wise. |
| 51 |
|
| 52 |
I guess this is a good time to make sure my sysrescue and other tools |
| 53 |
work. That slipped my mind completely. Thanks for the reminder. Hmmm, |
| 54 |
I need to check on the current mount and chroot process for this too. |
| 55 |
|
| 56 |
Thanks. |
| 57 |
|
| 58 |
Dale |
| 59 |
|
| 60 |
:-) :-) |
Archives