Ubuntu: No sound from speakers, headphones jack detected even when no headphones are connected

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












I have a problem with the audio in Ubuntu 17.10.
No sound from speakers unless auto-mute from alsamixer is disabled. In that case sound goes to both speakers and headphones.



All sound cards are installed, however, even when headphones are not connected the only available output remains headphones-internal audio.



So far I did a fresh install of Ubuntu 17.10, run a live version of Ubuntu 16.04, 17.10, and Fedora, but no luck.



All this makes me think of a harware failure, in particular that the switch of headphones output jack socket is not working as it should.
I tried to gently clean it, but nothing. However, audio hardware failure is quite unlikely to happen (I hope at least).



After each boot speakers are muted in alsamixer, unmuting them and increasing the volume produce sound from speakers, but of course the speakers are not automatically disabled when headphones are connected.



Note that the audio worked properly with Ubuntu 17.04, and also with 17.10 (at least for a week), then suddenly stopped without updating anything.



Machine: Lenovo Yoga 2 Pro.



arecord -l
**** Lista di CAPTURE dispositivi hardware ****
scheda 1: PCH [HDA Intel PCH], dispositivo 0: ALC3239 Analog [ALC3239 Analog]
Sottoperiferiche: 1/1
Sottoperiferica #0: subdevice #0


EDIT:
Here the output for cat /proc/asound/card*/codec#*



Moreover:



  • I just tried to run a live usb with Windows and the problem is still there;


  • evtest for mic and heaphones reports them always connected (even if not).


  • I conclude that actually this is a hardware problem. I am going to replace the entire sound card, and I will update this post as soon as I have a final response.


SOLUTION (hardware problem):
Replacing the sound board fixed the problem (40 Euros for a new one from eBay).







