I can not install any Ubuntu distros in the UEFI mode (but BIOS-compability mode works without efforts): "Unable to install GRUB in /dev/sda"

Bug #1835664 reported by Artyom Pozharov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux
Confirmed
Medium
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

You also can see the screens that show this problem:
https://photos.app.goo.gl/4Pimhpr8SwPerA1h7
https://photos.app.goo.gl/kq5zV5GPrunQpT7j9
https://photos.app.goo.gl/CqjuADV6zURpwECB6
https://photos.app.goo.gl/xzNJ6Xt2BSGBYjXR6

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.5
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CasperVersion: 1.411
Date: Sun Jul 7 18:38:45 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash ---
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190707)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :
description: updated
summary: - I can not install any Ubuntu distros in the UEFI mode (BIOS-compability
- mode works)
+ I can not install any Ubuntu distros in the UEFI mode (but BIOS-
+ compability mode works without efforts)
description: updated
summary: I can not install any Ubuntu distros in the UEFI mode (but BIOS-
- compability mode works without efforts)
+ compability mode works without efforts): "Unable to install GRUB in
+ /dev/sda"
Changed in casper (Ubuntu):
importance: Undecided → Critical
Changed in grub-installer (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote : Re: [Bug 1835664] Re: I can not install any Ubuntu distros in the UEFI mode (but BIOS-compability mode works without efforts): "Unable to install GRUB in /dev/sda"

Daniel, thank you for your reaction.

ср, 10 июл. 2019 г., 10:20 Daniel van Vugt <email address hidden>:

> ** Summary changed:
>
> - I can not install any Ubuntu distros in the UEFI mode (but
> BIOS-compability mode works without efforts)
> + I can not install any Ubuntu distros in the UEFI mode (but
> BIOS-compability mode works without efforts): "Unable to install GRUB in
> /dev/sda"
>
> ** Also affects: casper (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: casper (Ubuntu)
> Importance: Undecided => Critical
>
> ** Changed in: grub-installer (Ubuntu)
> Importance: Undecided => Critical
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835664
>
> Title:
> I can not install any Ubuntu distros in the UEFI mode (but BIOS-
> compability mode works without efforts): "Unable to install GRUB in
> /dev/sda"
>
> Status in casper package in Ubuntu:
> New
> Status in grub-installer package in Ubuntu:
> New
>
> Bug description:
> You also can see the screens that show this problem:
> https://photos.app.goo.gl/4Pimhpr8SwPerA1h7
> https://photos.app.goo.gl/kq5zV5GPrunQpT7j9
> https://photos.app.goo.gl/CqjuADV6zURpwECB6
> https://photos.app.goo.gl/xzNJ6Xt2BSGBYjXR6
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.10
> Package: ubiquity 19.10.5
> ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
> Uname: Linux 5.0.0-20-generic x86_64
> ApportVersion: 2.20.11-0ubuntu3
> Architecture: amd64
> CasperVersion: 1.411
> Date: Sun Jul 7 18:38:45 2019
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed quiet splash ---
> LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190707)
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1835664/+subscriptions
>

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :
no longer affects: grub-installer
Changed in casper (Ubuntu):
importance: Critical → Undecided
Changed in grub-installer (Ubuntu):
importance: Critical → Undecided
Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :

Why problem is undecided?

ср, 17 июл. 2019 г., 12:55 Daniel van Vugt <email address hidden>:

> ** Changed in: casper (Ubuntu)
> Importance: Critical => Undecided
>
> ** Changed in: grub-installer (Ubuntu)
> Importance: Critical => Undecided
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835664
>
> Title:
> I can not install any Ubuntu distros in the UEFI mode (but BIOS-
> compability mode works without efforts): "Unable to install GRUB in
> /dev/sda"
>
> Status in casper package in Ubuntu:
> New
> Status in grub-installer package in Ubuntu:
> New
>
> Bug description:
> You also can see the screens that show this problem:
> https://photos.app.goo.gl/4Pimhpr8SwPerA1h7
> https://photos.app.goo.gl/kq5zV5GPrunQpT7j9
> https://photos.app.goo.gl/CqjuADV6zURpwECB6
> https://photos.app.goo.gl/xzNJ6Xt2BSGBYjXR6
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.10
> Package: ubiquity 19.10.5
> ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
> Uname: Linux 5.0.0-20-generic x86_64
> ApportVersion: 2.20.11-0ubuntu3
> Architecture: amd64
> CasperVersion: 1.411
> Date: Sun Jul 7 18:38:45 2019
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed quiet splash ---
> LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190707)
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1835664/+subscriptions
>

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :

