unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mameka <mameka@mailbox.org>
Cc: Mameka <help-guix@gnu.org>
Subject: Re: No sound - Intel HDA SOF driver and Nvidia HDMI
Date: Fri, 29 Oct 2021 11:32:09 +0200	[thread overview]
Message-ID: <20211029093127.lyjb6zg5zedwyjeh@pelzflorian.localdomain> (raw)
In-Reply-To: <20211028162202.eicldzkvxhnavtbe@pelzflorian.localdomain>

You could set a different Linux-libre kernel version in your operating
system declaration, e.g.
(kernel (@ (gnu packages linux) linux-libre-5.10))
or (kernel (@ (gnu packages linux) linux-libre-5.4)).

If you don’t mind recompiling your kernel: Searching in my

/run/current-system/kernel/.config

reveals a few occurrences of HDMI in the kernel configuration.  You
could set in your operating system declaration:

(kernel
 ((@@ (gnu packages linux) make-linux-libre*)
  (@@ (gnu packages linux) linux-libre-5.14-version)
  (@@ (gnu packages linux) linux-libre-5.14-gnu-revision)
  (@@ (gnu packages linux) linux-libre-5.14-source)
  '("x86_64-linux")
  #:configuration-file (@@ (gnu packages linux) kernel-config)
  #:extra-options
  (append
   '(("CONFIG_SND_HDA_INTEL" . #f))
   (@@ (gnu packages linux) %default-extra-linux-options))))

or similar, but this may need to be adapted with future Guix versions.
If it works at all.

Also I suppose you have exactly the same hardware setup as with
Trisquel or Debian.  For example, I remember something advertised as
an HDMI cable but it could not carry sound.

Regards,
Florian


      reply	other threads:[~2021-10-29 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 22:57 No sound - Intel HDA SOF driver and Nvidia HDMI Mameka via
2021-10-25 23:22 ` Mameka
2021-10-28 16:22   ` pelzflorian (Florian Pelz)
2021-10-29  9:32     ` pelzflorian (Florian Pelz) [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211029093127.lyjb6zg5zedwyjeh@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=mameka@mailbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).