No sound

leonard14

New Member
Joined
Jun 20, 2023
Messages
22
Reaction score
1
Credits
162
Hello everyone.
I am new to Linux. I run Kali Purple on hardware.
I run the OS with nomodeset parameter in the kernel boot options since without it the system just would not run and a blank screen shows up.
There is no audio on the computer no matter what it is/what is playing.
I really don't know what is the issue and nothing on the internet works.



Thank you for your help.
 


Try putting into a Terminal
sudo apt install isenkram
then
sudo isenkram-autoinstall-firmware
and try running without nomodeset

Moving to Kali Linux Sub-forum
 
Try putting into a Terminal
sudo apt install isenkram
then
sudo isenkram-autoinstall-firmware
and try running without nomodeset

Moving to Kali Linux Sub-forum
Hello arochester,
Thank you for the help.
I installed isenkram as you mentioned and then run this command: sudo isenkram-autoinstall-firmware

the following text pops up:

info: some kernel driver requested extra firmware files: rtl_bt/rtl8723b_config.bin rtl_bt/rtl8723bs_config.bin rtl_bt/rtl8723ds_config.bin rtl_bt/rtl8723ds_fw.bin rtl_bt/rtl8761a_config.bin
info: unable to find any local firmware info for dist kali-rolling, using info for sid
info: locating packages with the requested firmware files
info: determining whether enabling other components is required
info: No new firmware package with requested firmware detected.
 
Then I don't understand why you have to use nomodeset.
 
i don't have a lot of experience with kali or pipewire (which kali uses for audio), but it is functional in a newly created virtual machine. you could check output of the command lspci -knn | grep -iA3 audio to see if your audio adapter is identified and has a "Kernel driver in use". in my vm the pci bus for the audio adapter was shown to be 00:1b.0 and the driver in use was snd_hda_intel (yours may be different). given those examples, you could check for system journal messages about all of the above with
journalctl -b | grep -iE '00:1b.0|snd|pipe|audio'
(changing 00:1b.0 and/or snd for your pci bus and driver if they are different) to see if there are any errors or warnings. even though my vm audio was functional, there were still some errors and warnings so all of them won't necessarily be fatal or cause your lack of sound.

you could check systemctl status --user 'pipewire*' to see if the services and sockets are active and running. i believe because of the connection between pipewire and pulseaudio (pipewire-pulse maybe?) you can check volume levels with
pactl list | grep -iE 'volume|mute'

that should cover lots of the basics. in case it might be of use, it looks like pipewire also has a process viewer you can start with the command pw-top
 
Hello arochester,
My problem is not that i used nomodeset ( although I am not sure that it's not the problem).
The problem is that i have no sound on the computer.
I use nomodeset because without it the screen would turn off and the system would not boot.

Also, what does isenkram do?
Thanks.
 
i don't have a lot of experience with kali or pipewire (which kali uses for audio), but it is functional in a newly created virtual machine. you could check output of the command lspci -knn | grep -iA3 audio to see if your audio adapter is identified and has a "Kernel driver in use". in my vm the pci bus for the audio adapter was shown to be 00:1b.0 and the driver in use was snd_hda_intel (yours may be different). given those examples, you could check for system journal messages about all of the above with
journalctl -b | grep -iE '00:1b.0|snd|pipe|audio'
(changing 00:1b.0 and/or snd for your pci bus and driver if they are different) to see if there are any errors or warnings. even though my vm audio was functional, there were still some errors and warnings so all of them won't necessarily be fatal or cause your lack of sound.

you could check systemctl status --user 'pipewire*' to see if the services and sockets are active and running. i believe because of the connection between pipewire and pulseaudio (pipewire-pulse maybe?) you can check volume levels with
pactl list | grep -iE 'volume|mute'

that should cover lots of the basics. in case it might be of use, it looks like pipewire also has a process viewer you can start with the command pw-top
Hello z7vl7abxc.
Thank you for reaching out.
As i mentioned in my post, I'm not a Linux expert, therefore I don't understand what some of these commands do and what they show/respond.
Is there anything simpler?

Thanks.
 
Hello z7vl7abxc.
Thank you for reaching out.
As i mentioned in my post, I'm not a Linux expert, therefore I don't understand what some of these commands do and what they show/respond.
Is there anything simpler?

Thanks.
you're welcome. the only simple thing i can think of in your situation would be something i figured you would have already tried, but i'll mention that just in case. this may depend on what desktop environment you installed (i used xfce in my virtual machine), but did you click on the volume icon on the panel or taskbar? sometimes it has an option to open the audio mixer where you could try checking to see if anything is muted or possibly if there is any activity when you play audio.

i'll run a couple of those commands and explain the output a bit:

Code:
lspci -knn | grep -iA3 audio
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
    Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [17aa:2211]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel

lspci lists your system's pci devices. usually audio is handled by a pci device. in order to work, it requires a driver. as you can see in the "Kernel driver in use" line, my audio adapter has one.

in combination with a program called pipewire, pulseaudio is a program that handles some of the audio tasks on the software side. this command uses pulseaudio to check volume levels and to see if anything is muted:

Code:
pactl list | grep -iE 'volume|mute'
    Mute: no
    Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
    Base Volume: 65536 / 100% / 0.00 dB
    Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
    Mute: no
    Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
    Base Volume: 65536 / 100% / 0.00 dB
    Flags: DECIBEL_VOLUME LATENCY
    Mute: no
    Volume: front-left: 20724 /  32% / -30.00 dB,   front-right: 20724 /  32% / -30.00 dB
    Base Volume: 13076 /  20% / -42.00 dB
    Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
    Mute: no
    Volume: front-left: 52016 /  79% / -6.02 dB,   front-right: 52016 /  79% / -6.02 dB
        application.icon_name = "multimedia-volume-control"

basically with that one you would be looking to see if anything was muted or had the volume set to a very low level.
 
Hello arochester,
Thank you for the help.
I installed isenkram as you mentioned and then run this command: sudo isenkram-autoinstall-firmware

the following text pops up:

info: some kernel driver requested extra firmware files: rtl_bt/rtl8723b_config.bin rtl_bt/rtl8723bs_config.bin rtl_bt/rtl8723ds_config.bin rtl_bt/rtl8723ds_fw.bin rtl_bt/rtl8761a_config.bin
info: unable to find any local firmware info for dist kali-rolling, using info for sid
info: locating packages with the requested firmware files
info: determining whether enabling other components is required
info: No new firmware package with requested firmware detected.
Looks like you need to install firmware-realtec which you can get through the Synaptic Package Manager
 
you're welcome. the only simple thing i can think of in your situation would be something i figured you would have already tried, but i'll mention that just in case. this may depend on what desktop environment you installed (i used xfce in my virtual machine), but did you click on the volume icon on the panel or taskbar? sometimes it has an option to open the audio mixer where you could try checking to see if anything is muted or possibly if there is any activity when you play audio.

i'll run a couple of those commands and explain the output a bit:

Code:
lspci -knn | grep -iA3 audio
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
    Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [17aa:2211]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel

lspci lists your system's pci devices. usually audio is handled by a pci device. in order to work, it requires a driver. as you can see in the "Kernel driver in use" line, my audio adapter has one.

in combination with a program called pipewire, pulseaudio is a program that handles some of the audio tasks on the software side. this command uses pulseaudio to check volume levels and to see if anything is muted:

Code:
pactl list | grep -iE 'volume|mute'
    Mute: no
    Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
    Base Volume: 65536 / 100% / 0.00 dB
    Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
    Mute: no
    Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
    Base Volume: 65536 / 100% / 0.00 dB
    Flags: DECIBEL_VOLUME LATENCY
    Mute: no
    Volume: front-left: 20724 /  32% / -30.00 dB,   front-right: 20724 /  32% / -30.00 dB
    Base Volume: 13076 /  20% / -42.00 dB
    Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
    Mute: no
    Volume: front-left: 52016 /  79% / -6.02 dB,   front-right: 52016 /  79% / -6.02 dB
        application.icon_name = "multimedia-volume-control"

basically with that one you would be looking to see if anything was muted or had the volume set to a very low level.
It seems to be fine. I don't think the problem is here. Would it help if I PM you the output?
 
I am new to Linux. I run Kali Purple on hardware.
this from the Kali documentation.
"As the distribution’s developers, you might expect us to recommend that everyone should be using Kali Linux. The fact of the matter is, however, that Kali is a Linux distribution specifically geared towards professional penetration testers and security specialists, and given its unique nature, it is NOT a recommended distribution if you’re unfamiliar with Linux or are looking for a general-purpose Linux desktop distribution for development, web design, gaming, etc."
 
It seems to be fine. I don't think the problem is here. Would it help if I PM you the output?
just to be clear, when you say it seems fine are you referring to the settings you can see when clicking on the volume icon or something else?

as far as the output goes, it would help give others the opportunity to participate if you can post the output of the commands here. i know some of it can be more extensive. i'm a bit new here so i don't know how things are usually done. on other support platforms, if text to be pasted was a bit much i would suggest a site like pastebin: https://pastebin.com/

at least starting with the basics of lspci and pactl like i posted would be helpful.
 
just to be clear, when you say it seems fine are you referring to the settings you can see when clicking on the volume icon or something else?

as far as the output goes, it would help give others the opportunity to participate if you can post the output of the commands here. i know some of it can be more extensive. i'm a bit new here so i don't know how things are usually done. on other support platforms, if text to be pasted was a bit much i would suggest a site like pastebin: https://pastebin.com/

at least starting with the basics of lspci and pactl like i posted would be helpful.
When i said it seems fine I meant what you suggested to try (I tried all of them, and all of them seem to be fine).

Audio mixer is OK.


Output of the lspci command:
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22bd] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:25dd]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
08:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 62)
Subsystem: ASUSTeK Computer Inc. ACP/ACP3X/ACP6x Audio Coprocessor [1043:1d1f]
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x
08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
DeviceName: Realtek ALC1220
Subsystem: ASUSTeK Computer Inc. Family 17h/19h HD Audio Controller [1043:1d1f]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
09:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b8]

