unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Marco Menne" via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Blacklist Nouveau permanentely and no sound hda-intel
Date: Tue, 28 Sep 2021 20:46:23 +0000	[thread overview]
Message-ID: <561dcfe8efc9702eac31f463a60a0639@mailbox.org> (raw)

Hello together, this is my first post in your mailing list.

I searched a lot in the net but did'nt find an useful answer for Guix system.
I know to blacklist the nouveau graphics driver on boot but how can I blacklist it permanentely?
My second question is about the hda-intel sound driver. 
I have hda-intel and nvidia-hdmi sound modules. On Slackware I cloud blacklist the Nvidia driver and could get the intel driver working.
But as in Guix system there is no /etc/modprobe.d/ folder I don't know how to get my sound working.

cat /proc/asound/card*/codec* | grep Codec
Codec: Nvidia GPU 84 HDMI/DP

sudo dmesg | grep -i snd_hda_intel
[ 29.243097] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[ 29.243111] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 29.243171] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 29.243267] snd_hda_intel 0000:01:00.1: Disabling MSI
[ 29.243270] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[ 29.725366] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])

lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)

Any advice would be great.
--
Mameka

             reply	other threads:[~2021-09-29 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 20:46 Marco Menne via [this message]
2021-09-29 13:02 ` Blacklist Nouveau permanentely and no sound hda-intel Tobias Geerinckx-Rice
2021-09-29 14:44 ` Marco Menne

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=561dcfe8efc9702eac31f463a60a0639@mailbox.org \
    --to=help-guix@gnu.org \
    --cc=marco.menne@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).