MX Linux Forum

Posted: **Tue Dec 20, 2022 6:47 pm**

Hi all,

I'm in a spin of MX-KDE with AHS support (provided very helpfully by dolphinoracle) and all has been well until recently when i lost sound output through the speakers in my laptop.

I can still get sound via BT, and in Windows all sound functions are okay.

Someone in another thread lost all sound and video, and a Konsole check that all updates had been properly installed with "sudo dpkg --configure -a
". I have tried this and found no difference.

This is a dump of system info:

Code: Select all

Snapshot created on: 20220924_1429
System:    Kernel: 6.0.0-4mx-amd64 [6.0.8-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.2.1_KDE__ahs_kernel_x64 Wildflower September 24  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: XPS 17 9720 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Dell model: 0KNF8J v: A00 serial: <filter> UEFI: Dell v: 1.12.0 date: 10/05/2022 
Battery:   ID-1: BAT0 charge: 91.3 Wh (100.0%) condition: 91.3/95.1 Wh (96.0%) volts: 13.1 
           min: 11.4 model: BYD DELL F8CPG24 type: Li-poly serial: <filter> status: Full 
CPU:       Info: 10-Core model: 12th Gen Intel Core i7-12700H bits: 64 type: MT MCP 
           arch: Alder Lake family: 6 model-id: 9A (154) stepping: 3 microcode: 423 cache: 
           L2: 24 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 107520 
           Speed: 609 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 609 2: 2700 3: 2700 4: 2700 
           5: 2700 6: 2700 7: 2700 8: 2700 9: 640 10: 2700 11: 803 12: 754 13: 2700 14: 2700 
           15: 747 16: 2700 17: 837 18: 804 19: 1229 20: 2700 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:46a6 class-ID: 0300 
           Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: N/A alternate: nvidia 
           bus-ID: 01:00.0 chip-ID: 10de:2520 class-ID: 0300 
           Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 
           chip-ID: 0c45:6732 class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5") 
           s-diag: 1165mm (45.9") 
           Monitor-1: DP-2-3 res: 3840x2160 hz: 60 dpi: 138 size: 708x399mm (27.9x15.7") 
           diag: 813mm (32") 
           OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Dell 
           driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel,snd_sof_pci_intel_tgl 
           bus-ID: 00:1f.3 chip-ID: 8086:51c8 class-ID: 0401 
           Device-2: NVIDIA driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:228e 
           class-ID: 0403 
           Sound Server-1: ALSA v: k6.0.0-4mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl 
           port: 4000 bus-ID: 00:14.3 chip-ID: 8086:51f0 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 
           bus-ID: 6-1.4:4 chip-ID: 0bda:8153 class-ID: 0000 serial: <filter> 
           IF: eth0 state: down mac: <filter> 
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-10:8 chip-ID: 8087:0033 
           class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 2.75 TiB used: 45.93 GiB (1.6%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Western Digital 
           model: PC SN810 NVMe WDC 1024GB size: 953.87 GiB block-size: physical: 512 B 
           logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 61520012 
           temp: 32.9 C scheme: GPT 
           ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Gigabyte model: GP-AG42TB size: 1.82 TiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: EGFM15.0 temp: 40.9 C scheme: GPT 
Partition: ID-1: / raw-size: 705.44 GiB size: 693.3 GiB (98.28%) used: 45.93 GiB (6.6%) fs: ext4 
           dev: /dev/nvme1n1p2 maj-min: 259:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 278 KiB (0.1%) fs: vfat 
           dev: /dev/nvme1n1p1 maj-min: 259:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme1n1p3 maj-min: 259:3 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2612 note: see --pkg apt: 2592 lib: 1529 flatpak: 20 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 360 Uptime: 1h 3m wakeups: 7 Memory: 31.05 GiB used: 4.19 GiB (13.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

I don't often use the sound form the laptop speakers, but I sometimes plug in earbuds.

I'd appreciate any and all help with resolving this issue.

Posted: **Tue Dec 20, 2022 6:52 pm**

Code: Select all

echo 'options snd-intel-dspcfg dsp_driver=1' | sudo tee /etc/modprobe.d/sound.conf

Code: Select all

echo 'options snd-hda-intel model=dell enable=yes' | sudo tee /etc/modprobe.d/sound2.conf

Reboot.

Posted: **Tue Dec 20, 2022 10:17 pm**

Thanks for the suggestion. I tried it and sound comes through the speakers that are part of my external monitor. The laptop speakers remain silent, when I disconnect the monitor.

There are times when I am away from my monitor and would like to get some sound. Is there some modification to either of the 2 sound config files that I can make so that I can include the laptop speakers as an output device?

I have found the file pc-speaker.conf. In it there is the entry "blacklist pcspkr" - would commenting that out let me use the laptop speakers for sound?

I'll try it. I did. Nothing worked: I tried all permutations I could think of in pc-speaker.conf to no avail. I have returned the file to it's non-fiddled-with condition.

Posted: **Wed Dec 21, 2022 3:44 am**

Have you tried Alsamixer from menu?

After you open it: F6 and select "0 Intel" (rather than "default") then press F5 , now play with the bars. Any item may be even at max, still muted. Under the bars: MM means muted , 00 : unmuted. M from keyboard mutes/unmutes.

Posted: **Wed Dec 21, 2022 7:16 pm**

Thanks for your further suggestion - I appreciate it. I'm sorry to take so long to reply: time zone difference here in Australia.

I tried Alsamixer several times, and again no success. Checked for muted items - I fell for that on my previous installation (older laptop) and was looking out for it.

I'm sure the laptop speakers were working when I first installed.

EDIT: it's quite likely the speakers didn't work from installI just booted up with my live MX-KDE-AHS thumbdrive, and after installing the drivers, found that the speakers were marked as "unavailable". This didn't stop music coming through my earbuds that I plugged-in.

Posted: **Wed Dec 21, 2022 7:20 pm**

Code: Select all

rm -r ~/.config/pulse

Reboot (or Logout, Login ) will reset Pulseaudio settings to defaults.

Posted: **Wed Dec 21, 2022 10:51 pm**

Thanks, I'll try this reset next:

Huckleberry Finn wrote: Wed Dec 21, 2022 7:20 pm
Code: Select all
rm -r ~/.config/pulse
Reboot (or Logout, Login ) will reset Pulseaudio settings to defaults.

Posted: **Thu Dec 22, 2022 3:17 pm**

Probably that won't work, too, however you can still do it, no harm .

The main problem is that it's the same everywhere with that device: 8086:51c8 (all distros, even the bleeding edge ones). And the weird thing is that sometimes it's ok with (say) kernel 5.15-38 and not with 5.15-43 then ok with 5.19.xx then not with 6.0.x ...

And (actually) the real problem is (as always) driver: sof-audio-pci-intel-tgl

So, what we did with the 1st command was to make it use the (traditional/classic) snd_hda_intel instead.

Whatever... we may be very close to the solution:

Could you just copy-paste here the "Chip" line from Alsamixer ? (Top-left corner)

i.e.

Chip: Realtek ALC298

or

Chip: Realtek ALC1220

or whatever.

Posted: **Thu Dec 22, 2022 5:51 pm**

Hi, H-F,

the contents of "Chip": PulseAudio
"Card" is also PulseAudio

I was considering moving to Pipewire purely because in my MX-19-KDE on a previous laptop, the audio became somewhat problematic towards the end.

Might this be worth trying, and attempting to fix that if it misbehaves.

Also, I'm on Kernel 6.0; I could always roll back to an earlier kernel if you feel it's worth a try. I take it I just have to uninstall via the Package Manager?

Posted: **Thu Dec 22, 2022 8:24 pm**

Let's delete the file we created first:

Code: Select all

sudo rm /etc/modprobe.d/sound.conf

Reboot.

(Now it should return to sof driver.)

Does it now show anything different in Alsamixer? (Chip and any others)

You don't have to uninstall the 6.0. You can (if you like) install any kernel (say 5.15) then boot with it via "Advanced Options" on Grub. Furthermore, yours is currently 6.0.0-4, you can even check the 6.0 and install (which will install at the moment linux-image-6.0.0-6mx-amd64-unsigned_6.0.12-1) and try the sound.

In the meantime, it may be solved by the upcoming 6.1 (without requiring workarounds...)

Pipewire ... you can try of course, but it won't take Pulseaudio's place. (At this point @AVLinux may give better info :) ). Also, distros like Fedora, Garuda (and many bleeding edge ones) have both Pipewire and kernel 6.0 ootb, still same problem there with the same card. (You can even try them on live session if you like).

The reason why I asked the Chip no: We used model=dell as the option (which's generic and works on most Dells). This way we can try a more model-specific option.

Posted: **Thu Dec 22, 2022 10:51 pm**

Huckleberry Finn wrote: Thu Dec 22, 2022 8:24 pm Let's delete the file we created first:
Code: Select all
sudo rm /etc/modprobe.d/sound.conf
Reboot.

(Now it should return to sof driver.)

Done, and yes sof has returned. Speakers are now being detected, though no sound is coming from them. I checked to make sure nothing was muted.

Does it now show anything different in Alsamixer? (Chip and any others)

Yes: Chip = Intel Alderlake-P HDMI
Card= sof-soundwire

You don't have to uninstall the 6.0. You can (if you like) install any kernel (say 5.15) then boot with it via "Advanced Options" on Grub. Furthermore, yours is currently 6.0.0-4, you can even check the 6.0 and install (which will install at the moment linux-image-6.0.0-6mx-amd64-unsigned_6.0.12-1) and try the sound.

I shall, and report back here.

In the meantime, it may be solved by the upcoming 6.1 (without requiring workarounds...)

Pipewire ... you can try of course, but it won't take Pulseaudio's place. (At this point @AVLinux may give better info :) ). Also, distros like Fedora, Garuda (and many bleeding edge ones) have both Pipewire and kernel 6.0 ootb, still same problem there with the same card. (You can even try them on live session if you like).

I understand.

The reason why I asked the Chip no: We used model=dell as the option (which's generic and works on most Dells). This way we can try a more model-specific option.

Got it. I'll follow your lead.

I tried the latest kernel. No change in terms of output. Card and Chip in alsamixer are unchanged.

Posted: **Fri Dec 23, 2022 12:24 am**

Huckleberry Finn wrote: Thu Dec 22, 2022 8:24 pm
Pipewire ... you can try of course, but it won't take Pulseaudio's place. (At this point @AVLinux may give better info :) ). Also, distros like Fedora, Garuda (and many bleeding edge ones) have both Pipewire and kernel 6.0 ootb, still same problem there with the same card. (You can even try them on live session if you like).

Actually I'm pretty ambivalent about PW currently, I've done some testing with the MX Packages and they work as good as you can expect, but for AV Linux and Pro Audio work a properly set up JACK/Pulse system is still to be preferred as there are some latency compensation and synchronization things to still be figured out in Pipewire.. You'd think I'd be forging ahead but I'm an "if it ain't broke then don't fix it" type...

Posted: **Fri Dec 23, 2022 4:34 am**

@Metal Mick Oh, sorry, we forgot something:

It's normal that it shows Chip: Pulseaudio etc.

In both cases you need to first press F6 and select the one that begins with zero: "0 HDA Intel PCH" (or so) (then look at the Chip ).

Also you can post

Code: Select all

aplay -l

(it'll show different outputs with different drivers: sof & snd_hda_intel (before & after the echo command and reboot ... If you don't feel lazy of course :D )

In the meantime, you can remove the previous (unnecessary) kernels with "MX Cleanup" . ('Kernel Removal Tool' below the window, easy to use, just 2 clicks.. for example you can remove the 6...-4 now since you already have a more recent one: -6 )

Posted: **Fri Dec 23, 2022 8:02 am**

Before you try any of the above (when it's still sof driver) , can you try these simply?

Boot with systemd (on Grub select that via 'Advanced Options'), then in a terminal
Code: Select all
```
systemctl --user enable pulseaudio ; systemctl --user start pulseaudio
```
try the sound.

Boot normally (with the default one as always)
- Code: Select all
```
mv .asoundrc .asoundrc.old
```
  This will backup the current file (if there is one)
- Code: Select all
```
tee .asoundrc <<!
defaults.pcm.card 0
defaults.pcm.device 2
defaults.ctl.card 0
!
```
  This will create a new one with these settings.
- Logout, login (or reboot if you don't feel lazy) try the sound (speakers).

P.S. Just a normal terminal (Ctrl+Alt+T) . No root, no sudo or su etc...

P.P.S. Hoping not to be confusing: Normally I need to wait for the aplay -l output (with sof driver). So, I wrote the above just guessing (not to lose time/make you wait due to long timezone difference). (Just the card no may be 1 instead of 0). So, in case that doesn't work, try also:

Code: Select all

tee .asoundrc <<!
defaults.pcm.card 1
defaults.pcm.device 2
defaults.ctl.card 1
!

Reboot.

Posted: **Fri Dec 23, 2022 11:27 pm**

Hi H-F,

I have tried your suggestions, being careful to follow each direction correctly> No sound from the speaker(s).

I was thinking/hoping this might be something that could be quickly resolved, but it seems to be a bit more intractable than I expected.

I am very grateful for all your hard work, and I'd understand if at this time of the year, you find you have family matters of more pressing importance, and you wish to put this on the backburner for a while. I won't be tearing my hair out if you do.

On the other hand, if you want to keep going I'm certainly going to be here as often as I can, following directions.

Posted: **Sat Dec 24, 2022 4:56 am**

I was really hopeful about the .asoundrc (that it would do it).

The only good thing is that it's not completely dead , you have sound. (In the meantime, if there's no sound from the headphones, too we could simply try another option model=... That would also be good, cause for example I use an old "radio-cassette player" as an amplifier : from headphones to that ... (though there's no problem with the speakers etc.) Whatever, in fact there are many things to try. Just: I know that we are very close to the solution ... )

Normally (just loudly thinking) we would install the latest sof firmware, however it's already 2.2.2 on AHS (MX KDE is also AHS) .. 2.2.3 and 2.3 will be available soon (hopefully).

The only thing you need to remember: Just try to use the most recent kernel as possible as they appear in "MX Package Installer" .. so, have a check whenever you remember.. 6.1.x (or higher later)

So, if you don't feel lazy, let's make it sure for the last time: Ctrl+Alt+T :

First let's delete all files we created (though the 1st one was already deleted):
Code: Select all
```
sudo rm /etc/modprobe.d/sound*.conf
```
Code: Select all
```
rm .asoundrc
```
Reboot.

Code: Select all
```
aplay -l
```
(Let's see what it shows)

Just while you're at it: Alsamixer: press F6 , select the one that begins with 0 , now let's see what it shows for the chip

Now,
Code: Select all
```
echo 'options snd-intel-dspcfg dsp_driver=1' | sudo tee /etc/modprobe.d/sound.conf
```
Reboot.

Repeat steps 2 and 3 (shortly, post the outputs in both cases..)

Posted: **Sun Dec 25, 2022 10:51 pm**

Hi H-F,

sorry to take so long to reply, but it was Christmas day in Australia yesterday, Boxing Day shopping this morning.

Files deleted, and rebooted.

The results of aplay -l:

Code: Select all

**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 12: HDMI 6 [HDMI 6]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofsoundwire [sof-soundwire], device 0: Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofsoundwire [sof-soundwire], device 31: Jack Out DeepBuffer (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

In Alsamixer, selecting option 0 of F6, has Card: HDA Nvidia; Chip: Nvidia GPU 9f HDMI/DP

Followed through to the end of your instructions and rebooting. I'll add the results of your final instructions in a short while.

After reboot

results of aplay -l:

Code: Select all

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 12: HDMI 6 [HDMI 6]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 13: HDMI 7 [HDMI 7]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 14: HDMI 8 [HDMI 8]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 15: HDMI 9 [HDMI 9]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 16: HDMI 10 [HDMI 10]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 17: HDMI 11 [HDMI 11]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 12: HDMI 6 [HDMI 6]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Alsamixer shows HDA Intel PCH for the card, Intel Alderlake-P HDMI for the chip, all for option 0

I hope I've followed your instructions correctly - I presumed that for instructions 2 and 3 you meant those which yielded the results above (aplay -l, and checking back with Alsamixer.

Posted: **Mon Dec 26, 2022 9:16 am**

At least we know our .asoundrc trial above was correct : card 1 device 2 "for speakers":

card 1: sofsoundwire [sof-soundwire], device 2: Speaker (*) []

Oh, I know this is really frustrating, but, could you just do the same for card 1 (option that begins with 1 : probably it looks like: 1 sof-soundwire ) (and look at "chip") ?

Files deleted, and rebooted.
In Alsamixer, selecting option 0 of F6, has Card: HDA Nvidia; Chip: Nvidia GPU 9f HDMI/DP

_______________________

By the way, (once you post the output for chip name) you can try to use it that way: when no (created) files: select sofsoundwire on "MX Select Sound" and/or in Alsamixer and try (in Alsamixer first F6, select 1 sof-soundwire ... then press F5 (for "all") and play with the bars.)

... Then if still nothing:

Code: Select all

tee .asoundrc <<!
defaults.pcm.card 1
defaults.pcm.device 2
defaults.ctl.card 1
!

or

Code: Select all

tee .asoundrc <<!
defaults.pcm.!card sofsoundwire
defaults.pcm.device 2
defaults.ctl.!card sofsoundwire
!

Reboot.

Posted: **Mon Dec 26, 2022 10:11 am**

Forgot to say:

Merry Christmas and a Happy New Year to you and your family,

and to all MXers, antiXers, even all Linuxers (even "Windowsers"

) on this opportunity.

Posted: **Mon Dec 26, 2022 6:08 pm**

Hi H-F,

thank you so much for the wishes re Christmas - that was very kind of you, particularly as you're working your heart out to help me with this.

I am not getting frustrated at all, just curious and interested in what we're doing, and more than a little amazed at the process which I'm sure would not be possible in Windows.

Back to business

In Alsamixer for Soundcard option 1, the card is HDA Nvidia; the chip is Nvidia GPU 9f HDMI/DP - this is not what you were expecting, so I wonder if I have done something wrong, and it makes the instructions that you've added not ones I can follow.

Each time I make an alteration, I try playing a music file and with varying options in Alsamixer and checking in Pulse Audio Control to see if there's any joy.

I am willing to try the samples of code you've embedded though.

Cheers,

Michael P.

Posted: **Tue Dec 27, 2022 7:50 am**

Ok, but, did you make sure there were no conf files before that? This step (or of course you can check/delete manually using the file manager)

Code: Select all

sudo rm /etc/modprobe.d/sound*.conf ; rm .asoundrc

Reboot.

Alsamixer .. F6 .. select 1 ...

________________________________________

(Cause that looks like the output when there is the .conf file (snd_hda_intel in use rather than sof)

card 0: PCH [HDA Intel PCH]

card 1: NVidia [HDA NVidia]

________________________________________

In fact, what we're trying to do is just this: Patches/fixes are being applied in time. Once you know the correct chip name you can try an option (if there is one of course) looking here. ( "pinpoint" )

I.e. On most Dells the problematic one is ALC1220 and the solution (for that one) is to simply create a .conf file (as we did) and use the option: model=clevo-p950 and use sof driver..

Posted: **Tue Dec 27, 2022 11:49 pm**

I didn't check for the existence of any conf files for the sound - I just applied your line of code. Sorry.

This time, I did check through file manager.

Now, I have in Alsamixer:

Card 1 = sof-soundwire; chip = Intel Alderlake-P HDMI
Card 0 = HDA NVidia; Chip = Nvidia GPU 9f HDMI/DP

I know I asked this before, but is it possible that the file pc-speaker.conf could be causing an issue? (And that I tried editing the file without rendering any difference.) The contents of the file are:

# file /etc/modprobe.d/pc-speaker.conf
#
# The line below disables the audible beeping in the console (and
# also in X-windows?) If you want the beeping enabled then
# comment out the line below and then run:
#
# sudo modprobe snd-pcsp

blacklist snd-pcsp
blacklist pcspkr

- I ask because it seems to me "blacklist" seems to have a fair degree of stopping power, although I lack any real knowledge of such things.

Posted: **Wed Dec 28, 2022 7:02 am**

Metal Mick wrote: Tue Dec 27, 2022 11:49 pm... but is it possible that the file pc-speaker.conf could be causing an issue?..

I guess no, cause that one is standard (all of us have it ootb), which's just to prevent that "beep" (not to disable speakers completely).

In the meantime, since you don't have conf files (on sof driver currently) , you can now retry the .asound conf as in post #18

(I also wonder if there is a speaker (also a PCM) bar in Alsamixer now after you press f6 .. select card1 , then press F5 .. You can post a screenshot if you like)

Posted: **Wed Dec 28, 2022 8:03 pm**

It's done.

With the first option from post #18 in effect:
https://drive.google.com/file/d/1LkjjIr ... share_link

With the second option in effect:
https://drive.google.com/file/d/1-kPkG7 ... share_link

- I tried embedding the images in the message, but they wouldn't display - I hope the links work for you, because I adjusted the permissions in Drive. If not I'll put them into Dropbox.

Posted: **Wed Dec 28, 2022 8:07 pm**

Just the links are enough, with the img code tags they're not visible/clickable (in general) (I saw/opened them as if quoting from you :) )

Edit: It's ok now :)

Posted: **Wed Dec 28, 2022 8:17 pm**

Those with MM are "muted" (especially Headphone and Headset that may be useful). You can unmute/mute pressing M from keyboard.

But.. I guess the bars (those and Speaker) aren't able to rise with the arrow (up) key right?

Posted: **Wed Dec 28, 2022 10:12 pm**

Huckleberry Finn wrote: Wed Dec 28, 2022 8:17 pm Those with MM are "muted" ... I guess the bars (those and Speaker) aren't able to rise with the arrow (up) key right?

That's correct. I tried them again, just prior to posting here.

MX Linux Forum

Lost sound through speakers

Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers

Re: Lost sound through speakers