Hi all
New guy from northern Norway here. I just signed up to the forum today.
Here the other day I went for Zorin on my aging HP 13-4080 laptop. The installation went smooth, except for one thing, no audio, neither on the internal speakers nor on external via jack interface. In the "settings" menu, there are no audio devices to choose apart from "dummy output"
According to the transcript below from my terminal window, it seems like the OS is aware there is an audio device present, so why does it not show up as an option to pick in "settings"?
Being completely new to Linux, I probably ask some stupid questions, so please bear with me.
Hi and welcome. I'm sure users with similar hardware on here have managed to resolve the issue by installing pulse audio's volume control.
Open a Terminal (just type terminal in the menu search bar then launch with enter key) and enter:
sudo apt install pavucontrol
When you enter a command with root (administrator) privileges (sudo) you wilk be prompted for your user password to elevate you to 'root'.
Once installed open it and see if you can get sound working.
(You may want to download the unofficial manual for Zorin 17 that I wrote from here:
Thank you, but I have already tried out PulseAudio volume control, to no avail I'm afraid.
PulseAudio control panel shows no hardware devices available, see screenshot.
Hit [F6] to see if your soundcard is listed.
Are speaker and headphone output channels showing. If you see MM that means channel is muted. Move cursor to that channel and hit "M" to unmute, then "up-arrow" to increase volume.
Maybe post screenshot of your alsamixer here:
Does selecting Sound Card "default 0" do anything?
FYI. I have been doing websearches using searchterm "HP 13-4080 bradwell-U sound dummy output Ubuntu 22.04" but I have yet to see any solution posted by others. I will come back if I do find something to help you. Zab
No, selecting "default 0" does not do anything.
The puzzling thing is that the OS seems to be aware of the sound card, se picture f2, system information
Yes, I've started searching myself as per your advice. Thank you for pointing me in the right direction.
It seems like this is a common problem, so I have hope that someone may have found a solution or a workaround.
I've seen posts about same soundcard, and the common approach to solve it is to use this command:
sudo alsa force-reload
There are additional potential solutions listed here:
The other issue is that ALSA is picking up HDMI in your audio card details and so Pulse Audio will be stuck deciding which card to use. To prevent this you need to create a sound.blacklist.conf - refer to my tutorial on how to do this:
Yes, " sudo alsa force-reload" did the trick!
How do I make it load at start up?
I tried an adaptation of MikeG247's advice to write a line into "modules"
To automatically run the alsa force-reload command at boot time, you can create a script and add it to the startup applications. Here’s how you can do it:
Create a Script : Write a script that includes the alsa force-reload command. For example, you can create a file named alsa_reload.sh with the following content:
Make the Script Executable : Ensure the script is executable by running chmod +x /path/to/alsa_reload.sh .
Add to Startup Applications : Add the script to your startup applications. You can do this by opening the Startup Applications Preferences and adding a new entry with the path to your script.
Alternatively, you can add the script to the rc.local file if you are using a version of Ubuntu that still uses this method for startup scripts. Edit the /etc/rc.local file and add the following line before the exit 0 command:
/path/to/alsa_reload.sh
Ensure you replace /path/to/alsa_reload.sh with the actual path to your script.
Some users have reported that simply being a member of the audio group can resolve the issue without needing to run the alsa force-reload command. You can add your user to the audio group with the following command:
sudo usermod -aG audio your_username
Replace your_username with your actual username. After adding yourself to the group, log out and log back in for the changes to take effect.
Then I tried a shot in the dark, to open the file, simply by typing "open alsa_reload.sh. And lo and behold, the file opened up, allowing me to paste in ```
#!/bin/bash
echo "Forcing Alsa to Reload Modules"
sudo alsa force-reload
echo "Completed."
``
before saving and closing the file.
Next step was to make the script executable:
chmod +x /home/dag/alsa_reload.sh
Final step, adding the script to the startup applications, may be where I goofed up?
sudo nano /etc/modules
Ah, there is a GUI for launching startup programs! I was not aware of that (blush). How very nifty.
Still no joy, though.
I have deleted all the clutter I added to nano /etc/modules too.
I have noticed that I am prompted for a password every time I use a sudo command.
Could it be that I have to add my password in somewhere in the startup program?