Output of the pactl list command:
Mute: no
Volume: front-left: 98699 / 151% / 10.67 dB, front-right: 98699 / 151% / 10.67 dB
Base Volume: 65536 / 100% / 0.00 dB
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
Base Volume: 65536 / 100% / 0.00 dB
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
Base Volume: 6554 / 10% / -60.00 dB
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Mute: no
Volume: mono: 65536 / 100% / 0.00 dB
application.icon_name = "multimedia-volume-control"
 
Output of the lspci command:
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22bd] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:25dd]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
08:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 62)
Subsystem: ASUSTeK Computer Inc. ACP/ACP3X/ACP6x Audio Coprocessor [1043:1d1f]
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x
08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
DeviceName: Realtek ALC1220
Subsystem: ASUSTeK Computer Inc. Family 17h/19h HD Audio Controller [1043:1d1f]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
09:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b8]
the pactl output looks like it should be ok. there is one volume that is only 10%, but i would think you might at least hear it faintly if it were working.

if you'll notice in the above output, the first and third devices both have "Kernel driver in use" lines. the second does not. i am not familiar with that particular type of device. i don't see one listed on my systems. these sets of numbers (1022:15e2 and 1043:1d1f) are pci id's. they can be used to search the linux hardware database to see if anyone else has used the device successfully. this is the page for that device: https://linux-hardware.org/?id=pci:1022-15e2-1043-1d1f

unfortunately there are no probes from systems running debian. however, looking through some of the data for this system running fedora, it seems like even that device might need to have a "Kernel driver in use" line: https://linux-hardware.org/?probe=13b0e73872

this is where checking for journal messages about those devices and drivers could possibly be helpful. now that you have the pci bus numbers for the devices, you could use something like

journalctl -b | grep -iE '01:00.1|08:00.5|08:00.6|snd|pipe|audio'
to see if there are any errors or warnings that might point the way to a solution.

