From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Upgrading from 5.14 to 6.0 version
Date: Mon, 21 Nov 2022 16:11:13 -0000 (UTC) [thread overview]
Message-ID: <tlg7v1$h5b$1@ciao.gmane.io> (raw)
In-Reply-To: 2446bc27-6406-dbe6-0076-ab01d49413c5@gmail.com
On 2022-11-21, Dale <rdalek1967@gmail.com> wrote:
> I did re-emerge the nvidia drivers for the old kernel. [...]
>
> If I get bored, and it warms up a little, I may build a 5.19 kernel.
> Thing is, by the time I get around to rebooting, nvidia may have updated
> and the new one I already got will work. :/
About 15 years ago, after a bad experience with ATI dropping Linux
driver support for a card that was only a year old (and no luck
getting the open source driver to work reliably), I switched to NVidia
(mostly Qaudro cards -- fanless until that ceased to be an
option). They always worked great using the NVidia blob drivers, but
using NVidia drivers was a constant source of minor pain. Often kernel
updates had to be postponed until NVidia driver support caught up, and
they too dropped support and forced me to replace a board that was
still working perfectly.
Eventually, I just gave up and started using built-in Intel
graphics. Life was much easier. A high-end gamer probably wouldn't be
happy, but my mid-range mainboard happily drove three decent-sized
displays (two DVI and one DP) at their native resolutions. I find the
same to be true on my newer AMD system with built-in Radeon Vega
graphics. It too "just works" with the in-kernel-tree support and
open-source Xorg drivers.
I did have to give up the option of having multiple X11 screens. The
proprietary NVidia driver supported multiple screens, but the drivers
for built-in Intel and Radeon drivers don't seem to.
--
Grant
next prev parent reply other threads:[~2022-11-21 16:11 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
2022-11-21 16:11 ` Grant Edwards [this message]
2022-11-21 16:27 ` [gentoo-user] " 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='tlg7v1$h5b$1@ciao.gmane.io' \
--to=grant.b.edwards@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