Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Alsa/PulseAudio supposedly works, but still no sound
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Sat Jul 30, 2016 6:09 am    Post subject: Alsa/PulseAudio supposedly works, but still no sound Reply with quote

After dual-booting as per Sakaki's method, I haven't been able to get sound to work in Gentoo no matter what I try. I have pulseaudio enabled in my USE flags and alsa-plugins is compiled as such, when I play audio the volume fluctuates as expected in pavucontrol (though the 100% level is also listed as 0dB, which is probably part of the problem in some way, but I don't know how to fix it), alsamixer responds to keypresses...but despite all of this, no sound comes out of the computer. I've removed myself from the audio group as per the wiki's recommendations, but when I try
Code:
getfacl /dev/snd/controlC0 | grep -Eo "user:.+:" | cut -d: -f2
it claims that there's no such file or directory, which I also don't know how to resolve--it seems as though this should exist judging from the wiki page. (I tried creating it myself and adding my username, but that proved to be impossible.)

Essentially, a lot of odd little things are wrong with my sound, and they all add up to everything being perfectly functional except for the actual sound-making part. How can I fix this?
Back to top
View user's profile Send private message
patrix_neo
Guru
Guru


Joined: 08 Jan 2004
Posts: 520
Location: The Maldives

PostPosted: Sat Jul 30, 2016 8:22 pm    Post subject: Reply with quote

I love systemD

Do not use genup as a magical key to everything. That is not a good way to deal with low level stuff like sound, graphics or using a keyboard.

FFS whom approved this????

someone wrote:

they all add up to everything being perfectly functional except for the actual sound-making part. How can I fix this?


How is this even mutual? Perfectly? Ok. Good luck.
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 6920

PostPosted: Sat Jul 30, 2016 9:15 pm    Post subject: Re: Alsa/PulseAudio supposedly works, but still no sound Reply with quote

ashlyw42 wrote:
but when I try
Code:
getfacl /dev/snd/controlC0 | grep -Eo "user:.+:" | cut -d: -f2
it claims that there's no such file or directory,

It looks like you don't have a functioning ALSA setup. Does /proc/asound/cards exist?
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Sat Jul 30, 2016 11:07 pm    Post subject: Re: Alsa/PulseAudio supposedly works, but still no sound Reply with quote

Ant P. wrote:
ashlyw42 wrote:
but when I try
Code:
getfacl /dev/snd/controlC0 | grep -Eo "user:.+:" | cut -d: -f2
it claims that there's no such file or directory,

It looks like you don't have a functioning ALSA setup. Does /proc/asound/cards exist?

No, /proc/asound doesn't even exist, which is most likely the problem. What should I do to rectify that?
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 6920

PostPosted: Sat Jul 30, 2016 11:55 pm    Post subject: Reply with quote

Your kernel is missing drivers for your sound card, or something else in your system is broken and not loading them. Post the output of these:
Code:
lspci -k
zgrep SND /proc/config.gz
dmesg | grep snd
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Sun Jul 31, 2016 12:49 am    Post subject: Reply with quote

lspci -k: http://bpaste.net/show/917dc5e09c37

zgrep SND /proc/config.gz returns nothing at all, and neither does dmesg | grep snd.

I take this to mean that I don't have the drivers in my kernel somehow? Though this is odd, because I checked the kernel settings cited in the wiki and they checked out fine.
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 6920

PostPosted: Sun Jul 31, 2016 4:31 pm    Post subject: Reply with quote

If /proc/config.gz doesn't even show you commented-out lines then you haven't got any kind of sound support in your kernel. How old is this kernel you're running?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W

PostPosted: Sun Jul 31, 2016 4:48 pm    Post subject: Reply with quote

ashlyw42,

Its easy to configure, build and install one kernel, then run another.
That could account for your symptoms.

What does
Code:
uname -v
show?
That's the build date/time of your running kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Sakaki
Guru
Guru


Joined: 21 May 2014
Posts: 409

PostPosted: Tue Aug 02, 2016 12:23 am    Post subject: Reply with quote

ashlyw42,

further to what NeddySeagoon has just said, there is one particular issue that can cause a kernel mismatch, when following my EFI install guide. Specifically, the boot file used early in the install process is /EFI/Boot/bootx64.efi, but (to avoid conflict with other OSes in the case where the EFI system partition will be shared), this is changed (at a later stage in the guide) to /EFI/Boot/gentoo.efi.

If your EFI BIOS somehow loses the corresponding "Gentoo USB" entry in the EFI boot list, it may still try booting the old /EFI/Boot/bootx64.efi kernel (as this is a default path for most BIOSes) - leaving you unwittingly running the mid-install kernel (which has a config derived from the Gentoo minimal install ISO image kernel, and so has very few drivers activated), instead than the one you think you are working on.

Try commenting out the EFIBOOTFILE line in /etc/buildkernel.conf, running buildkernel again, and rebooting - this will ensure that the /EFI/Boot/bootx64.efi is up to date (and is definitely the path your BIOS tries to boot from).
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Sat Aug 06, 2016 4:19 am    Post subject: Reply with quote

Thanks for the replies everyone, unfortunately the past few days I've been focused more on getting electricity in my apartment again so I hadn't gotten a chance to read through this until now.

NeddySeagoon and Ant P.: uname shows that the kernel is from 29 June 2016.

Sakaki: I tried what you suggested, and while that did open up lots more options in make menuconfig, when I recompiled the kernel with support for my sound card, alsamixer now shows the proper device but doesn't offer volume controls--the display where the sound levels would normally be is there, but it looks like this: https://www.dropbox.com/s/n34yge9vfqkz90u/fixed%20Screenshot%20from%202016-08-05%2023-12-08.png?dl=0 and nothing I do will change the volume--none of the keyboard controls work. Additionally, testing it from the command line as per the ALSA wiki page fails--the command works fine according to the command line output, but still no sound is emitted.

...so at least now I have a different problem?
Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2678

PostPosted: Sat Aug 06, 2016 5:31 am    Post subject: Reply with quote

Have you taken a look at the F6 options?

You probably need to give your user an .asoundrc config file.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Sat Aug 06, 2016 9:04 pm    Post subject: Reply with quote

The Doctor: I have to go into the F6 options to even get the HDMI card in the first place--the default is PulseAudio for some reason, which lspci -k doesn't even show. I tried putting together an .asoundrc file as per the ALSA wiki page for HDMI devices, but now when I attempt to run speaker-test I get the error:
Code:
 Playback open error: -2,No such file or directory
. I have two HDMI devices listed, and I get the same error no matter which is set in the .asoundrc.
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1555
Location: Montréal

PostPosted: Sat Aug 06, 2016 10:23 pm    Post subject: Reply with quote

The sound through HDMI in Linux is provided by the video driver. In your case it is the free Radeon support (with non free firmwares :D ). The Radeon support have an option to activate audio.

To have a chance to make it work you need to have the good firmware files available where the Radeon support is, if Radeon is compile in the kernel image, you need to have the firmware files in the kernel image or in an initramfs. If the Radeon support is in module, you need to have the firmware files in the initramfs if the module is there. Otherwise, the radeon module and firmware files are loaded when the kernel mount the real root filesystem. In any case, this imply that the appropriate firmware files are emerged.

So, from the kernel command line you pass the parameter
Code:
radeon.audio=1

You add too a file /etc/modprobe.d/radeon.conf who contain the line
Code:
options radeon audio=1


When I had a radeon video card, I try this and never succeed to have sound through HDMI :D . A possible alternative to have sound through HDMI is to use the proprietary Amd/ Ati drivers Fglrx. I don't know if it work.

For sure, the Alsa support must be configure correctly for your sound card inlcuding the needed codecs, Hdmi and a specific other one for your sound card.
_________________
Paul
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Sun Aug 07, 2016 1:46 am    Post subject: Reply with quote

Logicien: well, that did something, because now speaker-test doesn't give the error I mentioned, but it still doesn't actually make any sound. How would I go about finding the Radeon firmware? I didn't see anything related to Radeon in the kernel that I hadn't already enabled.
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1555
Location: Montréal

PostPosted: Sun Aug 07, 2016 12:34 pm    Post subject: Reply with quote

Your suppose to have a directory /lib/firmware/radeon if you have install the appropriate package. There are the firmware files needed by Radeon to flash your card to dialog with it. Not all firmware files in this directory are needed but, there is no problem to put all of them in an initramfs to be sure all the needed one are available.

You can create an initramfs with the Radeon firmware files like this
Code:
find /lib/firmware/radeon -print -depth | cpio -ov > /boot/radeon-firmwares.cpio

Than you use this cpio file as an initramfs with your boot loader. Radeon support should find them even if it is compile in the kernel image [y]. If the Radeon support is compile in module [m], you need a tool like Dracut to put the radeon module in an initramfs. That will add it's dependancy modules and the firmware files too.

The best to have Radeon activated as soon as possible at boot time is to put all the support possible in the kernel image but, do not activate radeonfb or any other framebuffer because Radeon Drm provide radeondrmfb framebuffer with KMS support.

You can have multiple initramfs files in the boot command line. For Grub
Code:
initrd /boot/radeon-firmwares.cpio /boot/initramfs ...


You can have a look at the dmesg command output to see if Radeon and Drm have missing some firmware files during the boot. Something like
Code:
dmesg|grep -i -e drm -e firmware -e microcode -e radeon

_________________
Paul
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Mon Aug 08, 2016 3:58 am    Post subject: Reply with quote

Logicien: I followed those instructions as best I could, but still no dice. The output of
Code:
 dmesg | grep -i -e drm -e firmware -e microcode -e radeon
is here: http://bpaste.net/show/d3be6bff6308
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1555
Location: Montréal

PostPosted: Mon Aug 08, 2016 12:22 pm    Post subject: Reply with quote

I see no complain about missing firmware. radeondrmfb is the primary framebuffer fb0. So, if the display work with Hdmi and other video ports, the fact that the Hdmi audio do not work may depend on Alsamixer setup but more on Pulseaudio setup.

I think you are in the same situation than me when I had an Amd/Ati video card. I never been able to make Hdmi audio work and I don't remember if it was working with Fglrx. You can try this proprietary Xorg driver if you really want Hdmi audio work.

Now I have an Nvidia video card and Hdmi audio work with Nouveau. The same with i915 with an Intel video card. I don't use Hdmi audio, only Hdmi video. Most of the time I use Bluetooth or Usb headsets even not my desktop and laptops integrated sound cards.

I cannot help you more here. I can only say to wait someone who have any new idea or make a search on the subject on the Web.
_________________
Paul
Back to top
View user's profile Send private message
Dodec
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2012
Posts: 115

PostPosted: Wed Aug 10, 2016 5:44 am    Post subject: Reply with quote

...I figured it out, everyone. I went back through and reconfigured my kernel as per the Radeon wiki page, and added a couple of other things like the Realtek drivers because I remembered something about that from when I was configuring Windows...and it turns out that even though lspci -k was showing only the HDMI card, the Realtek one is the one that actually works, so I do indeed have working sound now. (Also, speaker-test is for some reason just completely broken, but any other kind of sound on my computer works just fine.)

So, lesson learned: Even if you think you know exactly what kind of hardware you have, try alternatives because they might just be the correct ones. :oops:
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum