From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading from 5.14 to 6.0 version
Date: Mon, 21 Nov 2022 14:52:58 -0600 [thread overview]
Message-ID: <a2cebc73-4b51-aa9e-ee55-94d1102d568b@gmail.com> (raw)
In-Reply-To: <CAGfcS_mdLdw-QJM24azgEE89MKwb9PJrrJxD_E0uYBPd6tJ0dg@mail.gmail.com>
Rich Freeman wrote:
> On Mon, Nov 21, 2022 at 1:10 AM Dale <rdalek1967@gmail.com> wrote:
>> I'm back to my old kernel tho since my nvidia-drivers won't work with a
>> kernel that high. I run into this on rare occasions.
> They are only rare because you aren't updating regularly.
>
> If you want to run external kernel modules like nvidia-drivers or zfs,
> stick to a longterm kernel. The ABI changes all the time, and so
> there will frequently be stable kernel version changes that break
> nvidia-drivers. Then there will be a lag before nvidia-drivers
> supports the new stable kernel. In the meantime you can't run the
> latest version, and that can mean security issues.
>
> The longterm kernels rarely break nvidia-drivers and get all the
> security and other fixes. They just don't get new features.
>
Well, I was calling how often this has happened since around 2003 or so
when I started using Linux. I think this has happened maybe two or
three times. While they always say they don't support above a certain
version, usually it just works. This time, not so much.
I did build a 5.19 version tho. I haven't rebooted yet tho. May be a
while. o_O
Dale
:-) :-)
next prev parent reply other threads:[~2022-11-21 20:53 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
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 [this message]
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=a2cebc73-4b51-aa9e-ee55-94d1102d568b@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