Announcing GNU GRUB 1.97 beta1

Announcing GNU GRUB 1.97 beta1

[Robert Millan]

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]


Hi,

I hereby announce the release of GNU GRUB 1.97 beta1.  This is the first of
the beta releases that will lead to 1.97.

I would appreciate if everyone reading this can help the GRUB project by
testing this release and making sure it builds, installs and runs as
expected.

Note: Since I am a new GNU maintainer, I don't yet have access to alpha.gnu.org
hosting facilities.  Therefore, it may take a while untill 1.97~beta1 tarballs
appear in the usual FTP directory [1] (when my key is processed, or when
another maintainer takes care of it).

In the meantime, you can already obtain this release from SVN:

  svn export svn://svn.sv.gnu.org/grub/tags/release_1_97~beta1 grub-1.97~beta1

Enjoy!

[1] http://alpha.gnu.org/gnu/grub/

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: Announcing GNU GRUB 1.97 beta1

[Michal Suchanek]

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

Hello

With 1.97 beta1 I cannot use config files like the one attached.

The message is 'You need to load the kernel first.'

I did not try with 1.97 beta1 yet but with recent trunk I could not
use the config file but I still could boot using these commands.

linux /boot/vmlinuz-... root=/dev/sda7 ro
initrd /boot/initrd.img-...
boot

A there is a suggestion in the Debian bug report to comment out the
search lines but that does not help.

Any ideas why booting with the config file might fail?


Thanks

Michal

[-- Attachment #2: grub.cfg --]
[-- Type: application/octet-stream, Size: 6122 bytes --]

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output.gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinux-2.6.30-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinux-2.6.30-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.30-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.30-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.29-1-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.29-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.29-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.29-1-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.29-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.29-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.28.3" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.28.3 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.28.3
}
menuentry "Debian GNU/Linux, Linux 2.6.28.3 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.28.3 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.28.3
}
menuentry "Debian GNU/Linux, Linux 2.6.26-2-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.26-2-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.26-2-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.26-2-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.26-1-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.26-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.26-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.26-1-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.26-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.26-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.25-2-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.25-2-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.25-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.25-2-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.25-2-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.25-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.24-1-amd64" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.24-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro  quiet
	initrd	/boot/initrd.img-2.6.24-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.24-1-amd64 (recovery mode)" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	linux	/boot/vmlinuz-2.6.24-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single 
	initrd	/boot/initrd.img-2.6.24-1-amd64
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86 ###
menuentry "Memory test (memtest86)" {
	linux	/memtest86.bin
}
### END /etc/grub.d/20_memtest86 ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	linux	/memtest86+.bin
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/22_invaders ###
menuentry "GRUB Invaders" {
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
	multiboot	/boot/invaders
}
### END /etc/grub.d/22_invaders ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###

Re: Announcing GNU GRUB 1.97 beta1

[Michal Suchanek]

2009/9/1 Michal Suchanek <hramrach@centrum.cz>:
> Hello
>
> With 1.97 beta1 I cannot use config files like the one attached.
>
> The message is 'You need to load the kernel first.'
>
> I did not try with 1.97 beta1 yet but with recent trunk I could not
> use the config file but I still could boot using these commands.
>
> linux /boot/vmlinuz-... root=/dev/sda7 ro
> initrd /boot/initrd.img-...
> boot
>
> A there is a suggestion in the Debian bug report to comment out the
> search lines but that does not help.
>
> Any ideas why booting with the config file might fail?
>

This is because the config file is from a previous broken grub
packaged in Debian.

I think this problem is caused by not loading the ext2 module before
attempting to load the kernel. I will try to test with some modified
config file to confirm if this is the case.

Thanks

Michal