On 2013-06-23 18:55 +0200, Andrei POPESCU wrote:
> On Sb, 22 iun 13, 19:02:20, CHK Webmaster wrote:
>> Hi,
>>
>> I write here cause I'm not sure where report this issue. It happens when
>> upgrading my system via apt-get. The upgrade includes
>> linux-image-3.9.1-amd64 but does not include nvidia-kernel-3.9.1-amd64
>> in which depends the nvidia proprietary driver.
>
> Well, it's amazing that there even are nvidia-kernel-<version> packages
> in testing and unstable. These used to be built only near releases.
Maybe it would be better to not build them at all, but rather rely on
the user to do that - this is how other kernel modules are handled these
days, and thanks to dkms it is not a big problem for users anymore.
>> So the result was a X system breaks, that cannot be loaded cause X.org
>> not found the nvidia module. The issue can be solved installing manually
>> the related nvidia-kernel package.
>
> Well, on testing and unstable you are expected to be able to watch out
> for such things. Besides, nvidia and related packages are mostly
> non-free, so they don't have the same priority as free packages do.
Exactly.
> It might be better, easier for you to install the nvidia-kernel-dkms
> package and make sure you have the matching kernel headers installed,
> e.g. by installing linux-image-amd64 and linux-headers-amd64. I expect
> those metapackages to be updated at the same time, but you won't be able
> to update to the latest & greatest kernel as soon as it is available,
> you'll have to wait until the metapackage pulls it.
Note that this is only a problem in unstable, testing users should not
suffer from it.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87k3lkagsx....@turtle.gmx.de
