Comment 14 for bug 1788727
Revision history for this message
| Jim Aird (jimaird1) wrote Re: [Bug 1788727] Re: upgrade crashing due to unsigned kernels | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Sandi, Answer to your last question first, I am a pensioner, I write
slow, make mistakes, (hence 20.18 should read 18.04), I need a good
spell checker, so I use writer to prepare what I want to say then I
paste it into the email, I must remember to paste as raw text in
future.
The computer that I am having problems with is as follows :-
HP ENVY 15-AH151s 15.6" Laptop - AMD A10-8700P - 8GB Ram - 1TB HDD -
Bang & Olufsen Audio Win10
Sold second hand by Amazon/Luzern, It arrived Saturday, June 25 2016
The computer came with windows 10 installed. My plan was to remove
windows 10 and install Ubuntu 16.04.
I had previously converted three desktop and two laptop PCs to Ubuntu
without any problems, the latter being a Lenovo G50-70 Laptop
converted from window 8 and is now running Ubuntu 18.04
I set the HP Notebook to Legacy Bios and disabled fast boot.
Startup Disk Creator was used to make a boot USB, with witch I used
the “try Ubuntu” option to ensure Ubuntu would run on this machine,
all seemed OK so I started the install procedure. I chose to use the
whole hard disk for Ubuntu as I don’t use Microsoft.
The install went fine, all complete I was instructed to re boot, a
black screen was the result.
I rebooted into setup mode and selected the ubuntu option and got a
screen full of cascading code.
I booted with the USB in the “try Ubuntu” mode, all the Ubuntu file
had been installed but the uefi would not let them load
I took the computer to a computer repair shop, the man said it will be
ready in 24 hours. Five weeks later he gave me the PC back and said it
was something microsoft or HP had done wrong!
Over the months that followed I saw many different screens, Ubuntu
logo, static code, blank screen etc!
I list things I have tried in many combinations (Note, I can copy and
paste code but compiling code is beyond me). Gparted, Boot repair,
Disks, re formatted the hard drive in both MBR and GPT, Legacy Bios
and Secure Boot.
When I click on “disks” I see the following three devices,
1.0 TB Hard Disk WDC WD10JPVX-60JC3TO
1.0 GB Drive Generic Flash Disk, (this is my USB boot drive)
1.5 GB Loop Device /cdrom/
I think the Loop Device is the cause of the problem.
I’ve tried to delete the Loop Device and or the rofs directory but
they won’t let me. I was hoping this would allow me to run Ubuntu in
legacy BIOS mode.
After about a year of trying all sorts to get the computer to work I
sort of gave up.
When the CPU manufactures where found out to have been making faulty
processors the computer manufactures started modifying firmware and
software to get round the problem.
I got my sick laptop out of the cupboard to see if it would work,
after many weeks of trying different ways of installing and trying to
boot Ubuntu it suddenly booted up, but it was several more weeks
before I got it to boot up again.
I never seems to boot up the same way twice, When I managed to get the
machine going occasionally with 17.10 in efi but never in legacy bios
mode.
When I first tried to install 18.04 by usb it would not load but it
did the last time ai tried.
The ratio booting up can be anything between first time and giving up
after 50 attempts
UKUU (Ubuntu Kernel Update Utility) ? I must investigate
On Sun, 16 Sep 2018 at 21:25, Sandi Vujaković
<email address hidden> wrote:
>
> Forewarning, I began switching to Antergos one day after your post and
> finished today, so I will not be able to provide any more hands-on data,
> since Antergos is an Arch-based distribution (tried to install Arch in a
> VM twice, failed both times). I switched because I was trying to make my
> Ubuntu install into a rolling one, so why not switch to a proper rolling
> one, like say Arch (or an Arch-based one, like Antergos). I had to
> disable Secure Boot though, so it defeats the purpose of this bug (yes,
> it seems that Arch kernels are unsigned), but whatever.
>
> It seems that you misunderstood me, at least a bit. The older kernels are the ones you're not supposed to remove during this procedure. I am not sure about the upgrade being interrupted by the newer kernels, but I didn't try UKUU before 18.04 anyway (speaking of which, did you mean 18.04 when you wrote 20.18?).
> Also, the kernels aren't "efi" and "non-efi", they're signed and unsigned, reflecting whether or not they would pass under Secure Boot, though it seems that my laptop doesn't care after GRUB is loaded, which is signed by Canonical as well (speaking of which, what's the model of your laptop? the number should be on the underside of it if it's a newer model, probably 2014 and later, but definitely 2016 and later, mine's 15-aw003nm).
>
> Could you please clarify what your course of action was after installing
> Ubuntu Artful?
>
> My understanding is that you didn't even touch UKUU (Ubuntu Kernel Update Utility) on Artful before upgrading to Bionic and not even after the upgrade. If that is the case, could you provide a few more details regarding that (the exact or near exact error message, whether or not you have Secure Boot enabled, generally what was going on, ...).
> Also, what sort of crash was it? Was it a full system crash or did it affect just a part of the system (also, whether you're using the Ubuntu or Ubuntu on Wayland session, you can check by clicking the cog left of Sign in, since I tend to get an error every time I log into the Xorg session/the default one/the one that is not Wayland on Ubuntu, though not on Antergos oddly enough, and you say it actually prompted for information, which does not happen if it crashes to the extend that some of my experiments made it crash, but only for application crashes and crashes of a similar scale)?
>
> One last thing I just realized. You're replying in an email? How?
>
> Anyway, good luck and have a nice day!
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1789107).
> https:/
>
> Title:
> upgrade crashing due to unsigned kernels
>
> Status in grub2 package in Ubuntu:
> Confirmed
>
> Bug description:
> not surre happened during upgrade to bionic beaver
>
> ProblemType: Package
> DistroRelease: Ubuntu 18.04
> Package: grub-efi-amd64 2.02-2ubuntu8.3
> Uname: Linux 4.7.0-040700-
> NonfreeKernelMo
> ApportVersion: 2.20.9-0ubuntu7.2
> Architecture: amd64
> Date: Thu Aug 23 19:33:07 2018
> ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2018-05-30 (85 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
> ProcCmdLine: BOOT_IMAGE=
> Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
> PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
> RelatedPackageV
> dpkg 1.19.0.5ubuntu2
> apt 1.6.3ubuntu0.1
> SourcePackage: grub2
> Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
> UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)
>
> To manage notifications about this bug go to:
> https:/