Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Put "autospawn = no" in /etc/pulse/client.conf and you can stop/start pulseaudio.
$ pulseaudio --kill
$ pulseaudio --start
$ sudo modinfo snd-hda-intel
Thanks for these! They didn't help, but I didn't know how to do them. LOL
I'm down to just "options snd-hda-intel model=generic" in my snd_hda_intel.conf file, now that I know that probe_mask is -1 (all ones) by default. I have headphones working. They switch the sink back and forth to HDMI like they should, but no output sound on the TV. I tried both HDMI input ports on the TV, as well as a new HDMI cable. This is Big progress. But it seems that I just can't finish the last mile.
I guess about the last thing to do is to put the Win 10 disk back in the computer and see if it works for sound once everything is configured. Maybe I somehow broke the sound on the connector? I dunno.
Last edited by Quakeboy02; 06-08-2019 at 12:12 PM.
So, after booting from power off, it became clear that something was retaining the last single_cmd, so I had to add that back to the conf file. But, that's where I'm stuck. I've got headphones, and it switches when the phones go in or out. I've just got no HDMI sound. Also, I did put the Win 10 disk in without changing anything else. The HDMI sound works with it in.
You might need a fancy .asoundrc if your HDMI audio only takes certain protocols like AAC, MP3, or other "formatted" audio, not PCM. I'm not quite sure though. My HDMI monitor lets you change from "digital" to "Line-In", and has a DDC/CI option to toggle ON/OFF in the monitors menu. None of which makes my HDMI audio work. Where outputing just to the hw:#,3 on my HDTV would work almost brain dead. So I might need a fancy .asoundrc file myself. I know my pocketchip doesn't output audio without it's fancy .asoundrc. But it's hardly a standard piece of kit and doesn't do HDMI.
I'm using Debian Stretch. Just for grins, I did a clean install of Stretch on an old disk I had laying around. No sound, codec doesn't load, wakeup waits. Grrrrrrrrrrrr. So, sometime in the past, possibly even in a previous release of Debian, I fixed something in the sound on the machine this OS was originally installed on. That was either an ASUS mobo with an AMD FX-8350 or something like that, or my little eeebox which is where I lifted the mostly running OS from. Oh, and to make matters worse, I've upgraded to all SSD drives, and the old drive I installed to was a hardware drive. ZZZZZZZZZZZZZZz LOL
Yeah, getting frustrated at all this time lost. So, I think that next I'm going to download a live CD and see what that does with this computer. I'll post the results when they happen.
You might need a fancy .asoundrc if your HDMI audio only takes certain protocols like AAC, MP3, or other "formatted" audio, not PCM. I'm not quite sure though. My HDMI monitor lets you change from "digital" to "Line-In", and has a DDC/CI option to toggle ON/OFF in the monitors menu. None of which makes my HDMI audio work. Where outputing just to the hw:#,3 on my HDTV would work almost brain dead. So I might need a fancy .asoundrc file myself. I know my pocketchip doesn't output audio without it's fancy .asoundrc. But it's hardly a standard piece of kit and doesn't do HDMI.
Here's the HDMI output from dmesg. As you can see, it only has dig-out. So, do I need something to tell it some kind of protocol for that through .asoundrc?
Also, I've tried a number of different "models" in /etc/modprobe.d/snd_hda_intel.conf, and the only one that shows any real sign of promise is "generic". Everything else gets a mess for the hdaudioC0D2 i.e. HDMI results.
I'm wondering if it would be easier to get a set of cheap powered speakers, or maybe even bluetooth speakers. Except bluetooth would probably be the same nightmare as this, which I don't need.
bluetooth nightmares are just having a driver that works and getting the device to connect. Which might not be an issue worth noting with "blessed" hardware and a DE with an easy button.
Running debian stretch here as well. With a flatpak of the game I tends towards, I don't need buster (yet) for the more recent video driver(amdgpu) (although I tend to recall HDMI audio working in buster/testing, since pulseaudio would switch to it everytime the screen blanked).
I just installed the backport package and I'm running the higher kernel. No improvement on the sound, but at least the onboard wifi is working, so I can pack away the wifi dongle. I've pretty much run out of ideas with the sound. I tried a lot of stuff from looking at the code. Most things I tried it returned "unplugged" for all the HDMI stuff. Generic seems to want to work, but it doesn't. At least it's not marked "unplugged", it simply doesn't work. So, I don't know whether that means I don't have something set right, or it's just so lost it doesn't know what to do. I did download the firmware package for Buster, so I may give that a try.
i915 is the intel video driver. With coffee lake coming out Oct 2018, so the newest of the CPUs. Not surprised that you needed to add a module parameter. You could also add that parameter in /etc/modprobe.d/
Yeah, I did have an i915 setting in modprobe.d, but it was the wrong one. LOL I've got my sources.list setup for stretch, so I won't change dists without doing something affirmative. I've tried dist upgrades in the past, and except for one, they were all disasters. So, I'll have to give long thought to upgrading to Buster. Maybe next year or the year after. Usually it's when there's something I want to do that I can't that causes me to upgrade. But, now that I'm living on this sailboat, my needs are pretty straightforward.
Thanks for all the help, even if you didn't come up with the final solution. Frustrating problems like this can make for a lonely job.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.