Comment 6 for bug 1851955

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: 0000
Timeout: 5 seconds
BootOrder: 0000,3000,0001,0002,2001,2002,2003
Boot0000* ubuntu
HD(1,GPT,ca9d4c6c-f90a-408b-9a27-1559c1619904,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0001* Network Adapter (IPv4 UEFI)
PciRoot(0x0)/Pci(0x1c,0x6)/Pci(0x0,0x0)/MAC(a0481cc2def7,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0002* Network Adapter (IPv6 UEFI)
PciRoot(0x0)/Pci(0x1c,0x6)/Pci(0x0,0x0)/MAC(a0481cc2def7,0)/IPv6([::]:<->[::]:,0,0)RC
Boot2001* USB Drive (UEFI) RC
Boot3000* Internal Hard Disk or Solid State Disk RC
Boot3001* Internal Hard Disk or Solid State Disk RC
Boot3002* Internal Hard Disk or Solid State Disk RC
Boot3003* Internal Hard Disk or Solid State Disk RC
Boot3004* Internal Hard Disk or Solid State Disk RC

I ran your command on another HP Pavilion dv6 that also has grub failure
using Ubuntu. It replied "EFI Variables are not installed on this system".

I checked BIOS in detail on both notebooks - no mention of anything unusual.

This second dv6 also had Grub install failure with Ubuntu and also Mint
19.3 - based on Ubuntu. It now dual boots Zorin OS and Mint 19.3. To
accomplish this I installed Zorin OS first, used its Grub repair feature,
installed Mint 19.3 for dual boot and Grub install failure occurred. I used
Zorin OS Grub repair on its USB install pen drive to get Grub to work, now
both OS are happy.

*I agree that this is definitely intentional by HP to motivate consumers to
buy another notebook - they hope one of theirs*. No way! Not Ever again
Steve!

Other anti-consumer behaviour - battery charge failures - proprietary 3-pin
connection on this Envy. It is impossible to wire in any other 19 V supply
- I tried this, it doesn't respond. I waited a week, it stopped playing
silly games.

I am quite certain given all this that HP Intentionally is motivating
consumers to ditch older notebook and buy another. They especially target
Ubuntu as I have described on several incidents, all based on Ubuntu.

Thanks for your assistance Steve. Although I have a workaround there may be
others who don't - If I can help others with HP shenanigans, no problem.

Lastly, on an older Acer 5920 notebook - never a problem. I use this one to
try lots of different OS, often. This behaviour is specific to HP.

Ian

On Tue, Jan 7, 2020 at 7:30 AM Steve Langasek <email address hidden>
wrote:

> On Mon, Jan 06, 2020 at 05:46:14PM -0000, 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 Boot0000.
> > grub-install: warning: efivarfs_set_variable: writing to fd 7 failed:
> Invalid argument.
> > grub-install: warning: _efi_set_variable_mode: ops->set_variable()
> failed: Invalid argument.
> > grub-install: error: failed to register the EFI boot entry: Invalid
> argument.
>
> > Any clue on where I should start looking?
>
> Look into reports of problems with your specific firmware for your specific
> device. See if an update is available. See if there are options in the
> BIOS menu that control whether these variables are locked.
>
> What is the output of 'efibootmgr -v' on this system?
>
> If Ubuntu can't control the boot variables, then it can't reliably boot on
> the system; so the package install failure is intentional.
>
> However you also mention that this started happening to you on upgrade and
> there has been a change in grub's implementation between 18.04 and 19.10,
> where previously grub shelled out to efibootmgr and now it writes the
> variables directly. So it's possible there is a bug in the grub
> implementation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1851955
>
> Title:
> ubuntu 19.10 boot installer failed
>
> Status in shim-signed package in Ubuntu:
> Incomplete
>
> Bug description:
> Installed on an ENVY notebook, installation afiled at the end with no
> bootloader message
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.10
> Package: ubiquity 19.10.21
> ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
> Uname: Linux 5.3.0-18-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> ApportVersion: 2.20.11-0ubuntu8
> Architecture: amd64
> CasperVersion: 1.427
> Date: Sun Nov 10 08:32:41 2019
> InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd
> quiet splash --- maybe-ubiquity
> LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
> SourcePackage: ubiquity
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1851955/+subscriptions
>