From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6DA65138334 for ; Thu, 6 Dec 2018 21:24:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 55DEAE09DD; Thu, 6 Dec 2018 21:24:10 +0000 (UTC) Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CD61CE0958 for ; Thu, 6 Dec 2018 21:24:09 +0000 (UTC) Received: by mail-qt1-f181.google.com with SMTP id d18so2227248qto.8 for ; Thu, 06 Dec 2018 13:24:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:in-reply-to:message-id :mime-version:content-disposition:content-transfer-encoding; bh=Bv1Zp5LQq48tJtZ3+rWL1FmT/CM7oCsPbPKWHGTCOQg=; b=qA0UtcbWS2TWC4aeHd2oLOgF5E6sFK9AeuqQtjl62exw6x9uJE/AiD1de1Br5vsS+d xPnwOjMB4B7T0e7rRIFlqulGAfmdQNOdBN6pftX74/FxJYaHfS1UD0vqfl4E+7/DfFW3 VL0G6gVj6BECjnn6S/Xi3sLmAgsOtouDqdXF9o2gIbMmy/DEJAF2sTPJsEq9Q4BdBn+v /mj+cNqfK+Pt7OstiIEj2FXO2ffOUhrAsYMtSWJf0qUmAWRz+Y2xZgiSayNCwnMnqAxM O1CqAzw4FcNu1plOBnrAKrLGQo8N/PQuV4K5HUvcLd0aRTiVFXCD5J31128X1wU+Qk0v wOwQ== X-Gm-Message-State: AA+aEWaZZdhy0+xncZKVo6iRQPOOm4RYhOolKsUVSXhbpkEIt3pshwpY cNP7qRTz1qB92YDb8b+CGcIQfC6H+pg= X-Google-Smtp-Source: AFSGD/WmMeT3NSQJEjKBi+E+9pKMXXq3g/i5olsi1DfpgA1fuPJaX5lN7224FzjAbCKoc20QJtZLlw== X-Received: by 2002:ac8:30e3:: with SMTP id w32mr28322545qta.176.1544131448863; Thu, 06 Dec 2018 13:24:08 -0800 (PST) Received: from ffortso4 ([2601:188:180:4f46:1ec1:deff:fe62:b72f]) by smtp.gmail.com with ESMTPSA id s46sm933757qtc.63.2018.12.06.13.24.07 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 06 Dec 2018 13:24:08 -0800 (PST) Date: Thu, 06 Dec 2018 16:24:07 -0500 From: Jack Subject: Re: [gentoo-user] CPU upgrade and LVM questions. To: gentoo-user@lists.gentoo.org In-Reply-To: (from rdalek1967@gmail.com on Thu Dec 6 15:58:06 2018) X-Mailer: Balsa 2.5.6-100-g6ab7b680e Message-Id: 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=ISO-8859-1; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 2abe3a6d-83ed-4c71-9957-735b500494f7 X-Archives-Hash: c3b9674f806cf06db03558b95e70fac5 On 2018.12.06 15:58, Dale wrote: [snip...] > My concern is this tho.=A0 I have my old CPU still installed and =20 > everything is compiled based on that.=A0 So, I'm stable with the old =20 > CPU.=A0 However, when I shutdown, take out the old CPU and install the =20 > new one, I'm concerned it may not boot at all because of the change =20 > or may boot but be very unstable.=A0 I recall years ago being able to =20 > set up the flags in such a way that it can run on virtually any CPU =20 > but it's been a long time ago and I don't know if it is needed or =20 > not.=A0 My hope was, someone did a very similar upgrade and can say for =20 > sure if it works or if I need to do things before changing the CPUs =20 > to make sure I can boot and be stable.=A0 If I can just get a stable =20 > console, I can do a emerge -e world and get the OS inline with the =20 > CPU.=A0 I'm just concerned whether I will have that or not.=A0 >=20 [snip...] >=20 > I just don't want to swap CPUs only to find out I've got to swap back =20 > because my system won't boot at all. Heck, it may even fail to load =20 > the kernel itself for all I know.=A0 I once made the mistake of getting a whole new (used...) PC and just =20 moved the HDD from the old one to the new, without thinking about any =20 of this. Of course it wouldn't boot at all, because I was switching =20 from an AMD to an Intel CPU and had set all flags accordingly in the =20 old box. In your case, as long as you include any flags necessary for =20 the new CPU, and remove any flags for features the new CPU does not =20 have, you should be good. (I know that sounds simple, but does ignore =20 how you find that info.) Given your two CPUs are relatively close =20 (unless I misread something) there should be little if anything =20 critical to change. However, if you have a live DVD, (or on USB stick) that will always =20 boot, and you can then do a chroot and reset flags and start =20 recompiling whatever might fail. I actually think the kernel IS the =20 likely failure if any, but once that boots, you should be good to =20 recompile whatever fails. (Yes, toolchain stuff might be an issue, but =20 again, just boot back to the live DVD.) You may need to reboot a few =20 times, but you won't need to swap the old CPU back in. Jack=