GNU GRUB volunteers say that it's due to kernel panic and isn't connected with GRUB.

Revision history for this message
In , pozharovartyom (pozharovartyom-linux-kernel-bugs) wrote :

There is "Unable to install GRUB in /dev/sda". At first I thought that it's grub-installer bug, but GNU GRUB developers say that this error due to kernel panic that appears when GRUB installs. Installation stops abnormally. After rebooting, I get a non-operational system. This problem applies any GNU/Linux distributions as Ubuntu, Debian, Fedora, Debian, Solus etc. But I don't see such error when I install system in BIOS-compability mode. The detail apport is here: https://bugs.launchpad.net/kernel/+bug/1835664

Changed in kernel:
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
In , ard.biesheuvel (ard.biesheuvel-linux-kernel-bugs) wrote :

Could you please share the details of this kernel panic?

Revision history for this message
In , pozharovartyom (pozharovartyom-linux-kernel-bugs) wrote :

Created attachment 283949
attachment-5186-0.html

UEFI mode. Installation will go normally while "grub-install on dev/sda"
doesn't appear. Then installation will freeze. After that I will get an
error with GRUB-installer. GNU GRUB volunteers say that the reason of the
bug is kernel panic during the installation, but not GRUB-installer.
BIOS-compability mode. I don't see any efforts with installation.
This bug applies all GNU/Linux distributions, as Debian, Ubuntu, Fedora,
Solus, Cloudready etc. But FydeOS and ArnoldTheBat Chromium are exepctions.
I guess, it's connected with modified Linux kernels that use FydeOS and ATB
Chromium.

Revision history for this message
In , ard.biesheuvel (ard.biesheuvel-linux-kernel-bugs) wrote :

If you have no details to share about this alleged kernel panic, there is unfortunately no way to confirm that this is indeed a kernel bug, or whether there is a way to fix it.

Revision history for this message
In , pozharovartyom (pozharovartyom-linux-kernel-bugs) wrote :

Created attachment 283953
attachment-8355-0.html

I say all I know. I am not developer, I am user. I had done my job - I had
sent apport with full information about bug. Canonical say that this bug is
not Ubuntu specific problem. Then I had written to GNU GRUB. They say that
this problem connected with Linux kernel. I had written to you. And you had
sent me to hell too. Anyone want to troubleshoot. Therefore, GNOME 3 lags,
Microsoft documents are incorrectly rendered in LibreOffice, Linux is not
compatible with half the hardware. FOSS is shifting responsibilities to
others.

чт, 25 июл. 2019 г., 12:14 <email address hidden>:

> https://bugzilla.kernel.org/show_bug.cgi?id=204289
>
> --- Comment #3 from Ard Biesheuvel (<email address hidden>) ---
> If you have no details to share about this alleged kernel panic, there is
> unfortunately no way to confirm that this is indeed a kernel bug, or
> whether
> there is a way to fix it.
>
> --
> You are receiving this mail because:
> You reported the bug.

Revision history for this message
In , pozharovartyom (pozharovartyom-linux-kernel-bugs) wrote :

