SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't get sound to go down the hdmi cable.
I seem to have this issue back in Slackware Current. I've had it before, I had a mega-thread in 2015 on sound, but I can't find it in a thread search. 'Aplay -l' shows me
Now with something playing, I used to be able to open pavucontrol, select the 'Output Devices' tab, and find the HDMI in Ports, click on hdmi and sound came through the HDMI device. But now, I never see the HDMI device in pavucontrol, although aplay -l does see the card. I only get offered (joke) Speakers or headphones
How do I fix that?. BTW, lspci follows
Quote:
bash-5.0$ sudo lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 IDE interface: Intel Corporation 7 Series Chipset Family 4-port SATA Controller [IDE mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
00:1f.5 IDE interface: Intel Corporation 7 Series Chipset Family 2-port SATA Controller [IDE mode] (rev 04)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
bash-5.0$
can I be rude? and point out....auto mute is a jack sense where headphones are inserted to an analog sound device
....if detected....sound is muted to analog speakers.
umm I do not wish to interfere with abga.
but if his solutions do not work....a simple .asoundrc should work but leaping ahead....some sound devices need SPDIF toggled on or off
or off on etc to enable hdmi.
#####
Code:
cat .asoundrc
pcm.!default {
type hw
card 0
device 3
}
ctl.!default {
type hw
card 0
device 3
}
Nothing to interfere with, I was just trying to gather more info about OPs setup/situation - helping define the problem. Any (additional) hints are welcome here. Skaendo already addressed the Auto-Mute potential cause in post #2.
Great - 2 sound gurus here. Thanks for replies, guys.
@aus9: I think I'll leave the .asoundrc idea until I get pulse sorted (See below). Pulse piddles all over alsa configs anyhow.
@agba: Hit a problem with pulseaudio starting in system mode, so the pacmd commands gave me the middle finger. I eventually restarted with simply 'pulseaudio &' to get around it. Now your outputs:
As you no doubt noticed, there's a real issue keeping pulseaudio running. It normally respawns in Slackware. I started it again with 'pulseaudio --disallow-exit &' and that gets me going. I am getting sound through HDMI. But I really don't like changing recently updated rc files without fully understanding what I'm doing. I take it the '&' bit tells it to daemonize itself. Over to you!
BTW, I got 6 options in pavucontrol on a configuration tab not visible unless I maximise pavucontrol. But I can get hdmi sound, which is nice. I'll await your reply before marking this solved, but the answer appears to be changing the pulseaudio startup command from this
Great - 2 sound gurus here. Thanks for replies, guys.
Who are they ? If you ask me, I'm just a pulseaudio "survivor", treating pulseaudio with respect (remember? I told you that in an older thread) who learned a lot from some of the posts of the actual guru @enorbet
Quote:
Originally Posted by business_kid
@agba: Hit a problem with pulseaudio starting in system mode, so the pacmd commands gave me the middle finger. I eventually restarted with simply 'pulseaudio &' to get around it.
....
As you no doubt noticed, there's a real issue keeping pulseaudio running. It normally respawns in Slackware. I started it again with 'pulseaudio --disallow-exit &' and that gets me going. I am getting sound through HDMI. But I really don't like changing recently updated rc files without fully understanding what I'm doing. I take it the '&' bit tells it to daemonize itself. Over to you!
Well, I mentioned that pulseaudio must be running in order to be able to execute the pacmd commands.
Basically, you have two ways to run pulseaudio:
- the default/standard one, adopted by Slackware, in which pulseaudio is only executed upon request (Autospawning), thus, no need to modify your rc. init files https://www.freedesktop.org/wiki/Sof.../User/Running/
- system wide, not really recommended, unless you have a special request/scenario for it https://www.freedesktop.org/wiki/Sof...er/SystemWide/
Now, launching pulseaudio manually is to be done by issuing:
Code:
/usr/bin/pulseaudio -D
- it will launch and if it hits the default 20 secs - exit-idle-time (defined in /etc/pulse/daemon.conf), it will exit. Meaning, once you launch it manually, you need to hurry with the pacmd commands, or, uncomment the exit-idle-time and increase the idle to your desired time (better hurry, no need to keep pulseaudio running).
To kill it, just run:
Code:
/usr/bin/pulseaudio -k
The outputs of the commands I asked you to run show that the HDMI is activated and available. Not sure why it didn't work in the first place. If you believe that you have messed up the pulseaudio configuration - it happened to me on older versions - then, you could backup and delete the directory .config/pulse from the user's home and restart pulseaudio in order to re-create & populate it:
Code:
/usr/bin/pulseaudio -k
/usr/bin/pulseaudio -D
Obviously, the procedure should be done without X/pavucontrol running.
Quote:
Originally Posted by business_kid
BTW, I got 6 options in pavucontrol on a configuration tab not visible unless I maximise pavucontrol. But I can get hdmi sound, which is nice. I'll await your reply before marking this solved, but the answer appears to be changing the pulseaudio startup command from this
to this
EDIT: That startup config is unchanged for the last year. This worked with the original config. What's up now?
Sorry, only running Slackware -current on ARM (Raspberry Pi) and not using X at all. Additional, the Slackware ARM -current wasn't updated for almost a month now, drmozes seems to wait until he hits his targeted income/donations and able to prioritize it again over the podcasts.
Therefore I cannot replicate your scenario -> packages versions ...
Try removing & reinstalling pavucontrol, don't know if it helps. Maybe you have some DE issues there, some oversized buttons/fonts/etc. that are breaking the pavucontrol window.
On the startup config, already addressed it, leave it alone.
umm I am not a PA guy....but if you continue to run PA in system mode you will have interference because in post 4 you were asked to
kill PA
restart PA in daemon mode AFAIK.
IMHO you are better off in the long run...staying with PA but copying user configs to your home dir
.config/pulse
edit the config to not autospawn PA
kill PA
make changes to whatever then just restart PA.
autospawn only effects PA if it is killed. I am not asking you to disable it on boot with your (probable) systemd setup.
hidden agenda....giggles....kill PA...never try to delete it as its a monster.....well I am joking but it pretty bad...
and use alsa .asoundrc file to play thru hdmi.
It does have 2 uses.....it is really easy to use to swap sound devices on the fly
and it easy to .....modesty forbids to reveal I think it might have a second use.
I had all this working just dandy under alsa, sorted it for pulse, and had it working 6-9 months ago. I got into this issue because it slipped out of config sometime, and I updated it recently. I also overwrote configs fairly recently, which I hadn't done for years. I changed kernels to a home brewed one, and generally sort of brought the house down on myself a little. I thought all was sorted out, but then this showed up.
~/.config/pulse has all very recent files (Feb 10 or 11), so I'm not tempted to fiddle with that. Adding modules into the long file that is /etc/pulse/default.pa is something I looked at but didn't do. It does have
### Automatically suspend sinks/sources that become idle for too long
<stuff> and HDMI certainly fell into that category.
/etc/xdg/autostart/pulseaudio.desktop is a file in multiple languages. Once it exists, I left it alone.
I really don't understand the benefits of having pulse die off and then restart as required in --system mode. Sure, it saves a few K of ram while compromising response time. PA is a total POS imho, and has plainly failed to start up as required, like when sound was playing and pavucontrol was running. I install PA not because I want or like it, but because programs require it.
Somebody was asking me for my kernel version: 5.4.18, with the option of 5.4.14 or slackware-huge (purely while I sort this out).
At this stage, I'm sure there is a techno-ethical way to get pulse self starting; I don't have it, so I've forbidden exits, and the sky hasn't fallen in. Rule #1 in maintenance beckons: "If it works, don't fix it!"
profiles:
input:analog-stereo: Analog Stereo Input (priority 65, available: unknown)
output:analog-stereo: Analog Stereo Output (priority 6500, available: unknown)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6565, available: unknown)
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: unknown)
off: Off (priority 0, available: unknown)
active profile: <output:analog-stereo+input:analog-stereo>
I think this is your problem. You want the sound card on the HDMI profiles. You can change that on the configuration tab in pavucontrol. I think this line should do it from the command line:
I'll admit I haven't read the whole thread (I am not a pulseaudio guru... I know nothing about sinks or pacmd -- I'm one of the lucky ones where it has just worked), so if this has already been discounted, please ignore. Do you happen to have any modules blacklisted? I remember a recent thread had some people disabling some module to prevent some spamming error on systems using the Nvidia driver. I think it had to do with the USB on the video card that is used for VR. If that module is also used for hdmi, it could've knocked it out and prevent pulse from using it.
umm I am not a PA guy....but if you continue to run PA in system mode you will have interference because in post 4 you were asked to
kill PA
restart PA in daemon mode AFAIK.
I didn't know how the OP was running pulseaudio and expected the standard, autospawning mode. Instructing to kill pulseaudio in such a case (autospawning) is pretty redundant, but you never know what other app could use it (pavucontrol & co) and I just wanted to be sure it's killed and started again clean for the following instructions I presented.
@zuriel
Configuring the default profile on shell (say, putting it in /etc/rc.d/rc.local) requires pulseaudio to be running for the pactl command:
On configuring the default ouput, as suggested by @zuriel, by using the shell (and completed by me in this post), you have the alternative to use pavucontrol. Follow what @wirelessmc is describing here: https://www.linuxquestions.org/quest...3/#post6045996
I didn't know how the OP was running pulseaudio and expected the standard, autospawning mode.
I know little about PA and what little I do know convinces me it's unnecessary alpha software, unfortunately used by programmers. I was running off the SysVinit script in Slackware
'/usr/bin/pulseaudio --system --disallow-module-loading 1 > /dev/null 2 > /dev/null'
I set up /etc/default.pa as per instructions, thank you agba; reset the original start line and it hung on rc.pulseaudio - silently, of course. So I rebooted on a live USB key, and killed PA & ran the line without the piping to /dev/null on the usb key and got myself a lecture:
Quote:
bash-5.0$ sudo pulseaudio --system
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set. # In fairness, the slackware rc script sets it.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode. # Shared Memory?
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.
W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Soft...ithSystemWide/ for an explanation why system mode is usually a bad idea.
I read that link and decided system mode was a bad idea. System mode is only for headless embedded stuff, not Desktops. So I'm marking this solved, sticking with what I've now got.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.