grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fwd: Bug#536846: grub-pc: /boot/vmlinux entry cannot be booted]


From: Jordi Mallach
Subject: Re: [Fwd: Bug#536846: grub-pc: /boot/vmlinux entry cannot be booted]
Date: Fri, 24 Jul 2009 15:53:12 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Jul 24, 2009 at 02:55:01PM +0200, Felix Zielcke wrote:
> How about just removing support for vmlinux kernels in grub-mkconfig?
> I.e:
> 
> Index: util/grub.d/10_linux.in
> ===================================================================
> --- util/grub.d/10_linux.in   (revision 2441)
> +++ util/grub.d/10_linux.in   (working copy)
> @@ -112,7 +112,7 @@ EOF
>  EOF
>  }
>  
> -list=`for i in /boot/vmlinu[xz]-* /vmlinu[xz]-* ; do
> +list=`for i in /boot/vmlinuz* /vmlinuz-* ; do
>          if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
>        done`

This was added because I requested it a year ago, when I started using
GRUB on PowerPC, powerpc Debian kernels didn't ship a vmlinuz file, only
vmlinux. This is not the case since 2.6.30, as apparently vmlinuz is now
generating a vmlinuz file in postinstall,  and I'm getting two entries for 
the same 2.6.30 kernel, 1 for vmlinux and one for vmlinuz.

More interestingly, if I try to boot the vmlinuz entry I get dropped to
OpenFirmware, with a friendly Illegal Memory Access error message.

In short, I *need* vmlinux to boot my PPC, but need to hide the vmlinuz
entries as they fail and are suppossed to be useful only to boot directly
from OF. Ie, just the contrary that this user is asking for.

Jordi
-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
address@hidden     address@hidden     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


On Fri, Jul 24, 2009 at 02:55:01PM +0200, Felix Zielcke wrote:
> How about just removing support for vmlinux kernels in grub-mkconfig?
> I.e:
> 
> Index: util/grub.d/10_linux.in
> ===================================================================
> --- util/grub.d/10_linux.in   (revision 2441)
> +++ util/grub.d/10_linux.in   (working copy)
> @@ -112,7 +112,7 @@ EOF
>  EOF
>  }
>  
> -list=`for i in /boot/vmlinu[xz]-* /vmlinu[xz]-* ; do
> +list=`for i in /boot/vmlinuz* /vmlinuz-* ; do
>          if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
>        done`
> 
> -------- Weitergeleitete Nachricht --------
> > Von: Alvaro Herrera <address@hidden>
> > Reply-to: Alvaro Herrera <address@hidden>,
> > address@hidden
> > An: Debian Bug Tracking System <address@hidden>
> > Betreff: Bug#536846: grub-pc: /boot/vmlinux entry cannot be booted
> > Datum: Mon, 13 Jul 2009 19:58:42 -0400
> > 
> > Package: grub-pc
> > Version: 1.96+20090603-2
> > Severity: normal
> > 
> > 
> > I have a /boot/vmlinux-2.6.26 file that I installed some time ago for
> > use with oprofile.  Since the /etc/grub.d/10_linux script looks for
> > files using the pattern /boot/vmlinu[xz]*, this file is automatically
> > added to the boot menu, and moreover it is selected as the first entry.
> > 
> > However, this file doesn't boot properly.  Grub gives a message saying
> > so and then sits there waiting for user input.  In practice it means I
> > have to watch over the boot sequence or the workstation is as good as
> > halted for all practical purposes.
> > 
> > What I've been doing is edit 10_linux and change the /boot/vmlinu[xz]*
> > pattern to /boot/vmlinuz*, but each time grub-pc is upgraded I have to
> > edit the file again.  I've been doing this for several releases and it
> > has gotten old now.
> > 
> > So my request is: can this pattern be turned into /boot/vmlinuz* in the
> > file distributed with the package?  I guess it boils down to whether
> > there are still valid uncompressed (vmlinux) kernels that can be booted
> > at all.
> > 
> > 
> > -- Package-specific info:
> > 
> > *********************** BEGIN /proc/mounts
> > /dev/sda1 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
> > /dev/sda6 /usr ext3 rw,relatime,errors=continue,data=ordered 0 0
> > /dev/sda7 /var ext3 rw,noatime,errors=continue,data=ordered 0 0
> > /dev/md3 /home ext3 rw,noatime,errors=continue,data=writeback 0 0
> > /dev/md4 /home/fotos ext3 rw,noatime,errors=continue,data=ordered 0 0
> > /dev/dm-0 /home/media ext3 rw,noatime,errors=continue,data=ordered 0 0
> > /dev/sda5 /tmp ext2 rw,noatime,errors=continue 0 0
> > *********************** END /proc/mounts
> > 
> > *********************** BEGIN /boot/grub/device.map
> > (hd0)       /dev/sda
> > (hd1)       /dev/sdb
> > (hd2)       /dev/sdc
> > *********************** END /boot/grub/device.map
> > 
> > *********************** BEGIN /boot/grub/grub.cfg
> > #
> > # 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,6)
> > search --fs-uuid --set 9cf20f48-136a-4284-9048-4720baa20dfb
> > if loadfont /share/grub/ascii.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 root=(hd0,1)
> > search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> > insmod png
> > if background_image /boot/grub/moreblue-orbit-grub.png ; then
> >   set color_normal=black/black
> >   set color_highlight=magenta/black
> > else
> >   set menu_color_normal=cyan/blue
> >   set menu_color_highlight=white/blue
> > fi
> > ### END /etc/grub.d/05_debian_theme ###
> > 
> > ### BEGIN /etc/grub.d/10_linux ###
> > menuentry "Debian GNU/Linux, linux 2.6.26" {
> >     set root=(hd0,1)
> >     search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> >     linux   /boot/vmlinux-2.6.26 root=/dev/sda1 ro quiet 
> >     initrd  /boot/initrd.img-2.6.26
> > }
> > menuentry "Debian GNU/Linux, linux 2.6.26 (recovery mode)" {
> >     set root=(hd0,1)
> >     search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> >     linux   /boot/vmlinux-2.6.26 root=/dev/sda1 ro single quiet
> >     initrd  /boot/initrd.img-2.6.26
> > }
> > menuentry "Debian GNU/Linux, linux 2.6.26" {
> >     set root=(hd0,1)
> >     search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> >     linux   /boot/vmlinuz-2.6.26 root=/dev/sda1 ro quiet 
> >     initrd  /boot/initrd.img-2.6.26
> > }
> > menuentry "Debian GNU/Linux, linux 2.6.26 (recovery mode)" {
> >     set root=(hd0,1)
> >     search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> >     linux   /boot/vmlinuz-2.6.26 root=/dev/sda1 ro single quiet
> >     initrd  /boot/initrd.img-2.6.26
> > }
> > menuentry "Debian GNU/Linux, linux 2.6.25-2-amd64" {
> >     set root=(hd0,1)
> >     search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> >     linux   /boot/vmlinuz-2.6.25-2-amd64 root=/dev/sda1 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,1)
> >     search --fs-uuid --set 550f142c-dd6e-46cf-a267-c32d331b6da8
> >     linux   /boot/vmlinuz-2.6.25-2-amd64 root=/dev/sda1 ro single quiet
> >     initrd  /boot/initrd.img-2.6.25-2-amd64
> > }
> > ### END /etc/grub.d/10_linux ###
> > 
> > ### 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 ###
> > *********************** END /boot/grub/grub.cfg
> > 
> > -- System Information:
> > Debian Release: squeeze/sid
> >   APT prefers testing
> >   APT policy: (990, 'testing')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 2.6.26 (SMP w/2 CPU cores)
> > Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/bash
> > 
> > Versions of packages grub-pc depends on:
> > ii  debconf [debconf-2.0]    1.5.26          Debian configuration 
> > management sy
> > ii  grub-common              1.96+20090603-2 GRand Unified Bootloader, 
> > version 
> > ii  libc6                    2.9-12          GNU C Library: Shared libraries
> > 
> > grub-pc recommends no packages.
> > 
> > Versions of packages grub-pc suggests:
> > ii  desktop-base                  5.0.5      common files for the Debian 
> > Deskto
> > ii  genisoimage                   9:1.1.9-1  Creates ISO-9660 CD-ROM 
> > filesystem
> > pn  os-prober                     <none>     (no description available)
> > 
> > -- debconf information:
> > * grub-pc/linux_cmdline:
> > * grub-pc/chainload_from_menu.lst: true
> > * grub-pc/install_devices: /dev/sda
> > 
> > 
> > 
> > _______________________________________________
> > Pkg-grub-devel mailing list
> > address@hidden
> > http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
> 
> 
> -- 
> Felix Zielcke
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel

-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
address@hidden     address@hidden     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]