(In reply to Ard Biesheuvel from comment #3)
> If you have no details to share about this alleged kernel panic, there is
> unfortunately no way to confirm that this is indeed a kernel bug, or whether
> there is a way to fix it.

Which details do you want to see? How can I get this information?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Download full text (7.3 KiB)

Oh I see the "kernel panic" people are referring to:

Jul 7 15:32:56 ubuntu kernel: [ 478.430126] ------------[ cut here ]------------
Jul 7 15:32:56 ubuntu kernel: [ 478.430131] [Firmware Bug]: Page fault caused by firmware at PA: 0x67963770
Jul 7 15:32:56 ubuntu kernel: [ 478.430143] WARNING: CPU: 0 PID: 149 at arch/x86/platform/efi/quirks.c:735 efi_recover_from_page_fault+0x30/0xce
Jul 7 15:32:56 ubuntu kernel: [ 478.430143] Modules linked in: nls_iso8859_1 ufs qnx4 hfsplus hfs minix ntfs msdos xfs jfs btrfs zstd_compress libcrc32c xor raid6_pq ccm rfcomm cmac bnep snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_rapl snd_soc_core intel_telemetry_pltdrv intel_punit_ipc intel_telemetry_core snd_compress intel_pmc_ipc ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal ledtrig_audio intel_powerclamp coretemp snd_hda_intel arc4 uvcvideo iwlmvm kvm_intel snd_hda_codec videobuf2_vmalloc videobuf2_memops mac80211 videobuf2_v4l2 crct10dif_pclmul crc32_pclmul snd_hda_core videobuf2_common snd_hwdep ghash_clmulni_intel iwlwifi snd_pcm videodev btusb media btrtl btbcm cfg80211 aesni_intel snd_seq_midi snd_seq_midi_event btintel snd_rawmidi bluetooth aes_x86_64 snd_seq crypto_simd cryptd glue_helper input_leds intel_cstate joydev snd_seq_device snd_timer
Jul 7 15:32:56 ubuntu kernel: [ 478.430185] intel_rapl_perf ecdh_generic intel_xhci_usb_role_switch mei_me wmi_bmof hp_wmi processor_thermal_device roles sparse_keymap serio_raw snd mei soundcore int340x_thermal_zone intel_soc_dts_iosf mac_hid int3400_thermal int3406_thermal hp_wireless dptf_power acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log uas usb_storage i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm ahci lpc_ich i2c_i801 realtek libahci pinctrl_broxton wmi video pinctrl_intel
Jul 7 15:32:56 ubuntu kernel: [ 478.430219] CPU: 0 PID: 149 Comm: kworker/u8:3 Not tainted 5.0.0-20-generic #21-Ubuntu
Jul 7 15:32:56 ubuntu kernel: [ 478.430220] Hardware name: HP HP 250 G6 Notebook PC/832E, BIOS F.40 05/17/2018
Jul 7 15:32:56 ubuntu kernel: [ 478.430225] Workqueue: efi_rts_wq efi_call_rts
Jul 7 15:32:56 ubuntu kernel: [ 478.430228] RIP: 0010:efi_recover_from_page_fault+0x30/0xce
Jul 7 15:32:56 ubuntu kernel: [ 478.430229] Code: 05 15 f7 ca 01 85 c0 74 09 48 81 ff ff 0f 00 00 77 01 c3 55 48 89 fe 48 c7 c7 b8 5d ad 8d 48 89 e5 48 83 ec 08 e8 32 9b 00 00 <0f> 0b 83 3d e7 f6 ca 01 0a 0f 84 8f 00 00 00 48 8b 05 e2 63 7b 01
Jul 7 15:32:56 ubuntu kernel: [ 478.430231] RSP: 0018:ffffa0a7c08e39d8 EFLAGS: 00010086
Jul 7 15:32:56 ubuntu kernel: [ 478.430232] RAX: 0000000000000000 RBX: 0000000067963770 RCX: 0000000000000006
Jul 7 15:32:56 ubuntu kernel: [ 478.430233] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff9528bba16440
Jul 7 15:32:56 ubuntu kernel: [ 478.430234] RBP: ffffa0a7c08e39e0 R08: 0000000000000001 R09: 00000000000004a0
Jul 7...

Read more...

Changed in casper (Ubuntu):
status: New → Incomplete
Changed in grub-installer (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: New → Incomplete
Changed in casper (Ubuntu):
status: Incomplete → New
Changed in grub-installer (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
In , daniel.van.vugt (daniel.van.vugt-linux-kernel-bugs) wrote :
Download full text (7.4 KiB)

Here are the details:

Jul 7 15:32:56 ubuntu kernel: [ 478.430126] ------------[ cut here ]------------
Jul 7 15:32:56 ubuntu kernel: [ 478.430131] [Firmware Bug]: Page fault caused by firmware at PA: 0x67963770
Jul 7 15:32:56 ubuntu kernel: [ 478.430143] WARNING: CPU: 0 PID: 149 at arch/x86/platform/efi/quirks.c:735 efi_recover_from_page_fault+0x30/0xce
Jul 7 15:32:56 ubuntu kernel: [ 478.430143] Modules linked in: nls_iso8859_1 ufs qnx4 hfsplus hfs minix ntfs msdos xfs jfs btrfs zstd_compress libcrc32c xor raid6_pq ccm rfcomm cmac bnep snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_rapl snd_soc_core intel_telemetry_pltdrv intel_punit_ipc intel_telemetry_core snd_compress intel_pmc_ipc ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal ledtrig_audio intel_powerclamp coretemp snd_hda_intel arc4 uvcvideo iwlmvm kvm_intel snd_hda_codec videobuf2_vmalloc videobuf2_memops mac80211 videobuf2_v4l2 crct10dif_pclmul crc32_pclmul snd_hda_core videobuf2_common snd_hwdep ghash_clmulni_intel iwlwifi snd_pcm videodev btusb media btrtl btbcm cfg80211 aesni_intel snd_seq_midi snd_seq_midi_event btintel snd_rawmidi bluetooth aes_x86_64 snd_seq crypto_simd cryptd glue_helper input_leds intel_cstate joydev snd_seq_device snd_timer
Jul 7 15:32:56 ubuntu kernel: [ 478.430185] intel_rapl_perf ecdh_generic intel_xhci_usb_role_switch mei_me wmi_bmof hp_wmi processor_thermal_device roles sparse_keymap serio_raw snd mei soundcore int340x_thermal_zone intel_soc_dts_iosf mac_hid int3400_thermal int3406_thermal hp_wireless dptf_power acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log uas usb_storage i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm ahci lpc_ich i2c_i801 realtek libahci pinctrl_broxton wmi video pinctrl_intel
Jul 7 15:32:56 ubuntu kernel: [ 478.430219] CPU: 0 PID: 149 Comm: kworker/u8:3 Not tainted 5.0.0-20-generic #21-Ubuntu
Jul 7 15:32:56 ubuntu kernel: [ 478.430220] Hardware name: HP HP 250 G6 Notebook PC/832E, BIOS F.40 05/17/2018
Jul 7 15:32:56 ubuntu kernel: [ 478.430225] Workqueue: efi_rts_wq efi_call_rts
Jul 7 15:32:56 ubuntu kernel: [ 478.430228] RIP: 0010:efi_recover_from_page_fault+0x30/0xce
Jul 7 15:32:56 ubuntu kernel: [ 478.430229] Code: 05 15 f7 ca 01 85 c0 74 09 48 81 ff ff 0f 00 00 77 01 c3 55 48 89 fe 48 c7 c7 b8 5d ad 8d 48 89 e5 48 83 ec 08 e8 32 9b 00 00 <0f> 0b 83 3d e7 f6 ca 01 0a 0f 84 8f 00 00 00 48 8b 05 e2 63 7b 01
Jul 7 15:32:56 ubuntu kernel: [ 478.430231] RSP: 0018:ffffa0a7c08e39d8 EFLAGS: 00010086
Jul 7 15:32:56 ubuntu kernel: [ 478.430232] RAX: 0000000000000000 RBX: 0000000067963770 RCX: 0000000000000006
Jul 7 15:32:56 ubuntu kernel: [ 478.430233] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff9528bba16440
Jul 7 15:32:56 ubuntu kernel: [ 478.430234] RBP: ffffa0a7c08e39e0 R08: 0000000000000001 R09: 00000000000004a0
Jul 7 15:32:56 ubuntu kernel: [ 478...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It sounds like a BIOS bug and your logs show you are using version:

  BIOS F.40 05/17/2018

which is now out of date. To try and fix this you will need to reinstall Windows (sorry), and then install the new BIOS version F.52 from:

  https://ftp.hp.com/pub/softpaq/sp95001-95500/sp95307.exe

(found via https://support.hp.com/au-en/drivers/selfservice/hp-250-g6-notebook-pc/15747807)

no longer affects: casper (Ubuntu)
no longer affects: grub-installer (Ubuntu)
affects: linuxmint → ubuntu
no longer affects: ubuntu
affects: elementaryos → ubuntu
no longer affects: ubuntu
affects: debian → ubuntu
no longer affects: ubuntu
affects: fedora → ubuntu
no longer affects: ubuntu
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1835664

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote : Re: [Bug 1835664] Re: I can not install any Ubuntu distros in the UEFI mode (but BIOS-compability mode works without efforts): "Unable to install GRUB in /dev/sda"

Sorry, Daniel. Now I download Windows 10. After I will install it and
update my UEFI-BIOS. If I use Rufus, do I need to write Ubuntu to GPT or
should I use MBR / GPT?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I am not familiar with Rufus, but I *think* if you want UEFI to work then the more moden GPT is a better bet.

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :

OK, I will notice you about success after this manipulations.

Revision history for this message
In , ard.biesheuvel (ard.biesheuvel-linux-kernel-bugs) wrote :

Thanks for the info.

The second line has all the info you need:

[ 478.430131] [Firmware Bug]: Page fault caused by firmware at PA: 0x67963770

Note that this is *not* a kernel panic. The kernel does exactly what we intended, which is to contain the page fault caused by the buggy firmware, and proceed without EFI runtime services. Unfortunately, this means that the installer cannot update the boot path so that grub gets invoked at boot by default. The only way to achieve this is probably to use 'bcfg' from the UEFI shell.

Since this is closed source firmware provided by the hardware vendor, there is really very little we can do about this except complaining to them that their firmware is buggy.

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :

I have been completing all needing actions (install Windows 10, update
UEFI-BIOS to F52 version), but problem with grub-installer also repeats. I
even create an apport with refresh information. Look it here:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1838017

пт, 26 июл. 2019 г. в 08:50, Daniel van Vugt <<email address hidden>
>:

> I am not familiar with Rufus, but I *think* if you want UEFI to work
> then the more moden GPT is a better bet.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835664
>
> Title:
> I can not install any Ubuntu distros in the UEFI mode (but BIOS-
> compability mode works without efforts): "Unable to install GRUB in
> /dev/sda"
>
> Status in linux:
> Unknown
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> You also can see the screens that show this problem:
> https://photos.app.goo.gl/4Pimhpr8SwPerA1h7
> https://photos.app.goo.gl/kq5zV5GPrunQpT7j9
> https://photos.app.goo.gl/CqjuADV6zURpwECB6
> https://photos.app.goo.gl/xzNJ6Xt2BSGBYjXR6
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.10
> Package: ubiquity 19.10.5
> ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
> Uname: Linux 5.0.0-20-generic x86_64
> ApportVersion: 2.20.11-0ubuntu3
> Architecture: amd64
> CasperVersion: 1.411
> Date: Sun Jul 7 18:38:45 2019
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed quiet splash ---
> LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190707)
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kernel/+bug/1835664/+subscriptions
>

Revision history for this message
In , pozharovartyom (pozharovartyom-linux-kernel-bugs) wrote :

Created attachment 283985
attachment-29240-0.html

I don't understand what is bcfg and how I can to use it

пт, 26 июл. 2019 г., 12:15 <email address hidden>:

> https://bugzilla.kernel.org/show_bug.cgi?id=204289
>
> --- Comment #7 from Ard Biesheuvel (<email address hidden>) ---
> Thanks for the info.
>
> The second line has all the info you need:
>
> [ 478.430131] [Firmware Bug]: Page fault caused by firmware at PA:
> 0x67963770
>
> Note that this is *not* a kernel panic. The kernel does exactly what we
> intended, which is to contain the page fault caused by the buggy firmware,
> and
> proceed without EFI runtime services. Unfortunately, this means that the
> installer cannot update the boot path so that grub gets invoked at boot by
> default. The only way to achieve this is probably to use 'bcfg' from the
> UEFI
> shell.
>
> Since this is closed source firmware provided by the hardware vendor,
> there is
> really very little we can do about this except complaining to them that
> their
> firmware is buggy.
>
> --
> You are receiving this mail because:
> You reported the bug.

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :

What do I need to do? Should I write to HP support?

пт, 26 июл. 2019 г., 14:29 Artyom Pozharov <email address hidden>:

> I have been completing all needing actions (install Windows 10, update
> UEFI-BIOS to F52 version), but problem with grub-installer also repeats. I
> even create an apport with refresh information. Look it here:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1838017
>
> пт, 26 июл. 2019 г. в 08:50, Daniel van Vugt <
> <email address hidden>>:
>
>> I am not familiar with Rufus, but I *think* if you want UEFI to work
>> then the more moden GPT is a better bet.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1835664
>>
>> Title:
>> I can not install any Ubuntu distros in the UEFI mode (but BIOS-
>> compability mode works without efforts): "Unable to install GRUB in
>> /dev/sda"
>>
>> Status in linux:
>> Unknown
>> Status in linux package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> You also can see the screens that show this problem:
>> https://photos.app.goo.gl/4Pimhpr8SwPerA1h7
>> https://photos.app.goo.gl/kq5zV5GPrunQpT7j9
>> https://photos.app.goo.gl/CqjuADV6zURpwECB6
>> https://photos.app.goo.gl/xzNJ6Xt2BSGBYjXR6
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 19.10
>> Package: ubiquity 19.10.5
>> ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
>> Uname: Linux 5.0.0-20-generic x86_64
>> ApportVersion: 2.20.11-0ubuntu3
>> Architecture: amd64
>> CasperVersion: 1.411
>> Date: Sun Jul 7 18:38:45 2019
>> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
>> file=/cdrom/preseed/ubuntu.seed quiet splash ---
>> LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190707)
>> SourcePackage: grub-installer
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/kernel/+bug/1835664/+subscriptions
>>
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes. Assuming upstream is correct that the problem is in the HP firmware [1] then the only options are to ask HP for a BIOS fix, or to avoid using UEFI on this machine.

I half believe it anyway... I also still wonder how Windows is able to work on the machine and why the BIOS is only broken for Linux.

Sorry we can't help more.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=204289

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :

Windows works excellent with UEFI. Some Chromium OS forks, as ArnoldTheBat
Vanilla and FydeOS works with UEFI amazing too, but they use GRUB 2 too, as
Ubuntu.

сб, 27 июл. 2019 г., 8:30 Daniel van Vugt <email address hidden>:

> Yes. Assuming upstream is correct that the problem is in the HP firmware
> [1] then the only options are to ask HP for a BIOS fix, or to avoid
> using UEFI on this machine.
>
> I half believe it anyway... I also still wonder how Windows is able to
> work on the machine and why the BIOS is only broken for Linux.
>
> Sorry we can't help more.
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=204289
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835664
>
> Title:
> I can not install any Ubuntu distros in the UEFI mode (but BIOS-
> compability mode works without efforts): "Unable to install GRUB in
> /dev/sda"
>
> Status in linux:
> Unknown
> Status in linux package in Ubuntu:
> Invalid
>
> Bug description:
> You also can see the screens that show this problem:
> https://photos.app.goo.gl/4Pimhpr8SwPerA1h7
> https://photos.app.goo.gl/kq5zV5GPrunQpT7j9
> https://photos.app.goo.gl/CqjuADV6zURpwECB6
> https://photos.app.goo.gl/xzNJ6Xt2BSGBYjXR6
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.10
> Package: ubiquity 19.10.5
> ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
> Uname: Linux 5.0.0-20-generic x86_64
> ApportVersion: 2.20.11-0ubuntu3
> Architecture: amd64
> CasperVersion: 1.411
> Date: Sun Jul 7 18:38:45 2019
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed quiet splash ---
> LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190707)
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kernel/+bug/1835664/+subscriptions
>

Changed in kernel:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , linux (linux-linux-kernel-bugs) wrote :

"bcfg" is the boot configuration command contained in the Tianocore/EDK II UEFI shell.

It is possible to boot the PC into the EFI shell rather than GRUB or an OS to use the shell.

There is further information on how to obtain and install the EFI shell version 2 in this thread:

https://superuser.com/questions/1035522/how-to-add-booting-parameters-to-the-kernel-with-bcfg-from-the-efi-shell

Revision history for this message
Artyom Pozharov (artyom-pozharov) wrote :
Revision history for this message
Ivan Ivanov (nesteroff561) wrote :

Hello, I've already solved this problem on Artyom's laptop. The problem really affects UEFI and GRUB. Solution of the problem:
1. Get this error (just install the system)
2. Reboot the system from drive with installation image
3. As soon as you'll boot to the GRUB, press C and write:
set root=(hdX,gptX)
where hdX is your OS hard drive
gptX - root partition. On the monoboot it'll be gpt2;
also you can see your filesystem with "ls /", hard drive with "ls", see which version of the kernel you have: ls /boot/; then write:
linux /boot/vmlinuz-kernelversion root=/dev/sdaX
where X is the number of your partition(matches gptX)
initrd /boot/initrd.img-kernelversion(it is located in the same place as the kernel)
boot
The system will start, after entering the system, open the terminal anyway, write: sudo update-grub2. Reboot. Now, the system'll start without any manual interruptions. Thanks for attention!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.