Should I reinstall Linux when changing the laptop's CPU?Will my device work with Ubuntu?How to keep the...
Does dispel magic end a master's control over their undead?
How do I draw the dashed lines as shown in this figure
Why zero tolerance on nudity in space?
How can I play a serial killer in a party of good PCs?
What is the difference between rolling more dice versus fewer dice?
Scripture(s) saying not to look at the sun during his rising and setting time
What is the data structure of $@ in shell?
How to deal with possible delayed baggage?
What to look for when criticizing poetry?
How should I handle players who ignore the session zero agreement?
Why was Lupin comfortable with saying Voldemort's name?
Is using an 'empty' metaphor considered bad style?
"on its way" vs. "in its way"
Alien invasion to probe us, why?
A Missing Symbol for This Logo
Am I a Rude Number?
Salsa20 Implementation: Sum of 2 Words with Carries Suppressed
Identify KNO3 and KH2PO4 at home
How to visualize the Riemann-Roch theorem from complex analysis or geometric topology considerations?
Picture with grey box as background
Why are all my replica super soldiers young adults or old teenagers?
Why is working on the same position for more than 15 years not a red flag?
Why would space fleets be aligned?
What is a good reason for every spaceship to carry a weapon on board?
Should I reinstall Linux when changing the laptop's CPU?
Will my device work with Ubuntu?How to keep the laptop's temperature low without hardware cleaning?Screenlets RingSensors has to many CPU sensors, what are they?How do I boot Ubuntu in VirtualBox complaining that my CPU is incompatible?top command on ubuntu multicore cpu shows cpu usage >100%CPU dual core both cores syncing only after rebootWhat is it with Ubuntu / Linux, Youtube / HTML5 videos and the high CPU load?Which platform of Ubuntu Server should i choose with i686 cpu?CPU usage is increased gradually until the computer is suspended, although doing nothingGnome Shell and high cpu usageShort freezing, sound crackling - (CPU seems not to be the problem)
I am planning on changing my laptop's CPU in the next few days.
Should I expect anything from Ubuntu? Like a slower/different start for the first time, or should I completely reinstall Ubuntu?
They are both of 64-bit architecture.
cpu cpu-architecture
add a comment |
I am planning on changing my laptop's CPU in the next few days.
Should I expect anything from Ubuntu? Like a slower/different start for the first time, or should I completely reinstall Ubuntu?
They are both of 64-bit architecture.
cpu cpu-architecture
2
Was your Original install 32 Bit compared to 64 and is the processor now 64?
– EODCraft Staff
yesterday
6
It is impossible to switch a laptop CPU from 32 to 64 bit on the same motherboard.
– Pilot6
yesterday
Related: Will my device work with Ubuntu?
– Melebius
yesterday
2
@Pilot6, I'm not familiar with laptops, but on the desktop, it's at least theoretically possible for a Socket 754 or LGA 775 board to support both 32-bit and 64-bit CPUs.
– Mark
17 hours ago
add a comment |
I am planning on changing my laptop's CPU in the next few days.
Should I expect anything from Ubuntu? Like a slower/different start for the first time, or should I completely reinstall Ubuntu?
They are both of 64-bit architecture.
cpu cpu-architecture
I am planning on changing my laptop's CPU in the next few days.
Should I expect anything from Ubuntu? Like a slower/different start for the first time, or should I completely reinstall Ubuntu?
They are both of 64-bit architecture.
cpu cpu-architecture
cpu cpu-architecture
edited 6 hours ago
Community♦
1
1
asked yesterday
hadarShadarS
20739
20739
2
Was your Original install 32 Bit compared to 64 and is the processor now 64?
– EODCraft Staff
yesterday
6
It is impossible to switch a laptop CPU from 32 to 64 bit on the same motherboard.
– Pilot6
yesterday
Related: Will my device work with Ubuntu?
– Melebius
yesterday
2
@Pilot6, I'm not familiar with laptops, but on the desktop, it's at least theoretically possible for a Socket 754 or LGA 775 board to support both 32-bit and 64-bit CPUs.
– Mark
17 hours ago
add a comment |
2
Was your Original install 32 Bit compared to 64 and is the processor now 64?
– EODCraft Staff
yesterday
6
It is impossible to switch a laptop CPU from 32 to 64 bit on the same motherboard.
– Pilot6
yesterday
Related: Will my device work with Ubuntu?
– Melebius
yesterday
2
@Pilot6, I'm not familiar with laptops, but on the desktop, it's at least theoretically possible for a Socket 754 or LGA 775 board to support both 32-bit and 64-bit CPUs.
– Mark
17 hours ago
2
2
Was your Original install 32 Bit compared to 64 and is the processor now 64?
– EODCraft Staff
yesterday
Was your Original install 32 Bit compared to 64 and is the processor now 64?
– EODCraft Staff
yesterday
6
6
It is impossible to switch a laptop CPU from 32 to 64 bit on the same motherboard.
– Pilot6
yesterday
It is impossible to switch a laptop CPU from 32 to 64 bit on the same motherboard.
– Pilot6
yesterday
Related: Will my device work with Ubuntu?
– Melebius
yesterday
Related: Will my device work with Ubuntu?
– Melebius
yesterday
2
2
@Pilot6, I'm not familiar with laptops, but on the desktop, it's at least theoretically possible for a Socket 754 or LGA 775 board to support both 32-bit and 64-bit CPUs.
– Mark
17 hours ago
@Pilot6, I'm not familiar with laptops, but on the desktop, it's at least theoretically possible for a Socket 754 or LGA 775 board to support both 32-bit and 64-bit CPUs.
– Mark
17 hours ago
add a comment |
4 Answers
4
active
oldest
votes
Ubuntu (and generally speaking Linux) don't particularly care what hardware they're running on, and will perform a check on all devices at boot rather than assuming that the same devices are there each time. So long as your CPU is compatible with your chipset, Ubuntu will see it and start using it. Ubuntu 18.04 is also only available in the 64-bit version, so that's not a concern either.
Windows, on the other hand, has licensing to worry about. When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware. This doesn't mean that you can't change hardware, but if you do it too frequently (like I've managed to do) it will start to say your key is invalid. If you're in a dual-boot system, this is something to keep in mind.
1
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
4
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
1
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
2
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
2
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
|
show 1 more comment
should I completely reinstall Ubuntu?
No.
Counter-intuitively, changing CPU is one the least meaningful changes in hardware. Usually it doesn't require any changes in software.
That's because your CPU swapping options are extremely limited by socket and chipset. Those limit you to CPUs coming from one or two product generations that are very similar feature-wise. Sure, they may differ in features that matter to you, like number of cores, clock speed and cache size. But those are virtually transparent to the software. The architecture, instructions, registers and all other details that are important to how the software uses CPU remain same. Top execution speed is not something that modern software depends on (the actual execution speed fluctuates all the time due to energy saving anyway).
Even non-open systems, which lock license to the hardware (like Windows) don't consider CPU as "important" hardware. Swapping CPU and RAM are considered standard customer procedures and don't invalidate license.
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
add a comment |
If the CPU architecture is the same (e.g. 64 bit/amd64) it should work out of the box. 15 years ago, I took a harddisk of one computer to a different one (both 32bit) and it worked out of the box as expected.
The "slower/different start" depends partly on the speed of the CPUs, so if your new CPU is faster/newer/more expensive it should be and boot faster.
add a comment |
No, you don't need to reinstall, because Ubuntu compiles all packages for what is known as "generic amd64". This is a collection of instruction sets present in every single amd64 CPU. Any programs that use instructions beyond this base set(also known as instruction set extensions) include fall-backs.
Now, let's assume:
- you were using packages that make use of instruction set extensions, such as AVX2 and don't provide fall-backs,
- you're moving to a CPU which doesn't support this particular instruction set.
This is highly unlikely to happen when only switching CPUs. You'd have to be downgrading the CPU to find one on the same motherboard that supports less instruction sets.
Even then, you wouldn't need to reinstall your OS, although it might be the easier option. You could instead recompile your packages to generic amd64. After switching everything would work fine, albeit slower. To accelerate it, you could recompile yet again, this time using extensions supported by the new CPU.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1121349%2fshould-i-reinstall-linux-when-changing-the-laptops-cpu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ubuntu (and generally speaking Linux) don't particularly care what hardware they're running on, and will perform a check on all devices at boot rather than assuming that the same devices are there each time. So long as your CPU is compatible with your chipset, Ubuntu will see it and start using it. Ubuntu 18.04 is also only available in the 64-bit version, so that's not a concern either.
Windows, on the other hand, has licensing to worry about. When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware. This doesn't mean that you can't change hardware, but if you do it too frequently (like I've managed to do) it will start to say your key is invalid. If you're in a dual-boot system, this is something to keep in mind.
1
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
4
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
1
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
2
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
2
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
|
show 1 more comment
Ubuntu (and generally speaking Linux) don't particularly care what hardware they're running on, and will perform a check on all devices at boot rather than assuming that the same devices are there each time. So long as your CPU is compatible with your chipset, Ubuntu will see it and start using it. Ubuntu 18.04 is also only available in the 64-bit version, so that's not a concern either.
Windows, on the other hand, has licensing to worry about. When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware. This doesn't mean that you can't change hardware, but if you do it too frequently (like I've managed to do) it will start to say your key is invalid. If you're in a dual-boot system, this is something to keep in mind.
1
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
4
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
1
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
2
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
2
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
|
show 1 more comment
Ubuntu (and generally speaking Linux) don't particularly care what hardware they're running on, and will perform a check on all devices at boot rather than assuming that the same devices are there each time. So long as your CPU is compatible with your chipset, Ubuntu will see it and start using it. Ubuntu 18.04 is also only available in the 64-bit version, so that's not a concern either.
Windows, on the other hand, has licensing to worry about. When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware. This doesn't mean that you can't change hardware, but if you do it too frequently (like I've managed to do) it will start to say your key is invalid. If you're in a dual-boot system, this is something to keep in mind.
Ubuntu (and generally speaking Linux) don't particularly care what hardware they're running on, and will perform a check on all devices at boot rather than assuming that the same devices are there each time. So long as your CPU is compatible with your chipset, Ubuntu will see it and start using it. Ubuntu 18.04 is also only available in the 64-bit version, so that's not a concern either.
Windows, on the other hand, has licensing to worry about. When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware. This doesn't mean that you can't change hardware, but if you do it too frequently (like I've managed to do) it will start to say your key is invalid. If you're in a dual-boot system, this is something to keep in mind.
answered yesterday
MintyMinty
74328
74328
1
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
4
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
1
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
2
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
2
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
|
show 1 more comment
1
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
4
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
1
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
2
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
2
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
1
1
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
This holds true even when you go from real hardware to a VM. At the company I'm working at, we've combined 3 servers into a single Debian machine with 3 VMs. One of them was my trusted web development machine. Before, it was a dedicated tower for it. It runs flawlessly. (For the record, I use VirtualBox)
– Ismael Miguel
21 hours ago
4
4
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
Note that it's only the "normal" Ubuntu which is 64-bit only: other flavors like Kubuntu and Xubuntu do offer 32-bit versions. And although Kubuntu doesn't seem to have a 32-bit download for 18.10, Xubuntu does for that version too.
– Ruslan
21 hours ago
1
1
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
@Minty "When you buy a copy of Windows, the idea is that you buy it for a single machine, so Windows tends to more or less "lock" itself to a system's hardware." Haha, sounds like the ship of Theseus. Unless it locks to one particular component, that could have interesting consequences. If I change my CPU, then my motherboard, then my graphics card, ..., one component at a time, booting each time to confirm Windows is still happy, will Windows eventually reject my system? What's the cut-off?
– Alexander
18 hours ago
2
2
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
@Alexander Windows almost always locks to the motherboard's onboard MAC address. You can change CPU, GPU, ram, drives, whatever else without issues.
– PascLeRasc
17 hours ago
2
2
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
@Alexander, the last time I looked at it, the cutoff was ten "points" of change in a six-month period, where different hardware parts had different point values (eg. a change in memory capacity was 1 point, while changing a network card was something like 5 points).
– Mark
17 hours ago
|
show 1 more comment
should I completely reinstall Ubuntu?
No.
Counter-intuitively, changing CPU is one the least meaningful changes in hardware. Usually it doesn't require any changes in software.
That's because your CPU swapping options are extremely limited by socket and chipset. Those limit you to CPUs coming from one or two product generations that are very similar feature-wise. Sure, they may differ in features that matter to you, like number of cores, clock speed and cache size. But those are virtually transparent to the software. The architecture, instructions, registers and all other details that are important to how the software uses CPU remain same. Top execution speed is not something that modern software depends on (the actual execution speed fluctuates all the time due to energy saving anyway).
Even non-open systems, which lock license to the hardware (like Windows) don't consider CPU as "important" hardware. Swapping CPU and RAM are considered standard customer procedures and don't invalidate license.
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
add a comment |
should I completely reinstall Ubuntu?
No.
Counter-intuitively, changing CPU is one the least meaningful changes in hardware. Usually it doesn't require any changes in software.
That's because your CPU swapping options are extremely limited by socket and chipset. Those limit you to CPUs coming from one or two product generations that are very similar feature-wise. Sure, they may differ in features that matter to you, like number of cores, clock speed and cache size. But those are virtually transparent to the software. The architecture, instructions, registers and all other details that are important to how the software uses CPU remain same. Top execution speed is not something that modern software depends on (the actual execution speed fluctuates all the time due to energy saving anyway).
Even non-open systems, which lock license to the hardware (like Windows) don't consider CPU as "important" hardware. Swapping CPU and RAM are considered standard customer procedures and don't invalidate license.
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
add a comment |
should I completely reinstall Ubuntu?
No.
Counter-intuitively, changing CPU is one the least meaningful changes in hardware. Usually it doesn't require any changes in software.
That's because your CPU swapping options are extremely limited by socket and chipset. Those limit you to CPUs coming from one or two product generations that are very similar feature-wise. Sure, they may differ in features that matter to you, like number of cores, clock speed and cache size. But those are virtually transparent to the software. The architecture, instructions, registers and all other details that are important to how the software uses CPU remain same. Top execution speed is not something that modern software depends on (the actual execution speed fluctuates all the time due to energy saving anyway).
Even non-open systems, which lock license to the hardware (like Windows) don't consider CPU as "important" hardware. Swapping CPU and RAM are considered standard customer procedures and don't invalidate license.
should I completely reinstall Ubuntu?
No.
Counter-intuitively, changing CPU is one the least meaningful changes in hardware. Usually it doesn't require any changes in software.
That's because your CPU swapping options are extremely limited by socket and chipset. Those limit you to CPUs coming from one or two product generations that are very similar feature-wise. Sure, they may differ in features that matter to you, like number of cores, clock speed and cache size. But those are virtually transparent to the software. The architecture, instructions, registers and all other details that are important to how the software uses CPU remain same. Top execution speed is not something that modern software depends on (the actual execution speed fluctuates all the time due to energy saving anyway).
Even non-open systems, which lock license to the hardware (like Windows) don't consider CPU as "important" hardware. Swapping CPU and RAM are considered standard customer procedures and don't invalidate license.
edited 18 hours ago
answered 18 hours ago
Agent_LAgent_L
20114
20114
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
add a comment |
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
Today, with everything being multi-core, it's true that the CPU is nearly the least significant thing you can change. But going from one core to more than one core is probably the most significant change you can make (multi-threading is a lot more complicated and bug-prone when you really can have two things happening at the same time).
– Mark
17 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: True, but the times where distributions came with separate kernels for SMP and non-SMP are long gone. Modern kernels (which I define very generously, because AFAIR this feature has existed for at least a decade) start up under the assumption that they run a native SMP CPU, and if they detect a single-core CPU without hyperthreading, they use runtime binary patching to overwrite the SMP code with more efficient one. Likewise, the kernel can dynamically detect a hypervisor and switch to paravirtualization on bootup.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
@Mark: After all, most distributions have a Live CD now, that runs a single kernel almost everywhere.
– Jörg W Mittag
9 hours ago
add a comment |
If the CPU architecture is the same (e.g. 64 bit/amd64) it should work out of the box. 15 years ago, I took a harddisk of one computer to a different one (both 32bit) and it worked out of the box as expected.
The "slower/different start" depends partly on the speed of the CPUs, so if your new CPU is faster/newer/more expensive it should be and boot faster.
add a comment |
If the CPU architecture is the same (e.g. 64 bit/amd64) it should work out of the box. 15 years ago, I took a harddisk of one computer to a different one (both 32bit) and it worked out of the box as expected.
The "slower/different start" depends partly on the speed of the CPUs, so if your new CPU is faster/newer/more expensive it should be and boot faster.
add a comment |
If the CPU architecture is the same (e.g. 64 bit/amd64) it should work out of the box. 15 years ago, I took a harddisk of one computer to a different one (both 32bit) and it worked out of the box as expected.
The "slower/different start" depends partly on the speed of the CPUs, so if your new CPU is faster/newer/more expensive it should be and boot faster.
If the CPU architecture is the same (e.g. 64 bit/amd64) it should work out of the box. 15 years ago, I took a harddisk of one computer to a different one (both 32bit) and it worked out of the box as expected.
The "slower/different start" depends partly on the speed of the CPUs, so if your new CPU is faster/newer/more expensive it should be and boot faster.
answered yesterday
tardistardis
341314
341314
add a comment |
add a comment |
No, you don't need to reinstall, because Ubuntu compiles all packages for what is known as "generic amd64". This is a collection of instruction sets present in every single amd64 CPU. Any programs that use instructions beyond this base set(also known as instruction set extensions) include fall-backs.
Now, let's assume:
- you were using packages that make use of instruction set extensions, such as AVX2 and don't provide fall-backs,
- you're moving to a CPU which doesn't support this particular instruction set.
This is highly unlikely to happen when only switching CPUs. You'd have to be downgrading the CPU to find one on the same motherboard that supports less instruction sets.
Even then, you wouldn't need to reinstall your OS, although it might be the easier option. You could instead recompile your packages to generic amd64. After switching everything would work fine, albeit slower. To accelerate it, you could recompile yet again, this time using extensions supported by the new CPU.
New contributor
add a comment |
No, you don't need to reinstall, because Ubuntu compiles all packages for what is known as "generic amd64". This is a collection of instruction sets present in every single amd64 CPU. Any programs that use instructions beyond this base set(also known as instruction set extensions) include fall-backs.
Now, let's assume:
- you were using packages that make use of instruction set extensions, such as AVX2 and don't provide fall-backs,
- you're moving to a CPU which doesn't support this particular instruction set.
This is highly unlikely to happen when only switching CPUs. You'd have to be downgrading the CPU to find one on the same motherboard that supports less instruction sets.
Even then, you wouldn't need to reinstall your OS, although it might be the easier option. You could instead recompile your packages to generic amd64. After switching everything would work fine, albeit slower. To accelerate it, you could recompile yet again, this time using extensions supported by the new CPU.
New contributor
add a comment |
No, you don't need to reinstall, because Ubuntu compiles all packages for what is known as "generic amd64". This is a collection of instruction sets present in every single amd64 CPU. Any programs that use instructions beyond this base set(also known as instruction set extensions) include fall-backs.
Now, let's assume:
- you were using packages that make use of instruction set extensions, such as AVX2 and don't provide fall-backs,
- you're moving to a CPU which doesn't support this particular instruction set.
This is highly unlikely to happen when only switching CPUs. You'd have to be downgrading the CPU to find one on the same motherboard that supports less instruction sets.
Even then, you wouldn't need to reinstall your OS, although it might be the easier option. You could instead recompile your packages to generic amd64. After switching everything would work fine, albeit slower. To accelerate it, you could recompile yet again, this time using extensions supported by the new CPU.
New contributor
No, you don't need to reinstall, because Ubuntu compiles all packages for what is known as "generic amd64". This is a collection of instruction sets present in every single amd64 CPU. Any programs that use instructions beyond this base set(also known as instruction set extensions) include fall-backs.
Now, let's assume:
- you were using packages that make use of instruction set extensions, such as AVX2 and don't provide fall-backs,
- you're moving to a CPU which doesn't support this particular instruction set.
This is highly unlikely to happen when only switching CPUs. You'd have to be downgrading the CPU to find one on the same motherboard that supports less instruction sets.
Even then, you wouldn't need to reinstall your OS, although it might be the easier option. You could instead recompile your packages to generic amd64. After switching everything would work fine, albeit slower. To accelerate it, you could recompile yet again, this time using extensions supported by the new CPU.
New contributor
New contributor
answered 10 hours ago
Syfer PolskiSyfer Polski
111
111
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1121349%2fshould-i-reinstall-linux-when-changing-the-laptops-cpu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Was your Original install 32 Bit compared to 64 and is the processor now 64?
– EODCraft Staff
yesterday
6
It is impossible to switch a laptop CPU from 32 to 64 bit on the same motherboard.
– Pilot6
yesterday
Related: Will my device work with Ubuntu?
– Melebius
yesterday
2
@Pilot6, I'm not familiar with laptops, but on the desktop, it's at least theoretically possible for a Socket 754 or LGA 775 board to support both 32-bit and 64-bit CPUs.
– Mark
17 hours ago