Sound not working with ALC262
HI,
I'm not able to ear any sound from my panel pc. It has a Gentoo kernel 3.19.8 and the sound hardware is the following: Code:
eposatom ~ # aplay -L Code:
# alsa configuration file Code:
eposatom ~ # zgrep -i snd_hda /boot/config-3.19.8-gentoo Code:
# Alsa kernel modules' configuration file. The system works under X without any windows manager but with a specific GUI application. What do I have to do to have the audio working? Thanks Claudio |
$ speaker-test -c 2 -l 1 -D hw:PCH,0
Assuming you want the 3.5mm jack output and not the HDMI. Also make sure the user is in the audio group. $ groups And that the mixer levels are NOT muted. $ alsamixer -c PCH Optionally try the "other" devices until one works. $ speaker-test -c 2 -l 1 -D hw:0,0 $ speaker-test -c 2 -l 1 -D hw:1,0 $ speaker-test -c 2 -l 1 -D hw:2,0 Or other device options, HDMI is often ,3 so... $ speaker-test -c 2 -l 1 -D hw:0,3 $ speaker-test -c 2 -l 1 -D hw:1,3 $ speaker-test -c 2 -l 1 -D hw:2,3 The details for which are often in /proc/asound/, although a bit of understanding is needed to decrypt them from various files in /proc/asound/. And other things can get in the way like pulseaudio and jackd. But mostly being in the audio group, and setting mixer levels is what most initially get wrong. Followed by selecting the wrong device, hw:0,0 is default by default. Which could be a webcam (input only) depending on how things loaded at boot. |
Hi, now I'm testing the sound as root, but even the user is in to the audio group.
The result of your command is the following: Code:
eposatom ~ # speaker-test -c 2 -l 1 -D hw:PCH,0 Just to complete the info of the system, dmesg says this: Code:
eposatom ~ # dmesg | grep -i audio Claudio |
C0D2 is the microphone input (typically). You might try a newer kernel, the snd-hda-intel driver is under constant change as most everything has a version of it these days. Version 3.19 is quite dated at this point, seem like 2015 was the last update to it and your hardware is likely newer than that. Unless you're building your alsa drivers from the alsa-project.org source and not the actual kernel tree for 3.19.
|
You might also try:
$ speaker-test -c 2 -l 1 -D default $ speaker-test -c 2 -l 1 -D pulse And use pavucontrol to select your audio option if pulseaudio is in play. It likely is as modern gui web browsers require it for sound. |
Hi,
the 3.19 is the higher version of kernel I can use because the system needs to work a specific usb driver that is incompatible with kernel 4. I will try to disable the alsa driver into the kernel and download the latest version. The system works as a kiosk with a custom graphic application under X but without any windows manager so I cannot install pavucontrol. The only tool I could use for the sound is aplay. Claudio |
Not entirely true. You can use rec and play from the sox package. Also command line based. Technically ffplay and cvlc will work too. Or mpv and a number of mplayer variants.
I use rec when doing down an dirty recordings as it has a CLI based meter to tell what your level is at. Which otherwise verifies that you "are" recording IMO. With arecord you're literally flying blind, baring some form of tee and sound routing to hear what you're recording while recording. Although I'll often use arecord + tee to record a high quality version and an mp3 version at the same time. The mp3 version I hand off to the subjects being recorded while I take the high quality one home to process. A down and dirty way of routing sound with alsa based systems. FILE: $HOME/.asoundrc Code:
defaults.ctl.card 1 |
HI,
I tried to follow your suggestion modifying the .asoundrc file, but I still have no sound. |
I did some test with different kernels
It works with kernel 4.19 and with kernel 3.15, so I suppose there is a bug with the sound HDA modules into the kernel 3.19 Any idea about how to solve this issue? Claudio |
There's often parameters that you can pass to tweak things. Which might help it work on other versions.
# modinfo snd-hda-intel Code:
filename: /lib/modules/4.19.0-1-amd64/kernel/sound/pci/hda/snd-hda-intel.ko |
Thanks for the suggestion. I will try to use the parameters.
In any case I saw with alsamixer that every time only the hdmi codec is activated. I tried to disable that codec recompiling the kernel, but the result is a strange chip name shown with alsamixer, but always of type hdmi The command "lsmod" shows that snd_hda_intel=0 always. Edit: I tried to use the "probe_mask" param to mask the hdmi codec. With this param in alsa.conf I have: Code:
eposatom ~ # lsmod Code:
eposatom ~ # aplay -l In any case no sound |
There's stuff in /proc/asound/* that details what's available. Things shown by other means like amixer or aplay -l. Just make sure the sound is routed to the desired device. Harder to do these days since HDMI has audio, webcams have audio (input only), motherboards, graphics cards, and everything is an audio device it seems these days #surveillancestate.
|
It'll be 0 in lsmod until something is using it. i.e. you have to be playing audio for it to not be 0. Not what you'd expect since other things like wifi, video, and such will always be in use by default (in most cases).
|
Hi,
if I try to use the command "aplay mysound.wav" I cannot ear any sound and snd-hda-intel remains 0 in lsmod In /proc/asound I see a folder named card0 and a link to this folder named Intel. Inside card0 there ar files referencing codecs, id and so on. My opinion is that some of these are wrong or the system is looking for something else Using kernel 4.19 it works properly, but in /proc/asound instead to have a folder named "Intel" there is a folder named "PCH" and in card0 there are more files |
$ cat /proc/asound/cards
Should list known devices and their index. There's also a generic "name" associated with it, which allows you to call it by name without knowing it's index (if it's a unique device). Code:
0 [Loopback ]: Loopback - Loopback There's other things that are card specific. $ ls -l /proc/asound/card2/ Code:
total 0 Not that you need to know any/most of that. But if there is no index for your card in /proc/asound/cards, then you do not have a driver for it. And if the details under /proc/asound/card#/ for it lack things, you do not have certain functionality. Like "p" for playback or "c" for capture. $ ls -l /proc/asound/card3/ Code:
total 0 Things like pavucontrol will GUI-ize this for you, so you don't need to know / understand most of it. As long as things "work" as expected. |
All times are GMT -5. The time now is 06:06 PM. |