# Dummy Output

**URL:** <https://www.debian-fr.org/t/dummy-output/90169>\
**Category:** Support Debian\
**Created:** [Juillet 12, 2024, 10:19 UTC](https://www.debian-fr.org/t/dummy-output/90169 "2024-07-12T10:19:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![titouan1](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@titouan1](https://www.debian-fr.org/u/titouan1)\
**Post date:** [Juillet 12, 2024, 10:19 UTC](https://www.debian-fr.org/t/dummy-output/90169/1 "2024-07-12T10:19:53Z")

</div>

Bonjour,

je suis nouveau sur Debian, et je n’y connais pas encore grand chose, et c’est pour cela que je vais sur ce forum pour régler un problème qui est que le son ne marche pas, et le système me marque «&nbsp;Dummy Output&nbsp;» en tant que sortie audio. Pouvez-vous m’aider s’il vous plaît ?

Merci d’avance pour votre réponse !

---

<div class="post-metadata">

**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\
**Post date:** [Juillet 12, 2024, 12:33 UTC](https://www.debian-fr.org/t/dummy-output/90169/2 "2024-07-12T12:33:20Z")

</div>

salut  
il te manque probablement un paquet  
en général tu trouves la réponse dans un fichier de log;  
tu peux essayer  
`sudo dmesg |egrep -i "firmware|error"`

explication :  
sudo : faire uen commande en root ( superutilisateur )  
dmesg : la commande dmesg marque les messages du système  
| : «&nbsp;tube&nbsp;» : prend la sortie ( l’affichage de sudo dmeg qui contient des centaines de ligne et l’envoie vers la suite de la ligne )  
egrep -i : regarde les caractères de chaque ligne ; -i : indépendamment de la casse ; -e regex ( permet d’interpréter le | suivant comme un OU logique )  
«&nbsp;firmware|error&nbsp;» : le mot firmware ou le mot error ( sans le e de egrep, la recherche se ferait sur le mot entier firmware|error

voir là aussi :

> **[SON : plus de son](https://dindoun.lautre.net/spip.php?article59)**
>
> documentations externes solution 1 : le fil solution 2 : controle du son / controleur de volume solution 3 : existence du programme de son (…)

vérifier l’existence du programme de son :  
`ps aux |egrep "pipewire|pulse" |grep -v grep` doit afficher /usr/bin/pipewire et /usr/bin/pipewire-pulse

```auto
user 2152 0.6 0.1 96920 37984 ? S<sl 19:35 1:12 /usr/bin/pipewire
user 2154 0.7 0.1 103980 52444 ? S<Lsl 19:35 1:33 /usr/bin/pipewire-pulse

```

Sinon, installer pipewire pipewire-bin et pipewire-pulse : `apt-get install pipewire pipewire-bin pipewire-pulse`

---

<div class="post-metadata">

**Author:** ![titouan1](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@titouan1](https://www.debian-fr.org/u/titouan1)\
**Post date:** [Juillet 12, 2024, 2:15 UTC](https://www.debian-fr.org/t/dummy-output/90169/3 "2024-07-12T14:15:15Z")

</div>

salut, et merci pour ta réponse !

J’ai effectué la première commande que tu m’a fournie, et voici le résultat :

```auto
$ sudo dmesg |egrep -i « firmware|error »
[1.287990] simple-framebuffer: probe of simple-framebuffer.0 failed with error -16
[2.661626] i915 0000:00:02.0: firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[2.661792] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4)
[4.629698] tpm_tis_spi spi-PRP0001:00: Cr50 firmware version: B2-C:0 RO_A:0.0.12/bf248b9d RW_A:0.5.241/cr50_v4.11_mp.62-2ef05a
[4.649732] elan_i2c i2c-ELAN0000:00: Elan Touchpad: Module ID: 0x00ae, Firmware: 0x0002, Sample: 0x0003, IAP: 0x0000
[4.770507] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[4.770767] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[4.844252] iwlwifi 0000:00:0c.0: firmware: direct-loading firmware iwlwifi-9000-pu-b0-jf-b0-46.ucode
[4.845043] iwlwifi 0000:00:0c.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[4.845082] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[4.845116] iwlwifi 0000:00:0c.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[4.845146] iwlwifi 0000:00:0c.0: loaded firmware version 46.ea3728ee.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[4.867499] gsmi: no gsmi handler in firmware
[5.656835] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[5.712317] bluetooth hci0: firmware: direct-loading firmware intel/ibt-17-16-1.sfi
[5.712334] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[5.712490] Bluetooth: hci0: Firmware Version: 108-45.22
[7.580792] Bluetooth: hci0: Waiting for firmware download to complete
[7.581775] Bluetooth: hci0: Firmware loaded in 1825621 usecs
[7.612882] bluetooth hci0: firmware: direct-loading firmware intel/ibt-17-16-1.ddc
[7.615805] Bluetooth: hci0: Firmware revision 0.1 build 108 week 45 2022
[3639.874469] (NULL device *): firmware: direct-loading firmware regulatory.db
[3639.874496] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[3639.874518] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.ddc
[3639.874906] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.sfi
[3639.875124] (NULL device *): firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[3639.875124] (NULL device *): firmware: direct-loading firmware iwlwifi-9000-pu-b0-jf-b0-46.ucode
[8135.401390] (NULL device *): firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[8135.401650] (NULL device *): firmware: direct-loading firmware regulatory.db
[8135.401801] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[8135.401858] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.ddc
[8135.408581] (NULL device *): firmware: direct-loading firmware iwlwifi-9000-pu-b0-jf-b0-46.ucode
[8135.408899] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.sfi
[8170.243849] (NULL device *): firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[8170.244067] (NULL device *): firmware: direct-loading firmware regulatory.db
[8170.244081] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[8170.244102] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.ddc
[8170.244498] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.sfi
[8170.244742] (NULL device *): firmware: direct-loading firmware iwlwifi-9000-pu-b0-jf-b0-46.ucode
[9207.433507] (NULL device *): firmware: direct-loading firmware i915/glk_dmc_ver1_04.bin
[9207.433700] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[9207.433703] (NULL device *): firmware: direct-loading firmware regulatory.db
[9207.433730] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.ddc
[9207.434131] (NULL device *): firmware: direct-loading firmware intel/ibt-17-16-1.sfi
[9207.434296] (NULL device *): firmware: direct-loading firmware iwlwifi-9000-pu-b0-jf-b0-46.ucode

```

Et pour la deuxième commande, j’ai bien le résultat attendu

---

<div class="post-metadata">

**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\
**Post date:** [Juillet 13, 2024, 3:42 UTC](https://www.debian-fr.org/t/dummy-output/90169/4 "2024-07-13T15:42:59Z")

</div>

je ne vois pas de truc à faire ;  
tu peux essayer ça :

**SOLUTION 1 ( peut être ): installer pleins de pilotes**  
selon que tu es sous bookworm ou autres, aller voir sur ces pages

> **[Programmes à installer deb13 amd64](https://dindoun.lautre.net/spip.php?article563)**
>
> Nouveautés de bookworm 
> 
> sources.list : \`\`\` deb https://deb.debian.org/debian trixie main contrib non-free non-free-firmware deb (…)

> **[Programmes à installer deb12 ( bookworm ) amd64](https://dindoun.lautre.net/spip.php?article483)**
>
> Nouveautés de bookworm 
> 
> sources.list : \`\`\` deb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware deb (…)

> **[Programmes à installer deb10 (buster ) amd64](https://dindoun.lautre.net/spip.php?article330)**
>
> Liste complète pour avoir un ordinateur prêt à tout.
> 
> Il faudra dire oui, parfois interagir avec , , , 
> 
> et si ça s'arrête sur un deux points, taper

et installer les pilotes(drivers) puis redémarrer

ou :  
deb13:  
`apt-get install -y -d broadcom-sta-common firmware-brcm80211 firmware-iwlwifi firmware-linux firmware-linux-free firmware-linux-nonfree firmware-misc-nonfree firmware-ralink linux-headers-amd64 atmel-firmware dahdi-firmware-nonfree firmware-amd-graphics firmware-ast firmware-ath9k-htc firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-free firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc firmware-qlogic firmware-realtek firmware-realtek-rtl8723cs-bt firmware-samsung firmware-siano firmware-sof-signed firmware-ti-connectivity firmware-zd1211 gnome-firmware grub-firmware-qemu nxt-firmware sigrok-firmware-fx2lafw `

deb12  
`apt-get install firmware-brcm80211 firmware-iwlwifi firmware-linux-free firmware-linux-nonfree firmware-misc-nonfree firmware-ralink broadcom-sta-common linux-headers-amd64 alsa-firmware-loaders atmel-firmware bladerf-firmware-fx3 dahdi-firmware-nonfree firmware-amd-graphics firmware-ast firmware-ath9k-htc firmware-atheros firmware-b43-installer firmware-b43legacy-installer firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-free firmware-linux-nonfree firmware-microbit-micropython firmware-microbit-micropython-doc firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc firmware-qlogic firmware-realtek firmware-realtek-rtl8723cs-bt firmware-samsung firmware-siano firmware-sof-signed firmware-ti-connectivity firmware-tomu firmware-zd1211 gnome-firmware grub-firmware-qemu hackrf-firmware hdmi2usb-fx2-firmware isight-firmware-tools midisport-firmware nxt-firmware sigrok-firmware-fx2lafw ubertooth-firmware ubertooth-firmware-source`

mais bon c’est un peu bourrin

**recherche 1**  
installe qjackctl et lance le en ligne de commande : y-a-t-il un message qui apparaît dans la ligne de commande?

**recherche 2**  
`cat /proc/asound/timers`

**recherche 3**  
`for DomBusFun in $(lspci |grep -i audio|sed "s/\ .*//g");do lspci -s "$DomBusFun" -nnvvv;done`

---

<div class="post-metadata">

**Author:** ![titouan1](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@titouan1](https://www.debian-fr.org/u/titouan1)\
**Post date:** [Juillet 13, 2024, 5:45 UTC](https://www.debian-fr.org/t/dummy-output/90169/5 "2024-07-13T17:45:15Z")

</div>

premièrement, j’ai effectué la commande qjackctl -s pour lancer directement depuis le terminal et voici ce qui apparais dans une nouvelle fenêtre :

```auto
19:42:27.158 Réinitialisation des statistiques.

19:42:27.182 Changement des connexions ALSA.

19:42:27.197 JACK démarre…

19:42:27.197 /usr/bin/jackd -dalsa -dhw:0

Cannot connect to server socket err = Aucun fichier ou dossier de ce type

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Cannot connect to server socket err = Aucun fichier ou dossier de ce type

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

19:42:27.209 Changement du graphe des connexions ALSA.

19:42:27.211 JACK a été démarré avec le PID=3689.

Cannot create RT messagebuffer thread: Operation not permitted (1)

Retrying messagebuffer thread without RT scheduling

Messagebuffer not realtime; consider enabling RT scheduling for user

no message buffer overruns

Cannot create RT messagebuffer thread: Operation not permitted (1)

Retrying messagebuffer thread without RT scheduling

Messagebuffer not realtime; consider enabling RT scheduling for user

no message buffer overruns

Cannot create RT messagebuffer thread: Operation not permitted (1)

Retrying messagebuffer thread without RT scheduling

Messagebuffer not realtime; consider enabling RT scheduling for user

no message buffer overruns

jackdmp 1.9.21

Copyright 2001-2005 Paul Davis and others.

Copyright 2004-2016 Grame.

Copyright 2016-2022 Filipe Coelho.

jackdmp comes with ABSOLUTELY NO WARRANTY

This is free software, and you are welcome to redistribute it

under certain conditions; see the file COPYING for details

JACK server starting in realtime mode with priority 10

self-connect-mode is "Don't restrict self connect requests"

audio_reservation_init

Acquire audio card Audio0

creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit

ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode

Released audio card Audio0

audio_reservation_finish

Cannot initialize driver

JackServer::Open failed with -1

Failed to open server

19:42:27.478 JACK a été arrêté

19:42:29.418 Impossible de connecter le serveur JACK comme client. - L'opération a échoué. - Incapable de se connecter au serveur. Veuillez consulter la fenêtre des messages pour plus d'informations.

Cannot connect to server socket err = Aucun fichier ou dossier de ce type

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

```

---

<div class="post-metadata">

**Author:** ![titouan1](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@titouan1](https://www.debian-fr.org/u/titouan1)\
**Post date:** [Juillet 13, 2024, 5:47 UTC](https://www.debian-fr.org/t/dummy-output/90169/6 "2024-07-13T17:47:29Z")

</div>

ensuite, j’ai fait la deuxième commande proposée et ça m’a donné ça :

```auto
$ cat /proc/asound/timers
G0: system timer : 4000.000us (10000000 ticks)
G3: HR timer : 0.001us (1000000000 ticks)
  Client sequencer queue 1 : stopped
P0-3-0: PCM playback 0-3-0 : SLAVE
P0-7-0: PCM playback 0-7-0 : SLAVE
P0-8-0: PCM playback 0-8-0 : SLAVE

```

---

<div class="post-metadata">

**Author:** ![titouan1](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@titouan1](https://www.debian-fr.org/u/titouan1)\
**Post date:** [Juillet 13, 2024, 5:48 UTC](https://www.debian-fr.org/t/dummy-output/90169/7 "2024-07-13T17:48:55Z")

</div>

Et concernant la troisième commande, voici la réponse :

```auto
$ for DomBusFun in $(lspci |grep -i audio|sed "s/\ .*//g");do lspci -s "$DomBusFun" -nnvvv;done
00:0e.0 Multimedia audio controller [0401]: Intel Corporation Celeron/Pentium Silver Processor High Definition Audio [8086:3198] (rev 03)
	DeviceName: Multimedia audio controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 129
	Region 0: Memory at 9111c000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at 91000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_apl

```

---

<div class="post-metadata">

**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\
**Post date:** [Juillet 14, 2024, 2:50 UTC](https://www.debian-fr.org/t/dummy-output/90169/8 "2024-07-14T14:50:42Z")

</div>

jack s’est lancé?

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Octobre 2, 2024, 8:31 UTC](https://www.debian-fr.org/t/dummy-output/90169/9 "2024-10-02T20:31:46Z")

</div>

Ce sujet peut être fermé.  
Voir suite: [Bug de son / HP chromebook x360 14b-ca0](https://www.debian-fr.org/t/bug-de-son-hp-chromebook-x360-14b-ca0/90401)
