Punting from linux-meta -> linux-restricted-modules-2.6.20
Bug #120943 addresses this for Gusty, however I suspect it is unlikely such an invasive change like this would be made for Feisty. In an ideal world you would "just" turn nvidia-glx-new into (which is currently 1,0-9755 series) into 100.14.09. However doing so WILL cause regressions and various issues on cards that currently work with with the 1,0-9755 driver. Introducing a fourth nvidia-glx package would be... tough... given that we are still seeing fallout from the creation of nvidia-glx-new (see Bug #105756 and Bug #98641 ). Trying to manage the migration path alone would be a headache.
Punting from linux-meta -> linux-restricte d-modules- 2.6.20
Bug #120943 addresses this for Gusty, however I suspect it is unlikely such an invasive change like this would be made for Feisty. In an ideal world you would "just" turn nvidia-glx-new into (which is currently 1,0-9755 series) into 100.14.09. However doing so WILL cause regressions and various issues on cards that currently work with with the 1,0-9755 driver. Introducing a fourth nvidia-glx package would be... tough... given that we are still seeing fallout from the creation of nvidia-glx-new (see Bug #105756 and Bug #98641 ). Trying to manage the migration path alone would be a headache.