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
Hello, I solved this problem on Artyom's system. The problem is UEFI and GRUB.
Solution to the problem:
should get this error (just install the system)
reboot the system from the media from which the system was installed
as soon as you go to the GRUB menu, press C and write:
set root=(hdX,gptX)
wh
Guys, I've already found the solution.
1) Install the system in UEFI mode.
2) When an error appears, you should reboot and click F9 button.
3) Boot from EFI file -> first line -> BOOT -> bootx64.efi
4) System will boot normally. Then Ctrl+Alt+T and type: sudo update-grub2
5) That's all!
Thanks to
Screenshots are there: https://bugs.launchpad.net/bugs/1835664
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835664
Title:
I can not install any Ubuntu distros in the UEFI mode (but BI
"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.
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=204289.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
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
:
> Yes. Assuming upstream is correct that the problem is in the HP firmware
> [1] then the only
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 Li
What do I need to do? Should I write to HP support?
пт, 26 июл. 2019 г., 14:29 Artyom Pozharov :
> 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.
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 г.
OK, I will notice you about success after this manipulations.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835664
Title:
I can not install any Ubuntu distros in the UEFI mode (but BIO
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 a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835664
Title:
I can not inst
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?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
The required information is in the attachment
https://bugs.launchpad.net/kernel/+bug/1835664/+attachment/5275486/+files/UbiquitySyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
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
** Project changed: linuxmint => ubuntu
** No longer affects: ubuntu
** Project changed: elementaryos => ubuntu
** No longer affects: ubuntu
** Package changed: debian => ubuntu
** No longer affects: ubuntu
** Package changed: fedora => ubuntu
** No longer affects: ubuntu
--
You received t
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
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] WARN
If there is a kernel panic somewhere then:
(1) Please show us the web page where you were told it was a kernel
panic.
(2) Assuming the kernel panic is real and happens during installation,
please reproduce the error again and immediately open a Terminal window.
Now run:
dmesg > dmesg.txt
and
19 matches
Mail list logo
