Upgrading kernel on debian 8 Jessie Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Problem upgrading kernel on debian 3.1update from debian lenny to squeezeCompile Kernel Debian SqueezeLinode Kernel HeadersDebian 8 Jessie - Docker can't run ImageWhy am I having issues upgrading the kernel on a fresh Ubuntu 16.04 installation?Cannot install openjdk-8-jre-headless on Debian JessieDebian Jessie Kernel won't install, could be a grub2 issue?What is the recommended method of installing an arbitrary version of a package using apt?Upgrading from Debian 8 (Jessie) to 9 (Stretch)

Irreducible of finite Krull dimension implies quasi-compact?

Why are the trig functions versine, haversine, exsecant, etc, rarely used in modern mathematics?

When a candle burns, why does the top of wick glow if bottom of flame is hottest?

Why aren't air breathing engines used as small first stages

また usage in a dictionary

How to show element name in portuguese using elements package?

Does classifying an integer as a discrete log require it be part of a multiplicative group?

What is the meaning of the simile “quick as silk”?

How to convince students of the implication truth values?

Can an alien society believe that their star system is the universe?

Can melee weapons be used to deliver Contact Poisons?

Is the Standard Deduction better than Itemized when both are the same amount?

How would a mousetrap for use in space work?

Why wasn't DOSKEY integrated with COMMAND.COM?

What is the longest distance a player character can jump in one leap?

Is there such thing as an Availability Group failover trigger?

Can a new player join a group only when a new campaign starts?

How to Make a Beautiful Stacked 3D Plot

How do I make this wiring inside cabinet safer? (Pic)

Is it fair for a professor to grade us on the possession of past papers?

Is "Reachable Object" really an NP-complete problem?

Do I really need to have a message in a novel to appeal to readers?

What's the meaning of "fortified infraction restraint"?

Circuit to "zoom in" on mV fluctuations of a DC signal?



Upgrading kernel on debian 8 Jessie



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Problem upgrading kernel on debian 3.1update from debian lenny to squeezeCompile Kernel Debian SqueezeLinode Kernel HeadersDebian 8 Jessie - Docker can't run ImageWhy am I having issues upgrading the kernel on a fresh Ubuntu 16.04 installation?Cannot install openjdk-8-jre-headless on Debian JessieDebian Jessie Kernel won't install, could be a grub2 issue?What is the recommended method of installing an arbitrary version of a package using apt?Upgrading from Debian 8 (Jessie) to 9 (Stretch)



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I have a Debian 8 Jessie server, and I'd like to upgrade my kernel to at least version 4, in order to use overlay fs with Docker.



My current kernel is:



$ uname -r
3.16.0-4-amd64


I followed a guide which stated to add the backports repository to the /etc/apt/sources.list file. I added this line:



deb http://httpredir.debian.org/debian jessie-backports main


I did an apt-get update and this is now the output of apt-cache search linux-image:



linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-headers-4.8.0-0.bpo.2-amd64 - Header files for Linux 4.8.0-0.bpo.2-amd64
linux-headers-4.8.0-0.bpo.2-rt-amd64 - Header files for Linux 4.8.0-0.bpo.2-rt-amd64
linux-headers-4.9.0-0.bpo.1-amd64 - Header files for Linux 4.9.0-0.bpo.1-amd64
linux-headers-4.9.0-0.bpo.1-rt-amd64 - Header files for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.8.0-0.bpo.2-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-amd64
linux-image-4.8.0-0.bpo.2-amd64-unsigned - Linux 4.8 for 64-bit PCs
linux-image-4.8.0-0.bpo.2-rt-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-rt-amd64
linux-image-4.8.0-0.bpo.2-rt-amd64-unsigned - Linux 4.8 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-0.bpo.1-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-amd64
linux-image-4.9.0-0.bpo.1-amd64-unsigned - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-0.bpo.1-rt-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.9.0-0.bpo.1-rt-amd64-unsigned - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-headers-4.8.0-2-grsec-amd64 - Header files for Linux 4.8.0-2-grsec-amd64
linux-image-4.8.0-2-grsec-amd64 - Linux 4.8 for 64-bit PCs, Grsecurity protection
linux-image-grsec-amd64 - Linux image meta-package, grsec featureset
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-image-4.8.0-0.bpo.2-amd64 - Linux 4.8 for 64-bit PCs (signed)
linux-image-4.8.0-0.bpo.2-rt-amd64 - Linux 4.8 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-4.9.0-0.bpo.1-amd64 - Linux 4.9 for 64-bit PCs (signed)
linux-image-4.9.0-0.bpo.1-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)


The guide said to continue with



sudo apt-get install linux-image-amd64/jessie-backports


I did it, and I got this output:



$ sudo apt-get install linux-image-amd64/jessie-backports

Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.9+78~bpo8+1' (Debian Backports:jessie-backports [amd64]) for 'linux-image-amd64'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
linux-image-amd64 : Depends: linux-image-4.9.0-0.bpo.1-amd64
E: Unable to correct problems, you have held broken packages.


What should I do from here? Should I explicitly install linux-image-4.9.0-0.bpo.1-rt-amd64 instead of linux-image-amd64? If yes, should I install other packages along with it?



p.s. Does installing a new kernel automatically remove the older one or do I have to remove the older one manually?










share|improve this question






















  • Can you maybe try to fix first the unmet dependencies with askubuntu.com/questions/140246/… ?

    – Tolsadus
    Feb 15 '17 at 16:39











  • @Tolsadus But the unmet dependencies came when I added that repo, so I think it is causing the issue. That's why I'm asking what should I do...

    – BackSlash
    Feb 15 '17 at 16:46











  • @Tolsadus In fact I can install any software, it is just the kernel update that fails with that message

    – BackSlash
    Feb 15 '17 at 16:48






  • 1





    It's perfectly fine to remove linux-image-amd64 (which is just a meta-package) and install a particular image. Not using the meta-package means you must explicitely upgrade your kernel next time. You'll have to remove the old one manually (unless you want both, for debugging/safety purposes). apt-get -t target_release often helps to sort out dependencies.

    – dirkt
    Feb 15 '17 at 18:56

















1















I have a Debian 8 Jessie server, and I'd like to upgrade my kernel to at least version 4, in order to use overlay fs with Docker.



My current kernel is:



$ uname -r
3.16.0-4-amd64


I followed a guide which stated to add the backports repository to the /etc/apt/sources.list file. I added this line:



deb http://httpredir.debian.org/debian jessie-backports main


I did an apt-get update and this is now the output of apt-cache search linux-image:



linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-headers-4.8.0-0.bpo.2-amd64 - Header files for Linux 4.8.0-0.bpo.2-amd64
linux-headers-4.8.0-0.bpo.2-rt-amd64 - Header files for Linux 4.8.0-0.bpo.2-rt-amd64
linux-headers-4.9.0-0.bpo.1-amd64 - Header files for Linux 4.9.0-0.bpo.1-amd64
linux-headers-4.9.0-0.bpo.1-rt-amd64 - Header files for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.8.0-0.bpo.2-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-amd64
linux-image-4.8.0-0.bpo.2-amd64-unsigned - Linux 4.8 for 64-bit PCs
linux-image-4.8.0-0.bpo.2-rt-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-rt-amd64
linux-image-4.8.0-0.bpo.2-rt-amd64-unsigned - Linux 4.8 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-0.bpo.1-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-amd64
linux-image-4.9.0-0.bpo.1-amd64-unsigned - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-0.bpo.1-rt-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.9.0-0.bpo.1-rt-amd64-unsigned - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-headers-4.8.0-2-grsec-amd64 - Header files for Linux 4.8.0-2-grsec-amd64
linux-image-4.8.0-2-grsec-amd64 - Linux 4.8 for 64-bit PCs, Grsecurity protection
linux-image-grsec-amd64 - Linux image meta-package, grsec featureset
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-image-4.8.0-0.bpo.2-amd64 - Linux 4.8 for 64-bit PCs (signed)
linux-image-4.8.0-0.bpo.2-rt-amd64 - Linux 4.8 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-4.9.0-0.bpo.1-amd64 - Linux 4.9 for 64-bit PCs (signed)
linux-image-4.9.0-0.bpo.1-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)


The guide said to continue with



sudo apt-get install linux-image-amd64/jessie-backports


I did it, and I got this output:



$ sudo apt-get install linux-image-amd64/jessie-backports

Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.9+78~bpo8+1' (Debian Backports:jessie-backports [amd64]) for 'linux-image-amd64'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
linux-image-amd64 : Depends: linux-image-4.9.0-0.bpo.1-amd64
E: Unable to correct problems, you have held broken packages.


