Upgrading kernel on debian 8 Jessie The 2019 Stack Overflow Developer Survey Results Are...
Why did Peik say, "I'm not an animal"?
What is the motivation for a law requiring 2 parties to consent for recording a conversation
Likelihood that a superbug or lethal virus could come from a landfill
Cooking pasta in a water boiler
Why does the nucleus not repel itself?
Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
Ubuntu Server install with full GUI
Short story: man watches girlfriend's spaceship entering a 'black hole' (?) forever
A word that means fill it to the required quantity
Why couldn't they take pictures of a closer black hole?
How do PCB vias affect signal quality?
Is Cinnamon a desktop environment or a window manager? (Or both?)
A female thief is not sold to make restitution -- so what happens instead?
What is preventing me from simply constructing a hash that's lower than the current target?
Why not take a picture of a closer black hole?
If I score a critical hit on an 18 or higher, what are my chances of getting a critical hit if I roll 3d20?
Is it okay to consider publishing in my first year of PhD?
Correct punctuation for showing a character's confusion
Pokemon Turn Based battle (Python)
Mathematics of imaging the black hole
Button changing its text & action. Good or terrible?
The phrase "to the numbers born"?
Why isn't the circumferential light around the M87 black hole's event horizon symmetric?
Accepted by European university, rejected by all American ones I applied to? Possible reasons?
Upgrading kernel on debian 8 Jessie
The 2019 Stack Overflow Developer Survey Results Are InProblem 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;
}
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
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
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
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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 removelinux-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_releaseoften helps to sort out dependencies.
– dirkt
Feb 15 '17 at 18:56
add a comment |
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
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
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
debian docker kernel linux-kernel debian-jessie
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
asked Feb 15 '17 at 14:57
BackSlashBackSlash
11115
11115
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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 removelinux-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_releaseoften helps to sort out dependencies.
– dirkt
Feb 15 '17 at 18:56
add a comment |
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 removelinux-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_releaseoften 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
add a comment |
1 Answer
1
active
oldest
votes
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
answered Feb 22 '17 at 8:05
user415594user415594
1
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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
answered Feb 22 '17 at 8:05
user415594user415594
1
add a comment |
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
answered Feb 22 '17 at 8:05
user415594user415594
1
add a comment |
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
answered Feb 22 '17 at 8:05
user415594user415594
1
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
answered Feb 22 '17 at 8:05
user415594user415594
1
answered Feb 22 '17 at 8:05
user415594user415594
1
answered Feb 22 '17 at 8:05
user415594user415594
1
answered Feb 22 '17 at 8:05
user415594user415594
1
1
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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_releaseoften helps to sort out dependencies.– dirkt
Feb 15 '17 at 18:56