No sound from speakers, Toughbook CF-19, Mint 18.3

[RomeoHotelOneTwo]

I'm running Mint 18.3 on my Panasonic Toughbook CF-19 and I currently have no sound from my speaker but the headphone jack does work. I'm not sure when the sound stopped but I know it has worked previously. I've been banging my head against the wall for two days researching with no luck. According to alsamixer nothing is muted. I've tried some other suggestions from research with no glory.


Thx,
RH-12

[MrEen]

Hi RH-12, and welcome to the forum.

Please post the output of the following terminal commands: inxi -Fxz and aplay -l

Also, start a song or video and while it is running get the output of pacmd list-sinks and include that output as well. Please do that while trying to get sound from the speakers, not with the headphones plugged in.

Thanks.

[RomeoHotelOneTwo]

Hi MrEen,

Thanks for the welcome and the willingness to help, I appreciate it very much. I have a couple other issues to solve with this thing but for now the no sound is driving me nuts. All results of the inquiries are without headphones plugged in:

Results of inxi -Fxz:

System: Host: romeohotelonetwo-CF-19ADUC01M Kernel: 4.15.0-55-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.3 Sylvia
Machine: System: Panasonic product: CF-19ADUC01M v: 005
Mobo: Panasonic model: CF19-5 v: 1
Bios: American Megatrends v: V5.00L12 date: 06/16/2011
CPU: Dual core Intel Core i5-2520M (-HT-MCP-) cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9977
clock speeds: max: 3200 MHz 1: 1408 MHz 2: 1383 MHz 3: 1496 MHz
4: 1345 MHz
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
bus-ID: 00:02.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1024x768@59.98hz
GLX Renderer: Mesa DRI Intel Sandybridge Mobile
GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes
Audio: Card Intel 6 Series/C200 Series Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.15.0-55-generic
Network: Card-1: Intel 82579LM Gigabit Network Connection (Lewisville)
driver: e1000e v: 3.2.6-k port: e080 bus-ID: 00:19.0
IF: enp0s25 state: down mac: <filter>
Card-2: Intel Centrino Advanced-N 6205 [Taylor Peak]
driver: iwlwifi bus-ID: 09:00.0
IF: wlp9s0 state: up mac: <filter>
Drives: HDD Total Size: 320.1GB (65.4% used)
ID-1: /dev/mmcblk0 model: N/A size: 32.0GB
ID-2: /dev/sda model: Hitachi_HTS72323 size: 320.1GB
Partition: ID-1: / size: 286G used: 188G (70%) fs: ext4 dev: /dev/dm-1
ID-2: /boot size: 472M used: 336M (75%) fs: ext2 dev: /dev/sda1
ID-3: swap-1 size: 8.47GB used: 0.00GB (0%) fs: swap dev: /dev/dm-2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 59.0C mobo: 59.0C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 234 Uptime: 1:43 Memory: 1641.2/7863.0MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35

Results of aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0

Results of pacmd list-sinks

1 sink(s) available.
* index: 0
name: <alsa_output.pci-0000_00_1b.0.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: RUNNING
suspend cause:
priority: 9959
volume: front-left: 62260 / 95% / -1.34 dB, front-right: 62260 / 95% / -1.34 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 24.49 ms
max request: 4 KiB
max rewind: 64 KiB
monitor source: 0
sample spec: s16le 2ch 48000Hz
channel map: front-left,front-right
Stereo
used by: 1
linked by: 1
configured latency: 25.00 ms; range is 0.50 .. 341.33 ms
card: 0 <alsa_card.pci-0000_00_1b.0>
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC269VB Analog"
alsa.id = "ALC269VB Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf7d28000 irq 30"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1b.0"
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1c20"
device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC269VB"
alsa.components = "HDA:10ec0269,10f70400,00100100 HDA:14f12c06,10f70000,00100000"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: <analog-output-speaker>

[MrEen]

Here's the issue:

Code: Select all

analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: unknown)

Solving these is a pain. I don't mind helping as much as it takes, but it is possible (I wouldn't say likely) it will all be in vain.