share|improve this question


























    up vote
    2
    down vote

    favorite












    I have a problem with the audio in Ubuntu 17.10.
    No sound from speakers unless auto-mute from alsamixer is disabled. In that case sound goes to both speakers and headphones.



    All sound cards are installed, however, even when headphones are not connected the only available output remains headphones-internal audio.



    So far I did a fresh install of Ubuntu 17.10, run a live version of Ubuntu 16.04, 17.10, and Fedora, but no luck.



    All this makes me think of a harware failure, in particular that the switch of headphones output jack socket is not working as it should.
    I tried to gently clean it, but nothing. However, audio hardware failure is quite unlikely to happen (I hope at least).



    After each boot speakers are muted in alsamixer, unmuting them and increasing the volume produce sound from speakers, but of course the speakers are not automatically disabled when headphones are connected.



    Note that the audio worked properly with Ubuntu 17.04, and also with 17.10 (at least for a week), then suddenly stopped without updating anything.



    Machine: Lenovo Yoga 2 Pro.



    arecord -l
    **** Lista di CAPTURE dispositivi hardware ****
    scheda 1: PCH [HDA Intel PCH], dispositivo 0: ALC3239 Analog [ALC3239 Analog]
    Sottoperiferiche: 1/1
    Sottoperiferica #0: subdevice #0


    EDIT:
    Here the output for cat /proc/asound/card*/codec#*



    Moreover:



    • I just tried to run a live usb with Windows and the problem is still there;


    • evtest for mic and heaphones reports them always connected (even if not).


    • I conclude that actually this is a hardware problem. I am going to replace the entire sound card, and I will update this post as soon as I have a final response.


    SOLUTION (hardware problem):
    Replacing the sound board fixed the problem (40 Euros for a new one from eBay).







    share|improve this question
























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I have a problem with the audio in Ubuntu 17.10.
      No sound from speakers unless auto-mute from alsamixer is disabled. In that case sound goes to both speakers and headphones.



      All sound cards are installed, however, even when headphones are not connected the only available output remains headphones-internal audio.



      So far I did a fresh install of Ubuntu 17.10, run a live version of Ubuntu 16.04, 17.10, and Fedora, but no luck.



      All this makes me think of a harware failure, in particular that the switch of headphones output jack socket is not working as it should.
      I tried to gently clean it, but nothing. However, audio hardware failure is quite unlikely to happen (I hope at least).



      After each boot speakers are muted in alsamixer, unmuting them and increasing the volume produce sound from speakers, but of course the speakers are not automatically disabled when headphones are connected.



      Note that the audio worked properly with Ubuntu 17.04, and also with 17.10 (at least for a week), then suddenly stopped without updating anything.



      Machine: Lenovo Yoga 2 Pro.



      arecord -l
      **** Lista di CAPTURE dispositivi hardware ****
      scheda 1: PCH [HDA Intel PCH], dispositivo 0: ALC3239 Analog [ALC3239 Analog]
      Sottoperiferiche: 1/1
      Sottoperiferica #0: subdevice #0


      EDIT:
      Here the output for cat /proc/asound/card*/codec#*



      Moreover:



      • I just tried to run a live usb with Windows and the problem is still there;


      • evtest for mic and heaphones reports them always connected (even if not).


      • I conclude that actually this is a hardware problem. I am going to replace the entire sound card, and I will update this post as soon as I have a final response.


      SOLUTION (hardware problem):
      Replacing the sound board fixed the problem (40 Euros for a new one from eBay).







      share|improve this question














      I have a problem with the audio in Ubuntu 17.10.
      No sound from speakers unless auto-mute from alsamixer is disabled. In that case sound goes to both speakers and headphones.



      All sound cards are installed, however, even when headphones are not connected the only available output remains headphones-internal audio.



      So far I did a fresh install of Ubuntu 17.10, run a live version of Ubuntu 16.04, 17.10, and Fedora, but no luck.



      All this makes me think of a harware failure, in particular that the switch of headphones output jack socket is not working as it should.
      I tried to gently clean it, but nothing. However, audio hardware failure is quite unlikely to happen (I hope at least).



      After each boot speakers are muted in alsamixer, unmuting them and increasing the volume produce sound from speakers, but of course the speakers are not automatically disabled when headphones are connected.



      Note that the audio worked properly with Ubuntu 17.04, and also with 17.10 (at least for a week), then suddenly stopped without updating anything.



      Machine: Lenovo Yoga 2 Pro.



      arecord -l
      **** Lista di CAPTURE dispositivi hardware ****
      scheda 1: PCH [HDA Intel PCH], dispositivo 0: ALC3239 Analog [ALC3239 Analog]
      Sottoperiferiche: 1/1
      Sottoperiferica #0: subdevice #0


      EDIT:
      Here the output for cat /proc/asound/card*/codec#*



      Moreover:



      • I just tried to run a live usb with Windows and the problem is still there;


      • evtest for mic and heaphones reports them always connected (even if not).


      • I conclude that actually this is a hardware problem. I am going to replace the entire sound card, and I will update this post as soon as I have a final response.


      SOLUTION (hardware problem):
      Replacing the sound board fixed the problem (40 Euros for a new one from eBay).









      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 5 '17 at 7:15

























      asked Oct 29 '17 at 11:13









      Hamid Oskorouchi

      1314




      1314




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          Guess: The laptop BIOS is lying to ALSA, and giving it a wrong headphone jack codec node which always detects "connected".



          Look at your analog codec with



          cat /proc/asound/card*/codec#*


          and use hdajackretask from package alsa-tools-gui to correct this if it is true.



          Also see here for background information.



          I don't know why it happened "suddenly", and can't explain the "sudden" change, but that's the first place I'd look. It's probably unrelated to the distro you are using, and it might have been always broken, and your hardware "suddenly" decided to switch from "undetected" to "detected" for the unused node with open pins. Or something complete different.



          Edit



          The Pin Complex info provided by the BIOS looks ok (or at least not as jumbled as the "lying" ones I've seen), so maybe it's something else. Try the following: Run evtest as root, select (in turn) each device that corresponds to soundcard plug events (usually they have HDA Intel or something similar in the name), and plug in/out your headphone and see if you actually receive events. According to the codec, you should have at least two of those, one for the headphone (Node 0x21) and one for the mic (Node 0x19).



          Possibly the headphone/mic jack detection hardware is just broken. Or maybe something completely different.






          share|improve this answer






















          • Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
            – Hamid Oskorouchi
            Oct 30 '17 at 10:35










          • This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
            – dirkt
            Oct 30 '17 at 12:46

















          up vote
          -2
          down vote













          1. Check terminal.

          2. Run alsamixer.

          3. Make sure nothing is muted.

          4. And ALSO check that AUTOMUTE IS DISABLED.





          share|improve this answer






















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f401196%2fubuntu-no-sound-from-speakers-headphones-jack-detected-even-when-no-headphones%23new-answer', 'question_page');

            );

            Post as a guest






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote



            accepted










            Guess: The laptop BIOS is lying to ALSA, and giving it a wrong headphone jack codec node which always detects "connected".



            Look at your analog codec with



            cat /proc/asound/card*/codec#*


            and use hdajackretask from package alsa-tools-gui to correct this if it is true.



            Also see here for background information.



            I don't know why it happened "suddenly", and can't explain the "sudden" change, but that's the first place I'd look. It's probably unrelated to the distro you are using, and it might have been always broken, and your hardware "suddenly" decided to switch from "undetected" to "detected" for the unused node with open pins. Or something complete different.



            Edit



            The Pin Complex info provided by the BIOS looks ok (or at least not as jumbled as the "lying" ones I've seen), so maybe it's something else. Try the following: Run evtest as root, select (in turn) each device that corresponds to soundcard plug events (usually they have HDA Intel or something similar in the name), and plug in/out your headphone and see if you actually receive events. According to the codec, you should have at least two of those, one for the headphone (Node 0x21) and one for the mic (Node 0x19).



            Possibly the headphone/mic jack detection hardware is just broken. Or maybe something completely different.






            share|improve this answer






















            • Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
              – Hamid Oskorouchi
              Oct 30 '17 at 10:35










            • This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
              – dirkt
              Oct 30 '17 at 12:46














            up vote
            2
            down vote



            accepted










            Guess: The laptop BIOS is lying to ALSA, and giving it a wrong headphone jack codec node which always detects "connected".



            Look at your analog codec with



            cat /proc/asound/card*/codec#*


            and use hdajackretask from package alsa-tools-gui to correct this if it is true.



            Also see here for background information.



            I don't know why it happened "suddenly", and can't explain the "sudden" change, but that's the first place I'd look. It's probably unrelated to the distro you are using, and it might have been always broken, and your hardware "suddenly" decided to switch from "undetected" to "detected" for the unused node with open pins. Or something complete different.



            Edit



            The Pin Complex info provided by the BIOS looks ok (or at least not as jumbled as the "lying" ones I've seen), so maybe it's something else. Try the following: Run evtest as root, select (in turn) each device that corresponds to soundcard plug events (usually they have HDA Intel or something similar in the name), and plug in/out your headphone and see if you actually receive events. According to the codec, you should have at least two of those, one for the headphone (Node 0x21) and one for the mic (Node 0x19).



            Possibly the headphone/mic jack detection hardware is just broken. Or maybe something completely different.






            share|improve this answer






















            • Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
              – Hamid Oskorouchi
              Oct 30 '17 at 10:35










            • This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
              – dirkt
              Oct 30 '17 at 12:46












            up vote
            2
            down vote



            accepted







            up vote
            2
            down vote



            accepted






            Guess: The laptop BIOS is lying to ALSA, and giving it a wrong headphone jack codec node which always detects "connected".



            Look at your analog codec with



            cat /proc/asound/card*/codec#*


            and use hdajackretask from package alsa-tools-gui to correct this if it is true.



            Also see here for background information.



            I don't know why it happened "suddenly", and can't explain the "sudden" change, but that's the first place I'd look. It's probably unrelated to the distro you are using, and it might have been always broken, and your hardware "suddenly" decided to switch from "undetected" to "detected" for the unused node with open pins. Or something complete different.



            Edit



            The Pin Complex info provided by the BIOS looks ok (or at least not as jumbled as the "lying" ones I've seen), so maybe it's something else. Try the following: Run evtest as root, select (in turn) each device that corresponds to soundcard plug events (usually they have HDA Intel or something similar in the name), and plug in/out your headphone and see if you actually receive events. According to the codec, you should have at least two of those, one for the headphone (Node 0x21) and one for the mic (Node 0x19).



            Possibly the headphone/mic jack detection hardware is just broken. Or maybe something completely different.






            share|improve this answer














            Guess: The laptop BIOS is lying to ALSA, and giving it a wrong headphone jack codec node which always detects "connected".



            Look at your analog codec with



            cat /proc/asound/card*/codec#*


            and use hdajackretask from package alsa-tools-gui to correct this if it is true.



            Also see here for background information.



            I don't know why it happened "suddenly", and can't explain the "sudden" change, but that's the first place I'd look. It's probably unrelated to the distro you are using, and it might have been always broken, and your hardware "suddenly" decided to switch from "undetected" to "detected" for the unused node with open pins. Or something complete different.



            Edit



            The Pin Complex info provided by the BIOS looks ok (or at least not as jumbled as the "lying" ones I've seen), so maybe it's something else. Try the following: Run evtest as root, select (in turn) each device that corresponds to soundcard plug events (usually they have HDA Intel or something similar in the name), and plug in/out your headphone and see if you actually receive events. According to the codec, you should have at least two of those, one for the headphone (Node 0x21) and one for the mic (Node 0x19).



            Possibly the headphone/mic jack detection hardware is just broken. Or maybe something completely different.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Oct 30 '17 at 16:09

























            answered Oct 30 '17 at 8:16









            dirkt

            14.2k2931




            14.2k2931











            • Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
              – Hamid Oskorouchi
              Oct 30 '17 at 10:35










            • This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
              – dirkt
              Oct 30 '17 at 12:46
















            • Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
              – Hamid Oskorouchi
              Oct 30 '17 at 10:35










            • This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
              – dirkt
              Oct 30 '17 at 12:46















            Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
            – Hamid Oskorouchi
            Oct 30 '17 at 10:35




            Cool thanks, however solving the problem is not really easy even if I think your hint here is fundamental. So far I can see that the jack is not detected as the outpute of cat /proc/asound/card*/codec#* does not change with/without jack. However, I am a bit confused on how to get this solved using hdajackretask. Could you help me a bit?
            – Hamid Oskorouchi
            Oct 30 '17 at 10:35












            This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
            – dirkt
            Oct 30 '17 at 12:46




            This output is a codec description as graph of nodes, it's not supposed to contain the connection state. So it won't change with/without jack, those signals appear in the kernel input layer. If you can't make sense of the codec description, please put the output in a pastebin, and edit question with link.
            – dirkt
            Oct 30 '17 at 12:46












            up vote
            -2
            down vote













            1. Check terminal.

            2. Run alsamixer.

            3. Make sure nothing is muted.

            4. And ALSO check that AUTOMUTE IS DISABLED.





            share|improve this answer


























              up vote
              -2
              down vote













              1. Check terminal.

              2. Run alsamixer.

              3. Make sure nothing is muted.

              4. And ALSO check that AUTOMUTE IS DISABLED.





              share|improve this answer
























                up vote
                -2
                down vote










                up vote
                -2
                down vote









                1. Check terminal.

                2. Run alsamixer.

                3. Make sure nothing is muted.

                4. And ALSO check that AUTOMUTE IS DISABLED.





                share|improve this answer














                1. Check terminal.

                2. Run alsamixer.

                3. Make sure nothing is muted.

                4. And ALSO check that AUTOMUTE IS DISABLED.






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 24 '17 at 16:35









                Stephen Rauch

                3,248101227




                3,248101227










                answered Dec 24 '17 at 16:04









                Vina

                1




                1



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f401196%2fubuntu-no-sound-from-speakers-headphones-jack-detected-even-when-no-headphones%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?