From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 299F6158074 for ; Sat, 28 Jun 2025 19:12:08 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 198A2341F3A for ; Sat, 28 Jun 2025 19:12:08 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 97C70110567; Sat, 28 Jun 2025 19:11:05 +0000 (UTC) Received: from hognose1.porkbun.com (hognose1.porkbun.com [35.82.102.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id 9A687110278 for ; Sat, 28 Jun 2025 19:11:04 +0000 (UTC) Received: from localhost (user-109-243-0-53.play-internet.pl [109.243.0.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: whiteman808@paraboletancza.org) by hognose1.porkbun.com (Postfix) with ESMTPSA id CABF5449E3 for ; Sat, 28 Jun 2025 19:11:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paraboletancza.org; s=default; t=1751137863; bh=29v2YPEBBB/KFkfxqlfOLXMRsbO0Pztiqal466wRXnI=; h=Date:From:To:Subject:References:In-Reply-To; b=B+281xRdiLwVR8A1Jks77dm4vWAyOoGL62OkLH8MldZsgmRW+5moRx+xXmbibZfzn 0ReUfCua98YS3lPAhBaWNcWC4lgxpUQnNhR04ExCAmk4Kpxa/ebzu18yIhEgcwvY9h GOJ8/IDKlk8RFQqiotzjYTNCOBuLpURoIHEGQAuk= Date: Sat, 28 Jun 2025 21:10:58 +0200 From: whiteman808 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Changing CPU and motherboard Message-ID: References: <56a33a7d-cad0-42a4-90f6-19477e567311@gentoo.org> <56a33a7d-cad0-42a4-90f6-19477e567311@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56a33a7d-cad0-42a4-90f6-19477e567311@gentoo.org> <56a33a7d-cad0-42a4-90f6-19477e567311@gentoo.org> X-Archives-Salt: 39a99b3c-d233-436e-a3cc-783ee3a81875 X-Archives-Hash: cb4cb7c5412d5ea76fda1339ef22add1 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?