public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel 6.0 upgrade broke sound to TV over HDMI
Date: Sat, 26 Nov 2022 05:10:52 -0500	[thread overview]
Message-ID: <CAGfcS_mxj0wZ8Hd6YAZ0RFVGQv_g=EY35XqixDwYXZ_U5dHN2w@mail.gmail.com> (raw)
In-Reply-To: <ddc1f175-477f-6c2c-7d0b-f6242b0e94c2@gmail.com>

On Fri, Nov 25, 2022 at 11:40 PM Dale <rdalek1967@gmail.com> wrote:
>
> I found a new version of the nvidia-drivers.  I figured it might work
> with the new 6.0 kernel so I tested it.  Sure enough, it compiled and
> installed.

And this is why compiling isn't evidence that something works.  :)

What nvidia driver version are you using?

Also, why are you using it at all?  The proprietary drivers their pros
and cons.  The issues you're running into are one of the well-known
cons - if you want to run stable kernels, they'll be occasionally
breaking, and if you run mainline kernels they'll break all the time.

If you're going to run out-of-tree kernels you should almost certainly
stick to longterm kernels.

Usually people use the proprietary drivers for gaming,
high-performance 3D graphics in general, or CUDA (AI, video encoding,
etc).  If you aren't doing one of those then I suspect the
linux-supplied drivers will just work and shouldn't ever break.  You
can run stable kernels all you want with those.

-- 
Rich


      parent reply	other threads:[~2022-11-26 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26  4:40 [gentoo-user] Kernel 6.0 upgrade broke sound to TV over HDMI Dale
2022-11-26  9:23 ` Arve Barsnes
2022-11-26 10:10 ` Rich Freeman [this message]

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='CAGfcS_mxj0wZ8Hd6YAZ0RFVGQv_g=EY35XqixDwYXZ_U5dHN2w@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --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