How do I apply a patched kernel?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
I was following the discussion on this bug report;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244
And the solution was applying a patched kernel from;
https://people.canonical.com/~khfeng/lp1728244-testing/
Now, I'm not sure which files I should be using or how I can apply them. Can someone help please?
drivers kernel patch
add a comment |Â
up vote
0
down vote
favorite
I was following the discussion on this bug report;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244
And the solution was applying a patched kernel from;
https://people.canonical.com/~khfeng/lp1728244-testing/
Now, I'm not sure which files I should be using or how I can apply them. Can someone help please?
drivers kernel patch
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was following the discussion on this bug report;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244
And the solution was applying a patched kernel from;
https://people.canonical.com/~khfeng/lp1728244-testing/
Now, I'm not sure which files I should be using or how I can apply them. Can someone help please?
drivers kernel patch
I was following the discussion on this bug report;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244
And the solution was applying a patched kernel from;
https://people.canonical.com/~khfeng/lp1728244-testing/
Now, I'm not sure which files I should be using or how I can apply them. Can someone help please?
drivers kernel patch
asked Jun 1 at 14:41
![](https://i.stack.imgur.com/mY03p.png?s=32&g=1)
![](https://i.stack.imgur.com/mY03p.png?s=32&g=1)
hussam
3118
3118
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
First, make sure that your system it set so that the grub menu shows during boot and for long enough that you have time to select which kernel to boot. Typically, I use GRUB_TIMEOUT=20
.
Download all 5 files into some temporary directory. Then execute:
sudo dpkg -i *.deb
Then re-boot and during boot, select the test kernel.
If you are not using grub, then I don't know.
Eventually, you will want to delete the test kernel. To do so, you must be booted to another kernel, not the test version (i.e. you can not delete the currently running kernel). You can use the excellent utility from here, or do it manually. While I only ever use the server version of the utility, I'll show the manual method:
doug@s15:~$ dpkg -l | grep 4.17.0-1
ii linux-headers-4.17.0-1 4.17.0-1.2~lp1728244 all Header files related to Linux kernel version 4.17.0
ii linux-headers-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel headers for version 4.17.0 on 64 bit x86 SMP
ii linux-image-unsigned-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel image for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-extra-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
doug@s15:~$
doug@s15:~$ sudo dpkg -P linux-modules-extra-4.17.0-1-generic linux-modules-4.17.0-1-generic linux-image-unsigned-4.17.0-1-generic linux-headers-4.17.0-1-generic linux-headers-4.17.0-1
(Reading database ... 1480661 files and directories currently installed.)
Removing linux-modules-extra-4.17.0-1-generic (4.17.0-1.2~lp1728244) ...
...[deleted a bunch of lines]...
rmdir: failed to remove '/lib/modules/4.17.0-1-generic': Directory not empty
...
Notice that I reversed the purge list, so as not to get into dependency issues.
The directory thing seems to occur with 4.17 kernels, but the directory has a sub-directory which I guess confuses things. However, on my system it is gone anyhow.
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
First, make sure that your system it set so that the grub menu shows during boot and for long enough that you have time to select which kernel to boot. Typically, I use GRUB_TIMEOUT=20
.
Download all 5 files into some temporary directory. Then execute:
sudo dpkg -i *.deb
Then re-boot and during boot, select the test kernel.
If you are not using grub, then I don't know.
Eventually, you will want to delete the test kernel. To do so, you must be booted to another kernel, not the test version (i.e. you can not delete the currently running kernel). You can use the excellent utility from here, or do it manually. While I only ever use the server version of the utility, I'll show the manual method:
doug@s15:~$ dpkg -l | grep 4.17.0-1
ii linux-headers-4.17.0-1 4.17.0-1.2~lp1728244 all Header files related to Linux kernel version 4.17.0
ii linux-headers-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel headers for version 4.17.0 on 64 bit x86 SMP
ii linux-image-unsigned-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel image for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-extra-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
doug@s15:~$
doug@s15:~$ sudo dpkg -P linux-modules-extra-4.17.0-1-generic linux-modules-4.17.0-1-generic linux-image-unsigned-4.17.0-1-generic linux-headers-4.17.0-1-generic linux-headers-4.17.0-1
(Reading database ... 1480661 files and directories currently installed.)
Removing linux-modules-extra-4.17.0-1-generic (4.17.0-1.2~lp1728244) ...
...[deleted a bunch of lines]...
rmdir: failed to remove '/lib/modules/4.17.0-1-generic': Directory not empty
...
Notice that I reversed the purge list, so as not to get into dependency issues.
The directory thing seems to occur with 4.17 kernels, but the directory has a sub-directory which I guess confuses things. However, on my system it is gone anyhow.
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
add a comment |Â
up vote
1
down vote
accepted
First, make sure that your system it set so that the grub menu shows during boot and for long enough that you have time to select which kernel to boot. Typically, I use GRUB_TIMEOUT=20
.
Download all 5 files into some temporary directory. Then execute:
sudo dpkg -i *.deb
Then re-boot and during boot, select the test kernel.
If you are not using grub, then I don't know.
Eventually, you will want to delete the test kernel. To do so, you must be booted to another kernel, not the test version (i.e. you can not delete the currently running kernel). You can use the excellent utility from here, or do it manually. While I only ever use the server version of the utility, I'll show the manual method:
doug@s15:~$ dpkg -l | grep 4.17.0-1
ii linux-headers-4.17.0-1 4.17.0-1.2~lp1728244 all Header files related to Linux kernel version 4.17.0
ii linux-headers-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel headers for version 4.17.0 on 64 bit x86 SMP
ii linux-image-unsigned-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel image for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-extra-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
doug@s15:~$
doug@s15:~$ sudo dpkg -P linux-modules-extra-4.17.0-1-generic linux-modules-4.17.0-1-generic linux-image-unsigned-4.17.0-1-generic linux-headers-4.17.0-1-generic linux-headers-4.17.0-1
(Reading database ... 1480661 files and directories currently installed.)
Removing linux-modules-extra-4.17.0-1-generic (4.17.0-1.2~lp1728244) ...
...[deleted a bunch of lines]...
rmdir: failed to remove '/lib/modules/4.17.0-1-generic': Directory not empty
...
Notice that I reversed the purge list, so as not to get into dependency issues.
The directory thing seems to occur with 4.17 kernels, but the directory has a sub-directory which I guess confuses things. However, on my system it is gone anyhow.
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
First, make sure that your system it set so that the grub menu shows during boot and for long enough that you have time to select which kernel to boot. Typically, I use GRUB_TIMEOUT=20
.
Download all 5 files into some temporary directory. Then execute:
sudo dpkg -i *.deb
Then re-boot and during boot, select the test kernel.
If you are not using grub, then I don't know.
Eventually, you will want to delete the test kernel. To do so, you must be booted to another kernel, not the test version (i.e. you can not delete the currently running kernel). You can use the excellent utility from here, or do it manually. While I only ever use the server version of the utility, I'll show the manual method:
doug@s15:~$ dpkg -l | grep 4.17.0-1
ii linux-headers-4.17.0-1 4.17.0-1.2~lp1728244 all Header files related to Linux kernel version 4.17.0
ii linux-headers-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel headers for version 4.17.0 on 64 bit x86 SMP
ii linux-image-unsigned-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel image for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-extra-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
doug@s15:~$
doug@s15:~$ sudo dpkg -P linux-modules-extra-4.17.0-1-generic linux-modules-4.17.0-1-generic linux-image-unsigned-4.17.0-1-generic linux-headers-4.17.0-1-generic linux-headers-4.17.0-1
(Reading database ... 1480661 files and directories currently installed.)
Removing linux-modules-extra-4.17.0-1-generic (4.17.0-1.2~lp1728244) ...
...[deleted a bunch of lines]...
rmdir: failed to remove '/lib/modules/4.17.0-1-generic': Directory not empty
...
Notice that I reversed the purge list, so as not to get into dependency issues.
The directory thing seems to occur with 4.17 kernels, but the directory has a sub-directory which I guess confuses things. However, on my system it is gone anyhow.
First, make sure that your system it set so that the grub menu shows during boot and for long enough that you have time to select which kernel to boot. Typically, I use GRUB_TIMEOUT=20
.
Download all 5 files into some temporary directory. Then execute:
sudo dpkg -i *.deb
Then re-boot and during boot, select the test kernel.
If you are not using grub, then I don't know.
Eventually, you will want to delete the test kernel. To do so, you must be booted to another kernel, not the test version (i.e. you can not delete the currently running kernel). You can use the excellent utility from here, or do it manually. While I only ever use the server version of the utility, I'll show the manual method:
doug@s15:~$ dpkg -l | grep 4.17.0-1
ii linux-headers-4.17.0-1 4.17.0-1.2~lp1728244 all Header files related to Linux kernel version 4.17.0
ii linux-headers-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel headers for version 4.17.0 on 64 bit x86 SMP
ii linux-image-unsigned-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel image for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
ii linux-modules-extra-4.17.0-1-generic 4.17.0-1.2~lp1728244 amd64 Linux kernel extra modules for version 4.17.0 on 64 bit x86 SMP
doug@s15:~$
doug@s15:~$ sudo dpkg -P linux-modules-extra-4.17.0-1-generic linux-modules-4.17.0-1-generic linux-image-unsigned-4.17.0-1-generic linux-headers-4.17.0-1-generic linux-headers-4.17.0-1
(Reading database ... 1480661 files and directories currently installed.)
Removing linux-modules-extra-4.17.0-1-generic (4.17.0-1.2~lp1728244) ...
...[deleted a bunch of lines]...
rmdir: failed to remove '/lib/modules/4.17.0-1-generic': Directory not empty
...
Notice that I reversed the purge list, so as not to get into dependency issues.
The directory thing seems to occur with 4.17 kernels, but the directory has a sub-directory which I guess confuses things. However, on my system it is gone anyhow.
edited Jun 1 at 15:52
answered Jun 1 at 15:29
![](https://i.stack.imgur.com/quzhv.png?s=32&g=1)
![](https://i.stack.imgur.com/quzhv.png?s=32&g=1)
Doug Smythies
6,24631426
6,24631426
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
add a comment |Â
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
Thank you so much. I successfully been able to boot to the patched kernel. I appreciate your help.
â hussam
Jun 1 at 16:24
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1042660%2fhow-do-i-apply-a-patched-kernel%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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