kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite
1












For years I have used kernels from this PPA, but now with kernels 4.16.4 and kernels 4.16.5 I am unable to install (and also uninstall) broken kernel packages.



Distro is Ubuntu MATE 16.04 (Xenial).



Looks like some helpers not found on installation of kernel package:



linux-update-symlinks
linux-check-removal


There is also an unusual kernel package name which contains 'unsigned':



linux-image-unsigned-4.16.5-041605-generic


What is going on?







share|improve this question














closed as unclear what you're asking by David Foerster, Pilot6, N0rbert, user535733, Kevin Bowen Jun 4 at 20:44


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • Welcome to Ask Ubuntu! Could you please add a little more detail? What exactly did you do, what did you expect to happen and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. Please edit your post to add information instead of posting a comment. (see How do I ask a good question?)
    – David Foerster
    Jun 4 at 9:26














up vote
1
down vote

favorite
1












For years I have used kernels from this PPA, but now with kernels 4.16.4 and kernels 4.16.5 I am unable to install (and also uninstall) broken kernel packages.



Distro is Ubuntu MATE 16.04 (Xenial).



Looks like some helpers not found on installation of kernel package:



linux-update-symlinks
linux-check-removal


There is also an unusual kernel package name which contains 'unsigned':



linux-image-unsigned-4.16.5-041605-generic


What is going on?







share|improve this question














closed as unclear what you're asking by David Foerster, Pilot6, N0rbert, user535733, Kevin Bowen Jun 4 at 20:44


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • Welcome to Ask Ubuntu! Could you please add a little more detail? What exactly did you do, what did you expect to happen and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. Please edit your post to add information instead of posting a comment. (see How do I ask a good question?)
    – David Foerster
    Jun 4 at 9:26












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





For years I have used kernels from this PPA, but now with kernels 4.16.4 and kernels 4.16.5 I am unable to install (and also uninstall) broken kernel packages.



Distro is Ubuntu MATE 16.04 (Xenial).



Looks like some helpers not found on installation of kernel package:



linux-update-symlinks
linux-check-removal


There is also an unusual kernel package name which contains 'unsigned':



linux-image-unsigned-4.16.5-041605-generic


What is going on?







share|improve this question














For years I have used kernels from this PPA, but now with kernels 4.16.4 and kernels 4.16.5 I am unable to install (and also uninstall) broken kernel packages.



Distro is Ubuntu MATE 16.04 (Xenial).



Looks like some helpers not found on installation of kernel package:



linux-update-symlinks
linux-check-removal


There is also an unusual kernel package name which contains 'unsigned':



linux-image-unsigned-4.16.5-041605-generic


What is going on?









share|improve this question













share|improve this question




share|improve this question








edited Apr 27 at 6:18









Zanna

48k13119227




48k13119227










asked Apr 27 at 5:48









IgorSimic

61




61




closed as unclear what you're asking by David Foerster, Pilot6, N0rbert, user535733, Kevin Bowen Jun 4 at 20:44


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






closed as unclear what you're asking by David Foerster, Pilot6, N0rbert, user535733, Kevin Bowen Jun 4 at 20:44


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.













  • Welcome to Ask Ubuntu! Could you please add a little more detail? What exactly did you do, what did you expect to happen and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. Please edit your post to add information instead of posting a comment. (see How do I ask a good question?)
    – David Foerster
    Jun 4 at 9:26
















  • Welcome to Ask Ubuntu! Could you please add a little more detail? What exactly did you do, what did you expect to happen and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. Please edit your post to add information instead of posting a comment. (see How do I ask a good question?)
    – David Foerster
    Jun 4 at 9:26















Welcome to Ask Ubuntu! Could you please add a little more detail? What exactly did you do, what did you expect to happen and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. Please edit your post to add information instead of posting a comment. (see How do I ask a good question?)
– David Foerster
Jun 4 at 9:26




Welcome to Ask Ubuntu! Could you please add a little more detail? What exactly did you do, what did you expect to happen and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. Please edit your post to add information instead of posting a comment. (see How do I ask a good question?)
– David Foerster
Jun 4 at 9:26










2 Answers
2






active

oldest

votes

















up vote
0
down vote













I'm not sure of what is going on but I managed to remove the unsigned kernels by commenting out the line:



linux-check-removal $version


in the files



/var/lib/dpkg/info/linux-image-unsigned-4.16.5-041605-generic.prerm


and / or



/var/lib/dpkg/info/linux-image-unsigned-4.16.4-041604-generic.prerm


and then continuing with apt-get standard removal procedure (ukuu-gtk also works fine).






share|improve this answer






















  • I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
    – IgorSimic
    Apr 27 at 6:16











  • This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
    – IgorSimic
    Apr 27 at 6:23











  • Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
    – IgorSimic
    Apr 27 at 6:29











  • ...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
    – IgorSimic
    Apr 27 at 6:38






  • 1




    'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
    – Serafim Dahl
    Apr 27 at 7:08


















up vote
0
down vote













I just rm'd the 1st script it complained about then ran



dpkg -r $pkg


then rm'd the 2nd script it complained about and re-ran:



dpkg -r $pkg


then I was able to successfully remove the unsigned kernel package.



In my case $pkg was linux-image-unsigned-4.16.5-041605-generic_4.16.5-041605.201804260630_amd64.deb



(Disclaimer: This worked for me. I install my latest kernels with dpkg. Try at your own risk!)






share|improve this answer






















  • Dangerous... be careful
    – ubashu
    Apr 27 at 7:34

















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













I'm not sure of what is going on but I managed to remove the unsigned kernels by commenting out the line:



linux-check-removal $version


in the files



/var/lib/dpkg/info/linux-image-unsigned-4.16.5-041605-generic.prerm


and / or



/var/lib/dpkg/info/linux-image-unsigned-4.16.4-041604-generic.prerm


and then continuing with apt-get standard removal procedure (ukuu-gtk also works fine).






share|improve this answer






















  • I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
    – IgorSimic
    Apr 27 at 6:16











  • This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
    – IgorSimic
    Apr 27 at 6:23











  • Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
    – IgorSimic
    Apr 27 at 6:29











  • ...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
    – IgorSimic
    Apr 27 at 6:38






  • 1




    'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
    – Serafim Dahl
    Apr 27 at 7:08















up vote
0
down vote













I'm not sure of what is going on but I managed to remove the unsigned kernels by commenting out the line:



linux-check-removal $version


in the files



/var/lib/dpkg/info/linux-image-unsigned-4.16.5-041605-generic.prerm


and / or



/var/lib/dpkg/info/linux-image-unsigned-4.16.4-041604-generic.prerm


and then continuing with apt-get standard removal procedure (ukuu-gtk also works fine).






share|improve this answer






















  • I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
    – IgorSimic
    Apr 27 at 6:16











  • This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
    – IgorSimic
    Apr 27 at 6:23











  • Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
    – IgorSimic
    Apr 27 at 6:29











  • ...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
    – IgorSimic
    Apr 27 at 6:38






  • 1




    'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
    – Serafim Dahl
    Apr 27 at 7:08













up vote
0
down vote










up vote
0
down vote









I'm not sure of what is going on but I managed to remove the unsigned kernels by commenting out the line:



linux-check-removal $version


in the files



/var/lib/dpkg/info/linux-image-unsigned-4.16.5-041605-generic.prerm


and / or



/var/lib/dpkg/info/linux-image-unsigned-4.16.4-041604-generic.prerm


and then continuing with apt-get standard removal procedure (ukuu-gtk also works fine).






share|improve this answer














I'm not sure of what is going on but I managed to remove the unsigned kernels by commenting out the line:



linux-check-removal $version


in the files



/var/lib/dpkg/info/linux-image-unsigned-4.16.5-041605-generic.prerm


and / or



/var/lib/dpkg/info/linux-image-unsigned-4.16.4-041604-generic.prerm


and then continuing with apt-get standard removal procedure (ukuu-gtk also works fine).







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 27 at 7:33









ubashu

2,23721736




2,23721736










answered Apr 27 at 6:12









Serafim Dahl

1042




1042











  • I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
    – IgorSimic
    Apr 27 at 6:16











  • This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
    – IgorSimic
    Apr 27 at 6:23











  • Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
    – IgorSimic
    Apr 27 at 6:29











  • ...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
    – IgorSimic
    Apr 27 at 6:38






  • 1




    'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
    – Serafim Dahl
    Apr 27 at 7:08

















  • I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
    – IgorSimic
    Apr 27 at 6:16











  • This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
    – IgorSimic
    Apr 27 at 6:23











  • Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
    – IgorSimic
    Apr 27 at 6:29











  • ...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
    – IgorSimic
    Apr 27 at 6:38






  • 1




    'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
    – Serafim Dahl
    Apr 27 at 7:08
















