It’s been a month since my last blog post. EnvyNG was included in Hardy but it had a few problems and I have worked to fix them. I can’t upload such fixes since Hardy is a stable release. This means that all the updates will have to be tested before they are moved to the stable repositories. This is why I need your help. The more users test the fixes the sooner we can get them into stable.
Special Thanks:
All this wouldn’t have been possible without the amazing support of Martin Pitt, who guided me and helped me with the SRU (Stable Release Update). He has spent a lot of time on EnvyNG, gave me a lot of extremely useful suggestions, therefore I can say that you should really thank Martin for this release.
Timo Aaltonen brought bugs #212648, #186382, #118605 to my attention and suggested the solution. In case you don’t know it already, he’s one of the guys who take care of Ubuntu’s restricted modules. Keep up the good work, Timo!
A stripped down list of Changes:
envyng-core (1.1.1ubuntu15) hardy-proposed; urgency=low
* Fix (LP: #224004) Update NVIDIA compatibility list.
* Fix (LP: #221304) Use the new l-r-m-envy packages now.
* Install -envy packages instead of the ones in main
* Hide FutureWarning caused by python-apt
* xorgconfig2 now ignores sections which are not relevant in xorg.conf
linux-restricted-modules-envy-2.6.24 (2.6.24.500-500.28) hardy-proposed; urgency=low
* Fix (LP: #228649) xorg-driver-fglrx-dev conflicted with
xorg-driver-fglrx
* Sync with the fixes in linux-restricted-modules-2.6.24 (2.6.24.12-17.36)
* nvidia: Do not divert libwfb.so, because if the xserver provides one
it should be used. This caused at least problems with some websites
crashing on certain pages (see #212648), and pink shadows with compiz.
(see: #186382)
* fglrx: Patch authatieventsd.sh to search for xauth files in
/var/run/xauth/. Otherwise the session would freeze on logout for KDM
users. Thanks Ilja Pavkovic! (see: #118605)
* Remove previous diversions of libwfb.so in the postinst. Thanks Timo
Aaltonen.
* Make sure that any previous module of fglrx and nvidia built by DKMS are
removed before the new module is built and installed.
* Use -envy so as not to conflict with Ubuntu's lrm
* Add fglrx driver 8.4
Envyng-core will also fix the problem which prevented the QT interface from working properly.
EnvyNG now relies on its own packages (available in multiverse) therefore you will have to install the driver from EnvyNG again so that the correct packages are installed. If you don’t do it you will keep using Ubuntu’s default restricted modules. Of course DKMS, CUDA, etc. are back in my packages.
The latest release of ATI’s proprietary driver (8.4) is also available and contains a patch which should fix bug #118605 (which doesn’t solve the problem on my computer though).
How to test it:
You will have to enable the hardy-proposed repositories (Go to System/Administration/Software Sources/Updates and select “Proposed Updates (hardy-proposed)”) and upgrade to envyng-core (1.1.1ubuntu15), then launch EnvyNG and install the drivers.
Where to report:
If you have problems with EnvyNG (e.g. if EnvyNG crashes during the installation of the driver) you can report them here.
If you have problems with the drivers which EnvyNG installed you can report them here.
You can simply add a comment to one of the bugreports which you will find at these links if your problems are related to those reports or if you just want to confirm that either EnvyNG or the drivers work well for you (this will really help us).
If you want you can use this model to report:
Used EnvyNG (yes/no):
Worked with Ubuntu’s default restricted modules (yes/no):
Graphic card model:
Problem (solved/otherwise describe the problem):
Example:
If it works for you:
Used EnvyNG: yes
Worked with Ubuntu’s default restricted modules (yes/no): yes
Graphic card model: Geforce 7300GT
Problem: solved
OR if it doesn’t solve the problem
Used EnvyNG: yes
Worked with Ubuntu’s default restricted modules (yes/no): yes
Graphic card model: Geforce 7300GT
Problem: NVIDIA driver 169.12 still freezes my computer when I visit this website…
NOTE:
I’m working on this Bug too.