The last toughbook user I tried to help found that when rebooting with headphones plugged in, then pulling the jack out after the system was up and running, they got sound from one speaker and really crappy sound at that. They disappeared before we resolved anything..

I'm going to take a shot that this fix might work for you. If it doesn't, it's easy to undo:

1. In the terminal enter apt install dkms
2. Download this file: https://code.launchpad.net/~ubuntu-audi ... .1_all.deb
3. Assuming your downloads go to your Downloads folder, in the terminal enter cd Downloads followed by sudo dpkg -i oem-audio-hda-daily-lts-xenial-dkms_0.201904020820~ubuntu16.04.1_all.deb
4. Watch the terminal while that is installing. I am hoping it finishes, but you may get a build directive error. If it completes, reboot then test your sound.

Good luck.

[RomeoHotelOneTwo]

Here's the issue:

Code: Select all

analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: unknown)

Solving these is a pain. I don't mind helping as much as it takes, but it is possible (I wouldn't say likely) it will all be in vain.

The last toughbook user I tried to help found that when rebooting with headphones plugged in, then pulling the jack out after the system was up and running, they got sound from one speaker and really crappy sound at that. They disappeared before we resolved anything..

I'm going to take a shot that this fix might work for you. If it doesn't, it's easy to undo:

1. In the terminal enter apt install dkms
2. Download this file: https://code.launchpad.net/~ubuntu-audi ... .1_all.deb
3. Assuming your downloads go to your Downloads folder, in the terminal enter cd Downloads followed by sudo dpkg -i oem-audio-hda-daily-lts-xenial-dkms_0.201904020820~ubuntu16.04.1_all.deb
4. Watch the terminal while that is installing. I am hoping it finishes, but you may get a build directive error. If it completes, reboot then test your sound.

Good luck.

MrEen,

Sadly, I am reporting no glory but as long as you are willing to pull teeth, so am I. Here is the result of your instructions:

Selecting previously unselected package oem-audio-hda-daily-lts-xenial-dkms.
(Reading database ... 349634 files and directories currently installed.)
Preparing to unpack oem-audio-hda-daily-lts-xenial-dkms_0.201904020820~ubuntu16.04.1_all.deb ...
Unpacking oem-audio-hda-daily-lts-xenial-dkms (0.201904020820~ubuntu16.04.1) ...
Setting up oem-audio-hda-daily-lts-xenial-dkms (0.201904020820~ubuntu16.04.1) ...
Loading new oem-audio-hda-daily-lts-xenial-0.201904020820~ubuntu16.04.1 DKMS files...
First Installation: checking all kernels...
Building only for 4.15.0-55-generic
Building for architecture amd64
Building initial module for 4.15.0-55-generic
Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.
Done.

Thanks,
RH-12

[MrEen]

I was afraid of that. It was built with 4.4 kernel so will only work with a kernel from that series. Before going nuts changing to that kernel series let's try some other things.

In the terminal enter cd ~/ followed by wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash alsa-info.sh

That's going to give us huge amount of info that might point us in the right direction. The script will let you upload the results or save locally. I'd prefer you select to upload then paste the URL it gives you here.

If you'd like to keep a copy on your machine as well, you can run it again with just bash alsa-info.sh and it'll save a copy in /tmp that you can then move elsewhere.

[RomeoHotelOneTwo]

I was afraid of that. It was built with 4.4 kernel so will only work with a kernel from that series. Before going nuts changing to that kernel series let's try some other things.

In the terminal enter cd ~/ followed by wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash alsa-info.sh

That's going to give us huge amount of info that might point us in the right direction. The script will let you upload the results or save locally. I'd prefer you select to upload then paste the URL it gives you here.

If you'd like to keep a copy on your machine as well, you can run it again with just bash alsa-info.sh and it'll save a copy in /tmp that you can then move elsewhere.

The results it gave me are:

Your ALSA information is located at http://alsa-project.org/db/?f=ebeec2843 ... b774e3df03

Please inform the person helping you.

[MrEen]

I'm getting tired and don't want to make mistakes, but here's the issue as I see it:

Code: Select all

Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Speaker Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x00010014: OUT EAPD Detect
  EAPD 0x2: EAPD
  Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
    Conn = ATAPI, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c 0x0d*