did you also check systemctl status --user 'pipewire*' to see if the services and sockets were active and running?
 
i'm not sure what the rest of it does, but this line from that answer might need a change:

systemctl --user restart pulseaudio.service

the vm i created a day or so ago is kali purple version 2023.2 (the iso was labeled 2023.2a). it uses pipewire and also has a pipewire-pulse service. so those might need to be restarted? i'm don't know exactly since i don't have any non-vm systems running pipewire yet.
 
1022:15e2, and such like codes are Vendor : Product codes, in this case in post #13, the vendor: 1022 is Advanced Micro Devices, Inc. [AMD], and the product: 15e2 is ACP/ACP3X/ACP6x Audio Coprocessor. Not pci bus references. The "PCI" reference at the linux hardware website mentioned in post #14 appears to stand for "product code identity" rather than "peripheral component interconnect", the latter referring to the bus on the motherboard.

On the issue itself, if it helps, these are the packages on this machine that have pipewire working:

Code:
libpipewire-0.3-0
libpipewire-0.3-common
libpipewire-0.3-modules
pipewire-bin
pipewire-doc
pipewire-pulse
pipewire
libwireplumber-0.4-0
wireplumber

The pipewire-doc is not necessary.
 
Last edited:
i'm not sure what the rest of it does, but this line from that answer might need a change:

systemctl --user restart pulseaudio.service

the vm i created a day or so ago is kali purple version 2023.2 (the iso was labeled 2023.2a). it uses pipewire and also has a pipewire-pulse service. so those might need to be restarted? i'm don't know exactly since i don't have any non-vm systems running pipewire yet.
The system can't find pulseaudio.service
Pipewire-pulse.service could not be found
pulseaudio.service could not be found
 
Has pavucontrol been installed ?
 
The system can't find pulseaudio.service
Pipewire-pulse.service could not be found
pulseaudio.service could not be found
did you use the --user option when trying to check the status of those services? without that option, i don't get any output. for example
Code:
systemctl status --user 'pipewire*'
or
Code:
systemctl status --user '*pulse*'

your original post says you are using kali purple. i thought there was only one version, but it may help to check and see if you are using the same version as my virtual machine so i am not giving you incorrect information. the command lsb_release -a should show some info about what you are running. this is the output i get in my virtual machine:
Code:
lsb_release -a
No LSB modules are available.
Distributor ID: Kali
Description:    Kali GNU/Linux Rolling
Release:        2023.2
Codename:       kali-rolling

someone else mentioned checking installed packages. that might be helpful. this command should check for installed packages that contain the word pipe, pulse and pavu (for pavucontrol):
apt list '*pipe*' '*pulse*' 'pavu*' -i
the output from my vm in case we are running the same version:
Code:
apt list '*pipe*' '*pulse*' 'pavu*' -i
Listing... Done
libpipeline1/kali-rolling,now 1.5.7-1 amd64 [installed,automatic]
libpipewire-0.3-0/kali-rolling,now 0.3.65-3 amd64 [installed,automatic]
libpipewire-0.3-common/kali-rolling,now 0.3.65-3 all [installed,automatic]
libpipewire-0.3-modules/kali-rolling,now 0.3.65-3 amd64 [installed,automatic]
libpulse-mainloop-glib0/kali-rolling,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
libpulse0/kali-rolling,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
libpulsedsp/kali-rolling,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
pavucontrol/kali-rolling,now 5.0-2 amd64 [installed,automatic]
pipewire-bin/kali-rolling,now 0.3.65-3 amd64 [installed,automatic]
pipewire-pulse/kali-rolling,now 0.3.65-3 amd64 [installed,automatic]
pipewire/kali-rolling,now 0.3.65-3 amd64 [installed,automatic]
pulseaudio-module-bluetooth/kali-rolling,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
pulseaudio-utils/kali-rolling,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
pulseaudio/kali-rolling,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
xfce4-pulseaudio-plugin/kali-rolling,now 0.4.5-1 amd64 [installed,automatic]
 

Members online


Top