What is hardware enablement (HWE)?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I see the linux-hwe-generic package as part of the kernels you can install in Ubuntu.
What is hardware enablement (HWE)?
kernel hardware-enablement-stack
add a comment |
I see the linux-hwe-generic package as part of the kernels you can install in Ubuntu.
What is hardware enablement (HWE)?
kernel hardware-enablement-stack
add a comment |
I see the linux-hwe-generic package as part of the kernels you can install in Ubuntu.
What is hardware enablement (HWE)?
kernel hardware-enablement-stack
I see the linux-hwe-generic package as part of the kernels you can install in Ubuntu.
What is hardware enablement (HWE)?
kernel hardware-enablement-stack
kernel hardware-enablement-stack
edited Nov 29 '16 at 15:35
Jorge Castro
37.4k107423618
37.4k107423618
asked Jan 29 '13 at 9:05
nelaaronelaaro
6,13242640
6,13242640
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Brand new hardware devices are released to the public always more frequently. And we want such hardware to be always working on Ubuntu, even if it has been released after an Ubuntu release. Six months (the time it takes for a new Ubuntu release to be made) is a very long period in the IT field. Hardware Enablement (HWE) is about that: catching up with the newest hardware technologies.
Now, how does Ubuntu want to reach the goal of Hardware Enablement? Using rolling releases for the kernel: as soon as a new kernel is released, it is packaged for Ubuntu, tested (via the proposed pocket and special Q/A methodologies), and made available to Ubuntu users. This method has of course some disadvantages: releasing a new kernel too quickly may introduce some bugs and issues, and may not be suitable for the enterprise.
The solution? Offering different kernels for different users. Therefore Ubuntu will offer at least two kernels: the General Availability (GA) kernel, i.e. the most stable kernel, which does not get updated to point releases; and the Hardware Enablement (HWE) kernel, i.e. the most recent kernel released. This is why you are seeing both the linux-generic and the linux-hwe-generic packages.
Finally, if you are interested in developing or testing the newest kernel technologies, look at the Ubuntu Hardware Debugging web site.
References:
- https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
4
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@w-sky You can check theBOOT_IMAGEparameter in/proc/cmdline. Run this command to find out the package name:sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.
– Anthony Wong
Sep 6 '18 at 9:44
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f248914%2fwhat-is-hardware-enablement-hwe%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
Brand new hardware devices are released to the public always more frequently. And we want such hardware to be always working on Ubuntu, even if it has been released after an Ubuntu release. Six months (the time it takes for a new Ubuntu release to be made) is a very long period in the IT field. Hardware Enablement (HWE) is about that: catching up with the newest hardware technologies.
Now, how does Ubuntu want to reach the goal of Hardware Enablement? Using rolling releases for the kernel: as soon as a new kernel is released, it is packaged for Ubuntu, tested (via the proposed pocket and special Q/A methodologies), and made available to Ubuntu users. This method has of course some disadvantages: releasing a new kernel too quickly may introduce some bugs and issues, and may not be suitable for the enterprise.
The solution? Offering different kernels for different users. Therefore Ubuntu will offer at least two kernels: the General Availability (GA) kernel, i.e. the most stable kernel, which does not get updated to point releases; and the Hardware Enablement (HWE) kernel, i.e. the most recent kernel released. This is why you are seeing both the linux-generic and the linux-hwe-generic packages.
Finally, if you are interested in developing or testing the newest kernel technologies, look at the Ubuntu Hardware Debugging web site.
References:
- https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
4
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@w-sky You can check theBOOT_IMAGEparameter in/proc/cmdline. Run this command to find out the package name:sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.
– Anthony Wong
Sep 6 '18 at 9:44
add a comment |
Brand new hardware devices are released to the public always more frequently. And we want such hardware to be always working on Ubuntu, even if it has been released after an Ubuntu release. Six months (the time it takes for a new Ubuntu release to be made) is a very long period in the IT field. Hardware Enablement (HWE) is about that: catching up with the newest hardware technologies.
Now, how does Ubuntu want to reach the goal of Hardware Enablement? Using rolling releases for the kernel: as soon as a new kernel is released, it is packaged for Ubuntu, tested (via the proposed pocket and special Q/A methodologies), and made available to Ubuntu users. This method has of course some disadvantages: releasing a new kernel too quickly may introduce some bugs and issues, and may not be suitable for the enterprise.
The solution? Offering different kernels for different users. Therefore Ubuntu will offer at least two kernels: the General Availability (GA) kernel, i.e. the most stable kernel, which does not get updated to point releases; and the Hardware Enablement (HWE) kernel, i.e. the most recent kernel released. This is why you are seeing both the linux-generic and the linux-hwe-generic packages.
Finally, if you are interested in developing or testing the newest kernel technologies, look at the Ubuntu Hardware Debugging web site.
References:
- https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
4
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@w-sky You can check theBOOT_IMAGEparameter in/proc/cmdline. Run this command to find out the package name:sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.
– Anthony Wong
Sep 6 '18 at 9:44
add a comment |
Brand new hardware devices are released to the public always more frequently. And we want such hardware to be always working on Ubuntu, even if it has been released after an Ubuntu release. Six months (the time it takes for a new Ubuntu release to be made) is a very long period in the IT field. Hardware Enablement (HWE) is about that: catching up with the newest hardware technologies.
Now, how does Ubuntu want to reach the goal of Hardware Enablement? Using rolling releases for the kernel: as soon as a new kernel is released, it is packaged for Ubuntu, tested (via the proposed pocket and special Q/A methodologies), and made available to Ubuntu users. This method has of course some disadvantages: releasing a new kernel too quickly may introduce some bugs and issues, and may not be suitable for the enterprise.
The solution? Offering different kernels for different users. Therefore Ubuntu will offer at least two kernels: the General Availability (GA) kernel, i.e. the most stable kernel, which does not get updated to point releases; and the Hardware Enablement (HWE) kernel, i.e. the most recent kernel released. This is why you are seeing both the linux-generic and the linux-hwe-generic packages.
Finally, if you are interested in developing or testing the newest kernel technologies, look at the Ubuntu Hardware Debugging web site.
References:
- https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
Brand new hardware devices are released to the public always more frequently. And we want such hardware to be always working on Ubuntu, even if it has been released after an Ubuntu release. Six months (the time it takes for a new Ubuntu release to be made) is a very long period in the IT field. Hardware Enablement (HWE) is about that: catching up with the newest hardware technologies.
Now, how does Ubuntu want to reach the goal of Hardware Enablement? Using rolling releases for the kernel: as soon as a new kernel is released, it is packaged for Ubuntu, tested (via the proposed pocket and special Q/A methodologies), and made available to Ubuntu users. This method has of course some disadvantages: releasing a new kernel too quickly may introduce some bugs and issues, and may not be suitable for the enterprise.
The solution? Offering different kernels for different users. Therefore Ubuntu will offer at least two kernels: the General Availability (GA) kernel, i.e. the most stable kernel, which does not get updated to point releases; and the Hardware Enablement (HWE) kernel, i.e. the most recent kernel released. This is why you are seeing both the linux-generic and the linux-hwe-generic packages.
Finally, if you are interested in developing or testing the newest kernel technologies, look at the Ubuntu Hardware Debugging web site.
References:
- https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
edited Nov 29 '16 at 15:36
Jorge Castro
37.4k107423618
37.4k107423618
answered Jan 29 '13 at 10:37
Andrea CorbelliniAndrea Corbellini
12.4k24566
12.4k24566
4
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@w-sky You can check theBOOT_IMAGEparameter in/proc/cmdline. Run this command to find out the package name:sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.
– Anthony Wong
Sep 6 '18 at 9:44
add a comment |
4
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@w-sky You can check theBOOT_IMAGEparameter in/proc/cmdline. Run this command to find out the package name:sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.
– Anthony Wong
Sep 6 '18 at 9:44
4
4
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Do you happen to know if there's a more current link describing the different kernel flavors? Currently a bit stumped between linux-generic, linux-current-generic, linux-generic-lts-<release> in precise lts
– Michael Renner
Jun 24 '15 at 14:11
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
Did this stop before Ubuntu 18.04? Ubuntu 18.04 contains transitional package linux-generic-hwe-16.04 which just depends on linux-generic.
– Stéphane Gourichon
May 29 '18 at 15:34
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
How do I see or choose which kernel is actually being used in my system? uname -r simply results: 4.15.0-24-generic
– w-sky
Jul 21 '18 at 12:01
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@StéphaneGourichon If you are using the 16.04 HWE stack, the kernel will keep rolling until the next LTS, which in this case is 18.04. After that, you will stay with the LTS kernel until 16.04 reaches EOL.
– Anthony Wong
Sep 6 '18 at 9:26
@w-sky You can check the
BOOT_IMAGE parameter in /proc/cmdline. Run this command to find out the package name: sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.– Anthony Wong
Sep 6 '18 at 9:44
@w-sky You can check the
BOOT_IMAGE parameter in /proc/cmdline. Run this command to find out the package name: sed 's/^BOOT_IMAGE=([^ ]*) .*/1/' /proc/cmdline | sed 's/.efi.signed//' | xargs dpkg -S.– Anthony Wong
Sep 6 '18 at 9:44
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f248914%2fwhat-is-hardware-enablement-hwe%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