No Audio on Acer Chromebook 14 under Ubuntu 17.10












1















This is a question about running Ubuntu on a Chromebook. I've taken this question to /r/chrubuntu and /r/galliumos, and I haven't gotten any help so far. Someone recommended I ask this question at AskUbuntu, so here goes:



I've installed Ubuntu 17.10 under chrx (dual-booting with Chrome OS). Everything seems to be working fine on my system except audio. The system doesn't appear to see my sound card. The only interface I have is Dummy Audio. arecord -l gives the following:



**** List of CAPTURE Hardware Devices ****
card 1: chtrt5650 [chtrt5650], device 0: Audio (*)
Subdevices: 1/1
Subdevice #0: subdevice #0


So, at most it seems my system is only finding the capture card, not the playback device. When logging in from a tty, I get tons of Audio Port: ASoC: No backend DAIs enabled for Audio Port messages. I've read about some braswell audio issues, and I found reynhout's fixes in Gallium, but from his documentation, they should have been implemented in kernel 4.11 or 4.12. uname -r is 4.13.0-16-generic, so I'm assuming they should already be there. If not, could someone give me some insight as to how to best implement those fixes under Ubuntu 17.10?



The machine is an Acer Chromebook 14 (CB3-431 / EDGAR). I know the sound card isn't dead because it works in Chrome OS.



Thank you in advance for any help you can provide. Cheers!










share|improve this question



























    1















    This is a question about running Ubuntu on a Chromebook. I've taken this question to /r/chrubuntu and /r/galliumos, and I haven't gotten any help so far. Someone recommended I ask this question at AskUbuntu, so here goes:



    I've installed Ubuntu 17.10 under chrx (dual-booting with Chrome OS). Everything seems to be working fine on my system except audio. The system doesn't appear to see my sound card. The only interface I have is Dummy Audio. arecord -l gives the following:



    **** List of CAPTURE Hardware Devices ****
    card 1: chtrt5650 [chtrt5650], device 0: Audio (*)
    Subdevices: 1/1
    Subdevice #0: subdevice #0


    So, at most it seems my system is only finding the capture card, not the playback device. When logging in from a tty, I get tons of Audio Port: ASoC: No backend DAIs enabled for Audio Port messages. I've read about some braswell audio issues, and I found reynhout's fixes in Gallium, but from his documentation, they should have been implemented in kernel 4.11 or 4.12. uname -r is 4.13.0-16-generic, so I'm assuming they should already be there. If not, could someone give me some insight as to how to best implement those fixes under Ubuntu 17.10?



    The machine is an Acer Chromebook 14 (CB3-431 / EDGAR). I know the sound card isn't dead because it works in Chrome OS.



    Thank you in advance for any help you can provide. Cheers!










    share|improve this question

























      1












      1








      1


      2






      This is a question about running Ubuntu on a Chromebook. I've taken this question to /r/chrubuntu and /r/galliumos, and I haven't gotten any help so far. Someone recommended I ask this question at AskUbuntu, so here goes:



      I've installed Ubuntu 17.10 under chrx (dual-booting with Chrome OS). Everything seems to be working fine on my system except audio. The system doesn't appear to see my sound card. The only interface I have is Dummy Audio. arecord -l gives the following:



      **** List of CAPTURE Hardware Devices ****
      card 1: chtrt5650 [chtrt5650], device 0: Audio (*)
      Subdevices: 1/1
      Subdevice #0: subdevice #0


      So, at most it seems my system is only finding the capture card, not the playback device. When logging in from a tty, I get tons of Audio Port: ASoC: No backend DAIs enabled for Audio Port messages. I've read about some braswell audio issues, and I found reynhout's fixes in Gallium, but from his documentation, they should have been implemented in kernel 4.11 or 4.12. uname -r is 4.13.0-16-generic, so I'm assuming they should already be there. If not, could someone give me some insight as to how to best implement those fixes under Ubuntu 17.10?



      The machine is an Acer Chromebook 14 (CB3-431 / EDGAR). I know the sound card isn't dead because it works in Chrome OS.



      Thank you in advance for any help you can provide. Cheers!










      share|improve this question














      This is a question about running Ubuntu on a Chromebook. I've taken this question to /r/chrubuntu and /r/galliumos, and I haven't gotten any help so far. Someone recommended I ask this question at AskUbuntu, so here goes:



      I've installed Ubuntu 17.10 under chrx (dual-booting with Chrome OS). Everything seems to be working fine on my system except audio. The system doesn't appear to see my sound card. The only interface I have is Dummy Audio. arecord -l gives the following:



      **** List of CAPTURE Hardware Devices ****
      card 1: chtrt5650 [chtrt5650], device 0: Audio (*)
      Subdevices: 1/1
      Subdevice #0: subdevice #0


      So, at most it seems my system is only finding the capture card, not the playback device. When logging in from a tty, I get tons of Audio Port: ASoC: No backend DAIs enabled for Audio Port messages. I've read about some braswell audio issues, and I found reynhout's fixes in Gallium, but from his documentation, they should have been implemented in kernel 4.11 or 4.12. uname -r is 4.13.0-16-generic, so I'm assuming they should already be there. If not, could someone give me some insight as to how to best implement those fixes under Ubuntu 17.10?



      The machine is an Acer Chromebook 14 (CB3-431 / EDGAR). I know the sound card isn't dead because it works in Chrome OS.



      Thank you in advance for any help you can provide. Cheers!







      sound pulseaudio alsa chromebook






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 7 '17 at 22:53









      James WaltersJames Walters

      612




      612






















          3 Answers
          3






          active

          oldest

          votes


















          0














          This is only a partial answer as I have not be able to get audio over hdmi to work, or test this except in a liveusb environment.



          In a ubuntu 17.10 liveusb environment run pgrep alsa to verify alsa is not running. Copy the asound.state file from a galliumos braswell install to /var/lib/alsa/asound.state. Then force reload alsa.



          pgrep alsa
          sudo cp /media/ubuntu/UUID/var/lib/alsa/asound.state /var/lib/alsa/asound.state
          sudo alsa force-reload


          Once completed the speakers can be tested from the sound mixer. I have included here a copy of the asound.state as found on my instance of galliumos for reference. Alternatively you may be able to use a copy of the asound.state file from chromeos.



          Once you have sound somewhat working running the following commands will instruct alsactl to attempt to initialize all devices to a default state. Then store the state and reload from that state.



          alsactl init
          sudo alsactl store --file /var/lib/alsa/asound.state
          sudo alsa force-reload





          share|improve this answer

































            0














            Unfortunately my reputation is too low to upvote J. Starnes answer just yet. But I performed his steps on an Acer Chromebook 14 (CB3-431 / EDGAR) running Kubuntu 17.10. Worked perfectly. Thank you J. Starnes!



            A side note that took a little bit of digging after I got the internal speakers working was when plugging in 3.5mm headphones into the jack, the sound card would switch to "Headphones" as expected however no sound would be produced. I found this thread https://ubuntuforums.org/showthread.php?t=1774627. I opened up the alsamixer in the terminal, hit F6 (Brightness Decrease button), selected the right card (chtrt5650 in my case), moved to "Headphone Channel" and hit the "M" key to unmute the channel. I'm sure there is another way to do this with the standard mixer but I was unable to find it.



            alsamixer
            F6
            ->
            M
            ESC





            share|improve this answer































              0














              This is a fix that I made, having compiled information from different sources. I would love to know if there is a way to fix this other than using this, but right now, this has been working for me. Hope it helps!






              share|improve this answer























                Your Answer








                StackExchange.ready(function() {
                var channelOptions = {
                tags: "".split(" "),
                id: "89"
                };
                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',
                autoActivateHeartbeat: false,
                convertImagesToLinks: true,
                noModals: true,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: 10,
                bindNavPrevention: true,
                postfix: "",
                imageUploader: {
                brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                allowUrls: true
                },
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                });


                }
                });














                draft saved

                draft discarded


















                StackExchange.ready(
                function () {
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f974073%2fno-audio-on-acer-chromebook-14-under-ubuntu-17-10%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                3 Answers
                3






                active

                oldest

                votes








                3 Answers
                3






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                0














                This is only a partial answer as I have not be able to get audio over hdmi to work, or test this except in a liveusb environment.



                In a ubuntu 17.10 liveusb environment run pgrep alsa to verify alsa is not running. Copy the asound.state file from a galliumos braswell install to /var/lib/alsa/asound.state. Then force reload alsa.



                pgrep alsa
                sudo cp /media/ubuntu/UUID/var/lib/alsa/asound.state /var/lib/alsa/asound.state
                sudo alsa force-reload


                Once completed the speakers can be tested from the sound mixer. I have included here a copy of the asound.state as found on my instance of galliumos for reference. Alternatively you may be able to use a copy of the asound.state file from chromeos.



                Once you have sound somewhat working running the following commands will instruct alsactl to attempt to initialize all devices to a default state. Then store the state and reload from that state.



                alsactl init
                sudo alsactl store --file /var/lib/alsa/asound.state
                sudo alsa force-reload





                share|improve this answer






























                  0














                  This is only a partial answer as I have not be able to get audio over hdmi to work, or test this except in a liveusb environment.



                  In a ubuntu 17.10 liveusb environment run pgrep alsa to verify alsa is not running. Copy the asound.state file from a galliumos braswell install to /var/lib/alsa/asound.state. Then force reload alsa.



                  pgrep alsa
                  sudo cp /media/ubuntu/UUID/var/lib/alsa/asound.state /var/lib/alsa/asound.state
                  sudo alsa force-reload


                  Once completed the speakers can be tested from the sound mixer. I have included here a copy of the asound.state as found on my instance of galliumos for reference. Alternatively you may be able to use a copy of the asound.state file from chromeos.



                  Once you have sound somewhat working running the following commands will instruct alsactl to attempt to initialize all devices to a default state. Then store the state and reload from that state.



                  alsactl init
                  sudo alsactl store --file /var/lib/alsa/asound.state
                  sudo alsa force-reload





                  share|improve this answer




























                    0












                    0








                    0







                    This is only a partial answer as I have not be able to get audio over hdmi to work, or test this except in a liveusb environment.



                    In a ubuntu 17.10 liveusb environment run pgrep alsa to verify alsa is not running. Copy the asound.state file from a galliumos braswell install to /var/lib/alsa/asound.state. Then force reload alsa.



                    pgrep alsa
                    sudo cp /media/ubuntu/UUID/var/lib/alsa/asound.state /var/lib/alsa/asound.state
                    sudo alsa force-reload


                    Once completed the speakers can be tested from the sound mixer. I have included here a copy of the asound.state as found on my instance of galliumos for reference. Alternatively you may be able to use a copy of the asound.state file from chromeos.



                    Once you have sound somewhat working running the following commands will instruct alsactl to attempt to initialize all devices to a default state. Then store the state and reload from that state.



                    alsactl init
                    sudo alsactl store --file /var/lib/alsa/asound.state
                    sudo alsa force-reload





                    share|improve this answer















                    This is only a partial answer as I have not be able to get audio over hdmi to work, or test this except in a liveusb environment.



                    In a ubuntu 17.10 liveusb environment run pgrep alsa to verify alsa is not running. Copy the asound.state file from a galliumos braswell install to /var/lib/alsa/asound.state. Then force reload alsa.



                    pgrep alsa
                    sudo cp /media/ubuntu/UUID/var/lib/alsa/asound.state /var/lib/alsa/asound.state
                    sudo alsa force-reload


                    Once completed the speakers can be tested from the sound mixer. I have included here a copy of the asound.state as found on my instance of galliumos for reference. Alternatively you may be able to use a copy of the asound.state file from chromeos.



                    Once you have sound somewhat working running the following commands will instruct alsactl to attempt to initialize all devices to a default state. Then store the state and reload from that state.



                    alsactl init
                    sudo alsactl store --file /var/lib/alsa/asound.state
                    sudo alsa force-reload






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Nov 21 '17 at 16:43

























                    answered Nov 21 '17 at 6:51









                    J. StarnesJ. Starnes

                    1,446416




                    1,446416

























                        0














                        Unfortunately my reputation is too low to upvote J. Starnes answer just yet. But I performed his steps on an Acer Chromebook 14 (CB3-431 / EDGAR) running Kubuntu 17.10. Worked perfectly. Thank you J. Starnes!



                        A side note that took a little bit of digging after I got the internal speakers working was when plugging in 3.5mm headphones into the jack, the sound card would switch to "Headphones" as expected however no sound would be produced. I found this thread https://ubuntuforums.org/showthread.php?t=1774627. I opened up the alsamixer in the terminal, hit F6 (Brightness Decrease button), selected the right card (chtrt5650 in my case), moved to "Headphone Channel" and hit the "M" key to unmute the channel. I'm sure there is another way to do this with the standard mixer but I was unable to find it.



                        alsamixer
                        F6
                        ->
                        M
                        ESC





                        share|improve this answer




























                          0














                          Unfortunately my reputation is too low to upvote J. Starnes answer just yet. But I performed his steps on an Acer Chromebook 14 (CB3-431 / EDGAR) running Kubuntu 17.10. Worked perfectly. Thank you J. Starnes!



                          A side note that took a little bit of digging after I got the internal speakers working was when plugging in 3.5mm headphones into the jack, the sound card would switch to "Headphones" as expected however no sound would be produced. I found this thread https://ubuntuforums.org/showthread.php?t=1774627. I opened up the alsamixer in the terminal, hit F6 (Brightness Decrease button), selected the right card (chtrt5650 in my case), moved to "Headphone Channel" and hit the "M" key to unmute the channel. I'm sure there is another way to do this with the standard mixer but I was unable to find it.



                          alsamixer
                          F6
                          ->
                          M
                          ESC





                          share|improve this answer


























                            0












                            0








                            0







                            Unfortunately my reputation is too low to upvote J. Starnes answer just yet. But I performed his steps on an Acer Chromebook 14 (CB3-431 / EDGAR) running Kubuntu 17.10. Worked perfectly. Thank you J. Starnes!



                            A side note that took a little bit of digging after I got the internal speakers working was when plugging in 3.5mm headphones into the jack, the sound card would switch to "Headphones" as expected however no sound would be produced. I found this thread https://ubuntuforums.org/showthread.php?t=1774627. I opened up the alsamixer in the terminal, hit F6 (Brightness Decrease button), selected the right card (chtrt5650 in my case), moved to "Headphone Channel" and hit the "M" key to unmute the channel. I'm sure there is another way to do this with the standard mixer but I was unable to find it.



                            alsamixer
                            F6
                            ->
                            M
                            ESC





                            share|improve this answer













                            Unfortunately my reputation is too low to upvote J. Starnes answer just yet. But I performed his steps on an Acer Chromebook 14 (CB3-431 / EDGAR) running Kubuntu 17.10. Worked perfectly. Thank you J. Starnes!



                            A side note that took a little bit of digging after I got the internal speakers working was when plugging in 3.5mm headphones into the jack, the sound card would switch to "Headphones" as expected however no sound would be produced. I found this thread https://ubuntuforums.org/showthread.php?t=1774627. I opened up the alsamixer in the terminal, hit F6 (Brightness Decrease button), selected the right card (chtrt5650 in my case), moved to "Headphone Channel" and hit the "M" key to unmute the channel. I'm sure there is another way to do this with the standard mixer but I was unable to find it.



                            alsamixer
                            F6
                            ->
                            M
                            ESC






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Mar 29 '18 at 19:52









                            Austin BaccusAustin Baccus

                            12




                            12























                                0














                                This is a fix that I made, having compiled information from different sources. I would love to know if there is a way to fix this other than using this, but right now, this has been working for me. Hope it helps!






                                share|improve this answer




























                                  0














                                  This is a fix that I made, having compiled information from different sources. I would love to know if there is a way to fix this other than using this, but right now, this has been working for me. Hope it helps!






                                  share|improve this answer


























                                    0












                                    0








                                    0







                                    This is a fix that I made, having compiled information from different sources. I would love to know if there is a way to fix this other than using this, but right now, this has been working for me. Hope it helps!






                                    share|improve this answer













                                    This is a fix that I made, having compiled information from different sources. I would love to know if there is a way to fix this other than using this, but right now, this has been working for me. Hope it helps!







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Apr 23 '18 at 3:23









                                    bliutwobliutwo

                                    1




                                    1






























                                        draft saved

                                        draft discarded




















































                                        Thanks for contributing an answer to Ask Ubuntu!


                                        • Please be sure to answer the question. Provide details and share your research!

                                        But avoid



                                        • Asking for help, clarification, or responding to other answers.

                                        • Making statements based on opinion; back them up with references or personal experience.


                                        To learn more, see our tips on writing great answers.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function () {
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f974073%2fno-audio-on-acer-chromebook-14-under-ubuntu-17-10%23new-answer', 'question_page');
                                        }
                                        );

                                        Post as a guest















                                        Required, but never shown





















































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown

































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown







                                        Popular posts from this blog

                                        flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                                        Mangá

                                        Eduardo VII do Reino Unido