I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
– IgorSimic
Apr 27 at 6:16





I did the same about removal. But installation... I found needed scripts in debian package linux-base_4.5. Now I am looking for same ubuntu package. Strange thing is that this never happened before 4.16.4
– IgorSimic
Apr 27 at 6:16













This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
– IgorSimic
Apr 27 at 6:23





This is a clue from ubuntu package search: Exact hits Package linux-base trusty (14.04LTS) (kernel): Linux image base package 3.5ubuntu4: all xenial (16.04LTS) (kernel): Linux image base package 4.0ubuntu1: all artful (kernel): Linux image base package 4.5ubuntu1: all bionic (kernel): Linux image base package 4.5ubuntu1: all Now is the question am I safe to upgrade to 4.5 on xenial?
– IgorSimic
Apr 27 at 6:23













Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
– IgorSimic
Apr 27 at 6:29





Confirmed! After installation of package: mirrors.kernel.org/ubuntu/pool/main/l/linux-base/… I am able to install and uninstall both 4.16.4 and 4.16.5
– IgorSimic
Apr 27 at 6:29













...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
– IgorSimic
Apr 27 at 6:38




...and it works: $ uname -a Linux hpEliteLin 4.16.5-041605-generic #201804260630 SMP Thu Apr 26 10:32:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Still don't know what is the meaning of 'unsigned', especially because it appears in just few architectures.
– IgorSimic
Apr 27 at 6:38




1




1




'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
– Serafim Dahl
Apr 27 at 7:08





'unsigned' kernels are not signed with EFI/UEFI keys. However, I tried to boot these unsigned kernels in unsafe mode on my ASUS z170 pro gaming with an Intel i5 6600k but I still get a kernel panic. I'll try to upgrade the BIOS and see what happens.
– Serafim Dahl
Apr 27 at 7:08













up vote
0
down vote













I just rm'd the 1st script it complained about then ran



dpkg -r $pkg


then rm'd the 2nd script it complained about and re-ran:



dpkg -r $pkg


then I was able to successfully remove the unsigned kernel package.



In my case $pkg was linux-image-unsigned-4.16.5-041605-generic_4.16.5-041605.201804260630_amd64.deb



(Disclaimer: This worked for me. I install my latest kernels with dpkg. Try at your own risk!)






share|improve this answer






















  • Dangerous... be careful
    – ubashu
    Apr 27 at 7:34














up vote
0
down vote













I just rm'd the 1st script it complained about then ran



dpkg -r $pkg


then rm'd the 2nd script it complained about and re-ran:



dpkg -r $pkg


then I was able to successfully remove the unsigned kernel package.



In my case $pkg was linux-image-unsigned-4.16.5-041605-generic_4.16.5-041605.201804260630_amd64.deb



(Disclaimer: This worked for me. I install my latest kernels with dpkg. Try at your own risk!)






share|improve this answer






















  • Dangerous... be careful
    – ubashu
    Apr 27 at 7:34












up vote
0
down vote










up vote
0
down vote









I just rm'd the 1st script it complained about then ran



dpkg -r $pkg


then rm'd the 2nd script it complained about and re-ran:



dpkg -r $pkg


then I was able to successfully remove the unsigned kernel package.



In my case $pkg was linux-image-unsigned-4.16.5-041605-generic_4.16.5-041605.201804260630_amd64.deb



(Disclaimer: This worked for me. I install my latest kernels with dpkg. Try at your own risk!)






share|improve this answer














I just rm'd the 1st script it complained about then ran



dpkg -r $pkg


then rm'd the 2nd script it complained about and re-ran:



dpkg -r $pkg


then I was able to successfully remove the unsigned kernel package.



In my case $pkg was linux-image-unsigned-4.16.5-041605-generic_4.16.5-041605.201804260630_amd64.deb



(Disclaimer: This worked for me. I install my latest kernels with dpkg. Try at your own risk!)







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 27 at 7:34









ubashu

2,23721736




2,23721736










answered Apr 27 at 6:28









ByteBeast

1




1











  • Dangerous... be careful
    – ubashu
    Apr 27 at 7:34
















  • Dangerous... be careful
    – ubashu
    Apr 27 at 7:34















Dangerous... be careful
– ubashu
Apr 27 at 7:34




Dangerous... be careful
– ubashu
Apr 27 at 7:34


Popular posts from this blog

Trouble downloading packages list due to a “Hash sum mismatch” error

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

How do I move numbers in filenames, in a batch renaming operation?