I think what we'll need to try is to retask the Speaker pin. To do that, install alsa-tools-gui then run hdajackretask. Make sure Select codec in the upper left shows Realtek ALC269VB.
Now click on Show unconnected pins then click the Override box for pin 0x14 and change it to Not connected, then click the Override box for a different unconnected pin and see if Internal speaker is available. If so, choose it, click Apply now, then test the sound. If no good, change that pin back to not connected and try another. If you find one that works, click on Install boot override then reboot and confirm it's still working.

Hope I explained that well enough. Good luck.

[RomeoHotelOneTwo]

I'm getting tired and don't want to make mistakes, but here's the issue as I see it:

Code: Select all

Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Speaker Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x00010014: OUT EAPD Detect
  EAPD 0x2: EAPD
  Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
    Conn = ATAPI, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c 0x0d*

I think what we'll need to try is to retask the Speaker pin. To do that, install alsa-tools-gui then run hdajackretask. Make sure Select codec in the upper left shows Realtek ALC269VB.
Now click on Show unconnected pins then click the Override box for pin 0x14 and change it to Not connected, then click the Override box for a different unconnected pin and see if Internal speaker is available. If so, choose it, click Apply now, then test the sound. If no good, change that pin back to not connected and try another. If you find one that works, click on Install boot override then reboot and confirm it's still working.

Hope I explained that well enough. Good luck.

You explained it quite well, thank you very much. I followed your instructions and did an Override on 0x14 changing it to "Not Connected" then changed 0x17 to "Internal Speaker". Tested the sound and it worked. From there I did the Install Boot Override and rebooted the machine. After reboot completed, I checked the sound again but it did not work. Not sure if this was the result you were hoping for but it at least tells me that there is nothing physically wrong with the speaker, its all in the brains.

Hope you have a good rest,
RH-12

[MrEen]

Okay, an unusual result.

Run hdajackretask again, just click on Apply now and test. It's possible you might have to do this after each boot, but if it works, it's something.

[RomeoHotelOneTwo]

Okay, an unusual result.

Run hdajackretask again, just click on Apply now and test. It's possible you might have to do this after each boot, but if it works, it's something.

Well, what you suggested did not work so I unchecked 0x17, changed 0x14 back to Internal Speaker, and hit Apply. Tested sound with nothing. Changed 0x14 to Not Connected, 0x17 to Internal Speaker, hit Apply then tested, and I had sound again. Will hold on anything else til I hear back from you.

[MrEen]

I'm not sure what is going wrong. I guess try Install boot override again and see what happens. I honestly don't know if you should hit Remove boot override first.

Play around with it a bit and see what you can find. Remove boot override should always bring you back to where you started before ever running hdajackretask.

[RomeoHotelOneTwo]

I'm not sure what is going wrong. I guess try Install boot override again and see what happens. I honestly don't know if you should hit Remove boot override first.

Play around with it a bit and see what you can find. Remove boot override should always bring you back to where you started before ever running hdajackretask.

Did the Remove Boot Override and reset the system back to what is was. Looking down through the list of available jacks I have the following listed as Not Connected:

