No sound

Raynec

I've installed the latest solus for about more than months, nothing really goes wrong except my poor level in Linux. Until one day, I forgot to charge my laptop and it dies. After I charged it and restarted it, it doesn't have emit sound anymore when I play videos on YouTube. However, it works when I plot my headset.
I understand that there are a lot of existent post where shares a similar situation, but I found each of them slightly different: my soundcard is enabled (I found a post on here, where is something like enable or disabled soundcard, I couldn't find it), I F6-ed alsamixer and it tell me that there are two soundcards, I switched, and nothing changes.
My laptop is Pixelbook Go (Really rare machine, I understand) and I sincerely hope someone can understand my poor English while helping me to fix the issue.

Axios

Raynec With your headphones unplugged run this from terminal and post ouput

pactl info

TraceyC

In order to help, we need to know what desktop environment you have installed.

Also, please clarify which audio devices are working and which are not working.
It sounds like you hear sound through your headset, but not through the laptop speakers. Do I understand correctly?

Raynec

TraceyC
Hello,
Yes, I hear the sound through headset, but not laptop speakers.
Desktop environment... I doesn't remember I've changed that, so it should be Budgie. 10.9.2 to be exact
About audio devices: I don't have a lot of audio devices at my hand, so the only info I can provide is that I hear nothing from the speaker but I can hear through plugging in my headset through 3.5 mm headphone jack.
Thank you for helping me!

qk4-li3

Go to Budgie Control Centre > Sound. How are things there?
Make sure that:

System Volume is a) full on (100%) b) NOT muted c) Over-Amplification is OFF.
System Sounds are a) full on (100%) b) NOT muted
a) Your output device(s) (speakers, headphones, hdmi, other digital... etc.) can be found in the Output Devices drop-down-menu. b) Balance is at the center c) Output Devices should automatically change from your speakers- device to headphones- device when you plug your headphones in, and vice versa. d) You push the Test button next to Output Devices drop- down list and test the speakers.
If part 3.c fails, you can have malfunctioning physical switch inside the 3.5mm jack, due to dirt, oxidation and or excessive wear and use. First aid is try plug in and out few times, if it doesn't help, wiggling also, but carefully, it's not intended to be twisted, and twisting the socket itself can contribute the switch not working properly.
Tell us how all this went, please.

Raynec

qk4-li3 Hello and sorry for replying late! I went through the set-up 1, 2 and 3b. 3a is where the things get different. It gives only one option 'Dummy Output' when I did not plug my headset in. When it is plugged in, it changes from 'Dummy Output' to 'Headphones - Built-in Audio'. I guess that means 3c works. 3d works well with my headphone, it has sound.
I had the same error when this laptop was originally booted with Zorin OS, if that helps. I chose to boot another system (Now Solus) rather fixing that.
How can I fix that?

qk4-li3

Raynec Hey, you followed my procedure, that's awesome!
Ok, switch is working, that's good.
One more thing comes to mind and I must ask: You (or someone else) haven't by chance or accidentally turned the sound device off or mute from BIOS/UEFI or from any possible hardware switch? Is there such possibility?
If not, then Dummy Output indicates... trouble, and that you may be out of luck. Since you mentioned this Pixelbook Go is rare, it could be that Linux don't have all firmware and drivers for it.
On the other hand the headphones are functioning, so I wonder what's going on here really. But the switch is functioning, that's for sure.
Dummy Output tells us that Solus can't detect your sound card's speaker- device, that is 100% true too.
Solus devs are busy people but I'd hope they would chime in on this. It's basically Hardware compatibility issue, I think. If I'm not totally wrong, that is.

Ahoy, Solus developers! Is Pixelbook Go 100% compatible with Solus?

Raynec

qk4-li3 hmmmmm I don't think so, is there a way that I could check BIOS/UEFI?
It's really weird, the speaker used to be working, and it malfunctioned after my laptop has shut down as out of battery, which is the first time that I've ever accidentally let it happened.

Raynec

Axios
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 308
Tile Size: 65472
User Name: raynec
Host Name: raynec-atlas-solus
Server Name: PulseAudio (on PipeWire 1.4.2)
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: cbfe:091a

qk4-li3

Raynec I'm sure there's some method to getting into BIOS/UEFI, but let's not go there. Let's forget that at least for now, because I just wanted to make sure that you haven't already been tinkering there turning off stuff, but obviously you haven't. So that's out.

From pictures of pixelbook I can see there's mute- button, upper row, fourth button from right. You're aware of this, yes? It is not pressed?

Also, Axios here seems to have more professional approach of troubleshooting computer problems so let's wait what this person has to say about the output of pactl info.
My (very little) educated guess is that, where it says default sink and default source, there shouldn't be device_null, instead there should be something indicating your default speakers.
edit. *device_null, I meant auto_null, or something... _null

Axios

Raynec Any time you have a low drop out voltage anything can happen
especially if hardware isnt designed good.
Its something thats hard to control so thats why things go through a fresh startup routine
but its not always perfect.

Try ( pactl list sinks) from terminal and lets see what it says.

Axios

qk4-li3 Ahhhhh its all good (we all learn from it) cool to think of button my mom and dad always got extra buttons pushed on keyboards (Drove me crazy) so it never hurts to check that stuff.

I dont think those two things are correct either never like seeing the word (auto).
From what I understand Auto_null is prob related to the Dummy output.

Raynec

qk4-li3 Function keys doesn't work in Linux (At least in my experiences), so I edited them as keyboard shortcuts. Shouldn't affect much.
I am sure that I'm even less educated than you, so I couldn't understand your paragraph ;( But anyway, thank you!

Raynec

Axios This is after 'pactl list sinks':
Sink #274
State: SUSPENDED
Name: auto_null
Description: Dummy Output
Driver: PipeWire
Sample Specification: float32le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 4294967295
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: auto_null.monitor
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
node.name = "auto_null"
device.description = "Dummy Output"
audio.rate = "48000"
audio.channels = "2"
audio.position = "FL,FR"
media.class = "Audio/Sink"
factory.name = "support.null-audio-sink"
node.virtual = "true"
monitor.channel-volumes = "true"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "38"
node.driver = "true"
port.group = "stream.0"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "95"
object.serial = "274"
Formats:
pcm

As as stocc mentioned, 'inxi -A':
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

stocc

Also inxi -A

stocc

Raynec HD Audio driver: snd_soc_avs

I did a search on the snd_soc_avs driver and it seems that a few people have had issues with this on different distributions. The fix looks like they blacklist the driver. I'm not sure how this is done with Solus, but it may be worth testing if someone is able to help with instructions. I think sudo modprobe -r snd_soc_avs will temporarily remove it. I'm not sure though whether the device will pick up another driver dynamically. I think driver snd_hda_intel should work.

Axios

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

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.

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.