From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 057761381F3 for ; Tue, 15 Oct 2013 05:38:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 00CE6E0AD6; Tue, 15 Oct 2013 05:38:03 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C33EBE0A8F for ; Tue, 15 Oct 2013 05:38:01 +0000 (UTC) Received: from mail-vb0-f50.google.com ([209.85.212.50]:38811) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VVxKU-002gIu-BG for gentoo-user@lists.gentoo.org; Tue, 15 Oct 2013 12:38:02 +0700 Received: by mail-vb0-f50.google.com with SMTP id x14so4830094vbb.23 for ; Mon, 14 Oct 2013 22:38:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VeRJoHXzBFkhdoW9ZqxHGPmLy9sXYNESDf469rhZCBE=; b=FoHoWiv4sUF9xbXHWPFijcW9LyTNzB3d1duBf/wZmCYBzdOVi/T8XPgSyVxEU8BXhQ QfDpO4/3+Dkzo9U/8ORIzFMObxImFjTyy2pwO+EY6lh1dni9n0l/MXQtiN+wLE5hRZtw 72JaKZyi3RM73+zT2PgMXdftdvTflkp/4il9HlgwclJaPdfna/VaKCxrHNg80t3n5xDt Mk4EtbLIA4exgrOB7SwjWPDXwVStMi9i8Pj0jx3RsERd52m7Czfc68yJEj1iRaJiOndq gSEJgx1oA/mNLM/s+mStdeo2cyO4FBLEl5QwEwuBlgW5UDqrQ1EwLObB/sYebL+0tuhS lI0Q== 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 MIME-Version: 1.0 X-Received: by 10.58.11.73 with SMTP id o9mr10207539veb.8.1381815480242; Mon, 14 Oct 2013 22:38:00 -0700 (PDT) Received: by 10.220.153.209 with HTTP; Mon, 14 Oct 2013 22:38:00 -0700 (PDT) Received: by 10.220.153.209 with HTTP; Mon, 14 Oct 2013 22:38:00 -0700 (PDT) In-Reply-To: <525CBB88.3070202@gmail.com> References: <525CBB88.3070202@gmail.com> Date: Tue, 15 Oct 2013 12:38:00 +0700 Message-ID: Subject: Re: [gentoo-user] New mobo change From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=047d7b2ed341d85c8f04e8c0fce6 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Get-Message-Sender-Via: svr-us4.tirtonadi.com: authenticated_id: rileyer+pandu.poluan.info/only user confirmed/virtual account not confirmed X-Archives-Salt: 479a6f36-8500-4f6f-b05a-a0b22b44b1ef X-Archives-Hash: ceec4d414341f687690e2d13f9409301 --047d7b2ed341d85c8f04e8c0fce6 Content-Type: text/plain; charset=UTF-8 On Oct 15, 2013 10:51 AM, "Dale" wrote: > > Howdy, > > I ordered the new mobo as much as I needed to wait. The mobo is the > same brand but a different chipset and a couple other things are > different. I have already built a kernel for those changes. I plan to > put everything on the old mobo on the new mobo. That includes the CPU. > I'm pretty sure this will not be needed but want to ask to be sure. Do > I need to do a emerge -e world or should it "just work" like it is? > Since the CPU is going to be the exact same CPU, I'm thinking it is not > needed. I do have march=native set in make.conf. > > Thoughts? Thanks. > Personally, I think all you need to do is to ensure that the kernel has all the drivers it needs to speak to the new mobo. Other members of the @world set relies on the drivers in the kernel. But I don't use any GUI or audio; if you're using a GUI and/or audio, you might also have to re-emerge the relevant bits. BSTS: just re-emerge @world :-) Rgds, -- --047d7b2ed341d85c8f04e8c0fce6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Oct 15, 2013 10:51 AM, "Dale" <rdalek1967@gmail.com> wrote:
>
> Howdy,
>
> I ordered the new mobo as much as I needed to wait. =C2=A0The mobo is = the
> same brand but a different chipset and a couple other things are
> different. =C2=A0I have already built a kernel for those changes. =C2= =A0I plan to
> put everything on the old mobo on the new mobo. =C2=A0That includes th= e CPU.
> I'm pretty sure this will not be needed but want to ask to be sure= . =C2=A0Do
> I need to do a emerge -e world or should it "just work" like= it is?
> Since the CPU is going to be the exact same CPU, I'm thinking it i= s not
> needed. =C2=A0I do have march=3Dnative set in make.conf.
>
> Thoughts? =C2=A0Thanks.
>

Personally, I think all you need to do is to ensure that the= kernel has all the drivers it needs to speak to the new mobo. Other member= s of the @world set relies on the drivers in the kernel.

But I don't use any GUI or audio; if you're using a = GUI and/or audio, you might also have to re-emerge the relevant bits.

BSTS: just re-emerge @world :-)

Rgds,
--

--047d7b2ed341d85c8f04e8c0fce6--