kernel nvidia dkms rebuild after upgrade?
Hello, After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in light of meltdown -- my nvidia drivers failed to load. Rebulding the modules manually -- https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017 -- did fix it. Did I miss something? Cheers! -- Boyan Penkov
Re: kernel nvidia dkms rebuild after upgrade?
Thanks, Yao — in messing around with this, I did end up finding a thread that suggested installing libelf-dev — I did so, but I guess the order in which I did it make me recompile my dkms modules manually. Thanks for the note! -- Boyan Penkov www.boyanpenkov.com > On Jan 7, 2018, at 18:31, Yao Wei wrote: > > It is caused by a missing dependency libelf-dev. > It is already reported against linux-headers-4.14.0-3-amd64: > https://bugs.debian.org/886474 <https://bugs.debian.org/886474> > > I have the same symptom of broadcom-sta-dkms > > On Mon, 8 Jan 2018 at 02:47 Boyan Penkov <mailto:boyan.pen...@gmail.com>> wrote: > Hello, > > After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in > light of meltdown -- my nvidia drivers failed to load. > > Rebulding the modules manually -- > https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017 > > <https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017> > -- did fix it. > > Did I miss something? > > Cheers! > > -- > Boyan Penkov >
Re: kernel nvidia dkms rebuild after upgrade?
Hello Dan — thanks kindly, I had indeed not noticed…. I guess I’ll have a chance to test if the libelf-dev issue is really the fix when the patches do roll out. In that vein, I would like to note that https://security-tracker.debian.org/tracker/CVE-2017-5754 <https://security-tracker.debian.org/tracker/CVE-2017-5754> makes no mention of bpo kernels in backports. Is this by design? Cheers! -- Boyan Penkov www.boyanpenkov.com > On Jan 7, 2018, at 18:44, Daniel Reichelt wrote: > > On 01/07/2018 07:47 PM, Boyan Penkov wrote: >> and a backport (4.14.0-bpo2) -- in light of meltdown -- > > To avoid a false sense of security: according to [1], [2], [3], the > current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT* > yet include any mitigations against meltdown. > > Daniel > > > > [1] https://security-tracker.debian.org/tracker/CVE-2017-5753 > [2] https://security-tracker.debian.org/tracker/CVE-2017-5754 > [3] https://security-tracker.debian.org/tracker/CVE-2017-5715 >
Fingerprint-GUI?
Hello all, Is there an effort to package fingerprint-GUI? Does anybody have a one-off .deb for Jessie for this that they may be using? http://www.ullrich-online.cc/fingerprint/ Cheers! -- Boyan Penkov http://www.boyanpenkov.com
Re: Fingerprint-GUI?
I could certainly see your point; also, all the relevant upstreams are pretty slowly developed. However, for some cases and with appropriate cautions, using fingerprint readers may be useful. This effort is not on the critical path, it seems. cheers! On Sat, May 07 2016, Andrew Shadura wrote: > On 7 May 2016 at 22:33, Boyan Penkov wrote: > > Is there an effort to package fingerprint-GUI? Does anybody have a one-off > > .deb for Jessie for this that they may be using? > > Fingerprint readers are insecure, and that's something that can't be > fixed. I'd prefer to see fewer fingerprint-related software packages > in Debian rather than more. -- Boyan Penkov http://www.boyanpenkov.com
