I have finished writing my thesis (in Latex) and I’ll graduate in March. In the meantime I’m studying PyQT4 and working on Envy.
I haven’t updated Envy yet as I’ve been working on EnvyNG (“NG” stands for “Next Generation”) i.e. the latest evolution of Envy. EnvyNG will support only Ubuntu Hardy (8.04) or higher while Envy Legacy will still support Ubuntu’s previous releases and Debian (stable).
The release of EnvyNG which you will see in time for Hardy is 1.0.x. Consider it a transitional release since many new features will be available only in version 1.1.x. Here is a (partial) list of the features in EnvyNG 1.0.x
-
I have worked with a group of Ubuntu developers (to which I’ll give credit when EnvyNG is officially released) in order to prevent Envy from causing troubles when if a user doesn’t do a “envy –uninstall-all” before a dist-upgrade (e.g. from Gutsy to Hardy). Ubuntu’s l-r-m (linux-restricted-modules) and the packages generated by EnvyNG will be able to overwrite each other in a sensible way so that, for example, if Ubuntu’s l-r-m provide the latest NVIDIA driver before EnvyNG does, the former will be perfectly capable of overwriting the packages generated by the latter without causing any problem to the user. Furthermore, thanks to DKMS and also thanks to a patch I wrote for the l-r-m (already applied in Hardy), there will be no need to blacklist Ubuntu’s drivers (in /etc/default/linux-restricted-modules-common). If the packages generated by EnvyNG are installed, they will be automatically loaded at boot.
-
In Envy a user had to reinstall the driver every time the kernel was updated. This is no longer the case as DKMS will automatically build and install the module for your kernel at boot (if necessary), provided that your kernel headers are installed.
-
It does it automatically (during both the installation and the uninstallation processes)
-
The same can’t be said about the fglrx driver but I guess this can be fixed later
I’ll reveal other details on version 1.0.x soon
In the meantime you might want to have a look at the list of features in version 1.1.x.
Does this mean that you wrote your thesis in the Latex language or that you wrote you thesis while wearing latex? To entirely different things! 😉
@CeeC
Congratulations for your thesis!
I started writing mine a month ago… Pain in the neck 😉
Keep up the good work, you’re helping a lot of people here
Many thanks!
@Billy Objor
Yes, I meant the Latex language. And by the way I don’t like snakes, Python is only my favourite programming language 😉
@QuÃmico
good luck with your thesis then 😉
Envy is really great with nVidia cards in Ubuntu 7.10, but new generation ATI cards don’t yet work as well with the 8.1 driver. Hopefully the 8.2 driver will stop fit-inducing, flashing video playback. I hope that there will be time to update Envy, but very good luck with your thesis etc, and thank you for Envy !
Hi !
> EnvyNG no longer asks you whether you would like to have your
> xorg.conf configured.
I’m a little concerned about this. Does it mean the former xorg.conf will be completely overwritten ?
I could raise some issues in my case : I usually have to add manually a line to support my French keyboard, and also, an external TV screen is also defined there…
Anyway, thanks for your great work !
@torturedutopian
It won’t destroy your xorg.conf.
It will make sure that the driver is set to NVIDIA and that the Desktop effects can be enabled. That’s all. It won’t touch your settings.
Hi. I am running Hardy and Ubuntu just updated the kernel to 2.6.24-17. After that I lost my nvidia restricted driver. I had installed it with EnvyNG (v 1.1.1). Under kernel -16 everything was working fine, however, my restricted driver was not listed in jockey (Ubuntu Hardware Devices). Now, every time I run EnvyNG, it installs kernel 2.6.24-16-386. How do I get EnvyNG to install nvidia for the -17 kernel? (That’s the only kernel image currently on my system. I have removed all others and I want to keep it that way.) Thanks.
@MountainX
what’s the output of this command?
uname -rHi Alberto. I worked around my problem as described in this thread: http://ubuntuforums.org/showthread.php?t=779716. (I manually installed the nVidia drivers without Envy while using kernel 2.6.24-17.) Today, since FF3 came out, I decided to update everything. (I am no longer getting update from hardy-proposed either.) I removed all prior nVidia drivers and completely cleaned out my system. Via Update Manager I installed the latest EnvyNG, kernel 2.6.24-19, and the rest of the updates offered. When I ran EnvyNG, it again tried to install kernel 2.6.24-16, just like it did when I had kernel 2.6.24-17 installed last month. I canceled out of EnvyNG before it could install the old kernel.
I thought the problem last time was related to the fact that I had the hardy-proposed repos enabled. Now that I removed that repos, I am confused as to why EnvyNG is not working correctly. Can you offer any help?
BTW, uname -r
2.6.24-19-generic
Hi Alberto – any thoughts on my situation? I’m still trying to understand it and solve it. Thanks.
I just updated my Ubuntu 8.04 to kernel 2.6.24-23-generic today. For the first time in many updates, the process went smoothly. I think my issue is resolved now. I will reply also to the Launchpad post here:
https://bugs.launchpad.net/envy/+bug/226286