From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0E439158020 for ; Mon, 21 Nov 2022 16:58:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 500C0E09D9; Mon, 21 Nov 2022 16:58:52 +0000 (UTC) Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0CF0AE09CF for ; Mon, 21 Nov 2022 16:58:51 +0000 (UTC) Received: by mail-lj1-x22c.google.com with SMTP id a15so15161832ljb.7 for ; Mon, 21 Nov 2022 08:58:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ZbP4Lfm6JGibJNLIrKMU4T6GzOJYpK0XgQZWWoHDfXQ=; b=Skoolq5pSS2S7dhREFPe2rUO5hWrDVRg8RXP+d3UP257Yfd5c1jzpHmm+qveQ7pd0F pMfUtekJ2VedZZ1U9SFOW/Irn7zhGfcPVyBQ6ry0FKHlf4sI3OMTQtrbfmX448a9BUQP wTaRrbDVBjYWsV8sC/hN0hMKTTbU3O+dK6/Ig5CC+itLMSeWBccrHJYV9Ef4706rZ1pL 6MUx5pao5P1jx3l9lg67UBA9SqwobToxHxaL5SNrjCvfsKoDSC7vm3/iuo2JZhJcNbo0 ga43kF755mNNeYBIUaWAH9gOHOV3ZfUHiKoLMckrUbZVcQTs9CmqVCVHkYInjYZGY6C5 R1hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZbP4Lfm6JGibJNLIrKMU4T6GzOJYpK0XgQZWWoHDfXQ=; b=5YDPPV/epJJykQvMmhGBv0GcRpKqLkArzcNZper/si3D7AJXRQnrvz0Vmmcu1xBjTv CUYtVaulFfTPN3Zz8FtlONnEgyNaRp1BXzjrfRqFP64kBD5+YLRElFIOTcHkSmSmI/44 HeI8x9nJWmUbWQnYn220rEbG7odRTE7DMEG4ei+HR3S1ATZYb1bK3nnyU5pIqp+uzmyf eXQpn3H17ByhKNX/hZZiLJ9UrCt6K+PyvgdvukwqG9JSzHCCHsBcbNZOM2iLx4NtKmSa YHelWMYmA+p8m2mQ5LHyavfW89tJdgh+7/f874LQjd/dOHcaFc9jbljVe/AT4maNGnTy 1OKg== X-Gm-Message-State: ANoB5pnWEQEInOtIeV5NtmjoHXroDe4wBrT/zpRM1+KXQRt17oOb6vIr AcR4BouETCOxcr1CO//SVXTmkuVwasif6/0cZdtZEvQD X-Google-Smtp-Source: AA0mqf7mZs42NWWVxV43GBY9yQO99TQnWR4Pb/h456ucGn2EkPh7Y69osDOnKsWk92qBSsocnRsnnBkmQ1cakvWgs9Q= X-Received: by 2002:a2e:be8a:0:b0:26f:c081:9aed with SMTP id a10-20020a2ebe8a000000b0026fc0819aedmr6009568ljr.222.1669049929942; Mon, 21 Nov 2022 08:58:49 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3418bb3d-f939-6606-7e19-5e883c198208@gmail.com> <2446bc27-6406-dbe6-0076-ab01d49413c5@gmail.com> In-Reply-To: From: Mark Knecht Date: Mon, 21 Nov 2022 09:58:38 -0700 Message-ID: Subject: Re: [gentoo-user] Re: Upgrading from 5.14 to 6.0 version To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="0000000000002fcc9205edfdf8e6" X-Archives-Salt: 62dd6a0c-1714-408a-bb60-89f939f04c04 X-Archives-Hash: ee2b627dfb1ab52db5f13e75434f3445 --0000000000002fcc9205edfdf8e6 Content-Type: text/plain; charset="UTF-8" On Mon, Nov 21, 2022 at 9:11 AM Grant Edwards wrote: > > 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. The "waiting to catch up issue" is the reason I switched to the LTS kernels. If the kernel got a minor bump the NVidia drivers still worked. When a new LTS kernel came out NVidia would have a new driver almost immediately and through the life of that LTS kernel I got easy kernel updates and easy NVidia driver updates. I don't personally remember NVidia ever dropping a card totally but I did get confused for awhile when they started segmenting their drivers by different families and it was up to me to figure out which driver package handled my card. - Mark --0000000000002fcc9205edfdf8e6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Nov 21, 2022 at 9:11 AM Grant Edwards <= grant.b.edwards@gmail.com&= gt; wrote:
>
> =C2=A0They always worked great using the NVidia = blob drivers, but
> using NVidia drivers was a constant source of min= or pain. Often kernel
> updates had to be postponed until NVidia driv= er support caught up, and
> they too dropped support and forced me to= replace a board that was
> still working perfectly.

The = "waiting to catch up issue" is the reason I switched to the LTS
kernels. If the kernel got a minor bump the NVidia drivers still w= orked.

When a new LTS kernel came out NVidia would= have a new driver
almost immediately and through the life of tha= t LTS kernel I got
easy kernel updates and easy NVidia driver upd= ates.

I don't personally remember NVidia ever = dropping a card totally
but I did get confused for awhile when th= ey started segmenting their
drivers by different families and it = was up to me to figure out which
driver package handled my card.<= /div>

- Mark
--0000000000002fcc9205edfdf8e6--