No Audio and failure to shutdown on Manjaro Xfce

Support
,
20

First off, I do need some of those tools - like NRF Connect.

The last time I was able to use my machine before it broke, end of December 2023, it all worked flawlessly. Just now after the updates it broke in that manner. The machine’s display broke, which led to me being unable to use it for months until I did Boardrepair on the PCB. I have removed the watchdog for now, and will see if rebooting still works.

Mesa should be there due to WINE, as i tried WINE/Proton quite some time ago.

My session shouldn’t be using gnome or MESA, no. I just removed gnome and some other stuff. I am going to reboot now to see what happens.

21

Reboot didn’t change anything. still no reboot without issue, still no sound. Did remove snap.

pactl info:

Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 67
Tile Size: 65472
User Name: actwo
Host Name: actwo
Server Name: PulseAudio (on PipeWire 1.0.3)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: auto_null
Default Source: auto_null.monitor
Cookie: 0e64:5309

journal:
https://0x0.st/XoF0.txt

status wireplumber:

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-04-23 09:39:03 CEST; 3min 41s ago
   Main PID: 833 (wireplumber)
      Tasks: 7 (limit: 38076)
     Memory: 14.5M (peak: 15.0M)
        CPU: 99ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─833 /usr/bin/wireplumber

Apr 23 09:39:03 actwo systemd[747]: Started Multimedia Service Session Manager.
Apr 23 09:39:03 actwo wireplumber[833]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Apr 23 09:39:03 actwo wireplumber[833]: [0:00:16.748285160] [833] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Apr 23 09:39:03 actwo wireplumber[833]: [0:00:16.748299371] [833] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Apr 23 09:39:03 actwo wireplumber[833]: [0:00:16.748322923] [833]  INFO Camera camera_manager.cpp:284 libcamera v0.2.0

systemctl --user status pipewire*:

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
     Active: active (running) since Tue 2024-04-23 09:39:03 CEST; 4min 36s ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 834 (pipewire-pulse)
      Tasks: 3 (limit: 38076)
     Memory: 7.7M (peak: 8.4M)
        CPU: 42ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─834 /usr/bin/pipewire-pulse

Apr 23 09:39:03 actwo systemd[747]: Started PipeWire PulseAudio.

