[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Recent linux-image update broke CPU fan



On Mon, 30 Nov 2015 18:31:46 +0000
Lisi Reisz <lisi.reisz@gmail.com> wrote:

> On Monday 30 November 2015 15:02:01 Sven Arvidsson wrote:
> > On Mon, 2015-11-30 at 12:10 +0000, Lisi Reisz wrote:
> > > On Sunday 29 November 2015 22:18:51 Neal P. Murphy wrote:
> > > > As of 28 November 2015, the latest update to linux-image-3.16.0-4
> > >
> > > -amd64
> > >
> > > > versus the previous update. I think the latest update is:
> > > > linux-image-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u6_amd64.deb
> > > > and the previous is probably ...deb8u5.... So how do I tell it to
> > >
> > > uninstall
> > >
> > > > 'u6' and install 'u5'?
> > >
> > > Surely you have not uninstalled the earlier one?  So just ask GRUB to
> > > change
> > > the default to the older kernel.
> >
> > That's an update to kernel package, so not a new kernel, are you sure
> > those can be installed in parallel?
> 
> You've slightly lost me - when is a new kernel a new kernel and when is it an 
> update?  I have:

I suspect that when it appears as a 'new package', it's a new kernel and will have a new entry in grub. That's usually when the kernel minor version is bumped. Or when one installs a kernel from backports, testing, or unstable.

But security updates do not count as new pkgs. Thus the kernel is merely 'replaced'. In fact, the previous updates (1-5) are no longer cached and I can't reinstall them.

In the case of stock Jessie, the kernel pkg is (pretty much) linux-image-3.16.0-4-amd64; that part does not change for security updates.

N


Reply to: