On Sun, Apr 09, 2017 at 09:23:02PM +0200, Andreas Beckmann wrote: > On 2017-04-09 19:32, A. F. Cano wrote: > > From /var/log/apt/history.log.1.gz: > > > > nvidia-legacy-304xx-alternative:i386 (304.131-1, 304-135-2) > > > > One of possibly hundreds of packages upgraded on: > > > > Start-Date: 2017-03-28 02:17:28 > > End-Date: 2017-03-28 05:12:29 > > > > Nothing else about this package in the log file. No errors apparently. > > /var/log/apt/term.log* should have the corresponding transcripts from > apt running dpkg ...
Yes, the same warnings below were generated on 2017-04-01 when processing triggers for nvidia-legacy-304xx-alternative (304.135-2) as a result of "previously unselected package libnvidia-legacy-304xx-cfg1:i386" The only other related message was: Processing triggers for nvidia-legacy-304xx-alternative (304.135-2) ... update-alternatives: updating alternative /usr/lib/nvidia/legacy-304xx because link group nvidia has changed slave links This last one was after the old (304.131-1) module was removed and before the new one was installed. It's pretty amazing that it all works so well with so many inter-dependencies. Kudos to the maintainers of the nvidia ecosystem. > > # dpkg-reconfigure nvidia-legacy-304xx-alternative > > Processing triggers for nvidia-legacy-304xx-alternative (304.135-2) ... > > update-alternatives: warning: forcing reinstallation of alternative > > /usr/lib/nvidia/legacy-304xx because link group nvidia is broken > > that is not unexpected > > > update-alternatives: warning: not replacing > > /etc/nvidia/nvidia-modprobe.conf with a link > > That looks like a local modification ... Probably a leftover from the Jessie installation. It has a date of Dec 14 2015 and I only set up this machine for the first time with Jessie in September 2016. The content of this file is: alias nvidia nvidia-current remove nvidia-current rmmod nvidia-uvm nvidia > Andreas Than you all. Augustine
