No sound

qk4-li3

Very interesting, if I understand this right: "correct" sound driver is present and loaded as intended, but this "correct" driver happens to be broken! Thanks to Intel, according to this post: https://bkhome.org/news/202502/intel-sound-avs-driver-still-too-immature.html

I think @stocc hit nail in the head.

I would encourage you @Raynec first try what happens with sudo modprobe -r snd_soc_avs (to see if then older, not-broken driver snd_hda_intel loads automatically as replacement, without further commands, as @stocc suggested)
I don't have experience blacklisting drivers, but in given situation I would try to figure it out, if I were you. It seems that's the only working solution at the moment (from what I've read).
But I think it's easier to test that sudo modprobe -r snd_soc_avs first.

Axios

Raynec I am just curious if you install pavucontrol and under config
if stuff shows up properly and can be set properly.

Raynec

First, pavucontrol and under config: I see two built-in audio and both of them have three profile, which is same: Pro HiFi quality music (unplugged) (unavaliable), Pro Audio, and Off. [the (unplugged) is shown, not labelled by me. I changed to choose Pro Audio.]
Then, sudo modprobe -r snd_soc_avs: Nothing changed, still no sound from speaker. Even worse, I lost the sound from the headphone. Seems that the not-broken driver did not load automatically.
P.S. after sudo modprobe -r snd_soc_avs, config in pavucontrol showed nothing. I guess that means the broken driver has been removed.
P.P.S. I've tried sudo modprobe snd_hda_intel and I assumed that it has been loaded. Still no sound from both speaker and headphones.

stocc

Raynec Did you run inxi -A after running sudo modprobe snd_hda_intel to see if it had been picked up as the driver? Perhaps it isn't picked up until a reboot, but that would require blacklisting the snd_soc_avs module.

To blacklist the module it looks as though you need to:
sudo su mkdir /etc/modprobe.d echo "blacklist snd_soc_avs >> /etc/modprobe.d/sound.conf
then reboot.
Once rebooted issue inxi -A to see whether the Intel Sunrise Point-LP HD Audio has picked up a new driver.
If not, try sudo modprobe snd_hda_intel and check inxi -A again.

If none of this helps, remove the /etc/modprobe.d/sound.conf file and reboot. That should at least get your headphones back working. Other than that, I'm not sure what else to suggest.

Axios

Raynec After you changed to pro audio did you try audio before doing
the modprobe?
I am just trying to eliminate an issue by doing this.
Just to comment if you are playing music and change pavucontrol those settings change on the fly.

qk4-li3

stocc Is there a typo: echo "blacklist snd_soc_avs >> /etc/modprobe.d/sound.conf
shouldn't there be second quotation mark somewhere?

Raynec

Nope, it doesn't pick up anything after '-r' command:
Audio:
Device-1: Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging
Unit driver: ipu3-imgu
Device-2: Intel CSI-2 Host driver: ipu3-cio2
Device-3: Intel Sunrise Point-LP HD Audio driver: N/A
API: ALSA v: k6.14.6-319.current status: kernel-api
Server-1: PipeWire v: 1.4.2 status: active

It said N/A even after sudo modprobe snd_soc_avs.
Also, after rebooting, I saw that it picked up the wrong one again. However, when I was testing for audio from headset, it gives nothing.
Also, I tried rm ~/etc/modprobe.d/sound.conf. It gives this:
rm: cannot remove '/etc/modprobe.d/sound.conf': No such file or directory
Living without a speaker? I'm fine, I'm not a big fan of speaker, and I'm thankful that the model comes with a 3.5mm headphone jack, which is really rare nowadays...

Raynec

P.S. this is what I get after rebooting:
Audio:
Device-1: Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging
Unit driver: ipu3-imgu
Device-2: Intel CSI-2 Host driver: ipu3-cio2
Device-3: Intel Sunrise Point-LP HD Audio driver: snd_soc_avs
API: ALSA v: k6.14.6-319.current status: kernel-api
Server-1: PipeWire v: 1.4.2 status: active

It picked the wrong one up.

stocc

qk4-li3 Yes, correct. It should be echo "blacklist snd_soc_avs" >> /etc/modprobe.d/sound.conf. Well spotted! @Raynec, please note my error as spotted by @qk4-li3. Please try the steps again.

Raynec

stocc Oops
bash: /etc/modprobe.d/sound.conf: Permission denied

I run that, and the terminal changed from raynec@ ~$ to >. And I paste the command again. It showed up this.
Also, suggested by Axios , how to un-suspend then?

Axios

DUH was right in front of me and I didnt see it but dont know what to do about it
musta happen some strange sleep or hibernat crap when power got low.
Makes sense.

Anybody see what I do and has a fix let us know
Going go out on a limb and say driver is ok.
It was even in bold Letters..lol

Appears to me two states can cause that turning OFF and SUSPEND. (NOT 100% SURE) in reference to the Dummy ouput
Un suspend I think it should work.

stocc

Raynec You need to be in sudo mode to add that, so sudo echo "blacklist snd_soc_avs" >>/etc/modprobe.d/sound.conf. Again, reboot after checking that the file exists with that content. If sound still doesn't work after rebooting then delete that file (using sudo privileges). The Suspended state I also see on my laptop until I use the speakers for the first time. It then changes to Active. I suspect that yours is stuck in Suspended because the driver isn't working properly.

Raynec

stocc I think I don't have the snd_hda_intel driver as I inxi -A ed after command and reboot:
Audio:
Device-1: Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging
Unit driver: ipu3-imgu
Device-2: Intel CSI-2 Host driver: ipu3-cio2
Device-3: Intel Sunrise Point-LP HD Audio driver: N/A
API: ALSA v: k6.14.6-319.current status: kernel-api
Server-1: PipeWire v: 1.4.2 status: active

No driver loaded.
Edit: Still N/A after sudo modprobe snd_hda_intel.

Axios

Ok yesterday I tested all that stuff thats the way it appeared to me on my machine.
But this morning I tested again and things are not that way and acting different.
Did shutdown last nite.

So since my results for some reason on my machine seem to vary or not be consistent.
I dont want lead down the wrong road.
Going step into the shadows.

stocc

Raynec OK, then you'll need to remove the blacklist configuration (sudo rm /etc/modprobe.d/sound.conf) and reboot. This will get you back to your initial problem, for which I am now out of ideas. Sorry!

Axios

Raynec I am curious if you run (sudo systemctl restart lightdm)
if it does anything for your audio woes.

Raynec

Ok nothing fixed... Can I reinstall the whole thing? I'm fine with that.

Edit: after lsmod | grep snd. I found snd_hda_intel.
snd_soc_hda_codec 24576 2 snd_soc_avs,snd_soc_avs_hdaudio
snd_hda_ext_core 36864 2 snd_soc_avs,snd_soc_hda_codec
snd_hda_intel 61440 0
snd_intel_dspcfg 36864 2 snd_soc_avs,snd_hda_intel
snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg

TraceyC

Raynec Ok nothing fixed... Can I reinstall the whole thing? I'm fine with that.

Well bummer. Before you go through the hassle of reinstalling, I recommend trying your sound out with a live ISO. It's possible that the hardware is the thing that's broken.

If both headphones and speakers work with the live ISO, you know the hardware is good and the current software is the problem.

If the speakers don't work with a live ISO, then the hardware is the problem.

Raynec

TraceyC What does live ISO mean? But anyways, I tried to run Linux Mint (Should I run Solus again? I don’t think the OS matters.) without installing, and, of course, no sound.
So that’s not the software problem? Or I should install Solus again? or anything else.
P.S. Yes, if Solus no longer works, I’m changing to Linux Mint. I’m trying to find the best OS that suits my old laptop.

Axios

Raynec Audio drivers should load from the Live Iso without a problem to test
Live Iso= File you downloaded and burnt to Usb

Did you run the live Iso and did the Audio work properly?
If I understand right you did and no sound (if thats the case its hardware or bios issue on your computer)

You might try this and see what happens with sound.

« Previous Page Next Page »