From: ralfconn <mentadent47@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading from 5.14 to 6.0 version
Date: Sat, 12 Nov 2022 13:08:31 +0100 [thread overview]
Message-ID: <baf69edf-20fb-b2b3-704e-e59fb95f8ec9@yahoo.com> (raw)
In-Reply-To: <3418bb3d-f939-6606-7e19-5e883c198208@gmail.com>
On 11/11/22 07:25, Dale wrote:
> Howdy,
>
> 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.
>
> I'm about to try to jump to version 6.0.5 which is latest in the tree.
> Is there some major change that causes copying .config file from 5.14 to
> 5.18 or higher to break? Do I need to configure a new kernel from
> scratch in other words? While I try to answer each question the best I
> can, either I'm breaking something or something else breaks preventing
> updating from older versions. I just don't know which it is. Me or it.
>
I've had a similar experience recently. I was using LTS (5.15) due to
old, no longer supported Nvidia video card, when I switched to nouveau I
tried 6.0.x but no go, either USB3 or USB2 where working, but not both.
After much fiddling with .config I ended up booting the PC from USB with
a recent, working binary distribution - Ubuntu 22.04 - and compared its
.config with mine, and found out the problem was in one of the kernel
boot parameters, not in the .config!
If you find the binary distribution kernel works, lsmod will tell you
which modules are actually used on your machine so you can pick just
those in your config. For the .config comparison, meld works just fine.
raffaele
next prev parent reply other threads:[~2022-11-12 12:08 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
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 [this message]
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=baf69edf-20fb-b2b3-704e-e59fb95f8ec9@yahoo.com \
--to=mentadent47@yahoo.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