3

Recently, I installed Debian 9 Stretch (dual booting with windows 10 using grub). Everything works fine for now, except my headphones.

The PulseAudio 'Volume Control' interface detects my headphones fine.

So does running alsamixer in the terminal. Even when I put on some music, the volume gage becomes active with a blue bar as if audio was coming through. But no sound coming through the headphones. I went back to windows 10 to definitively see if my 3.5mm jack on my laptop was the problem (or my headphones), and it works fine with windows 10.

It's a Debian.

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

PS. Sound works fine coming from my internal laptop speakers once I disconnect my headphones.

  • It's often a driver issue solved with a newer kernel. You could try stretch-backport's linux-image-amd64 currently pointing to linux-image-4.19.0-0.bpo.1-amd64. This is worth a try even if sometimes changes in the pulseaudio or alsa userland parts are also required – A.B Jan 31 at 2:03
  • Also check there: h30434.www3.hp.com/t5/Notebook-Audio/HP-spectre-x360-on-linux/… and the other link h30434.www3.hp.com/t5/Notebook-Audio/HP-spectre-x360-on-linux/… . Problem is the same, but it's from 2015 so ... – A.B Jan 31 at 2:13
  • Hey, @A.B thanks for your comments. I tried the solutions described in those links but to no avail. Before I ditch Linux all together and get back to Windows, might you suggest a different Linux Distro that is perhaps more suited toward laptops and less driver/hardware related configurations? I was thinking Ubuntu, but I've seen similar problems and since it's based on Debian, I might not fare any better there. – Juan Veliz Feb 1 at 18:38
  • You should check mailing lists about linux sound/alsa etc. and perhaps see how to submit a problem (this might not be easy). If one distribution did solve it cleanly, then it would be adopted on upstream and others: that's what open source is for. So chances are it wasn't reported loudly enough so nothing was made to correct the (unknown to kernel/alsa/whatever developpers) problem. – A.B Feb 2 at 11:33
  • You're perhaps not alone: superuser.com/questions/1360320/… . But at the same time you didn't put the most important thing in the question: your hardware exact model – A.B Feb 2 at 11:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.