EnvyNG installs Ubuntu's lrm but it should install its own packages

Bug #221304 reported by Alberto Milone on 2008-04-24
10
Affects Status Importance Assigned to Milestone
envyng-core (Ubuntu)
Undecided
Alberto Milone
Hardy
Undecided
Alberto Milone
linux-restricted-modules-envy-2.6.24 (Ubuntu)
Undecided
Alberto Milone
Hardy
Undecided
Unassigned

Bug Description

Binary package hint: envyng-core

EnvyNG used to install the restricted modules from my PPA however, because of some concerns about security, EnvyNG no longer does so and relies on Ubuntu's default linux-restricted-modules. See this bugreport:
https://bugs.launchpad.net/bugs/220385

This makes pointless the use of EnvyNG since the packages which it's supposed to install contain improvements (e.g. support for CUDA and dkms). As Steve Langasek pointed out, it is not possible to have linux-restricted-modules which have the same name (e.g. nvidia-glx-new) but different versions of the ones available in main.

A possible solution would be to build EnvyNG's restricted modules with different names so that for example we have packages like nvidia-glx-new-envy, nvidia-glx-envy, and so on. Such packages could be uploaded to multiverse and should not cause problems with the ones in main.

Dist-upgrades to Intrepid Ibex won't be broken if we make sure that Intrepid's restricted packages (in main) replace (by using something like “Replaces: nvidia-glx-new-envy”, etc.) the ones which we will upload to multiverse in Hardy.

TEST CASE: a user installs EnvyNG and expects it to install the packages with all the features which EnvyNG used to deliver.

Of course I'm open to other solutions.

Related branches

Changed in envyng-core:
assignee: nobody → albertomilone
status: New → Confirmed
Martin Pitt (pitti) wrote :

In Intrepid final, those -envy packages should just be transitional packages to nvidia-glx-new, etc., and those should have proper Conflicts/Replaces. That way, a dist-upgrade to intrepid will go back to the l-r-m ones (which are current at that time), but we can update-envy packages again in intrepid-updates.

Please attach a debdiff for approval, I'll help you with sponsoring.

Alberto Milone (albertomilone) wrote :

I set up a repository so that my new packages can be tested. You will have to add this line to your sources.list (opening the link in your browser won't work):
deb http://albertomilone.com/ubuntu/my-repository binary/

I have also replaced the fglrx driver 8.3 with 8.4 since it solves a nasty bug. I only had to change a line of code (and to add the new AMD installer) in order to do this. This driver works well on my ATI X1600 pro.

The latest revision of envyng-core deals with such packages:
https://code.launchpad.net/~albertomilone/envy/envyng-core

I will upload the source code of the new drivers soon

Alberto Milone (albertomilone) wrote :

And in case you want to get the debs directly:
http://albertomilone.com/ubuntu/my-repository/binary/fglrx-amdcccle-envy_2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/fglrx-control-envy_8-4+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/fglrx-kernel-source-envy_8-4+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-glx-dev-envy_96.43.05+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-glx-envy_96.43.05+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-glx-legacy-dev-envy_71.86.04+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-glx-legacy-envy_71.86.04+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-glx-new-dev-envy_169.12+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-glx-new-envy_169.12+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-kernel-source-envy_96.43.05+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-legacy-kernel-source-envy_71.86.04+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/nvidia-new-kernel-source-envy_169.12+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/xorg-driver-fglrx-dev-envy_7.1.0-8-4+2.6.24.500-500.25~envy_i386.deb
http://albertomilone.com/ubuntu/my-repository/binary/xorg-driver-fglrx-envy_7.1.0-8-4+2.6.24.500-500.25~envy_i386.deb

Furthermore have changed the way in which EnvyNG checks the versions of the packages so that it asks python-apt about them. It's all in revision 49 of my bazaar branch:
https://code.launchpad.net/~albertomilone/envy/envyng-core

Alberto Milone (albertomilone) wrote :

I think I will have to rename the source code to linux-restricted-modules-envy so that it doesn't conflict with linux-restricted-modules

Alberto Milone (albertomilone) wrote :

I have updated envyng-core's list of card ids so as to solve this problem:
https://bugs.launchpad.net/envy/+bug/224004

Martin Pitt (pitti) wrote :

Accepted and NEWed into hardy-proposed multiverse. Please test and give feedback here.

Changed in envyng-core:
status: Confirmed → Fix Committed
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Changed in linux-restricted-modules-envy-2.6.24:
status: New → Fix Committed
assignee: nobody → albertomilone
status: New → In Progress
Martin Pitt (pitti) wrote :

New l-r-m-envy accepted into hardy-proposed, please test.

Kame (jack-pot) wrote :

Roger that.
Waiting to see release .29 in repos.

Martin Pitt (pitti) wrote :

.29 accepted.

Alberto Milone (albertomilone) wrote :

As you can read in the following link to his comment, the problem reported by Kame didn't depend on the lrm-envy:
https://bugs.launchpad.net/ubuntu/+source/envyng-core/+bug/227717/comments/27

Furthermore a number of users have confirmed that the drivers work for them, not only in the following bugreport but also in private emails and on my blog:
https://bugs.launchpad.net/ubuntu/+source/envyng-core/+bug/227717

Link to the comments to my blog post:
http://albertomilone.com/wordpress/?p=187#comments

I think that the lrm-envy can be safely moved to stable and that we can close this bugreport.

Martin Pitt (pitti) wrote :

Copied l-r-m-envy-2.6.24 to hardy-updates and intrepid.

Changed in linux-restricted-modules-envy-2.6.24:
status: Fix Committed → Fix Released
status: In Progress → Fix Released
Bob Kline (bkline) wrote :

Alberto:

I tested the new version with the GeForce 7100 / NVIDIA nForce 630i as you requested, and the behavior is still the same as described in https://bugs.launchpad.net/envy/+bug/224004/comments/2 (using envyng to install the driver leaves the display in 800x600 resolution, even though if I run nVidia's installer directly the installed driver works correctly and I get the 1280x1024 resolution back again). I have to re-run the nVidia installer again periodically to keep up with Ubuntu kernel upgrades, so it would be nice to have the machine brought back into the Ubuntu/envy fold at some point.

Bob

Martin Pitt (pitti) wrote :

envyng-core copied to hardy-updates and intrepid.

Changed in envyng-core:
status: Fix Committed → Fix Released
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers