From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Palash Nigam <b116031@iiit-bh.ac.in>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Recover previous kernel
Date: Sat, 17 Oct 2020 16:59:09 -0400 [thread overview]
Message-ID: <242093.1602968349@turing-police> (raw)
In-Reply-To: <CACaadTZW-X1Qt6s_1PtYB8S3YrDg2wSY2qD2xzZBwmPiR5CxGQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]
On Sun, 18 Oct 2020 02:01:18 +0530, Palash Nigam said:
> While building a new kernel i forgot to change the name of
> CONFIG_LOCALVERSION in the .config file as a result my current kernel got
> replaced by the one I was building.
Hold that thought for a moment...
> My original kernel still exists as Pop_OS-oldkern.conf,
That would be a config file, not the actual kernel. Unless Pop_OS has a
*really* bad naming convention for things...
> and I can still boot into it once booting into the new kernel fails.
If you can boot into it, it can't have been replaced. So you've done something
to your system, but it's not what you *think* it is.
What does an 'ls -l' of /boot say (definitely need to check timestamps
on files)? And are you using grub2 or something
else to load the kernel?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-10-17 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 20:31 Recover previous kernel Palash Nigam
2020-10-17 20:59 ` Valdis Klētnieks [this message]
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=242093.1602968349@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=b116031@iiit-bh.ac.in \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).