From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading from 5.14 to 6.0 version
Date: Fri, 11 Nov 2022 13:18:08 -0600 [thread overview]
Message-ID: <f1493035-bc55-69f9-ee1c-71c7f644cb08@gmail.com> (raw)
In-Reply-To: <c81eceb3-6bd0-78d7-a068-b60c2eb0f23c@konstantinhansen.de>
hitachi303 wrote:
> Am 11.11.22 um 07:25 schrieb Dale:
>> I been stuck on gentoo-sources 5.14.15 for a while. I tried upgrading
>> to I think 5.16 and then more recently 5.18. I upgraded like I always
>> do, copy .config over and run make oldconfig. Once I get everything in
>> /boot, init thingy and all, I update grub. When I get around to
>> rebooting, the new kernels always fail part way through booting. I
>> can't recall the error since I last tried a newer kernel several months
>> ago.
>
> Do you follow the guide on gentoo wiki?
>
> https://wiki.gentoo.org/wiki/Kernel/Upgrade
>
> I don't know why but building and installing is not in this article.
> For that I do follow this one (there is a link from kernel upgrade to
> this on, but it is kind of hidden)
>
> https://wiki.gentoo.org/wiki/Kernel/Configuration#Build
>
> .
>
I haven't had to follow a guide in ages. I been building my own kernels
for almost 20 years now. My problem is that the two updated kernels
doesn't work. If it was just one version, it could just be a bad build
or something. Thing is, I tried updating from a working config to two
different versions and both failed. I suspect that something major
changed and going from a old config file may not work. Thing is, I
don't know if that is the case or not. It could be, hence the question,
but it could be something else or just that I missed something and
someone else knows what that something is because they ran into it
earlier.
I wish when they did major changes, they would also change the number
scheme to reflect that. As I read in another post, sometimes even a
number change in the third place can give a very different kernel,
something major removed or added. Unless one reads all the posts on the
kernel mailing list, one wouldn't know that change happened.
I did build a new kernel from the old config and running make
oldconfig. When I get around to rebooting, I'll see if it works or
not. If not, I'll note the error and see if that gives any clues.
Thanks.
Dale
:-) :-)
next prev parent reply other threads:[~2022-11-11 19:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 6:25 [gentoo-user] Upgrading from 5.14 to 6.0 version Dale
2022-11-11 10:30 ` Peter Humphrey
2022-11-11 10:35 ` Arve Barsnes
2022-11-11 10:56 ` Wols Lists
2022-11-11 18:12 ` Laurence Perkins
2022-11-11 12:24 ` hitachi303
2022-11-11 19:18 ` Dale [this message]
2022-11-11 22:08 ` Dr Rainer Woitok
2022-11-11 14:41 ` Rich Freeman
2022-11-11 19:42 ` Dale
2022-11-11 18:04 ` Laurence Perkins
2022-11-12 12:08 ` ralfconn
2022-11-12 16:00 ` [gentoo-user] " Nikos Chantziaras
2022-11-12 18:22 ` Dale
2022-11-12 18:43 ` Mark Knecht
2022-11-12 19:13 ` Wol
2022-11-12 20:02 ` Nikos Chantziaras
2022-11-12 20:03 ` Mark Knecht
2022-11-12 21:37 ` Dale
2022-11-14 19:57 ` Nikos Chantziaras
2022-11-14 21:05 ` Dale
2022-11-14 21:44 ` Michael
2022-11-14 23:56 ` Wol
2022-11-15 0:10 ` Dale
2022-11-15 17:46 ` Laurence Perkins
2022-11-15 2:36 ` Grant Edwards
2022-11-14 21:44 ` Mark Knecht
2022-11-12 21:17 ` Rich Freeman
2022-11-21 6:10 ` [gentoo-user] " Dale
2022-11-21 12:20 ` Rich Freeman
2022-11-21 20:52 ` Dale
2022-11-21 16:11 ` [gentoo-user] " Grant Edwards
2022-11-21 16:27 ` Michael
2022-11-21 16:50 ` Grant Edwards
2022-11-21 17:24 ` Michael
2022-11-21 18:12 ` Grant Edwards
2022-11-21 19:26 ` Michael
2022-11-21 19:37 ` Grant Edwards
2022-11-21 21:30 ` Frank Steinmetzger
2022-11-21 18:15 ` Laurence Perkins
2022-11-22 19:01 ` Wol
2022-11-21 16:58 ` Mark Knecht
2022-11-21 17:49 ` Grant Edwards
2022-11-21 19:42 ` Mark Knecht
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=f1493035-bc55-69f9-ee1c-71c7f644cb08@gmail.com \
--to=rdalek1967@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