<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.boot-loaders.grub.bugs">
    <title>gmane.comp.boot-loaders.grub.bugs</title>
    <link>http://blog.gmane.org/gmane.comp.boot-loaders.grub.bugs</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9108"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9106"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9105"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9101"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9086"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9085"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9081"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9080"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9077"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9074"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9073"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9071"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9068"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9067"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9065"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9064"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9057"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9041"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9039"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9037"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9108">
    <title>[bug #36532] boot in EFI mode (x86_64) fails on some systems</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9108</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36532&amp;gt;

                 Summary: boot in EFI mode (x86_64) fails on some systems
                 Project: GNU GRUB
            Submitted by: stuart_hayes
            Submitted on: Wed 23 May 2012 07:33:10 PM GMT
                Category: Booting
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: stuart_hayes
        Originator Email: stuart_hayes&amp;lt; at &amp;gt;dell.com
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: other
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

Grub v 1.99 is failing to boot on certain systems in EFI mode.

This was discovered on some Dell 12G server systems (the PowerEdge R720, for
example), using Ubuntu 12.04, but the issue was reproduced with vanilla grub
1.99.  Some systems will boot under certain circumstances (I have one R720
that will boot if I hit "F11" to go into a UEFI boot menu and then boot, but
not if the system tries to boot with no manual intervention), other systems
will not boot at all.

The problem is that grub2 is failing to get the EFI memory map in
grub-core/loader/i386/linux.c, when it calls grub_efi_finish_boot_services(),
because the buffer it allocated for the EFI memory map earlier in
allocate_pages() (in the same file) is not big enough.  (The EFI memory map
has grown considerably--like 50000 bytes or so--between the time that the
efi_mmap_buf was set up in allocate_pages() and the time it is used in
grub_efi_finish_boot_services()).

When allocate_pages() runs, it really has no way to know how large the EFI
memory map will be when it needs that buffer.  Also, the EFI memory map does
not need to be at an address under 1MB, either.

I've made a patch that modifies allocate_pages() so that it no longer
allocates a buffer for the EFI memory map.  Instead, the buffer is allocated
right before the call to grub_efi_finish_boot_services() in grub-linux_boot(),
and it tries to put it at the top of memory (or just below the initrd, if one
is loaded).

I have verified that this fixes the issue on my systems.

I'm attaching the patch.




    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Wed 23 May 2012 07:33:10 PM GMT  Name:
grub-1.99-upstream_efimm_late_malloc_3.patch  Size: 6kB   By: stuart_hayes
patch to allocate EFI mmap buffer later
&amp;lt;http://savannah.gnu.org/bugs/download.php?file_id=25912&amp;gt;

    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36532&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>stuart hayes</dc:creator>
    <dc:date>2012-05-23T19:33:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9106">
    <title>[bug #36525] Update overwrites /etc/default/grub</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9106</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36525&amp;gt;

                 Summary: Update overwrites /etc/default/grub
                 Project: GNU GRUB
            Submitted by: chiel92
            Submitted on: Tue 22 May 2012 04:24:41 PM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: other
         Reproducibility: Once
         Planned Release: None

    _______________________________________________________

Details:

Normal priority.
Today I ran an apt-get update on Ubuntu 12.04 and I noticed the file
/etc/default/grub was overwritten, so I lost all my tweaks.
This update involved a kernel update, which probably caused this problem.
I noticed that there are other people experiencing the same problem. 

The grub version I use is:
grub-install (GRUB) 1.99-21ubuntu3

Sorry, I don't know which value in the release field corresponds to this
version.

The OS I use is:
Ubuntu 12.04 precise pangolin




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36525&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Chiel</dc:creator>
    <dc:date>2012-05-22T16:24:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9105">
    <title>[bug #36522] wrong fonts for starfield theme - bold is missing</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9105</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36522&amp;gt;

                 Summary: wrong fonts for starfield theme - bold is missing
                 Project: GNU GRUB
            Submitted by: kiilerix
            Submitted on: Tue 22 May 2012 13:17:43 GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

I can't repopen https://savannah.gnu.org/bugs/index.php?36446 so I file this
instead:

Multiple font files will now be installed -
http://bzr.savannah.gnu.org/lh/grub/trunk/grub/annotate/4343/Makefile.am#L72 .
It will however only install non-bold fonts. The theme also uses some bold
fonts -
http://bzr.savannah.gnu.org/lh/grub/trunk/grub/annotate/4343/themes/starfield/theme.txt#L51
.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36522&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Mads Kiilerich</dc:creator>
    <dc:date>2012-05-22T13:17:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9101">
    <title>[bug #36509] Repository Contains Malformed Commits</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9101</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36509&amp;gt;

                 Summary: Repository Contains Malformed Commits
                 Project: GNU GRUB
            Submitted by: kphillis
            Submitted on: Sun 20 May 2012 09:52:29 PM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: Action Request
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

When attempting to perform a fast export of the grub bazaar tree to a git
repository, I found a few errors within the source repository. These errors
are commits that have been tagged with an empty Author. The exact commits are
Revision 3144 that was commited on March 30th, 2011, and Revision 2266 that
was posted on March 24th, 2010. These can be confirmed by doing a quick grep
of the bazaar log using the following command:

bzr log | grep author\:\ $ -a4



as for the Fix, Change the log entry to remove the empty author field, and
then the bazaar repository can easily be exported to other repository
software.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36509&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Kenney Phillis</dc:creator>
    <dc:date>2012-05-20T21:52:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9086">
    <title>[bug #36490] grub-probe doesn't work with fat32 file systems</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9086</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36490&amp;gt;

                 Summary: grub-probe doesn't work with fat32 file systems
                 Project: GNU GRUB
            Submitted by: gutworth
            Submitted on: Fri 18 May 2012 04:13:43 AM GMT
                Category: Filesystem
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

/boot/efi is a 


With latest bzr:

$ grub-probe -t fs /boot/efi
grub-probe: error: unknown filesystem

grub-probe from Ubuntu correclty identifies it.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36490&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Benjamin Peterson</dc:creator>
    <dc:date>2012-05-18T04:13:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9085">
    <title>[bug #36489] Countdown not show for GRUB_HIDDEN_TIMEOUT on gfxtermoutput.</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9085</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36489&amp;gt;

                 Summary: Countdown not show for GRUB_HIDDEN_TIMEOUT on
gfxterm output.
                 Project: GNU GRUB
            Submitted by: jordanu
            Submitted on: Fri 18 May 2012 01:00:58 AM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

Due to the way that gfxterm is implemented (I believe) "sleep --verbose" isn't
actually verbose at all when viewed via gfxterm. This means that using a
standard grub-mkconfig generated grub.cfg with GRUB_HIDDEN_TIMEOUT=10 and
GRUB_HIDDEN_TIMEOUT_QUIET=false there is no indication to the user that grub
has started and is counting down while waiting for input to show the grub
menu, they will simply see a completely black screen for ten seconds.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36489&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Jordan Uggla</dc:creator>
    <dc:date>2012-05-18T01:00:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9081">
    <title>Grub2 not recognise GPT when present hybrid MBR</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9081</link>
    <description>&lt;pre&gt;Root issue:
 grub ignore protective GPT record if that record is not the first one in
MBR.
Need to correct:
 If protective GPT record appears on any place in MBR - grub must consider
system as GPT.

My system is Ubuntu and package I using is grub-pc  1.99-21ubuntu3.
I trust that my error is not distributive specific

I have hybrid GPT/MBR. Hybrid MBR contains protective record 0xEE but that
record is NOT first.
Here is output of gdisk (hybrid MBR):
Number  Boot  Start Sector   End Sector   Status      Code
   1                468992    101480447   primary     0x07
   2             234375168    234569727   primary     0xEF
   3      *      550782882    574927413   primary     0x83
   4                     1       468991   primary     0xEE

gdisk (GPT):
Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          206847   100.0 MiB   EF00  EFI system
partition
   2          206848          468991   128.0 MiB   0C01  Microsoft reserved
part
   3          468992       101480447   48.2 GiB    0700  win7
   4       101480448       138344447   17.6 GiB    AF00  other
   5       390625280       527343615   65.2 GiB    8301  copyfilesWIN7
   6       527343616       550780927   11.2 GiB    AF00  backupfile
   7       581042176       625141759   21.0 GiB    2700  Samsung_diag
   8       138344448       234375167   45.8 GiB    0700  DATA
  11       574927414       581042175   2.9 GiB     8200
  12       234375168       234569727   95.0 MiB    EF02  grub
  13       550782882       574927413   11.5 GiB    0700  linux

After that it result in such errors:
root&amp;lt; at &amp;gt;helena:~# grub-install /dev/sda
/usr/sbin/grub-setup: warn: This msdos-style partition label has no
post-MBR gap; embedding won't be possible!.
/usr/sbin/grub-setup: warn: Embedding is not possible.  GRUB can only be
installed in this setup by using blocklists.  However, blocklists are
UNRELIABLE and their use is discouraged..
/usr/sbin/grub-setup: error: will not proceed with blocklists.

invoking grub-mkconfig manually gives:
root&amp;lt; at &amp;gt;helena:~# grub-mkconfig  -o test.conf
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-24-generic
Found initrd image: /boot/initrd.img-3.2.0-24-generic
Found linux image: /boot/vmlinuz-3.0.0-19-generic
Found initrd image: /boot/initrd.img-3.0.0-19-generic
Found linux image: /boot/vmlinuz-2.6.38-14-generic
Found initrd image: /boot/initrd.img-2.6.38-14-generic
Found linux image: /boot/vmlinuz-2.6.38-8-generic
Found initrd image: /boot/initrd.img-2.6.38-8-generic
Found memtest86+ image: /boot/memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/sda4.  Check your
device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda5.  Check your
device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda6.  Check your
device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda7.  Check your
device.map.
done

I have tried diferent approach - was  removed hybrid MBR (retained only
protective record). After that grub-install succeed. After that I have
created hybrid MBR (the same as above).
But after reboot I have got "grub rescue" prompt and error: no such
partition.

&lt;/pre&gt;</description>
    <dc:creator>Stanislav Davydov</dc:creator>
    <dc:date>2012-05-11T15:24:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9080">
    <title>upgrade-from-grub-legacy failure</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9080</link>
    <description>&lt;pre&gt;Hi all,

I was asked to report the failure of grup to be upgraded here. What
follows is the output of "/usr/sbin/grub-probe
--device-map=/boot/grub/device.map --target=fs -v /boot/grub":

build5:~# /usr/sbin/grub-probe --device-map=/boot/grub/device.map
--target=fs -v /boot/grub &amp;gt;/tmp/grub-failure.txt
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0GST8', skipping.
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0H7L9', skipping.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: changing current directory to dri.
/usr/sbin/grub-probe: info: changing current directory to snd.
/usr/sbin/grub-probe: info: changing current directory to net.
/usr/sbin/grub-probe: info: changing current directory to shm.
/usr/sbin/grub-probe: info: opening md0.
/usr/sbin/grub-probe: error: no such disk.

I should probably mention that there was a problem during the upgrade.
This machine runs entirely on a software RAID1 (no boot partition, and
root is mounted on /dev/md0). During the upgrade to squeeze, mdadm found
that the device ID for md0 had changed. I updated the
/etc/mdadm/mdadm.conf file, but forgot to run update-initramfs, and then
subsequent boots failed until I booted into rescue mode and ran the
command from the rescue shell.
The system now boots, using the chainloader. However, during the boot
process I also get error messages that some information could not be
read from the drives.

Detailed log files are available if needed.

&lt;/pre&gt;</description>
    <dc:creator>Wolfgang Schulze-Zachau</dc:creator>
    <dc:date>2012-05-10T13:22:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9077">
    <title>[bug #36446] wrong fonts for starfield theme</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9077</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36446&amp;gt;

                 Summary: wrong fonts for starfield theme
                 Project: GNU GRUB
            Submitted by: kiilerix
            Submitted on: Thu 10 May 2012 10:09:03 GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

The build system will create dejavu.pf2 with no special mkfont options and it
will thus be 16 point only. The starfield theme do however use other fonts.

As a work around I used something like

rm dejavu.pf2
grub-mkfont -o DejaVuSans-10.pf2      -s 10
/usr/share/fonts/dejavu/DejaVuSans.ttf # "DejaVu Sans Regular 10"
grub-mkfont -o DejaVuSans-12.pf2      -s 12
/usr/share/fonts/dejavu/DejaVuSans.ttf # "DejaVu Sans Regular 12"
grub-mkfont -o DejaVuSans-Bold-14.pf2 -s 14
/usr/share/fonts/dejavu/DejaVuSans-Bold.ttf # "DejaVu Sans Bold 14"

- but the theme installation is very hardcoded in the build system.


Slightly related:
It would be nice if mkfont showed exactly which "font name" it created.
It would be nice if mkfont didn't create empty pf2 files when no font source
is specified.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36446&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Mads Kiilerich</dc:creator>
    <dc:date>2012-05-10T10:09:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9074">
    <title>[bug #36433] Leading spaces after '\' line continuation cause syntaxerror</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9074</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36433&amp;gt;

                 Summary: Leading spaces after '\' line continuation cause
syntax error
                 Project: GNU GRUB
            Submitted by: jordanu
            Submitted on: Tue 08 May 2012 08:43:50 AM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

The following code causes a syntax error in grub but is completely valid and
causes no problems in bash:

echo \
 test

Note the space before "test". With a file test.cfg containing the above two
lines I can run "bash test.cfg" and it will simply print "test\n" as expected
but when I run "grub-script-check test.cfg" I get the following output:

error: out of memory.
error: syntax error.
Syntax error at line 2

I ran into this bug while trying to get bvk's autoiso.cfg working for Super
GRUB2 Disk.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36433&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Jordan Uggla</dc:creator>
    <dc:date>2012-05-08T08:43:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9073">
    <title>[bug #36404] Colons in environment variable identifiers are unreadable</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9073</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36404&amp;gt;

                 Summary: Colons in environment variable identifiers are
unreadable
                 Project: GNU GRUB
            Submitted by: christrenkamp
            Submitted on: Sat 05 May 2012 01:49:54 AM GMT
                Category: Terminal
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

If an environment variable has a colon in its identifier, it will be
inaccessible when attempting to read it.

For example, after the user runs 'net_bootp', the environment variable
'net_pxe:dhcp_boot_file' will be set.  If the user attempts to read it with
echo '${net_pxe:dhcp_boot_file}', the command will return these errors:
error: $.
error: syntax error.
error: Incorrect command.
error: syntax error.

I've tried various ways to read these variable, but can't find one that works.
 I know these variables were meant to be read-only, which is probably why
there's a colon in the identifier, but it would be extremely useful to be able
to read them.





    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36404&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Chris Trenkamp</dc:creator>
    <dc:date>2012-05-05T01:49:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9071">
    <title>grub-install doesn't work</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9071</link>
    <description>&lt;pre&gt; 

Hi 

I tryed to install grub but i get this error message: 

---


root&amp;lt; at &amp;gt;morgul:~# grub-install /dev/sdg
/usr/sbin/grub-probe: error: no
such disk.
Auto-detection of a filesystem of /dev/md1 failed.
Please
report this together with the output of "/usr/sbin/grub-probe
--device-map=/boot/grub/device.map --target=fs -v /boot/grub" to
&amp;lt;bug-grub&amp;lt; at &amp;gt;gnu.org&amp;gt;
root&amp;lt; at &amp;gt;morgul:~# /usr/sbin/grub-probe
--device-map=/boot/grub/device.map --target=fs -v
/boot/grub
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/ata-WDC_WD3200AAJS-00B4A0_WD-WMAT15012811',
skipping.
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/ata-WDC_WD3200AAJS-00B4A0_WD-WMAT15009217',
skipping.
/usr/sbin/grub-probe: info: changing current directory to
/dev.
/usr/sbin/grub-probe: info: changing current directory to
space.
/usr/sbin/grub-probe: info: changing current directory to
dri.
/usr/sbin/grub-probe: info: changing current directory to
snd.
/usr/sbin/grub-probe: info: changing current directory to
net.
/usr/sbin/grub-probe: info: changing current directory to
shm.
/usr/sbin/grub-probe: info: changing current directory to
mapper.
/usr/sbin/grub-probe: info: opening md/1.
/usr/sbin/grub-probe:
error: no such disk.
root&amp;lt; at &amp;gt;morgul:~# 

--- 

The operating system is a
Debian Squeeze. 

Have a nice day. 

&lt;/pre&gt;</description>
    <dc:creator>Jose Manuel Ferrer Mosteiro</dc:creator>
    <dc:date>2012-05-04T10:26:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9068">
    <title>grub with ubuntu 11.10</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9068</link>
    <description>&lt;pre&gt;hi there ,
 
maybe you can help me - updated ubuntu to 11.10 version , have installed xp too , bootloader does not
 
find xp - in other words , its not in listed in boot menue anymore
 
what can i do to resolve ?
 
regards
 
martin k, böblingen
_______________________________________________
Bug-grub mailing list
Bug-grub&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
&lt;/pre&gt;</description>
    <dc:creator>mkaiser-bb&lt; at &gt;freenet.de</dc:creator>
    <dc:date>2012-04-30T07:49:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9067">
    <title>[bug #36340] 'make html' fails</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9067</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36340&amp;gt;

                 Summary: 'make html' fails
                 Project: GNU GRUB
            Submitted by: kiilerix
            Submitted on: Sun 29 Apr 2012 10:49:36 PM GMT
                Category: Installation
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

'make html' fails with
grub-dev.texi:1692: &amp;lt; at &amp;gt;image file `font_char_metrics..png' (for HTML) not
readable: No such file or directory.
on the line
&amp;lt; at &amp;gt;image{font_char_metrics,,,,.png}

Removing the . from png makes it work ... apparently contrary to what makeinfo
documentation says. Leaving the extension out works for html - but might break
for other formats.

(Depending on how this is fixed, the next issues might be that other images
are completely missing and that 'make install-html' doesn't install the
images.)




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36340&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Mads Kiilerich</dc:creator>
    <dc:date>2012-04-29T22:49:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9065">
    <title>Grub bootloader installation bug report</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9065</link>
    <description>&lt;pre&gt;To whom it may concern:

I have tried and failed to manually install a grub bootloader onto an external hard drive. So here is the output from the `/usr/sbin/grub-probe --device-map="/media/EHD/boot/grub/device.map" --target=fs -v /media/EHD/boot/grub` command as requested:

Auto-detection of a filesystem of /dev/sdb1 failed.
/usr/sbin/grub-probe: info: cannot open `/media/EHD/boot/grub/device.map'.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: scanning hd1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: scanning hd0,msdos5 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: scanning hd0,msdos1 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: scanning hd1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: scanning hd1,msdos1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: /dev/sdb1 starts from 2048.
/usr/sbin/grub-probe: info: opening the device /dev/sdb.
/usr/sbin/grub-probe: info: the size of /dev/sdb is 155907768.
/usr/sbin/grub-probe: info: Partition 0 starts from 256.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.

I hope this is of use in resolving this situation.

Sincerely,
-matthew dodt
&amp;lt;randygaffer&amp;lt; at &amp;gt;yahoo.com&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>Midnight Matt</dc:creator>
    <dc:date>2012-04-29T03:51:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9064">
    <title>GRUB recovery mode has blank screen in Ubuntu Linux</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9064</link>
    <description>&lt;pre&gt;After my video card failed, I used the on-board video on the
motherboard. That changed caused the GRUB boot-time to not output a
readable signal by the monitor. (blank screen) Using the app Startup
Manager I set the advanced options for 800x600. That returned me to a
viewable selection of kernels, memory tests and boot windows options,
but not GRUB Recovery mode(s). After a week the vid card maker sent me a
replacement video card. I installed it, and switched the BIOS from
video-internal to pci-e (it's an EVGA 9500GT a pci-e device). 

On boot if I select Recovery mode, the screen still blanks and after a
moment a message flashes by (VGA=769 is deprecated) and a bunch of words
that go by way too quickly to read. I tried to take a photo, but it's
way too fast. Is there a way to edit grub.config to slow that down or
find the logfile with that error message?

After that VGA= message, the screen blanks. However, I can push the
Enter (CR) key, and that starts the "Resume Normal Boot" function. So,
presumably pressing the up or down cursor keys would take me somewhere
in the GRUB recover options. Which I don't do, without being able to see
what I am selecting. I have tried the one I know from memory: Resume
Normal Boot. 

I have manually updated the GRUB with sudo update-grub. All went well at
the terminal.

Anybody know how to return my system to normal????

I continue to have this problem in Precise Pangolin 12.04. I first
posted this message at Ubuntuforums.org in Nov. 2009.
&lt;/pre&gt;</description>
    <dc:creator>Mark Preston</dc:creator>
    <dc:date>2012-04-28T17:41:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9057">
    <title>[bug #36258] error grub-install v2.00 beta4</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9057</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36258&amp;gt;

                 Summary: error grub-install v2.00 beta4
                 Project: GNU GRUB
            Submitted by: gohlip
            Submitted on: Fri 20 Apr 2012 03:44:49 PM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: gohlip
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - experimental branch
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

Downloaded and make install grub v2.00 beta4.
Confirmed installation complete withour error with "grub-install -v" which
gives "grub-install (GRUB) 2.00~beta4"

However when I "sudo grub-install /dev/sda", the following error message
appears...
"/usr/local/sbin/grub-bios-setup: error: cannot write to `/dev/sda': Bad file
descriptor."




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36258&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Goh Lip</dc:creator>
    <dc:date>2012-04-20T15:44:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9041">
    <title>[bug #36239] can't find command 's'</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9041</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36239&amp;gt;

                 Summary: can't find command 's'
                 Project: GNU GRUB
            Submitted by: gohlip
            Submitted on: Wed 18 Apr 2012 12:11:22 PM GMT
                Category: Booting
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Goh Lip
        Originator Email: g.lip&amp;lt; at &amp;gt;gmx.com
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - experimental branch
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

grub v2.00 beta3

After editing menuentry using key 'e', I tried to boot either 'ctrl' +'x" or
'F10'. there is an error -  "can't find command -s" or "unknown command 's". 

Have this error even if I do not modify but hitting 'e' and F10.

There is no problem if I boot using grub prompt (key'c') but that requires
inputting all commands/parameters. 




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36239&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Goh Lip</dc:creator>
    <dc:date>2012-04-18T12:11:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9039">
    <title>[bug #36219] GRUB2 fails to shutdown from the CLI (reboots instead ofshutdown when doing "halt" from the CLI) - ThinkPad T510</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9039</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.gnu.org/bugs/?36219&amp;gt;

                 Summary: GRUB2 fails to shutdown from the CLI (reboots
instead of shutdown when doing "halt" from the CLI) - ThinkPad T510
                 Project: GNU GRUB
            Submitted by: diegoviola
            Submitted on: Tue 17 Apr 2012 06:58:39 AM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: other
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

Every time I turn on my laptop and GRUB2 appears, I type 'c' for CLI and then
type 'halt' [ENTER]. GRUB2 would reboot my laptop instead of shutting it
down.

My laptop is a ThinkPad T510 4313CTO, I've tried upgrading the BIOS to latest
(1.49) but same thing.

GRUB2 version is:

[diego&amp;lt; at &amp;gt;(none) ~]$ grub-install --version
grub-install (GRUB) 2.00~beta3
[diego&amp;lt; at &amp;gt;(none) ~]$ 

My distribution is Arch Linux x86_64.

I can reproduce this issue all the time on the laptop (ThinkPad T510).

Please let me know if you need more information. Thanks.




    _______________________________________________________

Reply to this item at:

  &amp;lt;http://savannah.gnu.org/bugs/?36219&amp;gt;

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
&lt;/pre&gt;</description>
    <dc:creator>Diego Viola</dc:creator>
    <dc:date>2012-04-17T06:58:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9037">
    <title>grub 0.97 does not work with FreeBSD9.0 and 10</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9037</link>
    <description>&lt;pre&gt;
grub does not work with specified versions of FreeBSD becase of there
are new device driver for HDD: ada
&lt;/pre&gt;</description>
    <dc:creator>Eugen Konkov</dc:creator>
    <dc:date>2012-04-16T20:19:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9035">
    <title>Ill located grub files</title>
    <link>http://comments.gmane.org/gmane.comp.boot-loaders.grub.bugs/9035</link>
    <description>&lt;pre&gt;Hi every body

It happens that Grub uses some files which are not located into the grub 
directory, as in the command
if loadfont /usr/share/grub/unicode.pf2 ;
which is to be found in the 00_header section.

To my opinion, Grub has to be independant of anything else. The file 
tree used when generating the grub.cfg file may be quite different than 
the one to be used when booting. So /usr/.../unicode.pf2 may be quite 
meaningless at boot time.

If some system files are to be used by Grub, grub-mkconfig has to copy 
those files into the grub directory, and no reference outside of this 
directory should be allowed.

Best regards

Arbiel
&lt;/pre&gt;</description>
    <dc:creator>Arbiel Perlacremaz</dc:creator>
    <dc:date>2012-04-16T13:47:37</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.boot-loaders.grub.bugs">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.boot-loaders.grub.bugs</link>
  </textinput>
</rdf:RDF>

