1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] Changing CPU and motherboard

    From whiteman808@21:1/5 to All on Sat Jun 28 18:40:01 2025
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I
    need to do these operations from chroot?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Sat Jun 28 18:49:23 2025
    On Saturday, 28 June 2025 18:33:24 British Summer Time Jay Faulkner wrote:
    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I need to do these operations from chroot?

    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS.
    If you're using -march=native, there's a chance your system won't work
    as compiled. This isn't always true, but these days it's no longer a guarantee that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch generic target works) -- https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help
    with this. - Ensure my system is fully updated, and `emerge
    --depclean`'d. - emerge -e @world # this will rebuild your entire system.


    You can *significantly* reduce the pain of this by using the binary
    package host.


    -JayF

    If you have compiled a bespoke kernel strictly specified for the CPU/MoBo hardware the system is running on and them move it to a different CPU/MoBo hardware, you will find the kernel may not boot at all, or it may boot but
    fail to initialise some hardware, e.g. NICs, graphics card, etc., because it
    is missing specific drivers and firmware. Using more generic settings will
    get you a bigger kernel which can boot more hardware than the original. -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmhgKyMACgkQseqq9sKV ZxkSMRAAhUrDy6mfBf93h5kuBWC4mNzJBse6pNa+0W9+JkOJOkW9J3/k1Pe3EniN oJYILWH/+m6aNlT036eF/5huBcPnrBwvchKDLbE3GW0KdvWHDDPMnmBQOI7dGirx 6/GN+qDACIg/ipyeNsyYm7ksRr9C1QAUrAz8/PUOp2QKSNNXFf+O6W3vZSue10t9 80Y5VIzNsS+Bf+3AASpsK2I1IYwOuuRVr31Rw8K/KXVF0ZOjagD6VfU3TSDkY6bC C97MoTkTvBmCGk+YyWywmQp4Wm5EXqACyIp7J9YCipHgXP9fiMy0E146sND4dZQ8 SLiG/FoVAMyjf916M23gRCyegSemET+hJwzuowFkAeQBiFfonq51Zr4713xGYqFZ VrhPGDN682dDYqEsq+Ke1F5fkPdBDuOB/jbcz+ZggXUk0Gluxi8okkZkjUUpfXTV gSOtjchgtPucOKi8W4T71hBkpxKwEMrP8rIA0g8gh/EXDJxdvW5mzppaH5iOB6Fh HB2m9MdqnVXWDclsYzg1GZn0u3bhQh3Feo7ttItsG/rDdMHxqAksePA2bfU2lLsj o85+LRJIZPz8oJLZaKfXzE6u3kFHvV+Wou4POJP8z+WfN7xK6IYR64LJJg0+PfNK HYXUraZN7G/DOClug1MlAMU0KJ0Ooe84TC9HHLSB78nnUn+M26Q=
    =OV6t
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jay Faulkner@21:1/5 to All on Sat Jun 28 19:40:01 2025
    This is a multi-part message in MIME format.
    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I
    need to do these operations from chroot?

    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS.
    If you're using -march=native, there's a chance your system won't work
    as compiled. This isn't always true, but these days it's no longer a
    guarantee that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch
    generic target works) -- https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help
    with this. - Ensure my system is fully updated, and `emerge
    --depclean`'d. - emerge -e @world # this will rebuild your entire system.


    You can *significantly* reduce the pain of this by using the binary
    package host.


    -JayF

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix">On 6/28/2025 9:38 AM, whiteman808
    wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:mb3w5oodmv4drpe66qql3lywzzck7oxtzeqcjt57abprtpy4sl@huttppasmphe">
    <pre wrap="" class="moz-quote-pre">Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I
    need to do these operations from chroot?
    </pre>
    </blockquote>
    <p><span style="white-space: pre-wrap">I'm assuming this is amd64-&gt;amd64.</span></p>
    <p>So the main thing to worry about is CPU compatibility, and your
    CFLAGS. If you're using -march=native, there's a chance your
    system won't work as compiled. This isn't always true, but these
    days it's no longer a guarantee that a newer CPU will have all the
    features of the old.</p>
    <p><br>
    </p>
    <p>What I usually do in this case is:<span
    style="white-space: pre-wrap">
    </span></p>
    <p><span style="white-space: pre-wrap">- set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch generic target works) -- <a class="moz-txt-link-freetext" href="https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels">https://wiki.
    gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels</a> can help with this.
    - Ensure my system is fully updated, and `emerge --depclean`'d.
    </span>- emerge -e @world # this will rebuild your entire system.</p>
    <p><br>
    </p>
    <p>You can *significantly* reduce the pain of this by using the
    binary package host.</p>
    <p><br>
    </p>
    <p>-JayF</p>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whiteman808@21:1/5 to Jay Faulkner on Sat Jun 28 21:20:01 2025
    On 28 Jun 2025, 10:33:24, Jay Faulkner wrote:
    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I need to do these operations from chroot?

    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS. If you're using -march=native, there's a chance your system won't work as compiled. This isn't always true, but these days it's no longer a guarantee that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch generic target works) -- https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help with this. - Ensure my system is fully updated, and `emerge --depclean`'d. - emerge -e @world # this will rebuild your entire system.


    You can *significantly* reduce the pain of this by using the binary package host.


    -JayF
    Should I execute `emerge -e @world` inside chroot on some livecd?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whiteman808@21:1/5 to Dale on Sat Jun 28 21:50:01 2025
    On 28 Jun 2025, 14:32:57, Dale wrote:
    Jay Faulkner wrote:

    On 6/28/2025 9:38 AM, whiteman808 wrote:

    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I
    need to do these operations from chroot?

    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS. If
    you're using -march=native, there's a chance your system won't work as
    compiled. This isn't always true, but these days it's no longer a guarantee
    that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch
    generic target works) -- https://wiki.gentoo.org/wiki/Safe_CFLAGS#
    Generic_psABI_levels can help with this. - Ensure my system is fully
    updated, and `emerge --depclean`'d. - emerge -e @world # this will rebuild
    your entire system.


    You can *significantly* reduce the pain of this by using the binary package
    host.


    -JayF



    Follow Jay's advice on the march setting in make.conf.  You want a setting that
    is compatible with both CPUs as Jay mentioned.  Do a emerge -e world.  Also,
    --depclean as well. 

    When you install the new CPU.  You will need a kernel.  Your current one may
    work, may not.  If it does, I'd stick to a console with no GUI running.  Method
    below may be faster since you only have to recompile once if you want to switch
    the march setting back to native.

    A somewhat shorter method, after you install new CPU, boot another boot media,
    Gentoo Live CD, Knoppix or whatever your system can boot with and you like.  Then mount your partitions as needed for the OS, chroot in, emerge -e world. 
    It should see the new CPU and change all the settings.  Since the boot media is
    handling the boot, it doesn't matter what your version of OS is as long as the
    Arch is the same.  Don't forget to build a new kernel as well.  The command lspci -k can be a really awesome friend.  Also, you can leave the MARCH set to
    native setting and this way you only compile once.

    If you can make it without the computer a bit, I'd boot from other media and rebuild only once.  Oh, don't forget to change the CPU flags if you have it set.  The command cpuid2cpuflags is good for that.  If you don't have it, package is the same name.  You can unmerge it when done if you want. 

    Just another idea.  There are likely several ways to accomplish this.  Biggest
    thing is the kernel. 

    Dale

    :-)  :-) 
    Does portage need to be able to execute some files already present on
    the system if I compile new software or recompile entire system using
    emerge -e? If yes, what if old CPU features and flags are entirely
    incompatible and not subset of the new CPU settings if I compile using
    livecd? How portage handles these cases?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jay Faulkner@21:1/5 to All on Sat Jun 28 22:00:01 2025
    On 6/28/2025 12:10 PM, whiteman808 wrote:
    On 28 Jun 2025, 10:33:24, Jay Faulkner wrote:
    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I >>> need to do these operations from chroot?
    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS. If >> you're using -march=native, there's a chance your system won't work as
    compiled. This isn't always true, but these days it's no longer a guarantee >> that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch
    generic target works) --
    https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help with >> this. - Ensure my system is fully updated, and `emerge --depclean`'d. -
    emerge -e @world # this will rebuild your entire system.


    You can *significantly* reduce the pain of this by using the binary package >> host.


    -JayF
    Should I execute `emerge -e @world` inside chroot on some livecd?

    As long as you pick a target that overlaps your current and future CPU,
    you should be able to perform 100% of the steps on the "before" PC.


    -JayF

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to I think you meant to on Sat Jun 28 21:15:59 2025
    On Saturday, 28 June 2025 21:10:59 British Summer Time Dale wrote:

    Me tho, I'd install the CPU and try booting. I'd just stick to a
    console, no GUI. Run emerge -ae world and go take a nap, go to work or whatever. Make sure to include --resume tho. If something fails, it
    will keep trying.

    I think you meant to write: '--keep-going y'


    If anything does fail, it will spit out a list. Try
    them on their own. If you don't have --oneshot set, make sure to
    oneshot those so your world file doesn't get full of unwanted entries.

    Someone else may have more info on that question. I just think it will
    work and at least worth a try. Save a lot of time for sure if it does
    work.

    Dale

    :-) :-)


    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmhgTX8ACgkQseqq9sKV Zxk0kg/9HDlFTSpz9jSuEe1nn3igbSvURLXkdEkksis6km1JwnUPsLdgYCaDynwp Bm+UD475u48Ex7/Br+X71HePCt2H9ghIC2wz7OA4yq2jhrSJWbzhlxLVcDpe2YPd iggHce6V+Ly4dZI/oIh+Fpqk0coYxYuv+rERUeUOXeWd+vokfjNVarrvU59APtjw tUVN5lMw1k4vZ3TUcNGAWnuajvFxfeo3yH9trnCb+CyXetLVp6kaOpm7Z4+RKAu1 3Z/uLzGdAQtFH4j98P91C0XQJeqDkWDIYs1qulFeuvw3FgM1/dadZ3A4t3Kbe99n Y4YkSXVA9J3EiVeVDfd74Z+9xenIEQ19TggnAp8tceDR/x1IbrET8mxee4p7O+Aj c757AaEbc4MEuBNRKGFj0U+eQ2ZycsVp21+U0bIvAmqDWSXFmxLWUpc2qcoapLUs 6TupZniCGXXLHfJYrjvNvBDIyM7rTUr6qf6t6maBsqmh+FDbeBXe4MTHDmhkx2mI Q5xPO4JFATRiSfSKeYWIj87yzvTGcewOjKT4hrCMMFmSd8dTmBQYGBaPKgNSRJ8l cZEkyd8A2P2ywPpQzTrN/0Q7UAJ7KZLOkkR6GzxGCvju15BYAgjCytY5GdBiE7sX w7qYp4lQ8szq8fiKyGJV11Xue9bZNX8inGk1GgNn09J/TomyyHA=
    =RRFC
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whiteman808@21:1/5 to All on Sun Jun 29 01:10:01 2025
    How does situation look in binary-based distros like Debian, Arch? Is
    rsyncing old Debian or Arch installation to PC with new processor or motherboard and configuring hardware-specific stuff sufficient?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jay Faulkner@21:1/5 to All on Sun Jun 29 03:20:01 2025
    This is a multi-part message in MIME format.
    On 6/28/2025 4:04 PM, whiteman808 wrote:
    How does situation look in binary-based distros like Debian, Arch? Is rsyncing old Debian or Arch installation to PC with new processor or motherboard and configuring hardware-specific stuff sufficient?


    These distributions target a generic architecture, like x86-64-v2 or
    x86-64-v3. Following my instructions earlier on getting a more generic
    CFLAGS setup and using binary packages will get you to the same place
    with Gentoo.

    -JayF

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 6/28/2025 4:04 PM, whiteman808
    wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:6mdbkfs6ekfa4kpliqnyzegzkjdtu6y2pijrzqkkvt2hyihkcx@n2ifzei7xna5">
    <pre wrap="" class="moz-quote-pre">How does situation look in binary-based distros like Debian, Arch? Is
    rsyncing old Debian or Arch installation to PC with new processor or motherboard and configuring hardware-specific stuff sufficient?
    </pre>
    </blockquote>
    <p><br>
    </p>
    <p><span style="white-space: pre-wrap">These distributions target a generic architecture, like x86-64-v2 or x86-64-v3. Following my instructions earlier on getting a more generic CFLAGS setup and using binary packages will get you to the same place
    with Gentoo.</span></p>
    <p><span style="white-space: pre-wrap">
    </span></p>
    <p><span style="white-space: pre-wrap">-JayF</span></p>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Steinmetzger@21:1/5 to All on Sun Jun 29 04:30:01 2025
    Am Sat, Jun 28, 2025 at 10:33:24AM -0700 schrieb Jay Faulkner:
    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
    not, what steps should be done on the existing Gentoo installation? Do I need to do these operations from chroot?

    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS. If you're using -march=native, there's a chance your system won't work as compiled. This isn't always true, but these days it's no longer a guarantee that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch generic target works) -- https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help with this. - Ensure my system is fully updated, and `emerge --depclean`'d. - emerge -e @world # this will rebuild your entire system.


    I see no point in rebuilding the system on the old machine with with a
    generic -march, just to migrate it to a new machine where you rebuild it
    again with -march=native. So if you do run march=native and it doesn’t just boot, I would build from scratch and migrate my settings. It’s more efficient.

    --
    Grüße | Greetings | Salut | Qapla’
    Please do not share anything from, with or about me on any social network.

    The Bible says to work for six days and rest on the seventh.
    But where is it written that we shall start fresh on the eigth?

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEVbE9o2D2lE5fhoVsizG+tUDUMMoFAmhgoswACgkQizG+tUDU MMr9WQ//QQ+hFUDAhj+5M6yGztGwq2vtgF6RzWz/B6Wld34e5A4BbhLTBPEERfeK awBQxijXOyMkkQc1FLj34WQngEWwKEdjbvRMERevaSsKbSSHP+Y74oRoiWdenr+G 0tZFwrH1FzMEQbEpMn99ALyqrj1BmHovhjw7Qq6hsBMyH+KnySvPNPFRT+Irq7od s9TVWqlsQrGoc+hnzd2X5TV6E40KE23Qdaxu6O74Hlf0sDMlqdtt59EVAYvOX80K gIo9xjqbHM5q1AAjW8YLZJ8J8o/8+yE2hdGEMf9094VGrga6NR9P92I7p8+ziWpU GaXALCzIUsnNVa4Rtcw+cSCOfhUFuhzVTHafSJiyhkKpn2M2o9hR3hN25oFigqx+ QceWe4v8RXSWc4UNr0wjZgEjxrz4y2EPeb2io/622SAdSnsZ09OevuucJQ61++gT dvzj31/iCn8VtJiH5C7veFeb0AfV0Hh9GdE5rgEVPPt6/QPEK0oy8KLjbhjvxbDj J06BUX0kG4Ymns0PEfvvYfMga8QJeeLjnacBOu1o2iwKAUBW1ePli8So6pVwzf0Z ftPDjIcOTK9F8wlMMawwRytlX24ynXQ57R3NgS21kbwR/r0A2KAXEYBupXfD1ev0
    2etR5kzOBhlFN
  • From Michael@21:1/5 to All on Sun Jun 29 08:44:38 2025
    On Sunday, 29 June 2025 03:19:59 British Summer Time Frank Steinmetzger wrote:
    Am Sat, Jun 28, 2025 at 10:33:24AM -0700 schrieb Jay Faulkner:
    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard? If not, what steps should be done on the existing Gentoo installation? Do I need to do these operations from chroot?

    I'm assuming this is amd64->amd64.

    So the main thing to worry about is CPU compatibility, and your CFLAGS. If you're using -march=native, there's a chance your system won't work as compiled. This isn't always true, but these days it's no longer a
    guarantee
    that a newer CPU will have all the features of the old.


    What I usually do in this case is:

    - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch generic target works) -- https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help
    with
    this. - Ensure my system is fully updated, and `emerge --depclean`'d. - emerge -e @world # this will rebuild your entire system.

    I see no point in rebuilding the system on the old machine with with a generic -march, just to migrate it to a new machine where you rebuild it again with -march=native. So if you do run march=native and it doesn’t just boot, I would build from scratch and migrate my settings. It’s more efficient.

    +1 ^^^

    When moving a Gentoo system from one hardware platform to another your need to check and adjust if necessary:

    1. The CPU architecture and compiler flags.
    2. The CPU microcode.
    3. The NICs drivers and firmware.
    4. The graphics drivers and firmware.
    5. The drivers for any change in MoBo bus(es), partition types and filesystems.
    6. The drivers and firmware for any peripherals.

    Unless I've missed anything, after you build the new kernel with the above in mind you should be able to boot with it. You can rebuild @world on the PC which runs faster.

    If you're using the Gentoo Distribution Kernel and Binhost packages, the migration could be much easier due to the generic choices of the precompiled software.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmhg7uYACgkQseqq9sKV Zxke0BAApfriUiaYGPU8K1toPb1YX17SlDnEJ8BSbFI9nT7EdW0DaeO9sr5PBDdi A1TrD1YCklqK16rT4UL2R8E8FIClpyWO4YJrECgAKHgb1U98y+E2Of6j27ID58cy dPzasR/7IDf7ULyUbwBBe/39pUvwLxQVv2Iklmpas8ZgVpU74EwAXZtDv2MaiUzl EJF+67Z+pbgCFGXkdCNMWC9Cy3h9ufLsMFwtGa7wH665ebvcdJiAwJBa4tkwIblo ygZGFiKeqCWHwWHkt2kT5orPI+2porIUohJIGN0YIlIRqDl1R5lNTuOeVwF9KtEm MR/zf28j+3pYmSsHI1aanDhaY1tfasMGp1fYAGJZwBEQ4xaCr9qTQB9In35Z5gfJ 2ZAm1AHFypU/UXpJucQnBN1xAUvG0NqaFyjrxfUlvnfAqppwmPrW5ajUtXhJeUOp +GLG2DpKQz/0WguYRAWG75oDCV3raL9XNfxrELKXTQ8Ep0BUgJOFIC71VN+ctLSW Gm4W3T57ClqcYlJYGpiQQuNHReSQoKDlTV7atpfaYkAEZCbAQquZ6LTCncbEacTL 9OH6kh8nzwEHEgeTuPkyKYiXkvDxUlJ/zjk2tKz4hOPc3bJ6U3VCJxmH78g5zDbm S7Fm65MEVux2+LY5x8b1hR44conj+IK85OPSj1bDzHXWSXGbthg=
    =lLo+
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steven Lembark@21:1/5 to Jay Faulkner on Tue Jul 1 18:30:01 2025
    On Sat, 28 Jun 2025 10:33:24 -0700
    Jay Faulkner <jayf@gentoo.org> wrote:

    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard?
    If not, what steps should be done on the existing Gentoo
    installation? Do I need to do these operations from chroot?

    You don't say if the kernel is compiled locally or if you use
    something like '-march=native' compiling everything.

    If you do then the simplest fix is (assuming you don't have it
    all glommed onto one partition) is just do a fresh install on
    a new /root + /var LV and mount the old stuff. The baseline
    stage3, mount your existing non-stage LV's, build a kernel,
    then "emerge @world" isn't that much hands-on time.

    If you are using a generic kernel with separate LV's then just
    skip compiling a new kernel.

    If you are using a single partition for all of it then consider
    this an excellent time to use LV's for managing it going forward.

    --
    Steven Lembark
    Workhorse Computing
    lembark@wrkhors.com
    +1 888 359 3508

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jay Faulkner@21:1/5 to Steven Lembark on Wed Jul 2 01:00:01 2025
    This is a multi-part message in MIME format.
    On 7/1/2025 9:22 AM, Steven Lembark wrote:
    On Sat, 28 Jun 2025 10:33:24 -0700
    Jay Faulkner<jayf@gentoo.org> wrote:

    On 6/28/2025 9:38 AM, whiteman808 wrote:
    Is it necessary to reinstall Gentoo if I change CPU or motherboard?
    If not, what steps should be done on the existing Gentoo
    installation? Do I need to do these operations from chroot?
    You don't say if the kernel is compiled locally or if you use
    something like '-march=native' compiling everything.

    If you do then the simplest fix is (assuming you don't have it
    all glommed onto one partition) is just do a fresh install on
    a new /root + /var LV and mount the old stuff. The baseline
    stage3, mount your existing non-stage LV's, build a kernel,
    then "emerge @world" isn't that much hands-on time.

    Honestly, I think this is overkill given you can:

    1) emerge gentoo-kernel-bin (for a starting point kernel that will work
    on both devices) 2) update make.conf and emerge -e @world (or read docs
    and get some certainty you don't need to for your CPU upgrade) 3) hooray
    it works on both systems \o/

    I always think that anytime with gentoo you do a reinstall instead of
    working through the process, you're giving up a chance to understand how
    stuff really works just a little bit better ... which is a lot of the
    point of running it for me personally :).

    -JayF

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix">On 7/1/2025 9:22 AM, Steven Lembark
    wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:20250701122211.3ee82a40.lembark@wrkhors.com">
    <pre wrap="" class="moz-quote-pre">On Sat, 28 Jun 2025 10:33:24 -0700
    Jay Faulkner <a class="moz-txt-link-rfc2396E" href="mailto:jayf@gentoo.org">&lt;jayf@gentoo.org&gt;</a> wrote:

    </pre>
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">On 6/28/2025 9:38 AM, whiteman808 wrote:
    </pre>
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">Is it necessary to reinstall Gentoo if I change CPU or motherboard?
    If not, what steps should be done on the existing Gentoo
    installation? Do I need to do these operations from chroot?
    </pre>
    </blockquote>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">
    You don't say if the kernel is compiled locally or if you use
    something like '-march=native' compiling everything.

    If you do then the simplest fix is (assuming you don't have it
    all glommed onto one partition) is just do a fresh install on
    a new /root + /var LV and mount the old stuff. The baseline
    stage3, mount your existing non-stage LV's, build a kernel,
    then "emerge @world" isn't that much hands-on time.
    </pre>
    </blockquote>
    <p><span style="white-space: pre-wrap">
    </span></p>
    <p><span style="white-space: pre-wrap">Honestly, I think this is overkill given you can:</span></p>
    <p><span style="white-space: pre-wrap">1) emerge gentoo-kernel-bin (for a starting point kernel that will work on both devices)
    2) update make.conf and emerge -e @world (or read docs and get some certainty you don't need to for your CPU upgrade)
    3) hooray it works on both systems \o/</span></p>
    <p><span style="white-space: pre-wrap">
    </span></p>
    <p>I always think that anytime with gentoo you do a reinstall
    instead of working through the process, you're giving up a chance
    to understand how stuff really works just a little bit better ...
    which is a lot of the point of running it for me personally :).</p>
    <p>-JayF</p>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)