Touchpad under 16.04 not working











up vote
12
down vote

favorite
8












I'm new to Ubuntu and just recently installed the Version 16.04
My Touchpad is not working at all and it seems as if it is not detected.
The USB Mouse however is working perfect.
I'd like to use the Touchpad though.



Is there a way to get it working?



I'm using a MEDION akoya E5218 notebook.



I did not disable it. I tried Fn+F6.










share|improve this question




















  • 1




    Maybe you disabled it. Try FN+F6
    – Motte001
    Apr 27 '16 at 15:21










  • in settings menu click on mouse and touch pad then choose "tap to click" option
    – guest
    Aug 5 '16 at 19:32










  • Only command worked for me sudo modprobe -r psmouse sudo modprobe psmouse proto=imps
    – raj
    Jan 15 '17 at 4:38










  • @Motte001 this is what happened to me. In my case, it is Fn+F7, but in general it depends on the keyboard layout. Luckily mine is drawn onto my keyboard.
    – scottlittle
    Nov 12 '17 at 0:33















up vote
12
down vote

favorite
8












I'm new to Ubuntu and just recently installed the Version 16.04
My Touchpad is not working at all and it seems as if it is not detected.
The USB Mouse however is working perfect.
I'd like to use the Touchpad though.



Is there a way to get it working?



I'm using a MEDION akoya E5218 notebook.



I did not disable it. I tried Fn+F6.










share|improve this question




















  • 1




    Maybe you disabled it. Try FN+F6
    – Motte001
    Apr 27 '16 at 15:21










  • in settings menu click on mouse and touch pad then choose "tap to click" option
    – guest
    Aug 5 '16 at 19:32










  • Only command worked for me sudo modprobe -r psmouse sudo modprobe psmouse proto=imps
    – raj
    Jan 15 '17 at 4:38










  • @Motte001 this is what happened to me. In my case, it is Fn+F7, but in general it depends on the keyboard layout. Luckily mine is drawn onto my keyboard.
    – scottlittle
    Nov 12 '17 at 0:33













up vote
12
down vote

favorite
8









up vote
12
down vote

favorite
8






8





I'm new to Ubuntu and just recently installed the Version 16.04
My Touchpad is not working at all and it seems as if it is not detected.
The USB Mouse however is working perfect.
I'd like to use the Touchpad though.



Is there a way to get it working?



I'm using a MEDION akoya E5218 notebook.



I did not disable it. I tried Fn+F6.










share|improve this question















I'm new to Ubuntu and just recently installed the Version 16.04
My Touchpad is not working at all and it seems as if it is not detected.
The USB Mouse however is working perfect.
I'd like to use the Touchpad though.



Is there a way to get it working?



I'm using a MEDION akoya E5218 notebook.



I did not disable it. I tried Fn+F6.







touchpad 16.04






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 3 '17 at 8:34









NeoTheThird

794528




794528










asked Apr 27 '16 at 13:40









B. Harle

1422310




1422310








  • 1




    Maybe you disabled it. Try FN+F6
    – Motte001
    Apr 27 '16 at 15:21










  • in settings menu click on mouse and touch pad then choose "tap to click" option
    – guest
    Aug 5 '16 at 19:32










  • Only command worked for me sudo modprobe -r psmouse sudo modprobe psmouse proto=imps
    – raj
    Jan 15 '17 at 4:38










  • @Motte001 this is what happened to me. In my case, it is Fn+F7, but in general it depends on the keyboard layout. Luckily mine is drawn onto my keyboard.
    – scottlittle
    Nov 12 '17 at 0:33














  • 1




    Maybe you disabled it. Try FN+F6
    – Motte001
    Apr 27 '16 at 15:21










  • in settings menu click on mouse and touch pad then choose "tap to click" option
    – guest
    Aug 5 '16 at 19:32










  • Only command worked for me sudo modprobe -r psmouse sudo modprobe psmouse proto=imps
    – raj
    Jan 15 '17 at 4:38










  • @Motte001 this is what happened to me. In my case, it is Fn+F7, but in general it depends on the keyboard layout. Luckily mine is drawn onto my keyboard.
    – scottlittle
    Nov 12 '17 at 0:33








1




1




Maybe you disabled it. Try FN+F6
– Motte001
Apr 27 '16 at 15:21




Maybe you disabled it. Try FN+F6
– Motte001
Apr 27 '16 at 15:21












in settings menu click on mouse and touch pad then choose "tap to click" option
– guest
Aug 5 '16 at 19:32




in settings menu click on mouse and touch pad then choose "tap to click" option
– guest
Aug 5 '16 at 19:32












Only command worked for me sudo modprobe -r psmouse sudo modprobe psmouse proto=imps
– raj
Jan 15 '17 at 4:38




Only command worked for me sudo modprobe -r psmouse sudo modprobe psmouse proto=imps
– raj
Jan 15 '17 at 4:38












@Motte001 this is what happened to me. In my case, it is Fn+F7, but in general it depends on the keyboard layout. Luckily mine is drawn onto my keyboard.
– scottlittle
Nov 12 '17 at 0:33




@Motte001 this is what happened to me. In my case, it is Fn+F7, but in general it depends on the keyboard layout. Luckily mine is drawn onto my keyboard.
– scottlittle
Nov 12 '17 at 0:33










6 Answers
6






active

oldest

votes

















up vote
6
down vote



accepted










If you type



less /proc/bus/input/devices


do you see a touchpad anywhere in that list? If not, then there is no support for your touchpad in the kernel and you are pretty much out of luck, at least for now. If your touchpad is detected then the problem is elsewhere. Typing



xinput


will show if the X server has detected your touchpad. If your touchpad is in that list it may be possible to modify the X config to make it work






share|improve this answer





















  • Can you explain How to change the xinput value? My touchpad is listed there.
    – Kolappan Nathan
    Aug 26 '16 at 17:50










  • @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
    – Kolappan Nathan
    Oct 1 '16 at 9:14












  • @KolappanNathan: Sorry, my oversight. Never mind then.
    – David Foerster
    Oct 1 '16 at 9:21










  • Touchpad is not listed.. Is there a driver I can install?
    – moonstar
    Dec 28 '16 at 7:57


















up vote
7
down vote













Follow these instructions to fix the issue,



modify grub file,



sudo nano /etc/default/grub


replace



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


with



GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash"


Save the file and then update grub using,



sudo update-grub command.
and then restart your OS,



sudo shutdown -r now





share|improve this answer






























    up vote
    6
    down vote













    My touchpad sometimes gets stuck (especially on a fresh boot).



    This makes it work again:



    sudo rmmod i2c_hid
    sudo modprobe i2c_hid





    share|improve this answer





















    • You're awesome!
      – Pankaj Garg
      Apr 12 at 8:26










    • It helps, but how does it work?
      – Josef Klimuk
      May 7 at 5:10










    • It's just reloading the i2c_hid module.
      – slow
      May 7 at 13:56


















    up vote
    3
    down vote















    1. Edit GRUB



      sudo -H gedit /etc/default/grub


      In the open window edit line



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


      It should look this way



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"


      Save file and run



      sudo update-grub



    2. Prevent i2c_hid from loading



      echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
      sudo depmod -a
      sudo update-initramfs -u
      echo "synaptics_i2c" | sudo tee -a /etc/modules


    3. Reboot.



    What it does is, it removes the synaptics hid drivers from the blacklist and allows them to be loaded at the initialization of the RAM file system, allowing your touch pad to work at boot






    share|improve this answer























    • Don't use sudo for graphical applications; use gksudo instead!
      – David Foerster
      Oct 1 '16 at 8:53












    • this solution worked for me. thanks
      – Fatemeh Karimi
      Jan 22 at 9:56










    • @FatemehKarimi Glad it worked for you :)
      – Pranit Raje
      Jan 22 at 9:58










    • @DavidFoerster Thanks for the suggestion :)
      – Pranit Raje
      Jan 22 at 9:59


















    up vote
    0
    down vote













    Perhaps you need to upgrade your kernel. I find that Ubuntu kernels below 4.5 don't find my Elantech touchpad by default.



    You can upgrade to a newer version, like 4.5 using the instructions found here:



    How to update kernel to the latest mainline version without any Distro-upgrade?






    share|improve this answer






























      up vote
      0
      down vote













      For my Akoya laptop this worked fine:



      1. Try the following:




      • reboot to the grub menu and type e (hope it is right, --> you have to edit your command line)


      • in the line starting with GRUB_CMDLINE_LINUX_DEFAULT
        insert the following kernel properties:



        "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


      • if your touchpad is now working, go to point 2.


      2. Permanent Grub modification





      • Make a backup of your grub file:



        sudo cp /etc/default/grub /etc/default/grub.backup 



      • Edit your grub file:



        sudo nano /etc/default/grub 



      • Now add the following paramters into the line starting with GRUB_CMDLINE_LINUX_DEFAULT :



        "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


      • Save the file



      • Update your grub



        sudo update-grub


      • Reboot.







      share|improve this answer






















        protected by Community Oct 13 '16 at 15:55



        Thank you for your interest in this question.
        Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



        Would you like to answer one of these unanswered questions instead?














        6 Answers
        6






        active

        oldest

        votes








        6 Answers
        6






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes








        up vote
        6
        down vote



        accepted










        If you type



        less /proc/bus/input/devices


        do you see a touchpad anywhere in that list? If not, then there is no support for your touchpad in the kernel and you are pretty much out of luck, at least for now. If your touchpad is detected then the problem is elsewhere. Typing



        xinput


        will show if the X server has detected your touchpad. If your touchpad is in that list it may be possible to modify the X config to make it work






        share|improve this answer





















        • Can you explain How to change the xinput value? My touchpad is listed there.
          – Kolappan Nathan
          Aug 26 '16 at 17:50










        • @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
          – Kolappan Nathan
          Oct 1 '16 at 9:14












        • @KolappanNathan: Sorry, my oversight. Never mind then.
          – David Foerster
          Oct 1 '16 at 9:21










        • Touchpad is not listed.. Is there a driver I can install?
          – moonstar
          Dec 28 '16 at 7:57















        up vote
        6
        down vote



        accepted










        If you type



        less /proc/bus/input/devices


        do you see a touchpad anywhere in that list? If not, then there is no support for your touchpad in the kernel and you are pretty much out of luck, at least for now. If your touchpad is detected then the problem is elsewhere. Typing



        xinput


        will show if the X server has detected your touchpad. If your touchpad is in that list it may be possible to modify the X config to make it work






        share|improve this answer





















        • Can you explain How to change the xinput value? My touchpad is listed there.
          – Kolappan Nathan
          Aug 26 '16 at 17:50










        • @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
          – Kolappan Nathan
          Oct 1 '16 at 9:14












        • @KolappanNathan: Sorry, my oversight. Never mind then.
          – David Foerster
          Oct 1 '16 at 9:21










        • Touchpad is not listed.. Is there a driver I can install?
          – moonstar
          Dec 28 '16 at 7:57













        up vote
        6
        down vote



        accepted







        up vote
        6
        down vote



        accepted






        If you type



        less /proc/bus/input/devices


        do you see a touchpad anywhere in that list? If not, then there is no support for your touchpad in the kernel and you are pretty much out of luck, at least for now. If your touchpad is detected then the problem is elsewhere. Typing



        xinput


        will show if the X server has detected your touchpad. If your touchpad is in that list it may be possible to modify the X config to make it work






        share|improve this answer












        If you type



        less /proc/bus/input/devices


        do you see a touchpad anywhere in that list? If not, then there is no support for your touchpad in the kernel and you are pretty much out of luck, at least for now. If your touchpad is detected then the problem is elsewhere. Typing



        xinput


        will show if the X server has detected your touchpad. If your touchpad is in that list it may be possible to modify the X config to make it work







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 28 '16 at 0:53









        Buddy Palumbo

        1483




        1483












        • Can you explain How to change the xinput value? My touchpad is listed there.
          – Kolappan Nathan
          Aug 26 '16 at 17:50










        • @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
          – Kolappan Nathan
          Oct 1 '16 at 9:14












        • @KolappanNathan: Sorry, my oversight. Never mind then.
          – David Foerster
          Oct 1 '16 at 9:21










        • Touchpad is not listed.. Is there a driver I can install?
          – moonstar
          Dec 28 '16 at 7:57


















        • Can you explain How to change the xinput value? My touchpad is listed there.
          – Kolappan Nathan
          Aug 26 '16 at 17:50










        • @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
          – Kolappan Nathan
          Oct 1 '16 at 9:14












        • @KolappanNathan: Sorry, my oversight. Never mind then.
          – David Foerster
          Oct 1 '16 at 9:21










        • Touchpad is not listed.. Is there a driver I can install?
          – moonstar
          Dec 28 '16 at 7:57
















        Can you explain How to change the xinput value? My touchpad is listed there.
        – Kolappan Nathan
        Aug 26 '16 at 17:50




        Can you explain How to change the xinput value? My touchpad is listed there.
        – Kolappan Nathan
        Aug 26 '16 at 17:50












        @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
        – Kolappan Nathan
        Oct 1 '16 at 9:14






        @DavidFoerster It is not my question. I faced a similar problem. So I commented on the accepted answer to get more details. The answer said we can modify x config value to fix things. I was asking him some detailed steps or reference links. Again, It is not my question.
        – Kolappan Nathan
        Oct 1 '16 at 9:14














        @KolappanNathan: Sorry, my oversight. Never mind then.
        – David Foerster
        Oct 1 '16 at 9:21




        @KolappanNathan: Sorry, my oversight. Never mind then.
        – David Foerster
        Oct 1 '16 at 9:21












        Touchpad is not listed.. Is there a driver I can install?
        – moonstar
        Dec 28 '16 at 7:57




        Touchpad is not listed.. Is there a driver I can install?
        – moonstar
        Dec 28 '16 at 7:57












        up vote
        7
        down vote













        Follow these instructions to fix the issue,



        modify grub file,



        sudo nano /etc/default/grub


        replace



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


        with



        GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash"


        Save the file and then update grub using,



        sudo update-grub command.
        and then restart your OS,



        sudo shutdown -r now





        share|improve this answer



























          up vote
          7
          down vote













          Follow these instructions to fix the issue,



          modify grub file,



          sudo nano /etc/default/grub


          replace



          GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


          with



          GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash"


          Save the file and then update grub using,



          sudo update-grub command.
          and then restart your OS,



          sudo shutdown -r now





          share|improve this answer

























            up vote
            7
            down vote










            up vote
            7
            down vote









            Follow these instructions to fix the issue,



            modify grub file,



            sudo nano /etc/default/grub


            replace



            GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


            with



            GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash"


            Save the file and then update grub using,



            sudo update-grub command.
            and then restart your OS,



            sudo shutdown -r now





            share|improve this answer














            Follow these instructions to fix the issue,



            modify grub file,



            sudo nano /etc/default/grub


            replace



            GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


            with



            GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash"


            Save the file and then update grub using,



            sudo update-grub command.
            and then restart your OS,



            sudo shutdown -r now






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Sep 26 '17 at 6:05

























            answered Sep 14 '16 at 4:13









            Sufiyan Ghori

            46058




            46058






















                up vote
                6
                down vote













                My touchpad sometimes gets stuck (especially on a fresh boot).



                This makes it work again:



                sudo rmmod i2c_hid
                sudo modprobe i2c_hid





                share|improve this answer





















                • You're awesome!
                  – Pankaj Garg
                  Apr 12 at 8:26










                • It helps, but how does it work?
                  – Josef Klimuk
                  May 7 at 5:10










                • It's just reloading the i2c_hid module.
                  – slow
                  May 7 at 13:56















                up vote
                6
                down vote













                My touchpad sometimes gets stuck (especially on a fresh boot).



                This makes it work again:



                sudo rmmod i2c_hid
                sudo modprobe i2c_hid





                share|improve this answer





















                • You're awesome!
                  – Pankaj Garg
                  Apr 12 at 8:26










                • It helps, but how does it work?
                  – Josef Klimuk
                  May 7 at 5:10










                • It's just reloading the i2c_hid module.
                  – slow
                  May 7 at 13:56













                up vote
                6
                down vote










                up vote
                6
                down vote









                My touchpad sometimes gets stuck (especially on a fresh boot).



                This makes it work again:



                sudo rmmod i2c_hid
                sudo modprobe i2c_hid





                share|improve this answer












                My touchpad sometimes gets stuck (especially on a fresh boot).



                This makes it work again:



                sudo rmmod i2c_hid
                sudo modprobe i2c_hid






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 23 '17 at 20:06









                slow

                25123




                25123












                • You're awesome!
                  – Pankaj Garg
                  Apr 12 at 8:26










                • It helps, but how does it work?
                  – Josef Klimuk
                  May 7 at 5:10










                • It's just reloading the i2c_hid module.
                  – slow
                  May 7 at 13:56


















                • You're awesome!
                  – Pankaj Garg
                  Apr 12 at 8:26










                • It helps, but how does it work?
                  – Josef Klimuk
                  May 7 at 5:10










                • It's just reloading the i2c_hid module.
                  – slow
                  May 7 at 13:56
















                You're awesome!
                – Pankaj Garg
                Apr 12 at 8:26




                You're awesome!
                – Pankaj Garg
                Apr 12 at 8:26












                It helps, but how does it work?
                – Josef Klimuk
                May 7 at 5:10




                It helps, but how does it work?
                – Josef Klimuk
                May 7 at 5:10












                It's just reloading the i2c_hid module.
                – slow
                May 7 at 13:56




                It's just reloading the i2c_hid module.
                – slow
                May 7 at 13:56










                up vote
                3
                down vote















                1. Edit GRUB



                  sudo -H gedit /etc/default/grub


                  In the open window edit line



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


                  It should look this way



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"


                  Save file and run



                  sudo update-grub



                2. Prevent i2c_hid from loading



                  echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
                  sudo depmod -a
                  sudo update-initramfs -u
                  echo "synaptics_i2c" | sudo tee -a /etc/modules


                3. Reboot.



                What it does is, it removes the synaptics hid drivers from the blacklist and allows them to be loaded at the initialization of the RAM file system, allowing your touch pad to work at boot






                share|improve this answer























                • Don't use sudo for graphical applications; use gksudo instead!
                  – David Foerster
                  Oct 1 '16 at 8:53












                • this solution worked for me. thanks
                  – Fatemeh Karimi
                  Jan 22 at 9:56










                • @FatemehKarimi Glad it worked for you :)
                  – Pranit Raje
                  Jan 22 at 9:58










                • @DavidFoerster Thanks for the suggestion :)
                  – Pranit Raje
                  Jan 22 at 9:59















                up vote
                3
                down vote















                1. Edit GRUB



                  sudo -H gedit /etc/default/grub


                  In the open window edit line



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


                  It should look this way



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"


                  Save file and run



                  sudo update-grub



                2. Prevent i2c_hid from loading



                  echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
                  sudo depmod -a
                  sudo update-initramfs -u
                  echo "synaptics_i2c" | sudo tee -a /etc/modules


                3. Reboot.



                What it does is, it removes the synaptics hid drivers from the blacklist and allows them to be loaded at the initialization of the RAM file system, allowing your touch pad to work at boot






                share|improve this answer























                • Don't use sudo for graphical applications; use gksudo instead!
                  – David Foerster
                  Oct 1 '16 at 8:53












                • this solution worked for me. thanks
                  – Fatemeh Karimi
                  Jan 22 at 9:56










                • @FatemehKarimi Glad it worked for you :)
                  – Pranit Raje
                  Jan 22 at 9:58










                • @DavidFoerster Thanks for the suggestion :)
                  – Pranit Raje
                  Jan 22 at 9:59













                up vote
                3
                down vote










                up vote
                3
                down vote











                1. Edit GRUB



                  sudo -H gedit /etc/default/grub


                  In the open window edit line



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


                  It should look this way



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"


                  Save file and run



                  sudo update-grub



                2. Prevent i2c_hid from loading



                  echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
                  sudo depmod -a
                  sudo update-initramfs -u
                  echo "synaptics_i2c" | sudo tee -a /etc/modules


                3. Reboot.



                What it does is, it removes the synaptics hid drivers from the blacklist and allows them to be loaded at the initialization of the RAM file system, allowing your touch pad to work at boot






                share|improve this answer
















                1. Edit GRUB



                  sudo -H gedit /etc/default/grub


                  In the open window edit line



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


                  It should look this way



                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"


                  Save file and run



                  sudo update-grub



                2. Prevent i2c_hid from loading



                  echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
                  sudo depmod -a
                  sudo update-initramfs -u
                  echo "synaptics_i2c" | sudo tee -a /etc/modules


                3. Reboot.



                What it does is, it removes the synaptics hid drivers from the blacklist and allows them to be loaded at the initialization of the RAM file system, allowing your touch pad to work at boot







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Oct 1 '16 at 9:06









                Thomas

                3,49081427




                3,49081427










                answered Oct 1 '16 at 7:21









                Pranit Raje

                315




                315












                • Don't use sudo for graphical applications; use gksudo instead!
                  – David Foerster
                  Oct 1 '16 at 8:53












                • this solution worked for me. thanks
                  – Fatemeh Karimi
                  Jan 22 at 9:56










                • @FatemehKarimi Glad it worked for you :)
                  – Pranit Raje
                  Jan 22 at 9:58










                • @DavidFoerster Thanks for the suggestion :)
                  – Pranit Raje
                  Jan 22 at 9:59


















                • Don't use sudo for graphical applications; use gksudo instead!
                  – David Foerster
                  Oct 1 '16 at 8:53












                • this solution worked for me. thanks
                  – Fatemeh Karimi
                  Jan 22 at 9:56










                • @FatemehKarimi Glad it worked for you :)
                  – Pranit Raje
                  Jan 22 at 9:58










                • @DavidFoerster Thanks for the suggestion :)
                  – Pranit Raje
                  Jan 22 at 9:59
















                Don't use sudo for graphical applications; use gksudo instead!
                – David Foerster
                Oct 1 '16 at 8:53






                Don't use sudo for graphical applications; use gksudo instead!
                – David Foerster
                Oct 1 '16 at 8:53














                this solution worked for me. thanks
                – Fatemeh Karimi
                Jan 22 at 9:56




                this solution worked for me. thanks
                – Fatemeh Karimi
                Jan 22 at 9:56












                @FatemehKarimi Glad it worked for you :)
                – Pranit Raje
                Jan 22 at 9:58




                @FatemehKarimi Glad it worked for you :)
                – Pranit Raje
                Jan 22 at 9:58












                @DavidFoerster Thanks for the suggestion :)
                – Pranit Raje
                Jan 22 at 9:59




                @DavidFoerster Thanks for the suggestion :)
                – Pranit Raje
                Jan 22 at 9:59










                up vote
                0
                down vote













                Perhaps you need to upgrade your kernel. I find that Ubuntu kernels below 4.5 don't find my Elantech touchpad by default.



                You can upgrade to a newer version, like 4.5 using the instructions found here:



                How to update kernel to the latest mainline version without any Distro-upgrade?






                share|improve this answer



























                  up vote
                  0
                  down vote













                  Perhaps you need to upgrade your kernel. I find that Ubuntu kernels below 4.5 don't find my Elantech touchpad by default.



                  You can upgrade to a newer version, like 4.5 using the instructions found here:



                  How to update kernel to the latest mainline version without any Distro-upgrade?






                  share|improve this answer

























                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    Perhaps you need to upgrade your kernel. I find that Ubuntu kernels below 4.5 don't find my Elantech touchpad by default.



                    You can upgrade to a newer version, like 4.5 using the instructions found here:



                    How to update kernel to the latest mainline version without any Distro-upgrade?






                    share|improve this answer














                    Perhaps you need to upgrade your kernel. I find that Ubuntu kernels below 4.5 don't find my Elantech touchpad by default.



                    You can upgrade to a newer version, like 4.5 using the instructions found here:



                    How to update kernel to the latest mainline version without any Distro-upgrade?







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Apr 13 '17 at 12:23









                    Community

                    1




                    1










                    answered Mar 20 '17 at 5:09









                    geru

                    565




                    565






















                        up vote
                        0
                        down vote













                        For my Akoya laptop this worked fine:



                        1. Try the following:




                        • reboot to the grub menu and type e (hope it is right, --> you have to edit your command line)


                        • in the line starting with GRUB_CMDLINE_LINUX_DEFAULT
                          insert the following kernel properties:



                          "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                        • if your touchpad is now working, go to point 2.


                        2. Permanent Grub modification





                        • Make a backup of your grub file:



                          sudo cp /etc/default/grub /etc/default/grub.backup 



                        • Edit your grub file:



                          sudo nano /etc/default/grub 



                        • Now add the following paramters into the line starting with GRUB_CMDLINE_LINUX_DEFAULT :



                          "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                        • Save the file



                        • Update your grub



                          sudo update-grub


                        • Reboot.







                        share|improve this answer



























                          up vote
                          0
                          down vote













                          For my Akoya laptop this worked fine:



                          1. Try the following:




                          • reboot to the grub menu and type e (hope it is right, --> you have to edit your command line)


                          • in the line starting with GRUB_CMDLINE_LINUX_DEFAULT
                            insert the following kernel properties:



                            "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                          • if your touchpad is now working, go to point 2.


                          2. Permanent Grub modification





                          • Make a backup of your grub file:



                            sudo cp /etc/default/grub /etc/default/grub.backup 



                          • Edit your grub file:



                            sudo nano /etc/default/grub 



                          • Now add the following paramters into the line starting with GRUB_CMDLINE_LINUX_DEFAULT :



                            "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                          • Save the file



                          • Update your grub



                            sudo update-grub


                          • Reboot.







                          share|improve this answer

























                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            For my Akoya laptop this worked fine:



                            1. Try the following:




                            • reboot to the grub menu and type e (hope it is right, --> you have to edit your command line)


                            • in the line starting with GRUB_CMDLINE_LINUX_DEFAULT
                              insert the following kernel properties:



                              "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                            • if your touchpad is now working, go to point 2.


                            2. Permanent Grub modification





                            • Make a backup of your grub file:



                              sudo cp /etc/default/grub /etc/default/grub.backup 



                            • Edit your grub file:



                              sudo nano /etc/default/grub 



                            • Now add the following paramters into the line starting with GRUB_CMDLINE_LINUX_DEFAULT :



                              "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                            • Save the file



                            • Update your grub



                              sudo update-grub


                            • Reboot.







                            share|improve this answer














                            For my Akoya laptop this worked fine:



                            1. Try the following:




                            • reboot to the grub menu and type e (hope it is right, --> you have to edit your command line)


                            • in the line starting with GRUB_CMDLINE_LINUX_DEFAULT
                              insert the following kernel properties:



                              "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                            • if your touchpad is now working, go to point 2.


                            2. Permanent Grub modification





                            • Make a backup of your grub file:



                              sudo cp /etc/default/grub /etc/default/grub.backup 



                            • Edit your grub file:



                              sudo nano /etc/default/grub 



                            • Now add the following paramters into the line starting with GRUB_CMDLINE_LINUX_DEFAULT :



                              "i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"


                            • Save the file



                            • Update your grub



                              sudo update-grub


                            • Reboot.








                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Dec 2 at 20:58

























                            answered Jun 27 at 11:24









                            abu_bua

                            3,16081023




                            3,16081023

















                                protected by Community Oct 13 '16 at 15:55



                                Thank you for your interest in this question.
                                Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                Would you like to answer one of these unanswered questions instead?



                                Popular posts from this blog

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

                                Mangá

                                 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