Hi all, I’m switching motherboards. No dGPU. Going from an Intel MB to an AMD one. I have my root partition on an nvme and the home one on a 2.5" sata. Do I need to reinstall, or can I just move the drives from the old MB to the new one without a problem? Figured since both Intel and AMD drivers are both baked into the kernel out of the box, wouldn’t it just work and I’ll only need to remove the Intel stuff? I’m running good ole endeavourOS with KDE Plasma if that makes any difference. Any insight is much appreciated
poVoq ( @poVoq@slrpnk.net ) 19•10 months agoNo need to change anything, it will just work.
mustardman ( @mustardman@discuss.tchncs.de ) English8•10 months agoMicrocode and iGPU drivers.
entropicdrift ( @entropicdrift@lemmy.sdf.org ) 1•10 months agoiGPU 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.
mustardman ( @mustardman@discuss.tchncs.de ) English1•10 months agoamdgpu is distinctly separate from Mesa. Some distos have additional Mesa packages that also need to be instealled, now that you mention it.
entropicdrift ( @entropicdrift@lemmy.sdf.org ) 2•10 months agoamdgpu 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.
mustardman ( @mustardman@discuss.tchncs.de ) English2•10 months agoYou’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🙏
d3Xt3r ( @d3Xt3r@lemmy.nz ) 17•10 months agoYou 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 yourgrub.cfg
and check theinitrd
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.
circuitfarmer ( @circuitfarmer@lemmy.sdf.org ) 8•10 months agoI just did this a couple weeks back. Absolutely no issues of any kind.
potpie ( @potpie@beehaw.org ) 8•10 months agoSure 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.
❤️ 🍻
J4g2F ( @J4g2F@lemmy.ml ) 7•10 months agoI 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!
neoney ( @neoney@lemmy.neoney.dev ) 6•10 months agoIt will work, but swap the microcode afterwards.
What’s the microcode? A driver?
neoney ( @neoney@lemmy.neoney.dev ) 4•10 months agoOn 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
bitwolf ( @bitwolf@lemmy.one ) 1•10 months agoIt’s a firmware blob. It’ll manifest as a package you have available in the repos usually.
Found it as AMD-ucode
hackris ( @hackris@lemmy.ml ) 5•10 months agoReinstalling 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
hackris ( @hackris@lemmy.ml ) 1•10 months agoHappy to help!
original_ish_name ( @original_ish_name@lemm.ee ) 5•10 months agoJust make sure to install
amd-ucode