What should I do from here? Should I explicitly install linux-image-4.9.0-0.bpo.1-rt-amd64 instead of linux-image-amd64? If yes, should I install other packages along with it?



p.s. Does installing a new kernel automatically remove the older one or do I have to remove the older one manually?










share|improve this question






















  • Can you maybe try to fix first the unmet dependencies with askubuntu.com/questions/140246/… ?

    – Tolsadus
    Feb 15 '17 at 16:39











  • @Tolsadus But the unmet dependencies came when I added that repo, so I think it is causing the issue. That's why I'm asking what should I do...

    – BackSlash
    Feb 15 '17 at 16:46











  • @Tolsadus In fact I can install any software, it is just the kernel update that fails with that message

    – BackSlash
    Feb 15 '17 at 16:48






  • 1





    It's perfectly fine to remove linux-image-amd64 (which is just a meta-package) and install a particular image. Not using the meta-package means you must explicitely upgrade your kernel next time. You'll have to remove the old one manually (unless you want both, for debugging/safety purposes). apt-get -t target_release often helps to sort out dependencies.

    – dirkt
    Feb 15 '17 at 18:56













1












1








1








I have a Debian 8 Jessie server, and I'd like to upgrade my kernel to at least version 4, in order to use overlay fs with Docker.



My current kernel is:



$ uname -r
3.16.0-4-amd64


I followed a guide which stated to add the backports repository to the /etc/apt/sources.list file. I added this line:



deb http://httpredir.debian.org/debian jessie-backports main


I did an apt-get update and this is now the output of apt-cache search linux-image:



linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-headers-4.8.0-0.bpo.2-amd64 - Header files for Linux 4.8.0-0.bpo.2-amd64
linux-headers-4.8.0-0.bpo.2-rt-amd64 - Header files for Linux 4.8.0-0.bpo.2-rt-amd64
linux-headers-4.9.0-0.bpo.1-amd64 - Header files for Linux 4.9.0-0.bpo.1-amd64
linux-headers-4.9.0-0.bpo.1-rt-amd64 - Header files for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.8.0-0.bpo.2-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-amd64
linux-image-4.8.0-0.bpo.2-amd64-unsigned - Linux 4.8 for 64-bit PCs
linux-image-4.8.0-0.bpo.2-rt-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-rt-amd64
linux-image-4.8.0-0.bpo.2-rt-amd64-unsigned - Linux 4.8 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-0.bpo.1-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-amd64
linux-image-4.9.0-0.bpo.1-amd64-unsigned - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-0.bpo.1-rt-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.9.0-0.bpo.1-rt-amd64-unsigned - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-headers-4.8.0-2-grsec-amd64 - Header files for Linux 4.8.0-2-grsec-amd64
linux-image-4.8.0-2-grsec-amd64 - Linux 4.8 for 64-bit PCs, Grsecurity protection
linux-image-grsec-amd64 - Linux image meta-package, grsec featureset
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-image-4.8.0-0.bpo.2-amd64 - Linux 4.8 for 64-bit PCs (signed)
linux-image-4.8.0-0.bpo.2-rt-amd64 - Linux 4.8 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-4.9.0-0.bpo.1-amd64 - Linux 4.9 for 64-bit PCs (signed)
linux-image-4.9.0-0.bpo.1-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)


The guide said to continue with



sudo apt-get install linux-image-amd64/jessie-backports


I did it, and I got this output:



$ sudo apt-get install linux-image-amd64/jessie-backports

Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.9+78~bpo8+1' (Debian Backports:jessie-backports [amd64]) for 'linux-image-amd64'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
linux-image-amd64 : Depends: linux-image-4.9.0-0.bpo.1-amd64
E: Unable to correct problems, you have held broken packages.


What should I do from here? Should I explicitly install linux-image-4.9.0-0.bpo.1-rt-amd64 instead of linux-image-amd64? If yes, should I install other packages along with it?



p.s. Does installing a new kernel automatically remove the older one or do I have to remove the older one manually?










share|improve this question














I have a Debian 8 Jessie server, and I'd like to upgrade my kernel to at least version 4, in order to use overlay fs with Docker.



My current kernel is:



$ uname -r
3.16.0-4-amd64


I followed a guide which stated to add the backports repository to the /etc/apt/sources.list file. I added this line:



deb http://httpredir.debian.org/debian jessie-backports main


I did an apt-get update and this is now the output of apt-cache search linux-image:



linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-headers-4.8.0-0.bpo.2-amd64 - Header files for Linux 4.8.0-0.bpo.2-amd64
linux-headers-4.8.0-0.bpo.2-rt-amd64 - Header files for Linux 4.8.0-0.bpo.2-rt-amd64
linux-headers-4.9.0-0.bpo.1-amd64 - Header files for Linux 4.9.0-0.bpo.1-amd64
linux-headers-4.9.0-0.bpo.1-rt-amd64 - Header files for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.8.0-0.bpo.2-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-amd64
linux-image-4.8.0-0.bpo.2-amd64-unsigned - Linux 4.8 for 64-bit PCs
linux-image-4.8.0-0.bpo.2-rt-amd64-dbg - Debugging symbols for Linux 4.8.0-0.bpo.2-rt-amd64
linux-image-4.8.0-0.bpo.2-rt-amd64-unsigned - Linux 4.8 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-0.bpo.1-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-amd64
linux-image-4.9.0-0.bpo.1-amd64-unsigned - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-0.bpo.1-rt-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.1-rt-amd64
linux-image-4.9.0-0.bpo.1-rt-amd64-unsigned - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-headers-4.8.0-2-grsec-amd64 - Header files for Linux 4.8.0-2-grsec-amd64
linux-image-4.8.0-2-grsec-amd64 - Linux 4.8 for 64-bit PCs, Grsecurity protection
linux-image-grsec-amd64 - Linux image meta-package, grsec featureset
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-image-4.8.0-0.bpo.2-amd64 - Linux 4.8 for 64-bit PCs (signed)
linux-image-4.8.0-0.bpo.2-rt-amd64 - Linux 4.8 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-4.9.0-0.bpo.1-amd64 - Linux 4.9 for 64-bit PCs (signed)
linux-image-4.9.0-0.bpo.1-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)


The guide said to continue with



sudo apt-get install linux-image-amd64/jessie-backports


I did it, and I got this output:



$ sudo apt-get install linux-image-amd64/jessie-backports

Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.9+78~bpo8+1' (Debian Backports:jessie-backports [amd64]) for 'linux-image-amd64'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
linux-image-amd64 : Depends: linux-image-4.9.0-0.bpo.1-amd64
E: Unable to correct problems, you have held broken packages.


What should I do from here? Should I explicitly install linux-image-4.9.0-0.bpo.1-rt-amd64 instead of linux-image-amd64? If yes, should I install other packages along with it?



p.s. Does installing a new kernel automatically remove the older one or do I have to remove the older one manually?







debian docker kernel linux-kernel debian-jessie






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 15 '17 at 14:57









BackSlashBackSlash

11115




11115












  • Can you maybe try to fix first the unmet dependencies with askubuntu.com/questions/140246/… ?

    – Tolsadus
    Feb 15 '17 at 16:39











  • @Tolsadus But the unmet dependencies came when I added that repo, so I think it is causing the issue. That's why I'm asking what should I do...

    – BackSlash
    Feb 15 '17 at 16:46











  • @Tolsadus In fact I can install any software, it is just the kernel update that fails with that message

    – BackSlash
    Feb 15 '17 at 16:48






  • 1





    It's perfectly fine to remove linux-image-amd64 (which is just a meta-package) and install a particular image. Not using the meta-package means you must explicitely upgrade your kernel next time. You'll have to remove the old one manually (unless you want both, for debugging/safety purposes). apt-get -t target_release often helps to sort out dependencies.

    – dirkt
    Feb 15 '17 at 18:56

















  • Can you maybe try to fix first the unmet dependencies with askubuntu.com/questions/140246/… ?

    – Tolsadus
    Feb 15 '17 at 16:39











  • @Tolsadus But the unmet dependencies came when I added that repo, so I think it is causing the issue. That's why I'm asking what should I do...

    – BackSlash
    Feb 15 '17 at 16:46











  • @Tolsadus In fact I can install any software, it is just the kernel update that fails with that message

    – BackSlash
    Feb 15 '17 at 16:48






  • 1





    It's perfectly fine to remove linux-image-amd64 (which is just a meta-package) and install a particular image. Not using the meta-package means you must explicitely upgrade your kernel next time. You'll have to remove the old one manually (unless you want both, for debugging/safety purposes). apt-get -t target_release often helps to sort out dependencies.

    – dirkt
    Feb 15 '17 at 18:56
















