Envy and NVIDIA CUDA

As you might already know, the latest release of the Nvidia driver includes the CUDA driver. Unfortunately the packages generated by Envy lacked the new files which made it possible to use the CUDA Toolkit (on both Debian and Ubuntu). This is no longer the case in envy_0.9.9-0ubuntu6 which I released about two days ago (but I was too busy and tired to announce it). Furthermore the wfb module of the NVIDIA driver wasn’t included in the packages generated by Envy because of a stupid typo.

Here’s the changelog:
* Changed: nvidia-glx-dev was not installed on Debian
* Fixed: Bug #180144 missing CUDA support on Ubuntu
* Fixed: Bug #180144 missing CUDA support on Debian
* Fixed: Bug #178291 Nvidia wfb module missing on Debian

NOTE: unless you need CUDA or you use Debian and the latest NVIDIA driver you will have no reason to install this new release.

On another note, this week I’ve been working on a website and I had to learn a bit of HTML DOM, Javascript, PHP, which I had *never* used. It was quite (painful but) interesting. Just to mention a problem I had, I was struggling with Internet Explorer when I discovered that it had a problem with Javascript’s array method indexOf(), which I had to create with “protoype” just for IE since it works well in Firefox. And of course making a website look good (and yes I do use CSS) in IE, Firefox and Opera at the same time can be a pain. If Firefox’s Firebug extension didn’t exist I think I would have never completed that website.

13 thoughts on “Envy and NVIDIA CUDA

  1. Alberto,

    You’ll find this site: http://webbugtrack.blogspot.com/ to be a great resource when you are trying to track down bugs in IE or any browser.

    I did a quick search, but I don’t see the [Array].indexOf() bug you mentioned. Maybe you can submit it so that we can all track it.

    Also, are you using a pure IE? or an IE for Linux?

    Have a great day.

  2. Pingback: Pages tagged "gnu"
  3. Hi Albert,

    Thanks so much for the work you do.

    I have a question. For various reasons I need to disconnect the TV from TV0 on a regular basis. Each time Nvidia settings no longer has knowledge of TV0, so when I reconnect it, I must run the ‘Detect Displays’ to get it going again. Is there any way to force TV0 on?

    Thanks, and apologies if this is not the right forum.

    cheers

    jamie

  4. For the first time using Envy, this latest version has not worked well for me. I have the Radeon X1300/X1550, and after this most recent installation, the screen resolution is wrong, and the correct choice doesn’t show in the screen resolution preferences screen.

  5. I just started learning JavaScript a few weeks ago and also noticed a real problem with IE. I was reading a book about it all and almost every function works perfectly in all browsers except IE, which needs its own “special” functions to work. What a pain. Then I found Yahoo’s UI toolkit. I’m usually not one for Yahoo (their mail filter sucks), but this toolkit rocks. They address alot of CSS and JavaScript cross-browser problems. Have a look: developer.yahoo.com/yui

  6. @Will Jaynes
    It’s a bug which affects ATI’s latest driver. It will be solved in the next release. It’s not Envy’s fault.

    @Ross Peoples
    I wasn’t aware of the existence of such a powerful tool. Thank you very much for the link.

  7. Hello Alberto
    I tried with the new envy and I get this error while it is installing
    ENVY ERROR: md5 Error! … something else

    then it installs the drivers and I boot up, afterwards I get a message that tells me that the monitor couldn’t be detected and I need to configure it, otherwise run in low graphics mode… What do I do now?

    Compaq Presario V3000 geforce go 6150
    Thanks!

  8. Hello Alberto,

    Envy works perfectly (thanks so lot) on my computer untill release based on 169.07 nvidia drivers.
    I’m doing everything as usually.
    The install seems to run OK (as usually).
    xorg.conf is well configured and nothing is wrong in Xorg.0.log, but I can not activate the 3D effects.

    When typing : glxinfo | grep “direct rendering”
    the prompt come back after few seconds with no answer.

    When typing : glxgears
    I have message : “instruction illegale (core dumped)”

    When starting /usr/bin/nvidia-settings, I’m unable to display the OpenGL/GLX information box and the nvidia-settings window is closed after few seconds.

    Ubuntu 7.10
    GeForce 6200-128RAM AGP 4x

    I know you are very busy and I have moving back to 100.14.23 drivers which are working well, so it is not and urgent issue for me.

    Thanks for all.

    Murex

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.