~Toughbooktalk~

Azrial wrote:

kode-niner wrote:Have you looked at volume and mute settings with pavucontrol? Also look into alsamixer. In the latter, you may need to type F6 and select the proper hardware for all the volume sliders to appear.

Pavucontrol is set to 100% and not muted.

I have no program called alsamixer when I search in the Dash.

You'd need to type alsamixer in the terminal.

It's also part of the alsa-utils package which might not be installed by default in bt5

Ok, that was helpful, but confuseing. When I brought up the alsamixer control in terminal. It was set to "default." I selected my Intel sound card.

I then made sure that nothing was muted, but found that what made the difference was when I raised the volume and made sure my headphone jack was un-muted! I guess that this version of Ubuntu has the headphones and speakers confused.

Now, lets see if it holds these settings through a re-start!

Damn, it resets every time I reboot and I have no sound until I return to alsamixer and un-mute the headphones, even though I am listening on the built in speakers.

I wonder if the settings for speaker and headphones are confused in this version of Ubuntu and because there is no headphone plugged in, it automatically mutes?

This seems a common problem on the Ubuntu boards.

try Also check for an auto-mute-mode setting in the mixer that should be disabled.

kode-niner wrote:try

Code: Select all

sudo alsactl store

Did not work, still was muited on start-up

kode-niner wrote:Also check for an auto-mute-mode setting in the mixer that should be disabled.

I could not find this setting.

From terminal:
Unmute headphone (M toggles mute)
Up-arrow to 100%

Temporary fix.

From here: http://www.linuxquestions.org/questions ... ost5290879

I'm still working on it.

Reading above I see you have tried this. Sorry for the duplication.

I deleted pulse audio through synaptic then re-installed through terminal: All new packages referred to Xenial Xerus.

I think we are looking for a config file.

FWIW

Azrial wrote:

kode-niner wrote:try

Code: Select all

sudo alsactl store

Did not work, still was muited on start-up

kode-niner wrote:Also check for an auto-mute-mode setting in the mixer that should be disabled.

I could not find this setting.

When in alsamixer use right arrow. There's more there than meets the eye.

Sadlmkr wrote:

Azrial wrote:

kode-niner wrote:try

Code: Select all

sudo alsactl store

Did not work, still was muited on start-up

kode-niner wrote:Also check for an auto-mute-mode setting in the mixer that should be disabled.

I could not find this setting.

When in alsamixer use right arrow. There's more there than meets the eye.

Thanks, I found this link, which explains it all. But while I can get sound now, I can not keep it. Everytime I reboot I lose it and much change the settings again in Alsamixer.

Better then no sound, I guess.

I've had swapped or misidentified channels before. I don't remember specifically which ones and I don't think it involved a channel that auto-muted itself. What I do remember is that it sorted itself out after a few upgrades.

In your case, it would be possible to issue a command with amixer. Then you could run the command automatically on startup or when you login.

It would looke like
I'd have to play around to figure it out, but the aim would be to unmute the proper channel on the specified card.