public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: new install for a new mainboard?
Date: Thu, 10 Dec 2020 22:20:08 -0000 (UTC)	[thread overview]
Message-ID: <rqu6uo$jh2$2@ciao.gmane.io> (raw)
In-Reply-To: 3360702.WD6VjIQDTK@eve

On 2020-12-10, J. Roeleveld <joost@antarean.org> wrote:
> On Thursday, December 10, 2020 4:23:09 PM CET n952162 wrote:
>> I need a new mainboard.  What will happen if I boot my existing system
>> on it?
>> 
>> If it would come up, what would need to be (re)emerged, as a minimum?
>> 
>> TIA
>
> Unless you really reduced the drivers available on your system or
> you're going to a lesser system (64 -> 32bit, or something like
> that), I would expect the system to simply boot.

Many of us do "reduce the drivers availabing" to match just the
hardware in our system.

> If not, you only need a live-cd/usb/... and rebuild the kernel and
> any drivers your new system needs.

> It's not MS Windows that might try to load incompatible drivers and
> ends up with a blue-screen.

Well, the screen doesn't turn blue, but it's possible the kernel won't
even boot.

--
Grant




  parent reply	other threads:[~2020-12-10 22:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 15:23 [gentoo-user] new install for a new mainboard? n952162
2020-12-10 15:38 ` Matt Connell (Gmail)
2020-12-10 15:49 ` J. Roeleveld
2020-12-10 16:07   ` Matt Connell (Gmail)
2020-12-10 22:20   ` Grant Edwards [this message]
2020-12-10 23:37   ` Miles Malone
2020-12-10 16:46 ` Raffaele BELARDI
2020-12-10 18:18 ` Rich Freeman
2020-12-10 21:18   ` n952162
2020-12-10 21:53     ` Rich Freeman
2020-12-11  6:08       ` n952162
2020-12-11 16:44     ` antlists
2020-12-10 22:18 ` [gentoo-user] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='rqu6uo$jh2$2@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox