*** This bug is a duplicate of bug 2080785 ***
https://bugs.launchpad.net/bugs/2080785
** This bug has been marked a duplicate of bug 2080785
GRUB menu doesn't show with os-prober entries on BIOS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Probably the last comment here: since 24.04 is really unusable on this
hardware, I have tried other distros, and Debian shows the same problem.
Fedora, however, is probably sufficiently far away, and Fedora 41 works
properly here.
So there is no alternative but to say "Good-Bye" to Ubuntu after
Since 24.04 is really non-workable on this Lenovo thinkpad (see my other
reports), and I am a curious person, I downloaded 18.04, wiped the disk
completely, reinstalled W10 followed by kubuntu 18.04, and found
everything to be working as expected. I did the same, yet another time,
and installed 24.
I have three identical helix 2. They all came with Windows preinstalled.
And I could add 18.04 LTS without problem, including getting the grub
boot menu presented without any further action. Only with a later LTS
update did it disappear. So to me this is a regression. I don't want to
indulge into a
is the windows installation also uefi? (dual booting a bios install of
windows from uefi grub is not possible, grub and windows have to match
for that to work)
what is in /etc/default/grub and /boot/grub/grub.cfg?
did you run update-grub? what was its output?
** Changed in: grub2 (Ubuntu)
(I didn't file a new bug to avoid cluttering - still possible if
necessary.)
I installed a fresh installation (that is nom upgrade, like it was in #13) to a
lenovo Helix 2, UEFI, set grub to "menu" and a timeout to "3". At neither hot
nor cold boot does any grub menu show.
Therefore I have to c
Fix released?
In 24.04.1 it still doesn't work here, unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898022
Title:
grub upgrade 18.04->20.04 loses dual-boot to W10
To manage notificat
Great!
How would I get it in a 'normal' way? Will it be retrofitted into 22.04? 24.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898022
Title:
grub upgrade 18.04->20.04 loses dual-boot to W10
Dual boot should work with the current EFI grub
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898022
Title:
grub upgrade 18.04-
Okay, picked up on this. Have two identical machines, lenovo Helix 2,
and both behave the same after the upgrade 18_04 to 20_04.
What I did, was
$ sudo apt-get --reinstall install grub-common grub-pc os-prober
to no avail.
Then, with a somewhat heavy heart
$ sudo grub-install /dev/sda
Installing
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898022
Title:
grub upgrade 18.04->20.04 loses dual-boot to W10
To manage notificati
Now it is too late to check; but I am somewhat sure that before there
was one more entry in the BIOS selection menu: W10, Linux, and one more.
Was ist 'grub' or what? Sorry, can't remember. As of now, I think
there's one less.
--
You received this bug notification because you are a member of Ubun
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-54-generic
Found initrd image: /boot/initrd.img-5.4.0-54-generic
Found linux image: /boot/vmlinuz-4.15.0-124-generic
Found initrd image
** Attachment added: "grub.cfg from some time during the update"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1898022/+attachment/5439684/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Also It seems those are UEFI systems not BIOS systems, so not having an
MBR is not particularly bad?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898022
Title:
grub upgrade 18.04->20.04 loses dual
Please attach /boot/grub/grub.cfg and output of update-grub.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898022
Title:
grub upgrad
Writing my bug report earlier, I was under the impression, the matter
would have to make with an abnormal upgrade to 20.04; earlier two W10
boot partitions, and what not.
I own two identical lenovo Helix 2; and just upgraded the second one.
NOW it IS a bug: because this time, despite of a very nor
I made some progress:
$ grub-probe -t device /boot/grub
/dev/sda6
$ mount
[...]
/dev/sda6 on /boot type ext4 (rw,relatime)
/dev/sda2 on /boot/efi type vfat
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
$ sudo ls /boot/efi/EFI/Ubuntu
BOOTX
I was looking around and found this:
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev3,8G 0 3,8G 0% /dev
tmpfs 786M 3,5M 783M 1% /run
/dev/sda828G 18G 9,0G 66% /
tmpfs 3,9G 277M 3,6G 8% /dev/shm
tmpfs 5,0M 4,0K 5,0
19 matches
Mail list logo
