For anyone who's interested, I installed systemd-boot as per the link
above, but my ESP partition was too small (Windows creates a 100Mb
partition but a 1Gb is more useful for dual boots). So, I created a new
ESP on my second disk, and pointed efibootmgr -d to use it. Eventually,
this seems to at
Hmm, apparently this is not well supported?
ref: https://askubuntu.com/questions/1318789/ubuntu-v20-does-not-detect-
systemd-boot-as-installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
As it seems grub won't be fixed, can you please at least tell me if it's
a good idea or not to replace grub with systemd-boot, and if Ubuntu is
planning to migrate to this too later?
ref: https://askubuntu.com/questions/1225791/how-to-replace-grub-with-
bootloader-systemd-boot-in-ubuntu-20-04
--
I've tested this now a number of times, and 99% of the time, the boot
selection does NOT work!
Is it possible for me to regress grub to an older version that worked
(my alternative boot systems are currently inaccessible, so this is
CRITICAL for me)? If so, can you tell me how, thanks.
(FYI: keys work find inside BIOS setup).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
Title:
menu-selection keys do not work (intermittently, but frequently making
boot choice
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
# SMBIOS implementations newer than version 3.2.0 are not
# fully supported by this version of dmidecode.
Table at 0xCB9F9000.
Handle 0x, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
@juliank
re: "Please check if it works for you before grub when that problem
occurs."
.. how do I do that please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
Title:
menu-selection keys
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1910571/+attachment/5466605/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1910571/+attachment/5466604/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(not sure why this is marked as "incomplete": do you need any other info
from me?)
** Description changed:
This has started happening in the last month or so. I have a clean LTS
20.04.1 that is kept up to date.
On boot, the menu is presented to select what to boot, but quite often
So, I updated to BIOS v3405 (2021/02/05), and the keys STILL do NOT
work! :(
So, the problem still exists: please investigate/fix! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
Title:
FYI: this fix seems to work for me.
Also, re "when": like the other reporter, this only started for me with
the previous update (I think 85.0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914147
I have the same problem: after a security update last night on 20.04
LTS, firefox is now completely broken (displays a window frame with no
content inside, ie it just copies the background image that was
underneath on startup in the framebuffer?).
firefox does work if I pass it a URL at startup.
My BIOS keys seem fine (and the USB mouse in the BIOS setup too).
I'm on v1403 x64 (10/31/2019) vs the latest v3001 (2020/12/9), for ASUS
Prime X570 PRO, but there don't seem to be any keyboard fixes (although
some fixes mention "system stability" whatever that might mean...).
Can anyone tell if this BIOS works or not from the version info?
(it did seem reliable for many months before starting to fail recently
which is a bit odd if it's a BIOS bug...)
What's the best way to test a key before grub: just see if I can go into
BIOS menu?
--
You received this bug
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Table at 0xDA31A000.
Handle 0x, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 1403
Release Date: 10/31/2019
Address: 0xF
Runtime Size: 64 kB
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1910571/+attachment/5450853/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
apport information
** Tags added: apport-collected focal
** Description changed:
This has started happening in the last month or so. I have a clean LTS
20.04.1 that is kept up to date.
On boot, the menu is presented to select what to boot, but quite often
(currently about 90% of
It's a USB keyboard that I'm using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
Title:
menu-selection keys do not work (intermittently, but frequently making
boot choice impossible!)
Public bug reported:
This has started happening in the last month or so. I have a clean LTS
20.04.1 that is kept up to date.
On boot, the menu is presented to select what to boot, but quite often
(currently about 90% of boots), NONE OF THE KEYS WORK, so I cannot
select what to boot!
Randomly,
20 matches
Mail list logo
