| 1 |
I don't think a straight 'drop-in/replacement' will boot. |
| 2 |
|
| 3 |
The CPU scheduler does change from 'fam10h' to 'fam15h'. |
| 4 |
The '3DNow!' && 'enhanced 3DNow!' ( used in fam10h ) instructions are |
| 5 |
dropped / removed in fam15h. |
| 6 |
|
| 7 |
Doing the 'emerge -e @world' with '-march=generic' is probably the only |
| 8 |
guaranteed to work solution. |
| 9 |
|
| 10 |
If you take this route set the CPU_FLAGS_X86= to MMX, SSE, SSE2 with no |
| 11 |
3DNow!, enhanced 3DNow! ( gcc flags / CFLAGS -mno-3dnow, -mno-3dnowa ) |
| 12 |
|
| 13 |
Just remember to change the kernel configuration also. |
| 14 |
|
| 15 |
Reference Links : |
| 16 |
https://en.wikipedia.org/wiki/Phenom_II |
| 17 |
https://en.wikipedia.org/wiki/List_of_AMD_FX_microprocessors |
| 18 |
|
| 19 |
On 12/6/18 2:58 PM, Dale wrote: |
| 20 |
> Hi, |
| 21 |
> |
| 22 |
> My concern is this tho. I have my old CPU still installed and |
| 23 |
> everything is compiled based on that. So, I'm stable with the old CPU. |
| 24 |
> However, when I shutdown, take out the old CPU and install the new one, |
| 25 |
> I'm concerned it may not boot at all because of the change or may boot |
| 26 |
> but be very unstable. I recall years ago being able to set up the flags |
| 27 |
> in such a way that it can run on virtually any CPU but it's been a long |
| 28 |
> time ago and I don't know if it is needed or not. My hope was, someone |
| 29 |
> did a very similar upgrade and can say for sure if it works or if I need |
| 30 |
> to do things before changing the CPUs to make sure I can boot and be |
| 31 |
> stable. If I can just get a stable console, I can do a emerge -e world |
| 32 |
> and get the OS inline with the CPU. I'm just concerned whether I will |
| 33 |
> have that or not. |
| 34 |
> |
Archives