• 0x17 (already tried this one

• 0x1a

• 0x1b

• 0x1d

• 0x1e

Do you think I should try each of those to see what the result is? I dont mind trying and failing but I dont want to jack something up worse than it already is either.

[MrEen]

Yeah, play with it! Like I said, the worst you can really do is stuff it up until removing the boot override again.

I should also mention. check alsamixer for mutes after rebooting as well after you've made changes. I somewhat doubt it'll make a difference, but just want to be sure.

I believe the worst case scenario right now is upon each boot you use hdajackretask to change 0x14 to 0x17 and click Apply now, then just close hdajackretask and compute away. Doing this means not bothering to install the boot override. I know it would be preferable to get one of them working properly.

[MrEen]

Oops. I finally got around to reading the full output from the script and just saw this:

Code: Select all

!!User specific config file (~/.asoundrc)

pcm.ARDOP{
type rate
slave{
pcm "hw:1,0"
rate 48000
}
}

Rename that file (~/.asoundrc) to anything else while testing to make sure it's not interfering.

[RomeoHotelOneTwo]

Oops. I finally got around to reading the full output from the script and just saw this:

Code: Select all

!!User specific config file (~/.asoundrc)

pcm.ARDOP{
type rate
slave{
pcm "hw:1,0"
rate 48000
}
}

Rename that file (~/.asoundrc) to anything else while testing to make sure it's not interfering.

Hmmmm ... I remember this file, it is related to amateur radio but my searches are coming up blank.

[MrEen]

It's probably not an issue, but I just want to be certain. I noticed the hw:1,0 which your system hasn't been reporting since we began. you only have hw:0

[RomeoHotelOneTwo]

It's probably not an issue, but I just want to be certain. I noticed the hw:1,0 which your system hasn't been reporting since we began. you only have hw:0

Any suggestion on how to locate the file? I ran a few searches but couldn't locate it.

[MrEen]

I did find one more oddity right near the bottom of the file from the dmesg section:

Code: Select all

[   39.436477] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[   39.438315] dell_smbios: Unable to run on non-Dell system
[   39.476509] snd_hda_codec_realtek hdaudioC0D0: Failed to find dell wmi symbol dell_micmute_led_set

Dunno why that stuff is there. I could understand if there'd been a change to alsa-base.conf with some Dell config but there hasn't been and I don't think that asoundrc content could cause it.

Ahh, that just put a thought into my head. Paste the output of ls -la /etc/modprobe.d please. There could be other conf files causing issues.

Ahh what timing. The .asoundrc file is in your home directory. In the file manager click on View > Show hidden files.

[RomeoHotelOneTwo]

I did find one more oddity right near the bottom of the file from the dmesg section:

Code: Select all

[   39.436477] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[   39.438315] dell_smbios: Unable to run on non-Dell system
[   39.476509] snd_hda_codec_realtek hdaudioC0D0: Failed to find dell wmi symbol dell_micmute_led_set

Dunno why that stuff is there. I could understand if there'd been a change to alsa-base.conf with some Dell config but there hasn't been and I don't think that asoundrc content could cause it.

Ahh, that just put a thought into my head. Paste the output of ls -la /etc/modprobe.d please. There could be other conf files causing issues.

Ahh what timing. The .asoundrc file is in your home directory. In the file manager click on View > Show hidden files.

Here is the output of ls -la /etc/modprobe.d

total 76
drwxr-xr-x 2 root root 4096 Aug 1 11:54 .
drwxrwxr-x 159 root root 12288 Jul 31 14:10 ..
-rw-r--r-- 1 root root 2507 Jul 30 2015 alsa-base.conf
-rw-r--r-- 1 root root 325 Mar 13 2016 blacklist-ath_pci.conf
-rw-r--r-- 1 root root 1667 Nov 12 2018 blacklist.conf
-rw-r--r-- 1 root root 210 Mar 13 2016 blacklist-firewire.conf
-rw-r--r-- 1 root root 697 Mar 13 2016 blacklist-framebuffer.conf
-rw-r--r-- 1 root root 156 Jul 30 2015 blacklist-modem.conf
lrwxrwxrwx 1 root root 41 Dec 21 2017 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r-- 1 root root 583 Mar 13 2016 blacklist-rare-network.conf
-rw-r--r-- 1 root root 1077 Mar 13 2016 blacklist-watchdog.conf
-rw-r--r-- 1 root root 127 Mar 11 2015 dkms.conf
-rw-r--r-- 1 root root 390 Apr 12 2016 fbdev-blacklist.conf
-rw-r--r-- 1 root root 154 Jul 27 2017 intel-microcode-blacklist.conf
-rw-r--r-- 1 root root 347 Mar 13 2016 iwlwifi.conf
-rw-r--r-- 1 root root 104 Mar 13 2016 mlx4.conf
-rw-r--r-- 1 root root 49 May 15 11:17 vmware-fuse.conf
-rw-r--r-- 1 root root 30 Mar 3 2016 vmwgfx-fbdev.conf

Still can't find asoundrc. I'm looking in the Home folder and the hidden files are showing but its not there. In fact, I did a search of all files in the File Manager and it turned up nothing.