Can you maybe try to fix first the unmet dependencies with askubuntu.com/questions/140246/… ?

– Tolsadus
Feb 15 '17 at 16:39





Can you maybe try to fix first the unmet dependencies with askubuntu.com/questions/140246/… ?

– Tolsadus
Feb 15 '17 at 16:39













@Tolsadus But the unmet dependencies came when I added that repo, so I think it is causing the issue. That's why I'm asking what should I do...

– BackSlash
Feb 15 '17 at 16:46





@Tolsadus But the unmet dependencies came when I added that repo, so I think it is causing the issue. That's why I'm asking what should I do...

– BackSlash
Feb 15 '17 at 16:46













@Tolsadus In fact I can install any software, it is just the kernel update that fails with that message

– BackSlash
Feb 15 '17 at 16:48





@Tolsadus In fact I can install any software, it is just the kernel update that fails with that message

– BackSlash
Feb 15 '17 at 16:48




1




1





It's perfectly fine to remove linux-image-amd64 (which is just a meta-package) and install a particular image. Not using the meta-package means you must explicitely upgrade your kernel next time. You'll have to remove the old one manually (unless you want both, for debugging/safety purposes). apt-get -t target_release often helps to sort out dependencies.

– dirkt
Feb 15 '17 at 18:56





It's perfectly fine to remove linux-image-amd64 (which is just a meta-package) and install a particular image. Not using the meta-package means you must explicitely upgrade your kernel next time. You'll have to remove the old one manually (unless you want both, for debugging/safety purposes). apt-get -t target_release often helps to sort out dependencies.

– dirkt
Feb 15 '17 at 18:56










1 Answer
1






active

oldest

votes


















0














I switched to the backport kernel for the same reason as you (docker). The backport kernel has dependencies on packages which are installed already, but not in a version that the backport kernel needs. The newer versions are also available in the backports repository. However, apt-get will not install dependencies automatically from the backports repo (unless configured to do so). In other words, you need to install the dependencies explicitly, together with the backport kernel.



The dependencies are



  • linux-base (I am sure about that)

  • kmod

  • initramfs-tools





share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f832713%2fupgrading-kernel-on-debian-8-jessie%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I switched to the backport kernel for the same reason as you (docker). The backport kernel has dependencies on packages which are installed already, but not in a version that the backport kernel needs. The newer versions are also available in the backports repository. However, apt-get will not install dependencies automatically from the backports repo (unless configured to do so). In other words, you need to install the dependencies explicitly, together with the backport kernel.



    The dependencies are



    • linux-base (I am sure about that)

    • kmod

    • initramfs-tools





    share|improve this answer



























      0














      I switched to the backport kernel for the same reason as you (docker). The backport kernel has dependencies on packages which are installed already, but not in a version that the backport kernel needs. The newer versions are also available in the backports repository. However, apt-get will not install dependencies automatically from the backports repo (unless configured to do so). In other words, you need to install the dependencies explicitly, together with the backport kernel.



      The dependencies are



      • linux-base (I am sure about that)

      • kmod

      • initramfs-tools





      share|improve this answer

























        0












        0








        0







        I switched to the backport kernel for the same reason as you (docker). The backport kernel has dependencies on packages which are installed already, but not in a version that the backport kernel needs. The newer versions are also available in the backports repository. However, apt-get will not install dependencies automatically from the backports repo (unless configured to do so). In other words, you need to install the dependencies explicitly, together with the backport kernel.



        The dependencies are



        • linux-base (I am sure about that)

        • kmod

        • initramfs-tools





        share|improve this answer













        I switched to the backport kernel for the same reason as you (docker). The backport kernel has dependencies on packages which are installed already, but not in a version that the backport kernel needs. The newer versions are also available in the backports repository. However, apt-get will not install dependencies automatically from the backports repo (unless configured to do so). In other words, you need to install the dependencies explicitly, together with the backport kernel.



        The dependencies are



        • linux-base (I am sure about that)

        • kmod

        • initramfs-tools






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 22 '17 at 8:05









        user415594user415594

        1




        1



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f832713%2fupgrading-kernel-on-debian-8-jessie%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

            Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

            What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company