How to remove nvidia driver from ubuntu 16.04 kernel client and kernel module, or get kernel clent & module to use the same nvidia driver? The 2019 Stack Overflow Developer Survey Results Are In Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar ManaraNvidia driver updated - mixed versions of 304.88 and 319.32Ubuntu stops using Nvidia driver after kernel upgradeUpdate manager updates the kernel mod but not the nvidia client, how to get them to match?Nvidia driver updated - mixed versions of 304.88 and 319.32How to debug why Nvidia-331 is not working?Ubuntu 14.04 Black screen nvidia driver 347. taints Kernel?Kernel update gets stuck (Ubuntu 16.04, Kernel 4.4.0-22)Strange artifacts along window borders after waking computer from sleep modeBoot partition is 100% full. Cant remove old packages to make spaceHow do I build a 4.15.7 kernel with LLVM/clang and a Nvidia 390.25 x86_64 driver on Ubuntu 17.10 x86_64?Ubuntu 18.04 boot fail on video driver

The following signatures were invalid: EXPKEYSIG 1397BC53640DB551

How do I design a circuit to convert a 100 mV and 50 Hz sine wave to a square wave?

How to read αἱμύλιος or when to aspirate

How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?

Accepted by European university, rejected by all American ones I applied to? Possible reasons?

Why can't devices on different VLANs, but on the same subnet, communicate?

What was the last x86 CPU that did not have the x87 floating-point unit built in?

Do I have Disadvantage attacking with an off-hand weapon?

Are there continuous functions who are the same in an interval but differ in at least one other point?

Deal with toxic manager when you can't quit

Was credit for the black hole image misappropriated?

How did passengers keep warm on sail ships?

Word for: a synonym with a positive connotation?

Is there a way to generate uniformly distributed points on a sphere from a fixed amount of random real numbers per point?

"is" operation returns false even though two objects have same id

Do warforged have souls?

Student Loan from years ago pops up and is taking my salary

Is an up-to-date browser secure on an out-of-date OS?

Homework question about an engine pulling a train

Mortgage adviser recommends a longer term than necessary combined with overpayments

Windows 10: How to Lock (not sleep) laptop on lid close?

Using dividends to reduce short term capital gains?

How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time

Identify 80s or 90s comics with ripped creatures (not dwarves)



How to remove nvidia driver from ubuntu 16.04 kernel client and kernel module, or get kernel clent & module to use the same nvidia driver?



The 2019 Stack Overflow Developer Survey Results Are In
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraNvidia driver updated - mixed versions of 304.88 and 319.32Ubuntu stops using Nvidia driver after kernel upgradeUpdate manager updates the kernel mod but not the nvidia client, how to get them to match?Nvidia driver updated - mixed versions of 304.88 and 319.32How to debug why Nvidia-331 is not working?Ubuntu 14.04 Black screen nvidia driver 347. taints Kernel?Kernel update gets stuck (Ubuntu 16.04, Kernel 4.4.0-22)Strange artifacts along window borders after waking computer from sleep modeBoot partition is 100% full. Cant remove old packages to make spaceHow do I build a 4.15.7 kernel with LLVM/clang and a Nvidia 390.25 x86_64 driver on Ubuntu 17.10 x86_64?Ubuntu 18.04 boot fail on video driver



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















After viewing /var/log/syslog and /var/log/kern.log I found the following kernel issue:



NVRM: API mistmatch: the client has version 375.26, but
NVRM: this kernel module has the version 375.39. Please
NVRM: make sure that kernel module and all NVIDIA driver
NVRM: components have the same version.


I found Nvidia driver updated - mixed versions of 304.88 and 319.32 describing the same problem. To resolve my issue, I ran commands:



dpkg -l | grep nvidia
sudo apt-get autoremove nvidia375
sudo apt-get --purge remove nvidia*
dpkg -l | grep nvidia


The output from the last command confirmed no nvidia packages are installed. Thereafter, I ran:



sudo update-grub
sudo update-initramfs -u
sudo reboot


However, I am still experiencing the same kernel issue. Upon bootup, I am stuck in low graphics mode setup and kernel and /var/log/syslog and /var/log/kern.log still complaining client has Nvidia driver 375.26 and kernel module has Nvidia driver 375.39.



My current kernel is 4.4.0-64-generic.



Update1: To see the nvidia modules read in by the kernel, I ran this command.



$ lsmod | grep nvidia
module size used by
nvidia_drm 53248 0
nvidia_modeset 790528 1 nvidia_drm
nvidia 12144640 1 nvidia_modeset
drm_helper 155648 2 i915_bpo,nvidia_drm
drm 364544 4 i915_bpo,drm_helper,nvidia_drm


Also found out using modinfo module_name that these modules are located in folder /lib/modules/4.4.0-64-generic/updates/dkms/ and their filenames are nvidia-drm.ko, nvidia-modeset.ko and nvidia.ko, and their version is 375.39.



2nd Question: Why do these modules still exist even after I have purged all nvidia packages? Should I remove them? If so, how?










share|improve this question






























    0















    After viewing /var/log/syslog and /var/log/kern.log I found the following kernel issue:



    NVRM: API mistmatch: the client has version 375.26, but
    NVRM: this kernel module has the version 375.39. Please
    NVRM: make sure that kernel module and all NVIDIA driver
    NVRM: components have the same version.


    I found Nvidia driver updated - mixed versions of 304.88 and 319.32 describing the same problem. To resolve my issue, I ran commands:



    dpkg -l | grep nvidia
    sudo apt-get autoremove nvidia375
    sudo apt-get --purge remove nvidia*
    dpkg -l | grep nvidia


    The output from the last command confirmed no nvidia packages are installed. Thereafter, I ran:



    sudo update-grub
    sudo update-initramfs -u
    sudo reboot


    However, I am still experiencing the same kernel issue. Upon bootup, I am stuck in low graphics mode setup and kernel and /var/log/syslog and /var/log/kern.log still complaining client has Nvidia driver 375.26 and kernel module has Nvidia driver 375.39.



    My current kernel is 4.4.0-64-generic.



    Update1: To see the nvidia modules read in by the kernel, I ran this command.



    $ lsmod | grep nvidia
    module size used by
    nvidia_drm 53248 0
    nvidia_modeset 790528 1 nvidia_drm
    nvidia 12144640 1 nvidia_modeset
    drm_helper 155648 2 i915_bpo,nvidia_drm
    drm 364544 4 i915_bpo,drm_helper,nvidia_drm


    Also found out using modinfo module_name that these modules are located in folder /lib/modules/4.4.0-64-generic/updates/dkms/ and their filenames are nvidia-drm.ko, nvidia-modeset.ko and nvidia.ko, and their version is 375.39.



    2nd Question: Why do these modules still exist even after I have purged all nvidia packages? Should I remove them? If so, how?










    share|improve this question


























      0












      0








      0








      After viewing /var/log/syslog and /var/log/kern.log I found the following kernel issue:



      NVRM: API mistmatch: the client has version 375.26, but
      NVRM: this kernel module has the version 375.39. Please
      NVRM: make sure that kernel module and all NVIDIA driver
      NVRM: components have the same version.


      I found Nvidia driver updated - mixed versions of 304.88 and 319.32 describing the same problem. To resolve my issue, I ran commands:



      dpkg -l | grep nvidia
      sudo apt-get autoremove nvidia375
      sudo apt-get --purge remove nvidia*
      dpkg -l | grep nvidia


      The output from the last command confirmed no nvidia packages are installed. Thereafter, I ran:



      sudo update-grub
      sudo update-initramfs -u
      sudo reboot


      However, I am still experiencing the same kernel issue. Upon bootup, I am stuck in low graphics mode setup and kernel and /var/log/syslog and /var/log/kern.log still complaining client has Nvidia driver 375.26 and kernel module has Nvidia driver 375.39.



      My current kernel is 4.4.0-64-generic.



      Update1: To see the nvidia modules read in by the kernel, I ran this command.



      $ lsmod | grep nvidia
      module size used by
      nvidia_drm 53248 0
      nvidia_modeset 790528 1 nvidia_drm
      nvidia 12144640 1 nvidia_modeset
      drm_helper 155648 2 i915_bpo,nvidia_drm
      drm 364544 4 i915_bpo,drm_helper,nvidia_drm


      Also found out using modinfo module_name that these modules are located in folder /lib/modules/4.4.0-64-generic/updates/dkms/ and their filenames are nvidia-drm.ko, nvidia-modeset.ko and nvidia.ko, and their version is 375.39.



      2nd Question: Why do these modules still exist even after I have purged all nvidia packages? Should I remove them? If so, how?










      share|improve this question
















      After viewing /var/log/syslog and /var/log/kern.log I found the following kernel issue:



      NVRM: API mistmatch: the client has version 375.26, but
      NVRM: this kernel module has the version 375.39. Please
      NVRM: make sure that kernel module and all NVIDIA driver
      NVRM: components have the same version.


      I found Nvidia driver updated - mixed versions of 304.88 and 319.32 describing the same problem. To resolve my issue, I ran commands:



      dpkg -l | grep nvidia
      sudo apt-get autoremove nvidia375
      sudo apt-get --purge remove nvidia*
      dpkg -l | grep nvidia


      The output from the last command confirmed no nvidia packages are installed. Thereafter, I ran:



      sudo update-grub
      sudo update-initramfs -u
      sudo reboot


      However, I am still experiencing the same kernel issue. Upon bootup, I am stuck in low graphics mode setup and kernel and /var/log/syslog and /var/log/kern.log still complaining client has Nvidia driver 375.26 and kernel module has Nvidia driver 375.39.



      My current kernel is 4.4.0-64-generic.



      Update1: To see the nvidia modules read in by the kernel, I ran this command.



      $ lsmod | grep nvidia
      module size used by
      nvidia_drm 53248 0
      nvidia_modeset 790528 1 nvidia_drm
      nvidia 12144640 1 nvidia_modeset
      drm_helper 155648 2 i915_bpo,nvidia_drm
      drm 364544 4 i915_bpo,drm_helper,nvidia_drm


      Also found out using modinfo module_name that these modules are located in folder /lib/modules/4.4.0-64-generic/updates/dkms/ and their filenames are nvidia-drm.ko, nvidia-modeset.ko and nvidia.ko, and their version is 375.39.



      2nd Question: Why do these modules still exist even after I have purged all nvidia packages? Should I remove them? If so, how?







      16.04 drivers nvidia kernel xorg






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 13 '17 at 12:24









      Community

      1




      1










      asked Feb 27 '17 at 8:00









      Sun BearSun Bear

      318215




      318215




















          1 Answer
          1






          active

          oldest

          votes


















          2














          I was able to resolve my issue by performing the following steps:



          1. First reinstall the nvidia-418 repository graphic driver.
            sudo apt-get install nvidia-418

          During the installation, I noticed that nvidia-418.26 driver was being installed.



          1. I moved the entire /lib/modules/4.18.0-17-generic/updates/dkms folder to my home directory backup folder. This was to make sure all old .ko files were removed.
            sudo mv /lib/modules/4.18.0-17-generic/updates/dkms/nvidia* /home//backup



          2. I regenerated the .ko files for the installed driver using
            sudo dpkg-reconfigure nvidia-418



            It created a new dkms folder with the relevant nvidia kernel modules. I also checked their version using command:



            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_drm.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_modeset.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_uvm.ko



            Their output showed that they were for version 418.26. Great, this confirmed that the kernel client and kernel modules were referring to the same NVidia driver version.



          3. (Optional but recommended to ensure apt-get works correctly) Uninstall and reinstall the driver
            sudo apt-get remove "nvidia"
            sudo apt-get install nvidia-driver-418


          4. I rebooted the system with
            sudo reboot


          Adapted from https://devtalk.nvidia.com/default/topic/525877/linux/api-mismatch-means-ubuntu-can-39-t-boot-i-can-39-t-fix-i-please-help-/1






          share|improve this answer

























          • This fixed my 17.10 upgrade with nvidia-384

            – TheLQ
            Nov 17 '17 at 9:02











          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%2f887743%2fhow-to-remove-nvidia-driver-from-ubuntu-16-04-kernel-client-and-kernel-module-o%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          I was able to resolve my issue by performing the following steps:



          1. First reinstall the nvidia-418 repository graphic driver.
            sudo apt-get install nvidia-418

          During the installation, I noticed that nvidia-418.26 driver was being installed.



          1. I moved the entire /lib/modules/4.18.0-17-generic/updates/dkms folder to my home directory backup folder. This was to make sure all old .ko files were removed.
            sudo mv /lib/modules/4.18.0-17-generic/updates/dkms/nvidia* /home//backup



          2. I regenerated the .ko files for the installed driver using
            sudo dpkg-reconfigure nvidia-418



            It created a new dkms folder with the relevant nvidia kernel modules. I also checked their version using command:



            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_drm.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_modeset.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_uvm.ko



            Their output showed that they were for version 418.26. Great, this confirmed that the kernel client and kernel modules were referring to the same NVidia driver version.



          3. (Optional but recommended to ensure apt-get works correctly) Uninstall and reinstall the driver
            sudo apt-get remove "nvidia"
            sudo apt-get install nvidia-driver-418


          4. I rebooted the system with
            sudo reboot


          Adapted from https://devtalk.nvidia.com/default/topic/525877/linux/api-mismatch-means-ubuntu-can-39-t-boot-i-can-39-t-fix-i-please-help-/1






          share|improve this answer

























          • This fixed my 17.10 upgrade with nvidia-384

            – TheLQ
            Nov 17 '17 at 9:02















          2














          I was able to resolve my issue by performing the following steps:



          1. First reinstall the nvidia-418 repository graphic driver.
            sudo apt-get install nvidia-418

          During the installation, I noticed that nvidia-418.26 driver was being installed.



          1. I moved the entire /lib/modules/4.18.0-17-generic/updates/dkms folder to my home directory backup folder. This was to make sure all old .ko files were removed.
            sudo mv /lib/modules/4.18.0-17-generic/updates/dkms/nvidia* /home//backup



          2. I regenerated the .ko files for the installed driver using
            sudo dpkg-reconfigure nvidia-418



            It created a new dkms folder with the relevant nvidia kernel modules. I also checked their version using command:



            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_drm.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_modeset.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_uvm.ko



            Their output showed that they were for version 418.26. Great, this confirmed that the kernel client and kernel modules were referring to the same NVidia driver version.



          3. (Optional but recommended to ensure apt-get works correctly) Uninstall and reinstall the driver
            sudo apt-get remove "nvidia"
            sudo apt-get install nvidia-driver-418


          4. I rebooted the system with
            sudo reboot


          Adapted from https://devtalk.nvidia.com/default/topic/525877/linux/api-mismatch-means-ubuntu-can-39-t-boot-i-can-39-t-fix-i-please-help-/1






          share|improve this answer

























          • This fixed my 17.10 upgrade with nvidia-384

            – TheLQ
            Nov 17 '17 at 9:02













          2












          2








          2







          I was able to resolve my issue by performing the following steps:



          1. First reinstall the nvidia-418 repository graphic driver.
            sudo apt-get install nvidia-418

          During the installation, I noticed that nvidia-418.26 driver was being installed.



          1. I moved the entire /lib/modules/4.18.0-17-generic/updates/dkms folder to my home directory backup folder. This was to make sure all old .ko files were removed.
            sudo mv /lib/modules/4.18.0-17-generic/updates/dkms/nvidia* /home//backup



          2. I regenerated the .ko files for the installed driver using
            sudo dpkg-reconfigure nvidia-418



            It created a new dkms folder with the relevant nvidia kernel modules. I also checked their version using command:



            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_drm.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_modeset.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_uvm.ko



            Their output showed that they were for version 418.26. Great, this confirmed that the kernel client and kernel modules were referring to the same NVidia driver version.



          3. (Optional but recommended to ensure apt-get works correctly) Uninstall and reinstall the driver
            sudo apt-get remove "nvidia"
            sudo apt-get install nvidia-driver-418


          4. I rebooted the system with
            sudo reboot


          Adapted from https://devtalk.nvidia.com/default/topic/525877/linux/api-mismatch-means-ubuntu-can-39-t-boot-i-can-39-t-fix-i-please-help-/1






          share|improve this answer















          I was able to resolve my issue by performing the following steps:



          1. First reinstall the nvidia-418 repository graphic driver.
            sudo apt-get install nvidia-418

          During the installation, I noticed that nvidia-418.26 driver was being installed.



          1. I moved the entire /lib/modules/4.18.0-17-generic/updates/dkms folder to my home directory backup folder. This was to make sure all old .ko files were removed.
            sudo mv /lib/modules/4.18.0-17-generic/updates/dkms/nvidia* /home//backup



          2. I regenerated the .ko files for the installed driver using
            sudo dpkg-reconfigure nvidia-418



            It created a new dkms folder with the relevant nvidia kernel modules. I also checked their version using command:



            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_drm.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_modeset.ko

            sudo modinfo /lib/modules/4.18.0-17-generic/updates/dkms/nvidia_uvm.ko



            Their output showed that they were for version 418.26. Great, this confirmed that the kernel client and kernel modules were referring to the same NVidia driver version.



          3. (Optional but recommended to ensure apt-get works correctly) Uninstall and reinstall the driver
            sudo apt-get remove "nvidia"
            sudo apt-get install nvidia-driver-418


          4. I rebooted the system with
            sudo reboot


          Adapted from https://devtalk.nvidia.com/default/topic/525877/linux/api-mismatch-means-ubuntu-can-39-t-boot-i-can-39-t-fix-i-please-help-/1







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 15 mins ago









          Community

          1




          1










          answered Feb 27 '17 at 15:41









          Sun BearSun Bear

          318215




          318215












          • This fixed my 17.10 upgrade with nvidia-384

            – TheLQ
            Nov 17 '17 at 9:02

















          • This fixed my 17.10 upgrade with nvidia-384

            – TheLQ
            Nov 17 '17 at 9:02
















          This fixed my 17.10 upgrade with nvidia-384

          – TheLQ
          Nov 17 '17 at 9:02





          This fixed my 17.10 upgrade with nvidia-384

          – TheLQ
          Nov 17 '17 at 9:02

















          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%2f887743%2fhow-to-remove-nvidia-driver-from-ubuntu-16-04-kernel-client-and-kernel-module-o%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

          Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

          Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

          Antonio De Lisio Carrera Referencias Menú de navegación«Caracas: evolución relacional multipleja»«Cuando los gobiernos subestiman a las localidades: L a Iniciativa para la Integración de la Infraestructura Regional Suramericana (IIRSA) en la frontera Colombo-Venezolana»«Maestría en Planificación Integral del Ambiente»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»«Conózcanos»«Caracas: evolución relacional multipleja»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»