3

I tried using hooking my laptop up to an external display through HDMI and now the built in audio does not work. I can still get audio through the audio jack. pavucontrol shows that audio should be playing through the built in speakers. I have tried reinstalling ALSA but that didn't work. My computer recognizes my soundcard, but still nothing plays. I tried updating drivers and got this error

W:Skipping acquire of configured file 'universe/binary-i386/Packages' as repository 'http://miktex.org/download/ubuntu bionic InRelease' doesn't support architecture 'i386', E:The repository 'http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu bionic Release' does not have a Release file.

I have a Razer Blade 2017 with Ubuntu 18.04 installed. Any suggestions?

edit: I dual boot with Windows 10 and the audio works fine there.

edit: I have found a non ideal solution. If I put my laptop into suspend and then log back in, audio works fine. Still have no idea what the root of the problem is though.

Mathias W.
  • 51
  • 1
  • 7

3 Answers3

0

I had a similar issue. Twice. I tried everything. Read every thread. Uninstalled/reinstalled everything.

I don't remember what exactly fixed the problem, but it was either one or a combination of these simple things:

  1. Plugged the laptop back into the HDMI port, and then unplugged it.
  2. System settings > Sound > Choose the correct output (e.g. "Speakers - Built-in Audio").
0

About

Razer is using Realtek based sound chips (with extensions for their "THX" stuff). They update the publicly available driver/CODEC software for linux was 2018...

It can be fixed by running some custom script shared by some hardworking and intelligent folks over at Kernel.org Bugzilla worked their magic and released a script that restores sound.

First analyze the card number and device number for the analog sound from the following command

ehsaan@ehsaan:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC298 Analog [ALC298 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

As you see, card number for the analog sound is 1 and device is 0 in mine case. So sound file name for speakers will be hwC1D0

Download, Update file name and Execute

Set script to run on system start automatically

  • first give permission to execute
sudo chmod +x RB14_2023_enable_internal_speakers_ver2.sh
  • create service file
sudo nano /etc/systemd/system/sound_driver_update.service
  • content of service file, Update file path as per yours in ExecStart
[Unit]
Description=patch for sound driver                                        
After=network.target

[Service] ExecStart=/home/username/sound_driver_update.sh Restart=always

[Install] WantedBy=multi-user.target

  • reload daemon and enable service
sudo systemctl daemon-reload
sudo systemctl enable sound_driver_update.service
-1

I dual boot windows as well, and just solved it on my machine twice.

The issue seems to arise when switching from Win10 back to Ubuntu.

For me simply entering BIOS fixed the problem both times. I did NOT change any settings, but when I booted back into Ubuntu the audio was working again.

Hope this helps!

edit:

Just as a note. My issue was that my built-in audio (my laptop's speaker) was not working. So according to your responses, it might be a different issue.