● pipewire-pulse.socket - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
     Active: active (running) since Tue 2024-04-23 09:39:02 CEST; 4min 37s ago
   Triggers: ● pipewire-pulse.service
     Listen: /run/user/1000/pulse/native (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

Apr 23 09:39:02 actwo systemd[747]: Listening on PipeWire PulseAudio.

● pipewire.socket - PipeWire Multimedia System Sockets
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Active: active (running) since Tue 2024-04-23 09:39:02 CEST; 4min 37s ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
             /run/user/1000/pipewire-0-manager (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Apr 23 09:39:02 actwo systemd[747]: Listening on PipeWire Multimedia System Sockets.

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
     Active: active (running) since Tue 2024-04-23 09:39:03 CEST; 4min 36s ago
TriggeredBy: ● pipewire.socket
   Main PID: 829 (pipewire)
      Tasks: 4 (limit: 38076)
     Memory: 10.3M (peak: 11.3M)
        CPU: 38ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─829 /usr/bin/pipewire

Apr 23 09:39:03 actwo systemd[747]: Started PipeWire Multimedia Service.

Any suggestions?

22

If there is no sound in PulseAudio or PipeWire replacement service, issue is probably in ALSA

I suggest check ALSA configuration

sudo alsa-info.sh --upload
23

http://alsa-project.org/db/?f=06bc12aa20cf5666a5357c67e8e7925f9634d0d9

24

Update: as soon as I run “sudo update-grub” the audio works, until the next reboot.
This is after I added snd_hda_intel.dmic_detect=0 to GRUB_CMDLINE_LINUX_DEFAULT=“” in /etc/default/grub.

The system also shuts down without issues after doing this.

How do I get it to persist now? Any advice?

25

ALSA data shows no soundcards detected

!!Soundcards recognised by ALSA
!!-----------------------------

--- no soundcards ---


!!Aplay/Arecord output
!!--------------------

APLAY

aplay: device_list:279: no soundcards found...

ARECORD

arecord: device_list:279: no soundcards found...

Section !!Amixer output is empty - consistent with previous error “Invalid card number ‘0’”

Section !!All Loaded Modules does not include alternate drivers snd_soc_skl or snd_sof_pci_intel_cnl

If ALSA is not working, PulseAudio/PipeWire can use Bluetooth devices for audio playback
But if no Bluetooth devices are available PulseAudio/PipeWire creates Dummy Output auto_null

26

So, right now it does work with bluetooth, but what am I supposed to do now?

SOF is already installed, so what should I do besides removing that GRUB Entry?

27

Remove snd_hda_intel.dmic_detect=0 from /etc/default/grub
Update GRUB - sudo update-grub
Reboot system

If audio is not working as expected check ALSA configuration sudo alsa-info.sh --upload

28

After rebooting, the machine was hung up at boot, so I had to powerkill it. Next reboot went well.

Here’s the ALSA dump:
http://alsa-project.org/db/?f=bde9a68ec3e91cbf890cee81aae69812807bb522

29

ALSA data shows a modprobe option for snd_hda_intel driver

!!Modprobe options (Sound related)
!!--------------------------------

snd_hda_intel: model=generic

If modprobe option has been added to /etc/default/grub remove it, update GRUB and reboot

If modprobe option is in a .conf file in folder /etc/modprobe.d/ remove it and reboot

After reboot check ALSA configuration sudo alsa-info.sh --upload

30

In /etc/modprobe.d/ there are two files, alsa-base.conf and blacklist-watchdog.conf. Should I remove one of them?
I do not remember adding anything else to /etc/default/grub.

Edit:
Sorry, I just now understood what you wrote. alsa-base.conf contains only

options snd-hda-intel model=generic

while blacklist-watchdog.conf contains only

blacklist iTCO_wdt

What should I do now?

31

Regarding /etc/modprobe.d/blacklist-watchdog.conf - this is likely a file you have added yourself in order to disable watchdog (for whatever reason). Beyond that, I can’t say whether it is directly connected to the current issue(s).

32

alsa-base.conf contains options snd-hda-intel model=generic

sudo rm /etc/modprobe.d/alsa-base.conf

Reboot

sudo alsa-info.sh --upload

1 Like
33

Alright, on poweroff and startup the pc hung up, I had to powerkill it again, jus tso you know.

Here’s the new link:
http://alsa-project.org/db/?f=e9f68829065b3a5486efe952f6e919d790b147d0

34

on poweroff and startup the pc hung up, I had to powerkill it again

If my system has a large number of updates installed (1.5-2 GB) it may take a long time (15-25 minutes) to clear old packages and settings before shutting down. From past experience I learned that system will continue to take a long time to shutdown if it is powered off during shutdown

For Audio issue: No changes in ALSA data. No soundcards recognised. No sof-firmware audio modules loaded

I suggest reinstall sof-firmware

pamac reinstall sof-firmware

and shutdown system

shutdown

When system is restarted, check if audio playback devices are detected in ALSA

aplay -l

If no playback devices are shown try re-initialising ALSA devices

sudo alsactl init

For shutdown issue post more information from journal

journalctl -b -1 | tail -n100 | curl -F 'file=@-' https://0x0.st
35

Yesterday I already left it on shutdown for at least 3 hours, probably more. It was a lot of updates (around 10GB), but that should still have been enough, shouldn’t it have been?

I will try that again later, but I kinda doubt it will help. When the audio worked (always just for one powercycle) the machine also had no issues shutting down and starting up…

36

By the way, here is a picture of the screen on shutdown

IMG_7092
IMG_70921008×756 310 KB

IMG_6983
IMG_69831008×756 316 KB

37

@nikgnomic any Ideas on this?

38

aplay -l finds no soundcards, alsactl init doesn’t improve this sadly.

Here is the journal link:
https://0x0.st/XXOZ.txt

39

I suggest boot system from a live ISO and check ALSA configuration

If there are no soundcards detected on live ISO it is likely a hardware failure

1 Like