Peter, I just noticed your more recent comment. I was pretty certain
this was fixed some time ago because os-prober will refuse to generate a
bios windows entry if you are running in EFI mode, but it sounds like
you are still seeing this. Are you running an older release?
--
You received this
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: os-prober (Ubuntu)
Status: Confirmed => 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/1024383
The attachment "Debian commit 6dba9e66 fixes debian #817023 and helps
fix ubuntu #1024383 was released as debian version 1.76" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't
This bug is (at least in our case) caused by libblkid (through
udevd/udevadm) reporting the disklabel type as "dos" while the os-prober
script looks for "msdos". This was fixed upstream in Debian os-prober
1.76 as a fix for Debian bug #817023 for which I have attached the
patch, though I recommend
** Changed in: grub2 (Ubuntu)
Assignee: MOHAMMED FAHAD MUSHAHID (89mfahad) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based
I have a new PC SSD using UEFI/GPT and I am experiencing none of these problems
booting Windows 10.
I installed Windows 10, then Xubuntu 16.04, Xubuntu 18.04 and today Xubuntu
18.10 with zero problems.
Boot entry for Windows 10 default:
menuentry 'Windows Boot Manager (on /dev/sdc1)' --class
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => MOHAMMED FAHAD MUSHAHID (89mfahad)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based
With following packages from Kubuntu Bionic Beaver Beta1 (18.04) :
grub-efi-amd64 2.02-2ubuntu8
grub-efi-amd64-bin 2.02-2ubuntu8
grub-efi-amd64-signed 1.93+2.02-2ubuntu8
os-prober 1.74ubuntu1
On UEFI system 'MSI GE62 7RE-210FR', this issue appears to be solved :
-
This happens in Windows 10 systems, too.
Dell Inspiron 13 5xxx series.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based menu entries for Windows,
** Changed in: grub2 (Ubuntu)
Status: Triaged => Incomplete
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
Yo, stop marking this bug as fixed for no reason.
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub
** Changed in: grub2 (Ubuntu)
Status: Confirmed => 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/1024383
Title:
update-grub generates only BIOS based menu entries for Windows,
I've had several times an update to my Ubuntu install has corrupted my Windows
Boot Manager.
See my Paste:
http://paste2.org/kpXd5p6k
-
Boot Info Script cfd9efe + Boot-Repair extra info [Boot-Info 26Apr2016]
= Boot Info Summary:
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: grub2 (Ubuntu)
Assignee: Gabriela (gabriela68) => (unassigned)
** Changed in: os-prober (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: os-prober (Ubuntu)
Assignee: Gabriela
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: os-prober (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Gabriela (gabriela68)
** Changed in: os-prober (Ubuntu)
Assignee: (unassigned) =>
Concerning comment #51 just above :
Correction :
In the WORKAROUND with 'Secure Boot' ENABLED, you must NOT reference the
Windows partition, but the 'EFI boot' partition :
Simply replace the set of '--hint-*=*' parameters by the output of 'sudo
grub-probe -t hints_string /boot/efi'.
Addition :
In order to boot Windows on UEFI systems :
WORKAROUND with 'Secure Boot' DISABLED
--
The 'grub.cfg' menuentry below, which may conceivably be generated by
'os-prober', works only with 'Secure Boot' disabled :
menuentry "Windows booted from its NTFS partition"
Same bug here: I'm running Kubuntu 15.10 and I can't boot Windows10.
If I pick Windows10 entry in the grub menu selection I obtain the same message
error written in the first post: "Invalid EFI file path".
apt-cache policy grub-efi
grub-efi:
Installato: 2.02~beta2-29ubuntu0.3
Candidato:
Assignment is for a developer who is working on fixing the issue; please
do not use it otherwise.
** Changed in: os-prober (Ubuntu)
Assignee: Sushmita (sush-patil-mita) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: os-prober (Ubuntu)
Assignee: (unassigned) => Sushmita (sush-patil-mita)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based menu
#FIRST
sudo rm /etc/X11/xorg.conf
sudo apt-get purge nvidia*
#AND
sudo apt-add-repository ppa:bumblebee/stable
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2 (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based menu entries for Windows,
I have exactly this same problem. I ran boot-repair but the problem was
not resolved. Th output from boot-repair can be found on
http://paste.ubuntu.com/8350528
Thanks for any helpful advice. I read through some of the posts above,
but if the solution is there I might not have sufficient ubuntu
** Changed in: grub2 (Debian)
Status: New = 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/1024383
Title:
update-grub generates only BIOS based menu entries for Windows, even
Hello, grub2 on Ubuntu has lots of problems.
Having Secure Boot enabled, grub2 is unable to load its modules to chainload
Windows 8.
Having Secure Boot disabled, grub2 is able to load its modules to chainload
Windows 8, but Windows 8 complains about Secure Boot and a watermark appaers on
the
** Changed in: grub2 (Ubuntu)
Status: Confirmed = 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/1024383
Title:
update-grub generates only BIOS based menu entries for Windows,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
affects ubuntu/grub2
status confirmed
thanks
Please don't mark bugs as fixed for no apparent reason.
On 9/19/2013 12:14 PM, lmg wrote:
** Changed in: grub2 (Ubuntu) Status: Confirmed = Fix Released
-BEGIN PGP SIGNATURE-
Version: GnuPG
** Changed in: grub2 (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based menu entries for Windows,
I am also affected by this bug; boot-repair did not work for me. I have
a Samsung Series 3 laptop which has EFI and was distributed with Windows
8 64-bit. http://paste.ubuntu.com/5719692 and
http://paste.ubuntu.com/5719766
--
You received this bug notification because you are a member of Ubuntu
On Fri, May 17, 2013 at 3:17 PM, Phillip Susi ps...@ubuntu.com wrote:
We're not going to support having both installed at the same time and
using the same config. You need to pick which mode you want to use
and stick with it, not flip flop every other boot.
Upstream grub has done a lot of
On 5/18/2013 12:14 AM, Jordan wrote:
Upstream grub has done a lot of work to make sure that you *can* have
support for multiple platforms installed and in use at the same time,
with the same config.
I've notice that same thing. Right after I suggested chainloader-efi
and chainloader-mbr
Phillip Susi wrote:
On 01/08/2013 09:41 PM, YannUbuntu wrote:
No, don't rely on the mode where grub-update is used !
Counter-examples: 1) Windows is installed in UEFI mode but
update-grub is used from a Ubuntu32bit liveCD (which cannot be
booted in UEFI mode, see Bug #102 ).
...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/17/2013 10:38 AM, Joseph Emenaker wrote:
Phillip Susi wrote:
You don't run update-grub from a live session; you have to chroot
into the install and run it from there, where you are running the
correct version, regardless of how you booted the
On 5/17/2013 8:17 AM, Phillip Susi wrote:
You don't seem to have understood the passage you quoted. Let me try
rephrasing it: when you boot from the livecd and update grub, you
first chroot into the hard drive, so you are running the update-grub
version on the hd, not the cd.
True, looking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/17/2013 12:32 PM, Joseph Emenaker wrote:
True, looking back through it, I think I misinterpreted it. I took
the original idea to be use the mode (UEFI vs BIOS) which was used
for this current boot session. You can generate a grub.cfg for
Another report, from one of our members at Kubuntu forums.
http://www.kubuntuforums.net/showthread.php?62191
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only
IMHO:
1) if only grub-pc is installed, then we should add Legacy entries only
2) if only grub-efi is installed, then we should add UEFI entries only
3) if grub-pc AND grub-efi are installed, then we should add Legacy AND UEFI
entries
--
You received this bug notification because you are a
You can't have both installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based menu entries for Windows, even
on UEFI systems
To manage
yep, but it would be nice if we could ;) see Bug #950
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024383
Title:
update-grub generates only BIOS based menu entries for Windows, even
on UEFI
Yes, I got that. Yannu was suggesting that grub add both entries. I
just said adding both is pointless since only one will work. Obviously,
the *correct* one should be added, and not the other.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Phillip Obviously you don't see the problem.
The problem is, Ubuntu installs grub-efi if the pc is in uefi mode but
adds a bios windows 8 entry even when the windows 8 is in uefi mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Christopher:
- your EFI entries have been added by Boot-Repair, you can rename them by
modifying your /etc/grub.d/25_custom file. This is not related to the bug we
are talking about here.
- the fact that you have some bad entries like /dev/sdXY (that come back
because automatically generated
Same here, i manually disabled bad entries like /dev/sdXY and use the
good ones (EFI entries). Still, whenever I get an update the entries
show up again. This is not a huge problem for me, but it would be
awesome if grub could fix this and I didn't have to edit my config
again. Also, this is
yes, grub-mkconfig should add Legacy AND/OR uefi entries according to
the presence of grub-pc AND/OR grub-efi in the install.
(not only if it finds windows, whatever the systems it finds)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/10/2013 2:18 AM, YannUbuntu wrote:
what do you mean by 'version', is it 'grub-pc' vs 'grub-efi' ? if
yes, which entries would you hide if both grub-pc and grub-efi are
installed in the installed Ubuntu? (i would suggest no hiding in
this
You don't run update-grub from a live session; you have to chroot into
the install and run it from there
of course :)
, where you are running the correct version, regardless of how you
booted the livecd.
what do you mean by 'version', is it 'grub-pc' vs 'grub-efi' ?
if yes, which entries
If you know one won't work, then there's no point in adding it. At
update-grub time, you know if you are EFI and should search for an EFI
bootable windows. It might be nice if you can detect that the windows
install is only bios bootable and warn about the problem, but I'm not
sure it's possible
At update-grub time, you know if you are EFI and should search for an
EFI bootable windows.
No, don't rely on the mode where grub-update is used !
Counter-examples:
1) Windows is installed in UEFI mode but update-grub is used from a Ubuntu32bit
liveCD (which cannot be booted in UEFI mode, see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/2013 09:41 PM, YannUbuntu wrote:
No, don't rely on the mode where grub-update is used !
Counter-examples: 1) Windows is installed in UEFI mode but
update-grub is used from a Ubuntu32bit liveCD (which cannot be
booted in UEFI mode, see
** Summary changed:
- grub-update generates MBR entries for GPT partitions
+ update-grub generates only BIOS based menu entries for Windows, even on UEFI
systems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've changed the title to something that I consider correct and
appropriate as the last change was indeed incorrect.
Separately from the title, I wonder if it's possible to have a Windows
installation which is bootable both via BIOS and via UEFI. If so, then
it may not always be clear what type
You can't boot windows in bios mode if grub is booted in efi mode (
since there is no bios ), and vice versa.
Just to make sure, you do have grub-efi installed, and not grub-pc
right? Check with apt-cache policy grub-efi and apt-cache policy grub-
pc.
--
You received this bug notification
I agree with Jordan's new title.
And also with Phillip statement (You can't boot windows in bios mode if grub is
booted in efi mode, and vice versa).
I saw several Windows installations which are bootable both via Legacy and via
UEFI.
I agree with Jordan's suggestion to always createdisplay
53 matches
Mail list logo
