Install Nvidia Graphics Drivers 190.42 in Ubuntu Karmic/Jaunty/Intrepid/Hardy

Sponsored Link
A week after the NVIDIA Linux engineering team released the 190.42 driver release candidate, this driver is now deemed stable and has been officially released on NVIDIA's web-site. The NVIDIA 190.42 driver is the first official release in the 190.xx Linux driver series, which has been in beta for a number of months and undergone numerous releases.
Compared to the NVIDIA 185.xx driver series, the NVIDIA 190.42 driver brings new hardware support, support for OpenGL 3.2, many VDPAU video playback improvements, initial support for X Server 1.7 / X.Org 7.5, support for configuring the NVIDIA GPU's fan-speed, and support for configuring the GPU PowerMizer mode. There are also various bug-fixes and other smaller improvements. Among the newly supported hardware is the GeForce GT 220, GeForce G102M, GeForce G210, GeForce G210M, GeForce GT 230M, GeForce GT 240M, GeForce GTS 250M, and GeForce GTS 260M.

The NVIDIA 190.42 driver, however, does not contain the OpenCL support that is found in this driver set, but we anticipate the Open Computing Language library to be merged into the mainline package soon.

The official NVIDIA 190.42 display driver is available for 64-bit Linux and 32-bit Linux. The FreeBSD and Solaris NVIDIA drivers have also reached version 190.42 with similar changes.

For Ubuntu Karmic Users

Use the following command to add PPA

sudo add-apt-repository ppa:nvidia-vdpau/ppa

Other User

First you need to edit /etc/apt/sources.list file

sudo gedit /etc/apt/sources.list

add one of the following lines

For Jaunty users

deb jaunty main
deb-src jaunty main

For Intrepid Users

deb intrepid main
deb-src intrepid main

For Hardy Users

deb hardy main
deb-src hardy main

Save and exit the file

Install GPG key using the following command

sudo apt-key adv --keyserver --recv-keys CEC06767

Update source list

sudo apt-get update

Install beta drivers

sudo apt-get install nvidia-190-modaliases nvidia-glx-190 nvidia-settings-190

Sponsored Link

You may also like...

47 Responses

  1. H says:


    I Follow the steps for jaunty but I wasn’t able to install GPG Key. I get a “keyserver timed out” error:

    “Executing: gpg –ignore-time-conflict –no-options –no-default-keyring –secret-keyring /etc/apt/secring.gpg –trustdb-name /etc/apt/trustdb.gpg –keyring /etc/apt/trusted.gpg –keyserver –recv-keys CEC06767
    gpg: requesting key CEC06767 from hkp server
    gpg: keyserver timed out
    gpg: keyserver receive failed: keyserver error”

  2. Mohsen says:

    Is it safe to install from package? I installed version 185.* from .run packages successfully.
    Thank you

  3. admin says:

    Thanks for your comment i have corrected now

  4. JesperSJensen says:

    sudo add-apt-repository ppa:nvidia-vdpau/ppa


    gpg: requesting key … from hkp server

    gpg: keyserver timed out
    gpg: keyserver receive failed: keyserver error

  5. JesperSJensen says:

    Now I succeed get the key… 3’rd time I tried…

  6. karmue says:

    keyserver timed out and libxine1-bin requires nvidia-185-libvdpau, which was removed by nvidia-190-libvdpau.

  7. blink4blog says:

    do i have to disable the Restricted Hardware of nVidia 185 first before proceed with the installation?

  8. admin says:

    Key server may be busy that is why you are getting timedout messages

  9. Ichigo says:

    Do i need to uninstall the old nvidia 185 driver before updating with the new one?

  10. Mark says:

    I’d rather hace the actual deb line than this fancy new repo add thing. Which aparantly depends on servers on the Internet to work 😉

    Could you?

  11. Mark says:

    Ah yes, ofcourse, simply adapt one of the other deb lines. Thanks anyway 😉

  12. Mark says:

    Ok.. So this install made my computer unable to boot. I just got a flickering screen and nothing else.

    I had to go press esc while booting to get in single user mode. And then:

    mount -o rw,remount /
    aptitude remove –purge nvidia-190-libvdpau nvidia-settings-190
    aptitude install nvidia-185-libvdpau nvidia-glx-185 nvidia-settings

    This will recompile the kernel module you need to get your laptop back in working condition (Which in my case is a T61P Lenovo)

  13. blink4blog says:


    luckily I did not install …

  14. Fabián Andrés says:

    This is the key CEC06767:

    File > Save As…

  15. tectux says:

    Nice. Works like a charm on a clean install of Karmic, amd64.

    Note the driver still needs to be activated after following this.

    Just reboot, go to System -> Administration -> Hardware drivers, select version 190 and hit ‘Activate’.

  16. scott says:

    yea so this caused by computer not to boot too. however, when i do what worked for mike i received a “this aptitude is not a super cow” message.

    any help getting this thing to boot up again would be helpful. thanks

  17. eschvoca says:


    I was going to try this but it wants to uninstall:

    libmyth-0.22-0 mythtv-frontend mythvideo

    Too bad. Otherwise I would try it out.


  18. blink4blog says:


    did you selected the 185 first from the Hardware Drivers before installing 190?

  19. whorider says:

    Nvidia-190 wants to uninstall amarok14 (Bogdan Butnaru PPA) as well. I will investigate the dependencies when I get home.

  20. Alex says:

    Hi. Tried this guide on the amd64 distro.
    Every step work s perfectly except that when i reboot, i have to use terminal 😉 ‘startx’ gives me this reply; [my main graphic-card is the nvidia, i have hybrid graphics] please help me =s

    (–) PCI:*(0:0:2:0) 8086:2a42:1734:1148 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
    (–) PCI: (0:1:0:0) 10de:0649:1734:1148 nVidia Corporation G96 [GeForce 9600M GT] rev 161, Mem @ 0xf2000000/16777
    (==) Using default built-in configuration (39 lines)
    (==) — Start of built-in configuration —
    Section “Device”
    Identifier “Builtin Default intel Device 0”
    Driver “intel”
    Section “Screen”
    Identifier “Builtin Default intel Screen 0”
    Device “Builtin Default intel Device 0”

  21. Alex says:

    Section “Screen”
    Identifier “Builtin Default intel Screen 0”
    I Xorg.0.log Row 70 Col 1 0:57 Ctrl-K H for help
    Section “Device”
    Identifier “Builtin Default i810 Device 0”
    Driver “i810”
    Section “Screen”
    Identifier “Builtin Default i810 Screen 0”
    Device “Builtin Default i810 Device 0”
    Section “Device”
    Identifier “Builtin Default vesa Device 0”
    Driver “vesa”
    Section “Screen”
    Identifier “Builtin Default vesa Screen 0”
    Device “Builtin Default vesa Device 0”
    Section “Device”
    Identifier “Builtin Default fbdev Device 0”
    Driver “fbdev”
    Section “Screen”
    Identifier “Builtin Default fbdev Screen 0”
    Device “Builtin Default fbdev Device 0”
    Section “ServerLayout”
    Identifier “Builtin Default Layout”
    Screen “Builtin Default intel Screen 0”
    Screen “Builtin Default i810 Screen 0”
    Screen “Builtin Default vesa Screen 0”
    Screen “Builtin Default fbdev Screen 0”
    (==) — End of built-in configuration —
    (==) ServerLayout “Builtin Default Layout”
    (**) |–>Screen “Builtin Default intel Screen 0” (0)

  22. Alex says:

    and so on… do i have to specify what pci: to use?

  23. Jeff says:

    Worked great for me on Karmic 64-bit! Hope this will fix the crashing and weird screen artifact issues I’ve been having since installing Karmic.

    Seems faster anyway. 🙂 Thanks!

  24. ben2talk says:

    Hmmm actually I’m very happy with the 180 driver at the moment – docky is very fluid and has no issues. Is there any real benefit to trying out a bleeding edge 190 driver? is it really worth the risk?

  25. blink4blog says:


    Would you detail your installation steps? I need to know did you need to unselect 180 from Hardware Drivers before installing 190?


  26. Jacques says:

    Worked great … although tv out stopped working. Reverted back to the previous one until I have time to sort out the tv bit.

  27. Jeff says:


    No, I didn’t. The 180 drivers were removed automatically before the 190 drivers were installed. I checked Hardware Drivers after I rebooted, and the 190 drivers had been activated.

    Good luck!

  28. bybuntu says:

    After installing nvidia 190.42, rkward is uninstalled. Its seems that I can not have both becoz they use libvdpau…. any expalnations or how can I go round this problem

  29. textux says:

    i tried 185 but they failed to work properly due to a bug in karmic. so I removed them completely, and followed the steps from here.
    this version works fine…

  30. sh says:

    i encounter this error after hitting enter

    sudo add-apt-repository ppa:nvidia-vdpau/ppa


Leave a Reply

Your email address will not be published. Required fields are marked *