From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo-sources 5.7.x
Date: Tue, 09 Jun 2020 15:46:43 +0100 [thread overview]
Message-ID: <2726922.e9J7NaK4W3@peak> (raw)
In-Reply-To: <8d269d5f-be1e-0afb-4e49-3cc3e1d2b71f@gmail.com>
On Monday, 8 June 2020 16:32:07 BST Andrew Udvare wrote:
> Sounds like missing drivers. oldconfig didn't do everything it was
> supposed to. Moving across multiple major versions, this is to be
> expected. A lot of names of things have changed.
>
> Do a comparison of your configuration between old and new.
>
> diff -uN old-config-file /usr/src/linux/.config
Hmm. 4570 lines, but much of it can be discounted.
> Make sure to at least enable NVME with CONFIG_BLK_DEV_NVME=y and try
> booting 5.7 again.
Yes, they were both set already - I couldn't have booted 5.4.38 without them.
> Other than that, the naming scheme may have changed but I don't know about
> this. For better future-proofing, use a UUID of your root partition rather
> than a device name.
>
> root=UUID=...
>
> You can get this UUID with the blkid command.
I'll try this in a minute - thanks for the idea. I've stuck with device names
so far because (i) I can read them, and (ii) I can't ever have more than one
NVMe device in this box.
--
Regards,
Peter.
next prev parent reply other threads:[~2020-06-09 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 15:06 [gentoo-user] Gentoo-sources 5.7.x Peter Humphrey
2020-06-08 15:32 ` Andrew Udvare
2020-06-09 14:46 ` Peter Humphrey [this message]
2020-06-09 14:56 ` Peter Humphrey
2020-06-09 16:07 ` [gentoo-user] Gentoo-sources 5.7.x [FIXED] Peter Humphrey
2020-06-09 17:29 ` Neil Bothwick
2020-06-10 8:57 ` Peter Humphrey
2020-06-10 10:01 ` Peter Humphrey
2020-06-10 14:49 ` Neil Bothwick
2020-06-10 17:19 ` Peter Humphrey
2020-06-09 18:32 ` Andrew Udvare
2020-06-10 10:13 ` Peter Humphrey
2020-06-09 15:45 ` [gentoo-user] Gentoo-sources 5.7.x Alan Mackenzie
2020-06-09 16:03 ` Peter Humphrey
2020-06-08 15:38 ` Rich Freeman
2020-06-08 15:54 ` Neil Bothwick
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=2726922.e9J7NaK4W3@peak \
--to=peter@prh.myzen.co.uk \
--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