- This topic has 5 replies, 6 voices, and was last updated Oct 11-4:35 pm by rokytnji.
-
AuthorPosts
-
May 25, 2020 at 8:34 pm #36300Member
angeldeluz
Hello I just installed antiX 19.2 64 Base and I have no sound.
In the “Sound Card Chooser” app I only can select “Generic:HDA-Intel-HD-Audio Generic”
and “Generic_1:HDA-Intel-HD-Audio Generic”
If I choose one the test fails because cannot connect to the device.
I guess I have to install a sound card driver but I don’t know how.
In Mx Linux I have sound.
Thank you!..us@antix1:~ $ inxi -zv7 System: Host: antix1 Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 1.6.5 dm: SLiM 1.3.6 Distro: antiX-19.2.1_x64-base Hannie Schaft 29 March 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop Mobo: BIOSTAR model: TA75M+ serial: <filter> BIOS: American Megatrends v: 4.6.4 date: 09/13/2011 Memory: RAM: total: 3.35 GiB used: 657.8 MiB (19.2%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Dual Core model: AMD A4-3300 APU with Radeon HD Graphics bits: 64 type: MCP arch: Fusion L2 cache: 1024 KiB bogomips: 9998 Speed: 1200 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 1200 2: 1600 Flags: 3dnow 3dnowext 3dnowprefetch abm aperfmperf apic arat clflush cmov cmp_legacy constant_tsc cr8_legacy cx16 cx8 de extapic extd_apicid fpu fxsr fxsr_opt ht hw_pstate ibs lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor msr mtrr nonstop_tsc nopl npt nrip_save nx osvw pae pat pausefilter pdpe1gb pge pni popcnt pse pse36 rdtscp rep_good sep skinit sse sse2 sse4a svm svm_lock syscall tsc vme vmmcall wdt Graphics: Device-1: AMD Sumo [Radeon HD 6410D] vendor: Biostar Microtech Intl Corp SuperSumo driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9645 Display: server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD SUMO2 (DRM 2.49.0 / 4.9.212-antix.1-amd64-smp LLVM 7.0.1) v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes Audio: Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series] driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:1714 Device-2: AMD FCH Azalia vendor: Biostar Microtech Intl Corp driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1022:780d Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Biostar Microtech Intl Corp driver: r8169 v: 2.3LK-NAPI port: e000 bus ID: 01:00.0 chip ID: 10ec:8168 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> type: dynamic mngtmpaddr scope: global IP v6: <filter> scope: link WAN IP: <filter> Drives: Local Storage: total: 938.74 GiB used: 523.65 GiB (55.8%) ID-1: /dev/sda type: USB vendor: SanDisk model: Cruzer Blade size: 7.23 GiB serial: <filter> rev: 1.27 scheme: MBR ID-2: /dev/sdb type: USB vendor: Western Digital model: WD10 JPVT-22A1YT0 size: 931.51 GiB serial: <filter> rev: 01.0 scheme: MBR Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH24NSC0 rev: LI00 dev-links: N/A Features: speed: 125 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running RAID: Message: No RAID data was found. Partition: ID-1: / size: 19.16 GiB used: 2.53 GiB (13.2%) fs: ext4 dev: /dev/sdb6 label: rootantiX19 uuid: addb67d1-032a-486e-8274-936a19ed334e ID-2: /media/us/LG-DATA size: 839.58 GiB used: 516.27 GiB (61.5%) fs: ntfs dev: /dev/sdb1 label: LG-DATA uuid: 01D59CA6B3A69280 ID-3: /media/us/MX-Live-usb size: 7.13 GiB used: 4.80 GiB (67.4%) fs: ext4 dev: /dev/sda1 label: MX-Live-usb uuid: dce2110c-fa5b-4144-a9c4-25c959bd0d6c ID-4: /media/us/MX-UEFI size: 48.2 MiB used: 4.2 MiB (8.7%) fs: vfat dev: /dev/sda2 label: MX-UEFI uuid: 6B9E-4A4D ID-5: /media/us/data1 size: 19.11 GiB used: 43.9 MiB (0.2%) fs: ext4 dev: /dev/sdb7 label: data1 uuid: 24037397-414e-47e1-9564-39063ece3b18 ID-6: swap-1 size: 2.03 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb5 label: N/A uuid: d5fcea2b-d3cc-4d68-a7b9-233a792d4fcc Unmounted: ID-1: /dev/sdb2 size: 1 KiB fs: <root required> label: N/A uuid: N/A USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 5 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Hub: 2-0:1 info: Full speed (or root) Hub ports: 5 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Device-1: 2-3:3 info: Cubeternet GL-UPC822 UVC WebCam type: Video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s chip ID: 1e4e:0102 Hub: 3-0:1 info: Full speed (or root) Hub ports: 5 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Hub: 4-0:1 info: Full speed (or root) Hub ports: 5 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Device-2: 4-2:2 info: Holtek Keyboard LKS02 type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s chip ID: 04d9:1702 Device-3: 4-4:3 info: Brother Industries type: Printer driver: usblp interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 04f9:0054 serial: <filter> Device-4: 4-5:4 info: KYE Systems (Mouse Systems) type: Mouse,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s chip ID: 0458:0186 Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Device-5: 6-1:2 info: SanDisk Cruzer Blade type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0781:5567 serial: <filter> Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s chip ID: 1d6b:0003 Device-6: 7-2:2 info: LG USA External HDD type: Mass Storage driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s chip ID: 043e:70f5 serial: <filter> Hub: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Hub: 9-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 19.0 C mobo: N/A gpu: radeon temp: 12 C Fan Speeds (RPM): N/A Info: Processes: 165 Uptime: 2h 41m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: roxterm inxi: 3.0.36- This topic was modified 2 years, 11 months ago by rokytnji.
May 26, 2020 at 2:51 am #36314Member
Xecure
::This may be a short and easy solution or may take a bit more effort to find the problem.
Make sure audio fails in all programs and not only in your browser. Use the Speaker test (Speaker Test in App Select or Control Centre > Hardware > Test Sound). Do it for both card devices. If Audio Test works on one specific device, it should work on Firefox-ESR. If you are using Firefox (the newest, not ESR) or other new browsers that don’t work out of the box with ALSA, then it is normal (you need to install apulse and launch the specific browser with apulse firefox)
If your audio problem is system wide, then we will explore different solutions.
You have confirmed it works on MX Linux in the same computer. This may be because of:
a) Using 4.19 kernel. Maybe a better working driver is available in a newer kernel. We will have this in mind.
b) pulseaudio instead of ALSA. MX Linux uses pulseaudio to manage audio in your system, so maybe you will not find the same problem using pulseaudio.Before going in and installing stuff, let us figure out if we can solve this in the current working system. You can use the “Speaker Test” program or an audio file after every step. Once you have sound working, you can stop there and rejoice with your working sound.
0. You will need a bit more info on your sound devices and cards. Check in terminal:
aplay -l
Thought your inxi tells us`Audio:
Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G
series]
driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:1714
Device-2: AMD FCH Azalia vendor: Biostar Microtech Intl Corp
driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1022:780d
Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp`It will be useful to know their real card/device numbers in case we need to adjust them manually.
You will need to answer these questions:
Are you using HDMI as sound output? Then you need to use Sound Card 0 (or whatever number is given above). If you are not, then you need to use Sound Card X (you will have to choose from the list). Keep this information handy in case you need to edit /etc/asound.conf in the future.1. Making sure your audio is not muted.
Go to Control Centre > Hardware > Adjust Mixer
Make sure non of the options are muted (you should see a MM instead of 00 under any of the bars if it is muted. If it is muted, hit M key to unmute).2. Restore ALSA configuration and rescan the soundcards.
alsactl nrestore
Sometimes the problems can easily be solved by restoring the ALSA configuration and rescanning the soundcards.
Then go back to the3. Test with XMMS to check if it is related to the Alsa card chooser program or the driver (you will need a song or any audio file for testing the audio on XMMS). Open XMMS, right-click anywhere, go to Options > Preferences. There, at the bottom of the new window, you should see “ALSA 1.2.11 output plugin” for Output Plugin. Hit configure and select the correct audio device. Remember what you saw in step 0, as you will have to select the correct audio device based on what you are using (after selecting, check the value for hw:X,Y where X is the card and Y is the audio device, comparing to what you saw in aplay -l output). Hit OK and test the audio by playing something with XMMS.
3.1. If XMMS had audio playing correctly, manually set the audio device for ALSA in /etc/asound.conf
Open the asound.conf file with your preferred text editor with root privileges. Example with geany:
sudo geany /etc/asound.conf
Knowing the card and device that worked on XMMS, edit these lines:# ***** Defaults ******************************************************* # Audio card/chip and device to use and control # In most cases these settings should remain commented (#) # When commented, card and device 0 are usually automatically selected # When uncommented, the item corresponding to the number is selected #defaults.pcm.card 0 #defaults.pcm.device 0 #defaults.ctl.card 0Uncommenting the default.* lines and changing the values to the correct card and device values that worked on XMMS. For example, hw:1,2 would mean Card 1 Device 2. the result would be:
# Audio card/chip and device to use and control # In most cases these settings should remain commented (#) # When commented, card and device 0 are usually automatically selected # When uncommented, the item corresponding to the number is selected defaults.pcm.card 1 defaults.pcm.device 2 defaults.ctl.card 1Save the file.
A reboot may be in order. This should solve the problems if you got audio to work on XMMS, now it should work on all the system. If it doesn’t, restore /etc/asound.conf to default values.4. If nothing above worked, maybe you need to update the kernel. There are many ways to do so (antiX package installer, synaptic, cli-aptiX). Install the latest 4.19 kernel and reboot. Try again to select the correct device and test your audio.
5. If no matter what you have tried you cannot get audio to work with ALSA, you may want to test pulseaudio, as you know it works with MX Linux. I have published the steps before.
Getting pulseaudio in your system:
1. Installing pulseaudio:
Open a terminal and execute
sudo apt-get install pulseaudio pavucontrol2. Make pulseaudio launch on startup
Edit startuo file
geany ~/.desktop-session/startup
Add a line that launches pulseaudio#launch pulseaudio Daemon on startup pulseaudio -D &Save and exit
3. Making volume-icon use pulseaudio (and manage volume and properties)
right-click the volume icon in your systray and click on Preferences.
Have External mixer execute pavucontrol. It originally says:
External mixer desktop-defaults-run -t alsamixer
Replace it with:
External mixer pavucontrolReboot your system.
Now you can use pavucontrol to select the audio output device and test if audio is working.
If I forgot something, hopefully I can come back and give you more info.
- This reply was modified 2 years, 11 months ago by Xecure. Reason: formating
- This reply was modified 2 years, 11 months ago by Xecure. Reason: fixing quote
antiX Live system enthusiast.
General Live Boot Parameters for antiX.May 26, 2020 at 4:22 am #36321Forum Admin
anticapitalista
::Check that sound is not muted (no M) via Contol Centre > Hardware > Adjust MIxer
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
October 10, 2022 at 10:22 pm #90560Memberto-the-moon
::I’m currently having the same issue as described above, with my Asus tuffbook gaming laptop, antix21
Will try this fix posted above for pulse audio, as I need the pulse GUI to switch from HDMI or internal Speaker’s
- This reply was modified 6 months, 3 weeks ago by to-the-moon.
- This reply was modified 6 months, 3 weeks ago by to-the-moon.
- This reply was modified 6 months, 3 weeks ago by to-the-moon.
October 11, 2022 at 4:10 pm #90586Member
Wallon
::Dear to-the-mon
I too have this problem since the IceWM 3.0.1 update. I have no sound with pulseaudio which worked fine with antiX 21.
I have followed the explanations given by Xecure but it doesn’t work.
Did you find a solution?Best regards,
WallonOctober 11, 2022 at 4:35 pm #90589Forum Admin
rokytnji
::Has anyone opened control panel and use the test sound button yet?
Usually when I lose sound. That is my 1st check stop.
Then next step I might try is rfkill commands.
harry@biker:~ $ rfkill list all 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: noThen if using pulse audio. Instead of alsa. I open Pulse audio settings and make sure my settings are on point.
That is how I go about trouble shooting sound. Good luck.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problems -
AuthorPosts
- You must be logged in to reply to this topic.