55
Intel and amd are compatible because they are both the same architecture. The only times you would need to reinstall is if the architecture changes; eg, 32-bit to 64-bit or you started using an arm based processor.
Got it. Thank you so much.
You may potentially need to edit your kernel boot parameters in grub or w/e bootloader you're using, in case you're early-loading any CPU microcode. For instance, if you're loading your Intel microcode via GRUB, you may need to run grub-mkconfig from a chroot (or your old system, if it's still accessible), or edit your grub.cfg and check the initrd parameter. But if you're late-loading microcode then you don't need to worry about it (although late-loading is discouraged and will taint the kernel).
Best to check your distro's documentation on how to update the initrd / microcode.
I have not made any special changes to the kernel parameters. Everything is stock. Only thing I did is hide grub menu from etc/default/grub. That's all.
No need to change anything, it will just work.
Microcode and iGPU drivers.
iGPU drivers should both be in Mesa, so no change needed by the user. Microcode it'd depend on the distro but most should support both out of the box.
amdgpu is distinctly separate from Mesa. Some distos have additional Mesa packages that also need to be instealled, now that you mention it.
amdgpu is a kernel module. Nearly every distro includes it in their kernel by default. Unless OP rolled their own kernel, they should already have it. If they start up their machine with an AMD graphics card of any kind they most likely shouldn't need to install or configure anything.
You're right about amdgpu, my mistake. On arch systems individual Mesa components need to be installed though, like the specific Vulkan modules to be used (amdvlk or RADV).
Thank you🙏
I upgraded my girlfriends PC grom a i7-4770 too a Ryzen 2600 and just moved the drive without any problems.
I don't needed to update or change anything. Only needed to select the drive in the bios.
That's reassuring, thank you!
I just did this a couple weeks back. Absolutely no issues of any kind.
Sure there are edge cases and whatnot, but just go ahead and move the drive over. If it doesn't work I'll buy you a beer.
❤️ 🍻
Should just work. No need to reinstall. You are correct in thinking that all the drivers are included, and furthermore, the drivers on Linux are typically loaded automatically when the hardware is detected on every boot, and this is not configured anywhere in a file or anything like that.
Usually, anyway. In theory it's possible that you manually (or some tool) hardcoded drivers somewhere, like in xorg.conf, but I'm willing to bet that isn't the case.
Awesome, thank you so much.
Tanget: Is it possible to skip this detection step for a faster boot?
I think you can regenerate your initramfs image to only include your currently loaded modules instead of all modules, which should speed things up a bit.
https://elundivided.wordpress.com/2020/01/23/faster-boot-with-trimmed-initramfs/
No... Not in practice anyway, maybe in theory. I know on ARM SoCs there's lack of auto-configuration (like you have on PCs with e.g. PCI), and the kernel has no way of knowing what hardware is available. So there's a file that lists all the devices, and how to talk to them, called (I think) a "device tree". This file gets appended to the kernel image, and so the bootloader just loads that together with the kernel. The kernel doesn't do any auto-configuration and rather just reads this file and loads the relevant drivers based on that. I guess it might be (in theory) possible to do this on PC, but I've never heard of such a thing. I also don't expect that to make any noticeable difference for boot times. Pretty sure boot times are dominated by user space, and not the kernel anyway.
Sidenote (don't do this): You can compile your own kernel (this used to be pretty common back in the day). You can select only the drivers you need, and can also select whether they should be compiled directly into the kernel or as modules that can be loaded later if needed. Pretty sure the auto-detection happens regardless for most hardware, since the driver needs to be initialized and told where the hardware is to be found. Compiling a driver right into the kernel just means the driver code is in memory right from the very start. I don't recommend doing this btw, the only difference you will notice is shit not working due to you screwing up, and you're going to waste a bunch of time and electricity compiling your kernel with every update. You sometimes needed to do this to get all your hardware working, but I haven't done this in ages.
Just make sure to install amd-ucode
It will work, but swap the microcode afterwards.
What's the microcode? A driver?
On Arch, the package names are amd-ucode and intel-ucode
It can be used to fix exploits like the infamous Spectre and Meltdown.
Thank you
It's a firmware blob. It'll manifest as a package you have available in the repos usually.
Found it as AMD-ucode
Reinstalling is only needed when the old and new CPU differ in architecture. Since these two don't, you don't have to reinstall, just make sure you install the amd-ucode package :)
Just installed the AMD-ucode. Thank you
Happy to help!
As you’ve read from the comments it will work just fine.
On the other hand I’ve never done this major of a hardware change without a reinstall. I’d always be concerned if something is wiggy if it was some ghost in the machine from the previous install.
Now I also work in enterprise level IT so even my home stuff is a fairly automated install process with ansible and the like. Then again a lot of it is also virtual so take this with a grain of salt.
I actually did run into some of those "ghosts". Lol Nothing major, though. I've been thinking of doing a complete clean install anyway since I haven't done it in a very long time. Like, I want to even nuke my home partition and redo the whole thing.
this post was submitted on 10 Sep 2023
55 points (93.7% liked)
Linux
46611 readers
1067 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS