Envy 0.8.1 includes a lot of changes (especially if you have a look at the source code), a new textual interface and adds the support for ATI cards. The uninstallation of Envy’s deb package should be smoother now. Here is the full changelog:
* Changed: Textual interface written from scratch
* Changed: written from scratch by using Object Oriented programming
* Changed: improved the framework for the detection of graphic card models
* Added: support for ATI cards
* Added: ATI driver 8.28.8 (legacy) and 8.33.6
* Added: Nvidia’s compatibility list has been updated
* Changed: removed “–force-yes” since Envy never used it
* Fixed: uninstalling Envy doesn’t make apt complain about folders being not empty any more
Please, read the instructions carefully:
http://albertomilone.com/nvidia_scripts1.html
It’s ubuntu-feisty compatible ?
fabrixx:
not yet. I’m waiting for a more stable release of Feisty.
I’ve just updated my Kubuntu Edgy’s kernel and X.org (according to those packages listed in the auto update).
Ever since then, I cannot start X with the nVidia driver (either the restricted modules from Ubuntu,, or the newer one installed by Envy). My screen simply go black (LCD monitor is still on, but only with backlight) whenever X starts, and I can only kill it by rebooting.
Has Envy been tested with the latest batch of updates in Ubuntu?
Flying
the updates didn’t break anything here.
On my father’s computer I only had to uninstall and reinstall the driver from Envy.
Peccato !!
uso feisty e non c’è verso di mettere i driver.
Neppure con la dapper e la edgy ci riuscivo (pur comportandomi nel modo giusto).
Solo envy (me la suggeristi tu nel forum di ubuntu)mi funzionava.
Attendo la relase per feisty.
Complimenti per quanto fai, sei un grande.
Ciao
Fabrizio.
New version didn’t worked on my Ubuntu 6.10 with Riva TNT 2 m64. By introducing some changes in classes.py i’ve managed it to work. Here they are:
1. Commented out whole ‘if’ except for line “wsite = ‘ http://download.nvidia.com/XFree86/‘” near line 199
2. Commented out whole ‘if’ except for line “os.system(‘sudo wget -c –tries=2 –timeout=20 ‘ + self.details[‘website’])” near line 231
3. Changed legacycards[card] to self.legacycards[card] on line 98
Also I had to run legacy/nvidia-xconfig manually, but I think it’s because i’ve run envy from build directory (without installing package)
Hope this helps
Gleb Peregud
I have a few questions for you:
a) Were the changes in point 1 and 2 necessary in order to install the legacy driver?
b) can you post the output of this command?:
lspci -n | grep 300
c) the correction in point 3 is right. I’ll upload a fix release of Envy (envy_0.8.1-0ubuntu2_all.deb)
d) yes, you should install Envy.
Thanks for reporting
That’s strange then… I cannot get nvidia driver to work even with Envy doing the job. Whenever I switch to nvidia driver, X gives me a blank screen (the log looks perfectly normal though, just no display…)
Thank you very much Alberto for your script!!
I messed up my xorg.conf file and my nvidia driver set-up, and thank you to your script i manage to configure everything up again!!
🙂
People like you make Ubuntu a wonderfull distro!!
Ah… I think I found what’s wrong!
I reverted back to 9629, and installed it using the package from nVidia. Everything is working again now.
So… despite lack of concrete research, I’ll conclude that the latest 9746 driver simply doesn’t work for my card (GeForce 6200) on my system.
And Alberto, is it possible that I can choose the version of driver to install using your script? (Just for the unfortunate ones like me, using an automatic script is convenient. But it can be frustrating when you need a different version of the driver than the latest.)
Flying
driver 9746 works just fine on my father’s 6200.
Anyway manual selection of the version of the driver to install will be implemented in Envy’s next release.
It will be released in February since I’m very busy with an exam at the moment.
Sorry for so late answer 🙂
1. Yes. Without these changes I complained about missing file on some remote server and something about wrong md5 (the same error as in 12th comment in http://albertomilone.com/wordpress/?p=58#comments)
2.
gleber@first:~$ lspci -n | grep 300
01:00.0 0300: 10de:002d (rev 15)
3. I was able to use it without installing and now everything works very well.
Oops, I’ve forgot to do something: Thanks for the script 😉
I’ve got a problem too. I ran envy and everything was perfect, but my Grapicscard is still “Unknown” “NVIDIA Corporation”?! It’s am Gainward GeForce 7950GT 512MB VIVO! So what can i do?
regards Guenther
Guenther
“Unknown” “NVIDIA Corporation” is just a a label.
If the output of this command is “yes” then the driver works fine:
glxinfo | grep direct
Thanks for all the work on envy Alberto. It made nvidia geforce4 mx420 ubuntu edgy install much easier.
How’s about posting a link to download the file when you advertise a new release? Just a thought.
5 minutes off my life
I’ve installed the latest envy script on kubuntu edgy 6.10 (nvidia GeForce4 MX 440)
after I’ve started kdm I got black screen. I wasn’t able to do anything, no alt+ctrl +F..) but to restart and copy the backed up xorg.conf.
I have a very slow dial up connection and I want to install the latest nvidia drivers via Envy script. I have already download the newest drivers from nvidia and now want to use envy to install it. The problem is that envy tries to download the drivers off the site again but I don’t want it to. I want it to use the driver from hard disk.
If it’s possible at all …
Please tell me how 🙁
Hadi:
move the installer to /usr/share/envy/
then run Envy
A recent update disabled (“blue screened” with a question whether to have a look at the logs) my nvidia-glx driver. Now I thought installing the restricted modules for 2.6.17-11 (was -10 before) would do the trick, but that wasn’t the case. After googling, I now ran envy, with the result that the installed driver (9631 for GeForce4 420 Go 32M) leaves me with a blank screen / black screen: no login (gdm), no NVIDIA logo, nothing. I can kill / restart the server using Ctrl-Alt-Backspace, and get to the blank screen again.
By the way – I’m stuck with the “nv” driver now. I can’t try out the newest blender, which is my main motivation to get back to a working “nvidia” driver.
Felix Rabe:
try point 7 of the Problems Section of this guide:
http://www.albertomilone.com/latest_nvidia_udsf_edgy.html#PROBLEMS_SECTION