[bug #62920] Memory address error when booting from LUKS-encrypted /boot

Follow-up Comment #3, bug #62920 (project grub): I was able to resolve my issue. It is not enough to run grub-mkimage to replace the file in the EFI System Partition after upgrading the Grub package. grub-install also needed to be run to replace the files in /boot/grub, THEN also use

[bug #62920] Memory address error when booting from LUKS-encrypted /boot

Follow-up Comment #2, bug #62920 (project grub): My setup is VERY similar to ljyip I found that I also had to stick with commit g2f4430cc0, else I would get an error such as: 452: out of range pointer: 0xb5dc1dc0 when selecting a grub menu item to boot Linux. I also use grub-mkimage to create

[bug #62920] Memory address error when booting from LUKS-encrypted /boot

Follow-up Comment #1, bug #62920 (project grub): I'm new here and I have created an account just for this issue. I would vote instead of leaving a comment, but I don't really understand how the votes work here :/ so I would be glad if this is fixed soon, since I am not the only one who has this

[bug #62920] Memory address error when booting from LUKS-encrypted /boot

URL: <https://savannah.gnu.org/bugs/?62920> Summary: Memory address error when booting from LUKS-encrypted /boot Project: GNU GRUB Submitter: ljyip Submitted: Fri 19 Aug 2022 03:08:33 PM UTC Category: B

[bug #62886] Wrong $cmdpath when booting from an optical disc

Follow-up Comment #3, bug #62886 (project grub): [comment #1 comment #1:] > FAT is case-insensitive While the El Torito image from which GRUB is launched is FAT, (cd0) which GRUB uses in its $cmdpath is ISO 9660 + Rock Ridge + Joliet. ___

[bug #62886] Wrong $cmdpath when booting from an optical disc

Follow-up Comment #2, bug #62886 (project grub): The issue is that configfile ${cmdpath}/grub.cfg doesn't work since $cmdpath is (cd0)/EFI/Boot. configfile (cd0)/EFI/Boot/grub.cfg doesn't work, while configfile (cd0)/EFI/BOOT/grub.cfg works. P.S. Sorry, I made a copy-paste fail in the

[bug #62886] Wrong $cmdpath when booting from an optical disc

Follow-up Comment #1, bug #62886 (project grub): What is the actual problem? FAT is case-insensitive so /EFI/Boot and /EFI/BOOT is the same thing on it. If some pay doesn't test it this way it's the problem of the days part ___ Reply to

[bug #62886] Wrong $cmdpath when booting from an optical disc

URL: <https://savannah.gnu.org/bugs/?62886> Summary: Wrong $cmdpath when booting from an optical disc Project: GNU GRUB Submitter: nl6720 Submitted: Thu 11 Aug 2022 12:55:39 PM EEST Category: B

grub2/uefi booting 32 bit kernels

Hi Team, the grub2 documentation states that this should be possible using grub2 on recent intel/uefi notebooks. I tested it using ubuntu, debian and arch. When booting a 32 bit linux kernel, the screen goes blank and stays like this. On ubuntu, it also gives an error saying the cpu does

Grub disabled my hdd booting

manager so you need to replace grub with something else, I tried but I couldn't disable grub. So then I decided to just replace pop os with windows 10 and skip all my files but I tried booting with my USB and it opened grub. So I'm stuck with MX Linux without the ability to boot to other OSe

[bug #59543] Booting GRUB entries with normal user keep asking for password

Follow-up Comment #1, bug #59543 (project grub): Recent upgrade fixed the issue. ___ Reply to this item at: ___ Message sent via Savannah

[bug #59543] Booting GRUB entries with normal user keep asking for password

URL: <https://savannah.gnu.org/bugs/?59543> Summary: Booting GRUB entries with normal user keep asking for password Project: GNU GRUB Submitted by: redhat48 Submitted on: Wed 25 Nov 2020 05:59:02 PM UTC Category: Se

grub boot fails to find .img files when booting linux w/separate /boot partition

5a1ca848-b27c-966c-8bb5-fb498991521a root disk arch_root / ├─sda316G cdb9e719-9cd1-47ed-911b-c6319b3c67a2 root disk ├─sda4 1K root disk └─sda5 367.7G 6ff811c8-7f8d-9d83-14ac-059816ad4367 root disk arch_home /home I am booting with grub

[bug #57282] Multiple Linux (Debian/Ubuntu 2018/2019, CentOS, Fedora) grub2 2.04 Installation and Booting Problems

URL: <https://savannah.gnu.org/bugs/?57282> Summary: Multiple Linux (Debian/Ubuntu 2018/2019, CentOS, Fedora) grub2 2.04 Installation and Booting Problems Project: GNU GRUB Submitted by: thomaspoetter Submitted on: Wed 20 Nov 2019

Failure when booting after BTRFS snapshot rollback (Kernel panic)

Hi, I have identified this issue on Debian 9.6 with linux-kernel 4.18.0, snapper 0.8.2-1 and grub-common 2.02+dfsg1-8: The system will not boot a snapshot that was rolled back with snapper and run into Kernel panic when selecting default grub entry. Steps to reproduce the issue: 1. Boot

Failure when booting after BTRFS snapshot rollback (Kernel panic)

Hi, I have identified this issue on Debian 9.6 with linux-kernel 4.18.0, snapper 0.8.2-1 and grub-common 2.02+dfsg1-8: The system will not boot a snapshot that was rolled back with snapper and run into Kernel panic when selecting default grub entry. Steps to reproduce the issue: 1. Boot

[bug #56217] Grub2 Booting in blind mode due to "invalid video mode specification `text'"

Follow-up Comment #3, bug #56217 (project grub): BTW, the bug only affects a UEFI platform. In the case of legacy BIOS platform, grub is able to support text mode and we don't see the "error: invalid video mode specification `text'. Booting in blind mode" message, though in this case

[bug #56217] Grub2 Booting in blind mode due to "invalid video mode specification `text'"

Follow-up Comment #2, bug #56217 (project grub): Attached the patch; thanks Dexuan for pointing out that I need to do a better job upstreaming them ;) ___ Reply to this item at:

[bug #56217] Grub2 Booting in blind mode due to "invalid video mode specification `text'"

Additional Item Attachment, bug #56217 (project grub): File name: skip_text_gfxpayload_where_not_supported.patch Size:1 KB ___ Reply to this

[bug #56217] Grub2 Booting in blind mode due to "invalid video mode specification `text'"

URL: <https://savannah.gnu.org/bugs/?56217> Summary: Grub2 Booting in blind mode due to "invalid video mode specification `text'" Project: GNU GRUB Submitted by: decui Submitted on: Thu 25 Apr 2019

[bug #56217] Grub2 Booting in blind mode due to "invalid video mode specification `text'"

Follow-up Comment #1, bug #56217 (project grub): FYI: this is the bug link for Ubuntu 16.04 and 14.04: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1826453 ___ Reply to this item at:

Failure when booting after BTRFS snapshot rollback (Kernel panic)

Hi, I have identified this issue on Debian 9.6 with linux-kernel 4.18.0, snapper 0.8.1 and grub-common 2.02+dfsg1-8: The system will not boot a snapshot that was rolled back with snapper and run into Kernel panic when selecting default grub entry. Steps to reproduce the issue: 1. Boot snapshot

[bug #51712] Issue with serial console redirection being lost over IPMI when booting to dos

Follow-up Comment #1, bug #51712 (project grub): Judging from the documentation I can find, all IPMI serial-over-LAN does is redirect serial port traffic to a network connection. This functionality doesn't seem include capturing writes to video memory, whether directly or via BIOS calls: the

[bug #51712] Issue with serial console redirection being lost over IPMI when booting to dos

URL: <http://savannah.gnu.org/bugs/?51712> Summary: Issue with serial console redirection being lost over IPMI when booting to dos Project: GNU GRUB Submitted by: evildesign Submitted on: Thu 10 Aug 2017 12:56:55

[bug #48100] Booting in blind mode on macmini-2,1

Update of bug #48100 (project grub): Planned Release:None => 2.03+ ___ Follow-up Comment #6: Does your config contain insmod efi_gop?

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #18, bug #50245 (project grub): Summary: I've put all my files ( for all different compilation/configuration ) here. ( all dumps, full configuration, and compilation scripts ) https://drive.google.com/file/d/0ByYkzo4DOiiscDhaYzdRVHdpRlU/view?usp=sharing Short summary: All

[bug #50245] Tftp error while booting via PXE

S tftp + i386/efi -> Grub is booting but I can not load 'R-Drive(Legacy)' or 'R-Drive(Efi)' entry. ( file timeout ) Today I've installed different architecture of Debian ( version x86 instead of amd64), compile grub ( with tftpd32-oack.patch of course ) and make grub-image, and I get completely

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #16, bug #50245 (project grub): > I'm using v4.60 which is newer that yours 4.52 Oops, sorry, I somehow had 4.50 in mind. Yes, 4.60 is 64 bit only, so I cannot easily test it (I do not have 64 bit Windows). This could of course be tftp32 regression.

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #15, bug #50245 (project grub): Ok. I can not find another path :) About tftps. I'm confused after your comment. I'm using v4.60 which is newer that yours 4.52. But I will try downgrade. ___ Reply to this item at:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #14, bug #50245 (project grub): BTW I cannot reproduce it with TFTPD32 v4.52 at all. There is "PXE compatibility" option which indeed makes TFTPD32 process only tsize option but even if I enable it, grub still boots just fine and tftpd32 log shows that it answered with tsize

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #13, bug #50245 (project grub): > tftpd v4.60 + i386 -> working like a charm OK, let's finish with this part. Could you please another version of the patch (please revert previous version first). It continues to send blksize but in different order. Please attach packet trace

[bug #50245] Tftp error while booting via PXE

VMware is restarting after trying to load boox64.efi )(tftpd_efi.pcapng). Boot file is ok because using RouterOS tftp I'm able to boot efi grub but have a problem described at point 3) 3) RouterOS tftp + i386/efi -> Grub is booting but I can not load 'R-Drive(Legacy)' or 'R-Drive(Efi)' entry ( ple

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #10, bug #50245 (project grub): I cannot reproduce it - version with patch boots correctly here. Please try with clean build out of GIT + patch and make sure to recreate netboot directory using just built grub: pkgdatadir=$PWD ./grub-mknetdir --net-directory ... -d grub-core

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #9, bug #50245 (project grub): With patch applied I get "push out of the packet range.." error. Attached: grub_packet_range.pcapng.gz Grub-2017-02-12-17-21-51.png (file #39737, file #39738) ___ Additional Item

[bug #50245] Tftp error while booting via PXE

Update of bug #50245 (project grub): Release:2.00 => 2.02~rc1 ___ Follow-up Comment #8: OK. Your packet trace shows that server does not respond with OACK for GRUB request. Firmware

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #7, bug #50245 (project grub): Sorry for that. I've also reproduce it on i386-pc platform. Seems platform independent. ___ Reply to this item at:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #6, bug #50245 (project grub): Sorry, I do not understand. You report problem with grub on x86_64-efi platform and attach packet capture for grub on i386-pc platform. How is it relevant for EFI problem? ___ Reply to this

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #5, bug #50245 (project grub): Files attached. I've used VMWare workstation 12.5.2 + tftpd v4.60 http://tftpd32.jounin.net No efi. I've used legacy bios. (file #39734, file #39735) ___ Additional Item Attachment:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #4, bug #50245 (project grub): So it did configure some address. Is it the correct one? Please run tcpdump or wireshark on TFTP server and provide packet capture together with IP address grub was using. ___ Reply to this

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #3, bug #50245 (project grub): grub> net_ls_cards efinet0 00:0c:29:20:99:56 grub> net_ls_addr efinet0 00:0c:29:20:99:56 192.168.1.82 ___ Reply to this item at:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #2, bug #50245 (project grub): what is output of net_ls_cards net_ls_addr ?? ___ Reply to this item at: ___ Message sent via/by

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #1, bug #50245 (project grub): I've check grub for legacy bios: grub-mkimage -d /usr/lib/grub/i386-pc/ -O i386-pc-pxe -o ./booti386 -p '(tftp)/grub' pxe tftp and there is no problem with tftp. Ale images are loading without problems. So it's seems problem is related with efi

[bug #50245] Tftp error while booting via PXE

URL: <http://savannah.gnu.org/bugs/?50245> Summary: Tftp error while booting via PXE Project: GNU GRUB Submitted by: marianob85 Submitted on: Tue Feb 7 19:32:02 2017 Category: Network Severity:

[bug #48100] Booting in blind mode on macmini-2,1

Follow-up Comment #5, bug #48100 (project grub): Still not sure what you mean by "your grub is started in text or graphical mode?". rEFIt sure looks graphical, but after that Grub looks "plain text" (just like the legacy Grub1) and I don't use any graphical boot in Debian either (that is, until

[bug #48100] Booting in blind mode on macmini-2,1

Follow-up Comment #4, bug #48100 (project grub): Not sure what you mean by "text or graphical mode". Its started by rEFIt in "the default mode". I could try to build it from Git master, if it can help, tho it'll take yet more time for me to get access to the machine and try

[bug #48100] Booting in blind mode on macmini-2,1

Follow-up Comment #3, bug #48100 (project grub): Just to be sure - your grub is started in text or graphical mode? Do you have possibility to run git master? Then we could try some debugging what's going on. ___ Reply to this item at:

[bug #48100] Booting in blind mode on macmini-2,1

Follow-up Comment #2, bug #48100 (project grub): Sorry 'bout the delay, but the system log didn't have the boot's dmesg any more, so I had to wait for an opportunity to reboot the machine. Note that I go through the Grub boot a lot more often than I reboot, because I hibernate the machine fairly

[bug #48100] Booting in blind mode on macmini-2,1

Additional Item Attachment, bug #48100 (project grub): File name: dmesg.boot Size:90 KB File name: grub.cfg Size:15 KB ___ Reply to this item at:

[bug #48100] Booting in blind mode on macmini-2,1

Follow-up Comment #1, bug #48100 (project grub): Could you attach your grub.cfg and dmesg output after Linux is booted? ___ Reply to this item at: ___

bug#48100 Booting in blind mode on macmini-2,1

I posted this half a year ago but haven't gotten any feedback yet. Any hint or idea what might be going on, how I could track it, debug, it, circumvent it, ... ? Stefan https://savannah.gnu.org/bugs/?48100 ___ Bug-grub mailing list

[bug #49365] Booting: GNU/Linux: partially incorrect information

Update of bug #49365 (project grub): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: It simply avoids

[bug #49365] Booting: GNU/Linux: partially incorrect information

URL: <http://savannah.gnu.org/bugs/?49365> Summary: Booting: GNU/Linux: partially incorrect information Project: GNU GRUB Submitted by: ing Submitted on: Sun 16 Oct 2016 06:09:31 PM GMT Category: Documen

[bug #48100] Booting in blind mode on macmini-2,1

URL: <http://savannah.gnu.org/bugs/?48100> Summary: Booting in blind mode on macmini-2,1 Project: GNU GRUB Submitted by: monnier Submitted on: Thu 02 Jun 2016 11:28:59 AM EDT Category: Terminal Se

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Follow-up Comment #6, bug #38738 (project grub): Please retest if it still happens with master ___ Reply to this item at: ___ Message sent via/by

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Update of bug #38738 (project grub): Item Group: Software Error => Hardware-specific Planned Release:None => 2.03+ ___ Reply to this item at:

[bug #37331] GRUB 2 hangs when booting from USB drive on HP laptop DV7-6190

Update of bug #37331 (project grub): Item Group:None => Hardware-specific Planned Release:None => 2.03+ ___ Reply to this item at:

[bug #34847] GRUB 1.99 doesn't read com.apple.Boot.plist when booting OS X 10.6

Update of bug #34847 (project grub): Planned Release:None => 2.03+ ___ Reply to this item at: ___

[bug #31973] make basic UNDI networking available to grub while NOT booting from a network card.

Update of bug #31973 (project grub): Planned Release:None => 2.03+ ___ Reply to this item at: ___

[bug #42976] grub2 waits forever for keystroke before booting

Update of bug #42976 (project grub): Status:None = Invalid Open/Closed:Open = Closed ___ Follow-up Comment #1: Upstream GRUB doesn't

[bug #42976] grub2 waits forever for keystroke before booting

URL: http://savannah.gnu.org/bugs/?42976 Summary: grub2 waits forever for keystroke before booting Project: GNU GRUB Submitted by: brycenesbitt Submitted on: Wed 13 Aug 2014 10:51:12 AM PDT Category: Booting

[bug #41883] Booting from NVMe Device Enters GRUB rescue

Update of bug #41883 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #4: Patch committed. The

[bug #41883] Booting from NVMe Device Enters GRUB rescue

/sysimage/boot /dev/nvme0n1 After rebooting and booting from NVMe device. It entered into grub prompt grub grubls (hd0) (hd0,msdos5) (hd0,msdos3) (hd0,msdos2) (hd0,mdos1) grub After Manually Setting root, linux and initrd we were able to boot Linux Fedora from NVMe device. Thanks Regards Vinayak

[bug #41883] Booting from NVMe Device Enters GRUB rescue

Follow-up Comment #3, bug #41883 (project grub): Hi phcoder(Vladimir), I have found also one thing i observed after booting. there were two grub directories grub and grub2. But grub.cfg was present inside grub2 folder. Hope this might help you further. Thanks Regards Vinayak Holikatti

[bug #41883] Booting from NVMe Device Enters GRUB rescue

Follow-up Comment #1, bug #41883 (project grub): Please try attached patch (file #31045) ___ Additional Item Attachment: File name: nvme.diff Size:0 KB ___

[bug #41655] booting problem with x86_64 specific image with GRUB (apparently in relocator.c)

Update of bug #41655 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #1: Fixed. Please retest

[bug #41883] Booting from NVMe Device Enters GRUB rescue

URL: http://savannah.gnu.org/bugs/?41883 Summary: Booting from NVMe Device Enters GRUB rescue Project: GNU GRUB Submitted by: vinholi Submitted on: Mon 17 Mar 2014 10:22:35 AM GMT Category: Installation

[Patches from Fedora package] Network booting changes

Hi, chained to this message are fixes and enhancements from Fedora package (Red Hat Enterprise Linux ships them too) related to network booting. I've made only minor changes to them, described in individual commit messages. Please have a look, and eventually merge; I think all of them

[bug #39750] Booting from syslinux via lnxboot no longer figures out root partition

Update of bug #39750 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Reply to this item at:

[bug #39750] Booting from syslinux via lnxboot no longer figures out root partition

Follow-up Comment #3, bug #39750 (project grub): As discussed on IRC offsets used seem to contradict official boot protocol documentation. Where did you get those values? ___ Reply to this item at: http://savannah.gnu.org/bugs/?39750

[bug #39750] Booting from syslinux via lnxboot no longer figures out root partition

Follow-up Comment #4, bug #39750 (project grub): As discussed on IRC offsets used seem to contradict official boot protocol documentation. Where did you get those values? From the original GRUB code removed in bzr revno 3592, from the syslinux source, and from testing and verifying that this

[bug #39750] Booting from syslinux via lnxboot no longer figures out root partition

Additional Item Attachment, bug #39750 (project grub): File name: grub-lnxboot-boot-device-partition.patch Size:1 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?39750 ___

[bug #39750] Booting from syslinux via lnxboot no longer figures out root partition

Follow-up Comment #2, bug #39750 (project grub): I've attached a new version of the patch, which removes extraneous autogen noise, and adds a changelog entry to be added to ChangeLog when applying the patch. ___ Reply to this item at:

[bug #39750] Booting from syslinux via lnxboot no longer figures out root partition

URL: http://savannah.gnu.org/bugs/?39750 Summary: Booting from syslinux via lnxboot no longer figures out root partition Project: GNU GRUB Submitted by: joshtriplett Submitted on: Sat 10 Aug 2013 11:24:27 PM PDT Category

[bug #39217] document booting submenu items in the grub-reboot --help output and manual page

Update of bug #39217 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Reply to this item at:

[bug #39217] document booting submenu items in the grub-reboot --help output and manual page

Follow-up Comment #1, bug #39217 (project grub): This also applies to grub-set-default. Also, using ** as the submenu separator is problematic, as you have to quote it or escape it with a backslash to prevent the shell from interpreting it as a redirection. Any documentation update should

[bug #39217] document booting submenu items in the grub-reboot --help output and manual page

URL: http://savannah.gnu.org/bugs/?39217 Summary: document booting submenu items in the grub-reboot --help output and manual page Project: GNU GRUB Submitted by: pabs Submitted on: Mon 10 Jun 2013 12:12:46 PM WST Category

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

URL: http://savannah.gnu.org/bugs/?38738 Summary: GRUB hangs up when booting if GRUB_GFXMODE=auto Project: GNU GRUB Submitted by: foxburu Submitted on: lun 15 abr 2013 06:44:34 GMT Category: Booting

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Follow-up Comment #1, bug #38738 (project grub): At which stage does it hang? Before or after the choice of entry? What's the last thing that you see? There is no GRUB_GFXMODE=text, you just make mode selection fail and it's equivalent to setting GRUB_TERMINAL_OUTPUT=console. Can you attach a

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Follow-up Comment #2, bug #38738 (project grub): It hangs after the choice of entry. The last think i see is the line Loading Linux Kernel... then it hangs. I've put some debug info, and the corrupted screen on attachments. Also the videoinfo on auto and console. I'll try adding resolution

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Follow-up Comment #3, bug #38738 (project grub): Oh, yes, File #27881 is on console, #27879 is on auto. The corrupted screen on #27880 is visible on the top of screen. ___ Reply to this item at: http://savannah.gnu.org/bugs/?38738

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Follow-up Comment #4, bug #38738 (project grub): Please attach your noth grub.cfg (you confuse concept so I'm not sure what you really mean) and don't use debug=all on EFI, it doesn't work due to EFI memory management. ___ Reply to this

[bug #38738] GRUB hangs up when booting if GRUB_GFXMODE=auto

Follow-up Comment #5, bug #38738 (project grub): Here the grub.cfg and the /etc/default/grub file. (file #27886, file #27887) ___ Additional Item Attachment: File name: default_grub Size:1 KB File name: grub.cfg

Translations with single quotes prevent grub from booting

When you generate a grub configuration file using grub-mkconfig and your system's language is set to Catalan, the file generated has a problem. It contains the following two lines for every linux entry, which prevent you from booting that entry: echo'S'està carregant el Linux (name

[bug #37331] GRUB 2 hangs when booting from USB drive on HP laptop DV7-6190

URL: http://savannah.gnu.org/bugs/?37331 Summary: GRUB 2 hangs when booting from USB drive on HP laptop DV7-6190 Project: GNU GRUB Submitted by: peppepz Submitted on: mar 11 set 2012 15:18:05 GMT Category: Booting

Re: Trouble booting off an md device with grub 1.99

can't locate the blocks to load next. Do you see GRUB or Welcome to GRUB messages? I also tried booting off a USB stick and using --boot-directory from the live distro rather than chrooting. I also tried specifying '(hd0)' and '(hd1)' instead of the device nodes. This is grub_1.99

Trouble booting off an md device with grub 1.99

/dev/sdb exit # umount everything and reboot After this, the machine won't boot off the new drives. It will simply hang with a black screen after the POST, when the grub menu would normally come up. It looks almost like the mbr can't locate the blocks to load next. I also tried booting off

[bug #34847] GRUB 1.99 doesn't read com.apple.Boot.plist when booting OS X 10.6

Update of bug #34847 (project grub): Priority: 5 - Normal = 3 - Low Item Group: Software Error = Feature Request ___ Reply to this item at:

Re: GRUB not booting from a BIOS+GPT+BTRFS setup

Can you supply the results of cat /proc/self/mountinfo cat /proc/mounts and other info about FS? -- Regards Vladimir 'φ-coder/phcoder' Serbinenko ___ Bug-grub mailing list Bug-grub@gnu.org https://lists.gnu.org/mailman/listinfo/bug-grub

grub 1.99: no TFTP-booting when GRUB is locally installed --- why?

Apparently, GRUB's network capabilities are only designed to be loaded as an etherboot/PXE image itself. There is currently no possibility (at least, none that I could derive) to install GRUB on a host, obtain a DHCP config and TFTP-boot a remotely served kernel that attaches its

Re: grub 1.99: no TFTP-booting when GRUB is locally installed --- why?

On 04.09.2011 20:33, René Kuligowski wrote: Apparently, GRUB's network capabilities are only designed to be loaded as an etherboot/PXE image itself. There is currently no possibility (at least, none that I could derive) to install GRUB on a host, obtain a DHCP config and TFTP-boot a

[bug #33162] grub2 1.99-rc2 alloc magic is broken error on booting UEFI shell the second time

Follow-up Comment #1, bug #33162 (project grub): Should be fixed in trunk. Can you confirm? ___ Reply to this item at: http://savannah.gnu.org/bugs/?33162 ___ Message sent via/by Savannah

[bug #33162] grub2 1.99-rc2 alloc magic is broken error on booting UEFI shell the second time

URL: http://savannah.gnu.org/bugs/?33162 Summary: grub2 1.99-rc2 alloc magic is broken error on booting UEFI shell the second time Project: GNU GRUB Submitted by: liucougar Submitted on: Tue 26 Apr 2011 02:26:00 AM GMT

[bug #29272] grub-install on bind mounted /boot/grub fails upon booting

Update of bug #29272 (project grub): Status:None = Fixed Open/Closed:Open = Closed Release:1.98 = Bazaar - experimental branch

[bug #27720] Weird BIOS keeps GRUB from booting correctly

Update of bug #27720 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #2: Documented in

Why is my system booting?

-booting--tp29973202p29973202.html Sent from the Grub - Bugs mailing list archive at Nabble.com. ___ Bug-grub mailing list Bug-grub@gnu.org http://lists.gnu.org/mailman/listinfo/bug-grub

[bug #27720] Weird BIOS keeps GRUB from booting correctly

Follow-up Comment #1, bug #27720 (project grub): r2630 on trunk fixed it, though the loop device trick mentioned at http://lists.gnu.org/archive/html/grub-devel/2009-09/msg00488.html needs to be applied. It'll most likely be commented at a more central place and probably be integrated into

[bug #29272] grub-install on bind mounted /boot/grub fails upon booting

URL: http://savannah.gnu.org/bugs/?29272 Summary: grub-install on bind mounted /boot/grub fails upon booting Project: GNU GRUB Submitted by: oli1417 Submitted on: Sat 20 Mar 2010 01:08:16 PM GMT Category: Installation

booting EsX4i

Hi All, when i try too boot esx4i by either giving grub an exit or too chainload the partition/disk it does not work. At this moment i am using the version wich is delivered with debian sqeeuze (so a version 2) if i do an grub exit then i starts booting ESX4i and on the first screen

[bug #28816] error booting windows xp

Update of bug #28816 (project grub): Status:None = Invalid Open/Closed:Open = Closed ___ Follow-up Comment #2: It's a known problem

[bug #28816] error booting windows xp

Follow-up Comment #1, bug #28816 (project grub): Do you use Debian or Ubuntu? Then run sudo dpkg-reconfigure grub-pc and check that the device listed in the debconf prompt for it is the one where your BIOS boots from. Else run grub-install on the right device. Such errors can only happen if

  1   2   3   4   5   >