Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851955
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: efivar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851955
Title:
Hi Sri
Thanks for the information. The HP Envy does not come with an optical drive
as with many notebooks these days, so therefore none should show in BIOS.
It does have 4 USB ports and all are working. I use one for a wireless
mouse, another for a WiFi dongle (its internal WiFi card is dodgy, as
And, just to note an observation fwiw, in response to comment #10, the
non-existant boot order variables probably corresponded to a USB drive
and an optical drive that were set in the BIOS Boot Order, but are
physically not present (the actual CD/DVD and a bootable USB stick). I
do see them set in
Checking in to see if anything moved on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851955
Title:
ubuntu 19.10 boot installer failed
To manage notifications about this bug go to:
Hi Steve, Sri
Of course I want to help. *My notebook is available as it is.* I have time
and intent.
Iaan
On Sat, Jan 11, 2020 at 4:41 AM Sri <1851...@bugs.launchpad.net> wrote:
> Steve,
> I downloaded (downgraded) libefiboot1 and libefivar1 per your suggestion
> in comment #14, and here is
Steve,
I downloaded (downgraded) libefiboot1 and libefivar1 per your suggestion in
comment #14, and here is the output (no change from previous results).
$ sudo dpkg -i libefiboot1_34-1_amd64.deb
dpkg: warning: downgrading libefiboot1:amd64 from 37-2ubuntu2 to 34-1
(Reading database ... 398727
Hi Steve
I can of course only reply on a notebook running an OS *that works*. How
could I reply on a notebook that doesn't work? *I have been clear and exact
on all I have replied*. I have tried to assist. I cannot do the impossible
Steve. Ubuntu definitely has a problem here. Can you solve this
On Wed, Jan 08, 2020 at 09:30:29PM -, Ian Scott wrote:
> I can install Ubuntu 20.04 on this notebook as I have an ISO for this -
> runs fine in Virtualbox.
I'm sorry, are you running these commands on Ubuntu, or not? I assumed it
was clear that I was looking for the output of these commands
Hi Steve
Some more information if it is of any help
I added another OS to dual boot with Zorin OS on this notebook. At first I
tried to dual boot with Ubuntu 20.04. It installed but with grub boot
failure. I tried several times to repair this using the Zorin USB repair
boot utility - all
Hi Steve
I downloaded both .deb files and ran using gdebi - it reports "same version
already installed" so I reinstalled anyway and then ran
sudo efibootmgr -o ,3000,0001,0002,2001; echo $?
Output is
Invalid BootOrder order entry value,3000,0001,0002,2001,2002
Sorry for the late reply Steve. Here are the commands you asked for
(which are consistent with what Ian reported and you observed):
$ sudo efibootmgr -o ,0003,0004,0001; echo $?
Invalid BootOrder order entry value,0003,0004
^
efibootmgr:
Thanks. Since this fails for you both with efibootmgr and with grub,
that suggests there might be a bug in the underlying efivar library.
Opening a task on that package.
Can you try installing the libefiboot1 and libefivar1 packages from
Hi Steve
Thanks - I remember the sudo dpkg --configure -a command and have had to
use it before - didn't know what it was called though. I ran it but the
terminal had no feedback to make. I then ran your new command and here is
the output
Could not set BootOrder: Invalid argument
8
Ian
On
On Tue, Jan 07, 2020 at 11:40:05PM -, Ian Scott wrote:
> I'm at the library at the moment on another notebook but I'll be back in
> an hour or so to try the new idea. However "And then, could you try
> finishing the configuration of the grub package?"
> Unfortunately I have no idea at all
Hi Steve
I'm at the library at the moment on another notebook but I'll be back in an
hour or so to try the new idea. However "nd then, could you try finishing
the
configuration of the grub package?"
Unfortunately I have no idea at all how to do this. Can you provide some
instructions Steve? I
The error message appears to be correct, you have both 2002 and 2003 in
your BootOrder but neither is present in your list of boot options. I
don't think this is the cause of the grub failure. Could you try
instead running the command:
sudo efibootmgr -o ,3000,0001,0002,2001; echo $?
and
Hi Steve
Here's the output
Invalid BootOrder order entry value,3000,0001,0002,2001,2002
^
efibootmgr: entry 2002 does not exist
8
Ian
On Wed, Jan 8, 2020 at 10:55 AM Steve Langasek
wrote:
> Ok. Ian, Sri, could you also both
Ok. Ian, Sri, could you also both check whether running efibootmgr on
Ubuntu 19.10 succeeds? Probably the easiest check is a no-op rewrite of
the boot order variable. Ian, for you the command would be:
sudo efibootmgr -o ,3000,0001,0002,2001,2002,2003; echo $?
Sri, for you the command
@steve
Here is the output you asked for. I'll log into my system's bios to see
if I find any locks (thought I don't expect any) and let you know.
[code]
$ efibootmgr -v
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0003,0004,0001
Boot* ubuntu
Hi Steve
Thanks for your reply. Here are the outputs for this Envy notebook - now
running Zorin OS as this installs and has a "Grub repair" feature on its
USB install stick - usually fixes all HP shenanigans.
BootCurrent:
Timeout: 5 seconds
BootOrder: ,3000,0001,0002,2001,2002,2003
On Mon, Jan 06, 2020 at 05:46:14PM -, Sri wrote:
> Setting up grub-efi-amd64-signed (1.128.1+2.04-1ubuntu12.1) ...
> Installing for x86_64-efi platform.
> grub-install: warning: Cannot set EFI variable Boot.
> grub-install: warning: efivarfs_set_variable: writing to fd 7 failed: Invalid
>
I started having this issue after I upgraded from Ubuntu 18.04 to 19.10
(through 18.10 and 19.04), everytime I try to run apt upgrade (or apt-
get upgrade). Here is an excerpt:
(When I was trying to install a new package, while an update was pending):
Unpacking atlassian-plugin-sdk (8.0.16) ...
Hi Jean-Baptiste and Steve
I admit I am baffled but I appreciate your replies. I had thought it might
be caused by a small hard drive error but that's just a guess.
Interestingly Mint 18 installs OK Mint 12.2 doesn't and any Ubuntu version
does not, although these used to.
More curious, I made a
The error in your logs is:
Nov 9 19:25:47 ubuntu ubiquity: grub-install: warning: Cannot set EFI variable
Boot.
Nov 9 19:25:47 ubuntu ubiquity: grub-install: warning: efivarfs_set_variable:
writing to fd 7 failed: Invalid argument.
Nov 9 19:25:47 ubuntu ubiquity: grub-install: warning:
** Package changed: ubiquity (Ubuntu) => shim-signed (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851955
Title:
ubuntu 19.10 boot installer failed
To manage notifications about this bug
26 matches
Mail list logo
